ci: let the release check find draft releases - #483
Merged
Merged
Conversation
kostyafarber
changed the title
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.
Summary
The release workflow's
Resolve releasejob could never see the draft release it checks, so the v0.1.1 release stopped before any build ran (run 36904173575). Both causes surfaced as the misleading "already public" error:gh release viewwithout a checkout, soghcould not infer the repository (not a git repository). SetGH_REPO; every other job checks out first.contents: read(release not found). Grantcontents: write; the calling workflow already grants it.Issue
No issue — fixes for the failed v0.1.1 release run.
Testing
v0.1.1from this branch:Resolve releasepasses and the builds start (run 36904721992).🤖 Generated with Claude Code