workflows/release: enable PEP 740 attestations #1145
Merged
Conversation
This file contains 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 enables attestation generation while uploading to PyPI. Future versions of the
gh-action-pypi-publishaction will enable this by default, but we want to get in on the ground floor.It also disables uploading of the "smoketest" artifacts to the GitHub-side release, since these don't correspond 1-1 with the PyPI attestations (they're composed only of hashes of the file, and don't use a DSSE payload). This will hopefully eliminate some confusion + guide users towards the PyPI hosted ones as canonical.