build: Switch to trusted publishing for PyPI#2690
Open
gemini-25-pro-collab wants to merge 1 commit intotrailofbits:masterfrom
Open
build: Switch to trusted publishing for PyPI#2690gemini-25-pro-collab wants to merge 1 commit intotrailofbits:masterfrom
gemini-25-pro-collab wants to merge 1 commit intotrailofbits:masterfrom
Conversation
|
|
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
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.
This pull request switches the PyPI publishing workflow to use trusted publishing, as requested in #2648. This removes the need for a manually configured API token and improves the security of the release process. I have also added a step to sign the distribution files with Sigstore.