Repository navigation
fix: isolate PyPI upload sidecars from verified distributions - #14
Merged
Merged
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
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.
PyPA's publishing action creates
.publish.attestationfiles in its package directory. This caused shared GitHub finalization to reject unexpected files after the sender's successful PyPI upload.Copy verified distributions into a fresh
pypi-dist/aftercheck-upload, then pass that directory to PyPA. Every shared phase and GitHub attestation continues using the unchangeddist/. Plainmkdirrefuses an existing staging directory; hash, provenance and release-identity checks remain intact.Update the shared example and documentation with the same integration. Remove stale claims that Aubio still has a TestPyPI lane; production-only publishing remains the documented policy.
Validation: Full shared suite: 255 passed; all configured hooks and final documentation checks passed. The behavioral regression executes the actual staging shell, simulates uploader sidecars, checks original filenames and bytes, and verifies that repeated staging fails without modifying either directory.