Final RC closure: status accuracy and immutable ref protection - #26
Merged
Merged
Conversation
github-actions
Bot
deleted the
release/rc1-final-status-and-ref-protection
branch
August 26, 2026 17:45
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.
Final documentation-only closure before
v1.3.0-rc.1tagging.This PR intentionally creates a successor release-candidate SHA because the previous frozen candidate still described PR #23 as under review after it had already merged. Shipping that stale living-status claim would be inaccurate.
Changes are limited to three release-governance documents:
CURRENT_RELEASE_STATUS.mdto reflect merged technical closure without self-authorizing the release;mainandv*ref protection before public publication, tracked by issue Release blocker: protect main and v* release tags before v1.3.0-rc.1 #25;ATTRIBUTABLE_PUBLICATION.mdandRELEASE.mdso trust policy and executable maintainer procedure agree.No implementation, workflow, packaging, benchmark implementation, adapter, or verification semantics are changed.
Because release identity is exact-SHA bound, the old candidate
99f478a3af5a5505d05319db8a816a0053089fe8must no longer be tagged after this PR. The final candidate will be this PR's exact head only after the complete pre-tag engineering matrix (CI, Repro baseline, Native Backends Tier 1, Native Backends Tier 1b) passes on that exact SHA. Consumer repositories must then be repinned to that final SHA before the tag-bound Consumer Pin Verification run.