Repository navigation
Fix draft release lookup after creation - #19
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.
Release publication can stop immediately after creating a draft because the next releases-list response can still omit it. The refactor in #17 added this second lookup; run 40460796147 left
v1.0.6as an empty draft before the release ID check exited silently.Capture the draft directly from the release creation API response, including its ID, and report a clear error if the ID is missing. Preserve generated notes, tag verification, draft recovery, and published-asset checks.
Validation: the release control suite passes. A regression test keeps the releases list stale after creation; the original script fails that test and the fixed script passes. Bash syntax and
git diff --checkalso pass.