Complete DriftGuard v0.3 launch readiness - #1
Merged
Merged
Conversation
DriftGuard ReportVerdict: Passed |
sidsri14
marked this pull request as ready for review
July 19, 2026 13:12
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.
What changed
driftguard doctorWhy
Public-repository onboarding trials exposed missing-manifest ambiguity, noisy placeholder prompt contracts, and the need for narrow suppression controls. This release closes those gaps while keeping execution local and deterministic.
Developer impact
Consumers get versioned machine output, clearer setup diagnostics, lower false-positive friction, and cross-platform validation. Existing terminal and Markdown check flows remain supported.
Validation
cargo fmt --checkcargo test --locked(26 tests)cargo clippy --all-targets --all-features --locked -- -D warningscargo run -- check --since origin/main --env-scope changed --jsoncargo bench --bench env_scancargo publish --dry-run --allow-dirtycargo install --path . --lockedRelease note
Actual crates.io publication still requires a locally configured crates.io token; no credential is stored in this repository.