Nova already knows which workspaces belong to a project, what each workspace is called, and how packages depend on one another. Workspace execution no longer needs a second tool to rediscover that same project model.
The native workspace runner now coordinates package scripts directly from nova.config.json and each workspace's package.json.
nova utility initialize made sense when Nova's guided setup had one obvious job: create the first nova.config.json file.
The command grew. It became the place to return whenever a project changed, whether you needed to add a workspace, revise repository settings, manage environment variables, or inspect GitHub environment status. Calling that ongoing work “initialization” stopped describing what the command actually did.
Nova 0.30.0 gives it a more accurate name: configure.
TypeScript files need different output policies depending on whether they are application code, published source, configuration, scripts, or tests.
Nova 0.30.0 moved those policies into role presets and unified checked emission behind one transpile utility.
A scaffold is only useful when the generated project behaves like a real consumer rather than a folder-shaped example.
Nova 0.29.0 expanded its scaffold system and began validating generated projects from the packed npm artifact through their own checks and production builds.
Installing dependencies is part tool selection and part trust decision, so both should be explicit in project configuration.
Nova 0.26.0 limited package-manager support to Corepack-compatible clients and documented the boundary around dependency lifecycle scripts.
Version numbers can describe either compatibility or time, and projects should be able to choose the signal that fits their releases.
Nova 0.23.0 added calendar versioning beside its existing semantic-versioning workflow.
Environment values become easier to reason about when configuration describes where each value is allowed to travel.
Nova 0.22.0 introduced reach as a required delivery classification for project and workspace environment values.
Repository settings are part of a project’s behavior even when they live behind switches in the GitHub website.
Nova 0.18.0 introduced GitHub recipes so those choices could be declared, reviewed, and reconciled from nova.config.json.
Publishing the same release to several destinations should not require rebuilding the same source several times.
Nova 0.16.0 replaced separate destination workflows with one build that fans out into independent publish jobs.
Documentation sites need more than a color palette when they are expected to feel like a finished product.
Docusaurus Preset Nova 0.15.0 launched as a coordinated design, content, search, and authoring layer for Docusaurus.