Skip to content

Open Nova v1.0.2

Choose a tag to compare

View all tags
@Neo-Isshin Neo-Isshin released this 15 Jul 02:48
· 71 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.0.2
82e4275

Open Nova v1.0.2

Open Nova v1.0.2 makes stable updates incremental, reproducible, and explicit about what actually happened.

Highlights

  • Reuses the active Runtime venv when the complete dependency contract is unchanged. This path performs no pip operation and no dependency download, while atomically promoting the new source generation and preserving rollback.

  • Rebuilds dependencies only in a separate candidate venv when the exact contract changes, using a hash-verified Runtime lock and a persistent, ownership- and permission-checked wheel cache.

  • Writes an immutable dependency manifest and normalized fingerprint for every new venv generation, covering Python ABI, platform, architecture, selected profiles, direct requirements, the complete lock hash, and resolved distributions.

  • Adds --source-only, --force-rebuild, and --offline update controls, plus human and JSON results derived from the actual transaction.

  • Publishes a version-neutral install.sh Release asset so the stable installer is now:

    curl -fsSL https://github.com/Neo-Isshin/open-nova/releases/latest/download/install.sh | zsh

  • Includes the post-v1.0.1 Dashboard demo and fixes for connection/source-health separation, canonical titles, session discovery, and related regressions.

Upgrade notes

  • A Runtime created by v1.0.1 has no trusted dependency marker, so its first update to v1.0.2 conservatively builds one new candidate venv. The old generation is retained. Subsequent updates with an unchanged dependency contract reuse that venv with zero pip work.
  • The active source manifest is the Runtime product-version authority. A reused venv may retain older open_nova-*.dist-info; Open Nova does not mutate an active venv merely to refresh product metadata.
  • Unsupported lock targets, damaged or untrusted markers, incompatible source-only requests, and offline cache misses fail before managed services are stopped or active pointers are changed.

Verification

  • 1,501 isolated tests: 0 failures, 0 errors, 8 reviewed expected skips.
  • Two independent clean-checkout Release builds produced byte-identical artifacts.
  • The frozen official Runtime artifact completed an isolated fresh-install E2E with a valid dependency marker and verified persistent cache.

Verify downloaded assets with SHA256SUMS. See the bilingual README and local operations runbooks for installation and update details.

Assets 12
Loading