Add production release governance and repository guardrails#41
Merged
Conversation
# Conflicts: # .github/workflows/release.yml
# Conflicts: # .github/workflows/release.yml
ctx analysisAnalyzed
Repository healthIndexed 110 files, 2161 symbols, 1602 functions, and 13360 relationships.
Audit findings (133)
New near-duplicate functions (1)
Architecture-rule findings (0)No .ctx/rules.toml is configured. Changed-code hotspots (1)
Architectural map (489 ranked symbols)
Full machine-readable results: workflow artifact. Generated by ctx. This comment is updated on every PR revision. |
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
Cargo.tomlas the sole authoritative version with deterministic show/check/set/bump/release-note toolinggovernance/while preservingdocs/for the public manualValidation
cargo fmt --all -- --checkcargo clippy --locked --all-targets --all-features -- -D warningscargo test --locked --all-featurescargo test --locked --no-default-featurescargo deny check advisories licenses sources banscargo publish --locked --dry-runRequired repository-admin follow-up
After merge, configure the
mainruleset, protectedv*tags, required status checks/CODEOWNERS review, trusted label permissions, and required reviewers on thereleaseenvironment as specified ingovernance/guardrails.md. These external settings are deliberately not claimed as repository-enforced until configured.