docs(release): disposition v4 release identity incident - #74
Merged
Conversation
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
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.
Refs: REL-000
Summary
v4.0.1as the sole verified root-module compatibility baselinev4.0.0,contrib/v4.0.0, andcontrib/v4.0.1without moving or recreating published tags[pr]as an active backlog status in the scorecard contractEvidence
docs/release-incident-v4-release-identity.mdGOWORK=off GOTOOLCHAIN=local make docs-checkpassedAPI_BASE_REF=v4.0.1 GOWORK=off GOTOOLCHAIN=local make release-checkwas run through its release subchecks; required protected CI remains the merge authoritySafety
This does not retag, delete, or overwrite releases. A later paired contrib repair must use a new SemVer-correct tag with clean protected release evidence.