Tested Version Snapshot
Nova generates every project from a bundled, tested version snapshot. It does not ask npm, GitHub, Docker Hub, Cloudflare, Gradle, or another registry for the newest release while scaffolding.
This gives every published Nova version a repeatable result:
- The same Nova release generates the same dependency and platform versions.
- Scaffolding keeps working offline after Nova is installed.
- A newly published upstream release cannot unexpectedly break a project halfway through generation.
- Nova's own package versions remain controlled by the normal Nova release process.
How Updates Reach the Snapshot
Nova maintainers review the snapshot explicitly before a release or whenever an upstream update needs consideration. The maintenance command finds stable candidates from authoritative upstream sources and can write them locally for review before the complete project check and build—including the scaffold matrix—are run.
Framework major versions, support ranges, Apple deployment targets, and Android SDK policy remain deliberate maintainer decisions.
Cloudflare's Wrangler version, Worker types, and compatibility date are reviewed together. Android libraries, Gradle, and the Gradle Wrapper are also validated as one platform set instead of unrelated numbers.
Generated workflow actions use complete owner/action@vN references from the same snapshot. The updater reads each action's latest stable GitHub release and proposes its floating major reference, while Nova's checks validate the resulting workflows before the review pull request can be merged.
Maintainer Commands
From Nova's repository root, run a read-only audit:
npm run scaffold-versions
Use --check when an available update should fail automation, or --write to apply the candidates locally for review:
npm run scaffold-versions -- --check
npm run scaffold-versions -- --write
Both long and short forms are supported. --group <group> limits a local audit, and --verbose includes manual policy entries.
After Scaffolding
The snapshot is a starting point, not a permanent lock. A generated project owns its files and can update dependencies normally. Nova only guarantees that the versions bundled with a released scaffold passed Nova's validation together.