feat: add data table and release checks

2026-03-19 20:10:36 +08:00
parent d5e4d5ece3
commit 3f77070802
12 changed files with 2157 additions and 86 deletions
@@ -6,8 +6,29 @@ The repo is still an internal/private monorepo, so Changesets is used conservati

 - track version intent for releasable workspace packages
 - keep release notes attached to code changes
- avoid auto-committing release files
 - avoid tagging private packages during early internal iteration
+- let CI verify release intent before package work merges
+
+## CI behavior
+
+This repo now has two release-adjacent workflows:
+
+- `Changeset Status` runs on pull requests and checks whether changes to releasable packages
+  include a `.changeset/*.md` entry.
+- `Release Version PR` runs on `main` and opens or updates a version PR by running
+  `pnpm changeset version`.
+
+The PR check intentionally focuses on the releasable packages in scope today:
+
+- `@ai-ui/ui`
+- `@ai-ui/tokens`
+
+If a PR touches those packages but should not create a release note, apply the
+`no-changeset-needed` label. This is the escape hatch for work such as:
+
+- docs-only follow-up near a package
+- test-only changes
+- internal refactors with no consumer-visible behavior change

 ## What should get a changeset

@@ -48,4 +69,7 @@ flow is enabled, treat Changesets as the source of truth for:
 - which changes deserve release notes
 - which internal dependency bumps should be coordinated

+The current automation stops at version intent and version PR creation. It does not publish to a
+registry, create tags, or assume any package registry credentials exist yet.
+
 See `docs/releasing.md` for the expected workflow around creating and consuming changesets.
@@ -0,0 +1,5 @@
+---
+"@ai-ui/ui": minor
+---
+
+Add the first DataTable implementation with sorting, selection, search, pagination, loading, empty states, and row actions.