Repository navigation
Fix PyPI and npm OIDC: add environment: release - #9
Merged
Merged
Conversation
PyPI trusted publisher is scoped to the "release" environment. Without it declared on the job, the OIDC token subject does not include the environment claim and PyPI rejects the token. Same applies to npm. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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
environment: releaseto bothpublish-npmandpublish-pypijobsWhy
PyPI trusted publisher is scoped to the
releaseenvironment. Without theenvironmentfield on the job, the OIDC token's subject claim omits the environment, and PyPI rejects it with:Same constraint applies to npm — adding it to both jobs preemptively.
After merge
Delete the
v0.2.0tag and re-tag from the new main to re-trigger the release workflow:🤖 Generated with Claude Code