Enable PEP 740 attestations when publishing to PyPI#16910
Merged
Conversation
Signed-off-by: William Woodruff <william@astral.sh>
woodruffw
temporarily deployed
to
uv-test-registries
GitHub Actions
Inactive
zanieb
approved these changes
Dec 1, 2025
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.
Summary
This uses our own
astral-sh/attest-actionto add PEP 740 attestations to our PyPI releases.Test Plan
There's no great way to test this, since it lives squarely in the release flow 😞. However,
attest-actionitself has integration tests and we're successfully using it onastral-sh/sigstore-models; I've also integrated it into some third-party projects' release workflows.