Repository navigation
Allow safe release draft resume across workflow runs - #5
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.
Summary
workflow_dispatchrecovery path for an existing signed release tagRoot cause
gh release create --draftsucceeded for SDK 1.4.0, but the immediately following paginated release listing did not yet expose the new draft. The workflow failed closed before uploading assets.Testing
make checkpython3 -m unittest tests.test_release_policy -vgit diff --checkRecovery
After merge, dispatch the updated release workflow from
mainwithrelease_tag=sdk-v1.4.0. It will checkout and revalidate the immutable signed tag, rebuild and sign assets, then resume draft ID 376340815 only if tag, commit, body ownership, and draft state still match.