ci: publish to PyPI via trusted publishing (OIDC)#29
Merged
Conversation
Replaces the PYPI_API_TOKEN secret (no longer present, causing a 403 on publish) with PyPI trusted publishing via OIDC, matching paradex-py. Adds the prod environment and id-token: write permission and drops the token env var. Requires a one-time trusted-publisher registration for this project on PyPI (repo + workflow + environment).
mj850
approved these changes
Jun 19, 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.
Why
The publish workflow failed with
403 Invalid or non-existent authentication informationbecause it authenticates withsecrets.PYPI_API_TOKEN, which no longer exists in the repo or org (the org now standardises on OIDC-based auth). The 0.1.x releases predate that secret's removal.What
Port the same tokenless flow paradex-py already uses — PyPI trusted publishing via OIDC:
permissions: id-token: write(+contents: read) so GitHub mints the OIDC tokenuv publishexchanges with PyPI.environment: prod(matches paradex-py).UV_PUBLISH_TOKEN/PYPI_API_TOKENsecret entirely.The tag trigger (
v*.*.*) and the tag-vs-pyproject version check are unchanged.Follow-up (admin, one-time)
Register a trusted publisher for the
paradex-cliproject on PyPI: repotradeparadex/paradex-cli, workflowpublish.yml, environmentprod— exactly as configured for paradex-py. Until that's registered, publish will still be rejected.