Repository navigation
ci: resume staged release with draft visibility - #75
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 selector's read-only token cannot see draft releases, so it incorrectly starts another preparation despite an already verified, staged candidate. Grant contents write permission only to the selection job so GitHub's releases API exposes the draft and its original receipt. Existing provenance, hash and preparation checks remain enforced.
Only one CI file changes. No library, package, version or documentation changes. Validation: actionlint and all eight workflow selection/gating scenarios pass. This reuses the already verified 1.1.0 artifacts after the Hackage gate was removed.