ci: move to PyPi Trusted Publishing - #1613
Open
qkaiser wants to merge 1 commit into
Open
Conversation
qkaiser
added
enhancement
Move to PyPi Trusted Publishing using an ID token instead of relying on a fixed token. Split the release workflow in 3 steps: - build phase with uv/maturin, followed by an artifact upload - publication to PyPi by pulling built artifacts first - publications to Test PyPi by pulling built artifacts first This follows official guidance from https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
qkaiser
force-pushed
the
trusted-publishing
branch
from
August 31, 2026 09:12
0b480d0 to
7f437ab
Compare
qkaiser
marked this pull request as draft
August 31, 2026 09:34
qkaiser
marked this pull request as ready for review
August 31, 2026 09:59
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.
Move to PyPi Trusted Publishing using an ID token instead of relying on a fixed token.
Split the release workflow in 3 steps:
This follows official guidance from
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/