Versioning & Stability

Volt UI reached 1.0.0 — the public API is locked and follows ordinary semantic versioning from here on.

The semver promise

Major — 2.0.0

The only place breaking changes happen: renamed or removed inputs/outputs/selectors, changed default behavior, dropped Angular major support.

Minor — 1.1.0

New components, new optional inputs/outputs, new CVA variants. Always backward-compatible with the previous minor.

Patch — 1.0.1

Bug fixes, accessibility corrections, internal refactors. Never changes the public contract.

The frozen surface itself is inventoried in specs/api-freeze-0.9.md — every input, output, and selector present at the 1.0.0 freeze. Upgrading from a 0.x release? See 0.x Migration Notes.

What status labels mean now

Every component in 1.0.0 is stable — see the component catalog for the per-component label. beta and experimental stay defined below because components added after 1.0 may start there; nothing carries either label today. The label is a confidence signal, not an availability gate: every component ships through the npm package and the CLI regardless of label.

Stable

Recommended for production use. Documented API, meaningful tests, known accessibility caveats (if any) written down.

Beta

Usable today, but may still gain forms, keyboard, or accessibility hardening in a minor or patch release — that hardening never breaks the existing public API, so moving from beta to stable is a documentation change, not a version bump on its own. Unused in 1.0.

Experimental

Reserved for future previews whose API may still change. Not currently used — no shipped component carries this label as of 1.0.0.

Angular version support

The 1.x line targets Angular ^21.2 and Node 20 or newer. Volt UI supports the latest declared Angular major only — widening that range requires consumer-fixture verification, not just a successful build, so it's never assumed.

When a new Angular major ships, moving Volt UI's support to it is a minor release with migration notes or release notes documenting anything that changed. A supported major is never dropped silently.

Where the project goes from here: Roadmap. Full per-component status table: component catalog. Upgrading an existing copy? 0.x Migration Notes. Full release history: CHANGELOG.md.