Repository navigation
Add release safety checks - #10
Merged
Merged
Conversation
smigolsmigol
marked this pull request as ready for review
August 23, 2026 00:39
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
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.
The tag-triggered release currently publishes whatever
uv buildproducedwithout checking that the tag matches the wheel metadata or starting the
installed package. This installs exactly one built wheel, runs
bumpcheck --help, reads the installed version, and rejects tags other thanv<version>. Manual workflow runs still build and smoke-test the wheel but donot publish.
The repository-specific
SECURITY.mddocuments latest-release support, theexisting reporting address, and the trusted-input boundary for case files and
requested packages.
Local verification:
v0.2.0passed,v0.2.1failed, and the branch/manual path passed