Changelog

Release history for @abbainitiative/ui. The authoritative record is CHANGELOG.md in the repository, which Changesets generates from the changeset files in each pull request.

0.1.0 Initial release

• 27 components across layout, typography, actions, forms, data display, feedback and overlays.
• Cedar & Ember token system with a complete dark theme under both [data-theme="dark"] and .dark.
• Per-component "use client" boundaries, never at the package root, with per-component chunks and an explicit exports map.
• A single compiled stylesheet — no Tailwind, PostCSS configuration or build-step coupling required in consuming applications.
• Unit, interaction and automated axe tests for every component.

Versioning policy

The package follows semantic versioning. While the major version is 0, minor releases may contain breaking changes; each one is documented in the changelog with the migration required.

• Patch — bug fixes, and visual corrections that do not change layout.
• Minor — new components, new props, new tokens. Existing code keeps working.
• Major — removed or renamed props, changed default behaviour, removed tokens, or a raised React peer range.

What counts as breaking

Class names are not part of the public API. They are content-hashed and change between builds, so styling against them will break without a major version bump. Use tokens or the className prop instead. Token names are public: removing or renaming one is a breaking change.

How releases are made

# Contributors add a changeset alongside their change:
pnpm changeset

# CI opens a release PR; merging it versions and publishes.

Every change that affects the published package ships with a changeset declaring its bump type. CI accumulates them into a release pull request; merging that request versions the package, writes the changelog and publishes to npm with provenance.