Fix release workflow: gh release create needs --repo - #26
Merged
Conversation
…that job The package-release job runs on a bare ubuntu-latest runner and only downloads build artifacts - it never checks out the repo. Without --repo, gh release create tries to auto-detect the target repository via a local git remote lookup, which fails outright with no working directory to look in. Confirmed by this workflow's first real run (tag v0.6.2): every job through packaging succeeded, and only this step failed with "fatal: not a git repository". Pass --repo "\$GITHUB_REPOSITORY" explicitly instead of adding a checkout step just for this. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GXAuGMLB44T5Zv5o5ZzKah
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 v0.6.2 tag push (this workflow's first real run ever, no prior
v*tag had ever existed) succeeded through every job - version check, build+test, all three publish legs, and packaging - and failed only on the finalgh release createcall:package-releaseruns on a bareubuntu-latestrunner that only downloads build artifacts from earlier jobs - it never checks out the repo. Without--repo,ghtries to resolve the target repository from a local git remote, which doesn't exist in that job. Same class of mistake this repo's ownCLAUDE.mdalready flags forgh pr createrun without--repo/--base.Fix
Pass
--repo "$GITHUB_REPOSITORY"explicitly (a built-in Actions env var,owner/repo) rather than adding anactions/checkoutstep just to giveghsomething to infer from.Test plan
v0.6.2run (run 31451068058).v0.6.2tag to the newmaintip and re-push to confirm the full workflow succeeds end-to-end and publishes the release.Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01GXAuGMLB44T5Zv5o5ZzKah