feat(release-tools): cut over staged recovery - #38
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Owner
Author
|
Codex Review: Didn't find any major issues. Breezy! 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". |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release-Fix-Forwardrecovery planning with strict terminal-trailer validationWhy
This completes the staged Release Set recovery and cut-over work while preserving Tenkit's security boundary: GitHub Actions may privately stage packages, but human npm 2FA approval, local verification, Promotion, and Finalize remain separate operations.
Impact
Maintainers get deterministic recovery after partial public approval, safer interruption guidance, and one staged publishing architecture without superseded publisher or changelog machinery. Malformed, misplaced, or multiline fix-forward markers stop planning. No new public release is performed by this change.
Validation
pnpm typecheckpnpm test- 50 test files, 361 passedpnpm release:plan -- --source HEAD- selected0.3.0from committed source without npm access