Repository navigation
ci(release): prepare verified assets before immutable publication - #52
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.
Release assets currently attach after GitHub publication, which prevents immutable releases and lets PyPI publishing proceed alongside a failed GitHub upload.
The release action dispatches preparation at the annotated tag. Preparation checks the tagged source, builds and tests the distributions, creates SBOMs and signatures, verifies them, and attaches all six assets to the draft. Upload retries compare existing bytes and upload only missing files.
After draft publication, the PyPI path requires an immutable release, verifies its release attestation, asset signatures, source commit and ref, and manifest, then publishes the existing wheel and sdist through the unchanged reviewer-gated Trusted Publisher. It does not rebuild or modify release assets.
Validation: workflow syntax and shell checks pass; the workflow security scan reports no findings. The full repository gate and regression tests cover missing, mismatched, partial, and stray assets.