Fix release action: remove invalid --target flag#114
Merged
Conversation
The --target flag was passing the tag name (e.g. "v0.2.0") as target_commitish, which GitHub API rejects with HTTP 422. Since the tag is already pushed before this step runs, gh release create automatically resolves the tag's commit. https://claude.ai/code/session_019YFSdMW7TobZNsmey63CYm
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
3 participants
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
--target "v${VERSION}"from thegh release createcommand in the release workflow--targetflag was passing a tag name astarget_commitish, which GitHub API rejects with HTTP 422 (Release.target_commitish is invalid)gh release createautomatically resolves the tag's commit — no--targetneededTest plan
${{ github.sha }}) is unaffectedhttps://claude.ai/code/session_019YFSdMW7TobZNsmey63CYm