fix: resume draft releases by exact tag - #8
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.
What changed
Unreleasedwithout changing the already published0.2.3version.Why
The v0.2.3 workflow created and uploaded the exact 16-asset draft successfully, but
GET /releases/tags/v0.2.3returned 404 because GitHub documents that endpoint as returning published releases. The authenticated release list does include drafts for tokens with push access. Both jobs need the fallback: staging resumes drafts after an interruption, and the final job must read the same draft before publishing it.Validation
verify-version-sync.ps1git diff --checkdraft: true