docs(releases): alpha.12/13 ladder entries; release-tag prints remaining release-day steps#27
Merged
Conversation
…maining release-day steps - §3.2 ladder: alpha.12 no longer marked 'next' (it shipped); alpha.13 entry added (§13.1 registry binding + resolver, two-phase flow, ratify-c pipeline fix) - release.sh tag phase now ends by printing the remaining release-day steps: the downstream claims bump (ratify-docs, identities-marketing, ladder line) and Phase-4 registry verification. The alpha.13 downstream bump was missed despite being documented — the checklist now surfaces at the exact moment the operator finishes tagging, not only in a doc they must remember to open. Signed-off-by: chuks <891251+chuks@users.noreply.github.com>
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.
Closes the round-N findings: the §3.2 ladder no longer calls alpha.12 'next' and gains alpha.13's entry. And the root cause of the missed downstream bump gets a guard:
make release-tagnow ends by printing steps 11–12 (downstream claims bump + Phase-4 registry verification) directly in the terminal — the checklist surfaces at the exact moment it applies instead of living only in a doc.bash -nclean,release-sync: ok.