feat(release-tools): support stable and rc release sets - #40
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2f4ebbb96d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dbf8da75ca
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 49837211a8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
pnpm release:verify -- --source-sha <sha> --version <version>classify private, dependency-prefix partial-public, complete-public, and published Release SetsWhy
Tenkit's replacement release architecture publishes Stable Release Sets directly under
latestand RC Release Sets directly undernext. Planning and maintainer-local verification must share one version-derived channel model while preserving dependency-first approval, immutable package identity, independent artifact reproduction, and GitHub/npm authority separation.Impact
Maintainers can plan, reproduce, and verify both Stable and RC Release Sets without passing a separate channel to verification. Valid interruptions resume at exactly one safe next action, while mixed, ambiguous, out-of-order, mismatched, or nonstandard states stop without mutation advice.
This PR implements release-process rederivation tickets 09 and 10. Draft workflow cutover and retirement of Candidate/Promotion remain separate follow-up tickets.
Validation
pnpm testpnpm -F @tenkit/release-tools typecheck