feat: updated pypi workflow to use trusted publishing#1916
Merged
CarsonRoscoe merged 1 commit intox402-foundation:mainfrom Apr 2, 2026
Merged
Conversation
erikreppel-cb
approved these changes
Apr 2, 2026
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
2 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.
The x402 pypi package is moving towards using trusted publishing
Two changes made:
id-token: writeto permissions — required for the GitHub Actions OIDC token that PyPI trusted publishing uses.password: ${{ secrets.PYPI_X402_TOKEN }}line — when no password is provided,pypa/gh-action-pypi-publishautomatically falls back to OIDC trusted publishing.This assumes we've already configured the trusted publisher on PyPI for the
x402package to trust thex402-foundation/x402repo, thepublish_pypi_x402.ymlworkflow, and thepypienvironment.