Design-system releases

Source

This page is published from docs/releases/README.md. Edit it there.

Use versioning and support, deprecation, migration v1 → v2.0 → v2.0.1 and the changelog format. These are additive release procedures prepared for the owner’s planned v2.1.0 approval, not evidence that any new tag, package, workflow or support team was created.

The lane brief and decision 382 identify v2.0.0 as the published kit baseline; local VERSION was 2.0.0 and no local tag was fetched during this batch. Decisions 389/390 describe v2.0.1 corrective work. Later decision 397 sets phase-2 additions to v2.1.0; do not package the new component/token/adoption surface as a patch. The actual version bump, release evidence and publication are the integration owner’s work.

Keep the kit semver (2.x), SpaceWorks app version (0.12.0) and brand-book edition (v1/v2) distinct. A product records the exact design tag/commit it consumes. See pinning.