kurihada/cadence-ui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add package-first release flow

Browse Source
This commit is contained in:
kurihada
2026-03-20 15:10:46 +08:00
parent 3600f3fcd9
commit e13a60369d
16 changed files with 764 additions and 191 deletions
Download Patch File Download Diff File Expand all files Collapse all files
roadmap.md
+9 -6
View File
@@ -16,12 +16,12 @@ completed most of that baseline work:
- phases 0 through 4 are effectively in place: workspace, tokens, authoring contract, core components, Storybook docs, and baseline tests
- phase 5 has shipped its first advanced-pattern slice with `DataTable`, alongside `Command`, `Combobox`, `Sheet`, and `EmptyState`
- phase 6 has shipped its baseline source-copy registry flow, Changesets gating, and version PR automation
- phase 6 now covers package-first release automation, fixed-version package publishing, and the optional source-copy registry flow
The next work is mostly hardening and distribution:
- keep the registry metadata and consumer smoke flow reliable
- decide publish and tagging policy
- keep package publish validation and tag automation reliable
- expand advanced patterns only where real product usage justifies them
## Product Principles
@@ -368,7 +368,7 @@ Exit criteria:
## Phase 6: Internal Registry and Distribution
Status:
Baseline source-copy distribution is shipped. Publish automation is still open.
Package-first publishing and optional source-copy distribution are both in place.
Objective:
Create an internal distribution model similar to `shadcn`, but based on our own rules.
@@ -382,6 +382,9 @@ Deliverables:
Delivered so far:
- fixed-version package release pair for `@ai-ui/ui` and `@ai-ui/tokens`
- package consumer smoke validation
- tag-driven publish workflow
- generated `registry/index.json`
- local `pnpm registry:install` copy-in workflow
- `pnpm test:registry:consumer` validation
@@ -389,13 +392,13 @@ Delivered so far:
Remaining follow-up:
- publish decision and package registry posture
- tagging policy for stable install points
- package registry operational hardening
- any automation beyond source-copy installs
Exit criteria:
- consumers can pull components from our registry
- package consumers can install the published packages
- source-copy consumers can pull components from our registry
- upgrades are documented and reproducible
## Testing Strategy