ci: publish to PyPI via Trusted Publishing (OIDC)#223
Merged
Conversation
Drop the long-lived PYPI_TOKEN secret in favor of OIDC. uv publish auto-detects the GitHub Actions id-token; publish.yml grants id-token: write (plus contents: read for checkout) and runs under a `pypi` environment that scopes the PyPI Trusted Publisher. The existing on: release: published trigger is unchanged. Requires a Trusted Publisher on the that-depends PyPI project with workflow publish.yml and environment pypi before the next release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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
Replace the long-lived
PYPI_TOKENsecret with PyPI Trusted Publishing (OIDC) onpublish.yml. The existingon: release: publishedtrigger is unchanged.Changes
publish.yml: addpermissions: { contents: read, id-token: write }, run thepublishjob under apypienvironment, drop thePYPI_TOKENenv.Justfile:uv publish --token $PYPI_TOKEN->uv publish.Why
No credential to leak or rotate; OIDC tokens are short-lived and scoped to this repo + workflow.
Required before the next release (maintainer, PyPI-side)
modern-python, repothat-depends, workflowpublish.yml(not release.yml), environmentpypi.pypienvironment under repo Settings -> Environments.PYPI_TOKENrepo secret.Cutting a release is unchanged: create a GitHub Release (tag) and
publish.ymlpublishes via OIDC.