fix: create draft release source tags explicitly - #12
Merged
Conversation
What changed: - create the immutable source ref through the GitHub API after draft creation - recover matching draft releases that do not yet have a tag - add regression coverage and refresh the source manifest Why: - GitHub draft releases do not publish their target tag automatically
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.
What changed
Root cause
Release run 32216391674 passed signing, attestations, GitHub verification, and anonymous pull. It then created a draft release, but
gh release create --draftdid not publishrefs/tags/v1.0.0; the immediate fetch therefore failed with exit 128.Validation
No image/runtime, database, signing, attestation, or Cloudflare behavior changes.