Stage 6: automate CI and release gates - #85
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
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.
Summary
Turn the existing release contract into automated GitHub gates.
mainCI for Python quality, Rust quality, and release packaging.Protected invariant
A PR must not merge when source tests pass but the release artifacts, native build profile, CLI entry point, packaged contents, frozen release identities, or source distribution boundary are wrong.
Validation
uv run ruff format --check .uv run ruff check .uv run pytest— 144 passedcargo fmt --manifest-path rust/Cargo.toml -- --checkcargo test --manifest-path rust/Cargo.toml— 60 passeduv buildClippy is not enabled because the current Rust code has existing unrelated warnings; the Stage 6 workflow keeps the required formatting and test gates.