requirements: bump pypi-attestations to 0.0.12 #16757
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
See pypa/gh-action-pypi-publish#262 for additional context. Signed-off-by: William Woodruff <william@trailofbits.com>
Signed-off-by: William Woodruff <william@trailofbits.com>
di
approved these changes
Sep 19, 2024
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 bumps
pypi-attestationsto 0.0.12 to fix a bug we discovered in the previous series (trailofbits/pypi-attestations#48). The TL;DR is that Pydantic's default Base64 encode/decode behavior isn't what we expected (it injects newlines into the encoded value), resulting in the generation of attestations that aren't consistent with PEP740.This could have been much worse had we begun to persist and serve attestations, but that fortunately hasn't happened yet 🙂.
See pypa/gh-action-pypi-publish#262 for additional context.