Fix GitHub release repository targeting - #2
Merged
Conversation
saivarun1410
marked this pull request as ready for review
August 8, 2026 16:52
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
Pass the Actions-provided
GITHUB_REPOSITORYexplicitly togh release create.Why
The
publish-githubjob downloads the package artifacts without checking out the repository. As a result, the v0.1.0 run failed with:Explicit repository targeting lets GitHub CLI verify the tag and create the release through the API without requiring a checkout.
Impact
Future version tags can publish GitHub Releases from the downloaded, verified build artifacts. PyPI Trusted Publishing is unchanged.
Verification
git diff --check--repotargeting