Repository navigation
Fix draft release ID lookup before signing - #115
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.
Draft releases cannot be resolved through the published-release tag endpoint, which caused v1.6.0 publication to fail after all four builds passed. Resolve the release through GraphQL and require a draft with a positive numeric database ID before signing its update manifests.
Only
.github/workflows/release.ymlchanges. Signing, artifact contents, release tags, and publication behavior are preserved.Validation:
cargo fmt --all --check, andgit diff --checkpass.All five required GitHub checks passed on commit
00dfc1d2ea967d8b88fe9bad46191e961e9bfe9c. Published v1.6.0 from the original verified artifacts; all 13 assets, platform checksums and both signatures verified before and after publication.