Repository navigation
Handle delayed release attestations and verify published releases safely - #20
Merged
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.
The RC publication succeeded, but its immediate final
gh release verifyfailed before GitHub made the generated release attestation available. The unchanged release verified successfully shortly afterward.Retry only an unavailable release attestation, with a 24-attempt/five-second bound. Invalid signatures and integrity failures still stop immediately. Manual recovery rechecks the exact source build, manifests, attestations and all eight uploaded hashes; an already-published immutable release is then verified without editing, uploading or replacing anything. The publication helper is loaded from the trusted workflow revision so the fixed recovery path works with older immutable tags.
Validation: 12 synthetic publication scenarios passed (delay, timeout, signature failure, inventory/hash/tag/kind rejection, mutable rejection, fresh/draft/published paths). The real RC passed the new verification-only recovery locally. The published tag and all release assets are unchanged. Added exact RC CI/package evidence and completed the candidate-verification checklist; stable deployment/signing gates remain pending.