Context
As shared tokens and components evolve, contributors need a predictable way to
document visual changes, migrations, accessibility impact, and breaking APIs.
Scope
- Add a design-system changelog with an initial baseline entry.
- Add a pull-request checklist for token or shared-component changes.
- Define Added, Changed, Deprecated, Removed, Fixed, and Accessibility sections.
- Document deprecation and migration-note expectations.
Acceptance criteria
- The checklist covers light/dark, keyboard, mobile, tests, screenshots, and API compatibility.
- Changelog format includes dates and links to relevant issues/PRs.
- Breaking changes require a migration note.
- Accessibility fixes are visible rather than buried under general fixes.
- Contribution documentation links to both artifacts.
Out of scope
- Automating package releases.
- Publishing the UI package to a public registry.
Context
As shared tokens and components evolve, contributors need a predictable way to
document visual changes, migrations, accessibility impact, and breaking APIs.
Scope
Acceptance criteria
Out of scope