Releases

The current work prepares the unpublished 0.2.0-next.2 candidate before a stable 0.2.0 release. This page describes the candidate and its consumer checks. The npm next tag selects a prerelease version. The latest tag remains a separate release choice. Existing source tags stay unchanged. The candidate needs a fresh v0.2.0-next.2 source tag after maintainer approval.

Candidate changesCopy Anchor Link

The candidate adds core, chart, sortable, and toast entry points. It adds content primitives, shared foundation exports, scoped styles, and an explicit reset entry. Existing root imports and theme fields remain available.

The candidate also updates dialog focus, field associations, keyboard selection, sorting, and reduced-motion behavior. The changelog records the final additions and fixes.

Editable Figma kitCopy Anchor Link

Download the 0.2.0-next.2 design kit for native editable components, text, variables, and styles. The download manifest records its version and SHA256 hash. SHA256 is a fingerprint that detects changed file bytes.

Extract the ZIP archive and follow its README to create a local Figma development plugin. Keep the plugin ID that Figma generates. Install Syne, IBM Plex Sans, and IBM Plex Mono before import. The importer makes no network requests and preserves existing pages.

The kit includes light and dark variants, with Modern and Flat appearances. Use the imported component sets to create instances for mockups. The ZIP contains an importer package, not a .fig file. Its static designs do not reproduce React behavior or guarantee the same component properties. Use Storybook for interactive behavior and accessibility examples.

Each alpha minor visual release includes a matching design kit. Each visual revision of an alpha release also includes a matching kit. Each production major visual release includes a matching kit. A production minor visual release includes one when its release notes specify it. Keep earlier kits with their matching versions.

Earlier versionsCopy Anchor Link

The published 0.1.5 package remains available on npm. Read its preserved documentation with the original installation requirements and source examples. Keep the 0.2 candidate on its feature branch through review. After release, use a separate 0.1 maintenance branch for focused fixes. Start that branch from the exact source commit recorded by npm. Each backport needs separate tests and a reviewed publishing path. The current workflow accepts only the 0.2 release line. Read the maintenance guide for the branch and distribution tag rules.

Preserve documentationCopy Anchor Link

The version switcher offers one evolving 0.2.0 edition with an Alpha badge and the preserved 0.1.5 documentation. Prerelease and patch updates revise the current edition instead of creating new documentation editions. Keep exact package versions, release notes, and design downloads separate from the edition label.

Before you replace a supported documentation edition, preserve its published source, routes, navigation, and search. Retain its matching design kits as immutable downloads. An immutable download keeps the same file bytes after release. Run the archive integrity and browser tests before publication. Unpublished candidates do not imply published releases or archived release documentation.

Release checksCopy Anchor Link

The package and documentation use the same packed candidate. Consumer checks cover module imports, declarations, stylesheet paths, rendering, and framework builds. Browser checks cover the examples and documentation navigation.

A package release requires maintainer authorization. A faulty published version receives a corrected version with migration notes. Read the release guide for the full contract.