chore: add registry install flow

2026-03-20 10:38:05 +08:00
parent 5045756525
commit e8aea4b88a
13 changed files with 1788 additions and 20 deletions
@@ -14,9 +14,9 @@ The repo is still an internal/private monorepo, so Changesets is used conservati
 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.
+  include a `.changeset/*.md` entry, while also verifying that `registry/index.json` is current.
 - `Release Version PR` runs on `main` and opens or updates a version PR by running
-  `pnpm changeset version`.
+  `pnpm release:version`.

 The PR check intentionally focuses on the releasable packages in scope today:

@@ -69,7 +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.
+The current automation stops at version intent, registry metadata refresh, and version PR creation.
+It does not publish to npm, create tags, or assume any package registry credentials exist yet.

 See `docs/releasing.md` for the expected workflow around creating and consuming changesets.