Repository navigation
ci(release): find draft releases through the draft-aware CLI - #53
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
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.
Draft preparation stops with HTTP 404 because GitHub's release-by-tag endpoint returns published releases only.
Use
gh release viewfor draft validation and asset counts, including the upload retry's publication check. Keep the published release API for immutable release verification. The retry test double refuses the published-only endpoint for drafts, and an executable preflight regression verifies the draft lookup.Validation: the replacement command finds the existing empty
v0.2.0draft, and workflow syntax and shell checks pass. Required CI runs the full repository gate and coverage before merge.