Repository navigation
Conversation
10 tasks
arun-pathiban-ddog
approved these changes
Oct 9, 2026
This branch has not been deployed
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.
Closes #528; tracked in #529.
Problem
The CI
Dependency isolationstep rancargo tree --no-devinside anif ... | grep -qpipeline with stderr suppressed. On the pinnednightly-2026-02-08toolchain that argument is unsupported: Cargo exits1 witherror: unexpected argument '--no-dev' found, the pipeline treats the empty graph as a negative match, and the step printsDependency isolation: OKwithout querying any dependencies.Change
scripts/check-dependency-isolation.sh: queriescargo tree --edges no-dev -p <crate> --color never, buffers the complete graph, requires a successful Cargo exit before inspection, preserves stderr and the failing status, and rejects empty/whitespace-only output. Package-name boundaries keep allowed lookalikes (stateright-helper,proptest-helper) passing. Policy unchanged:temper-verifyforbidden only intemper-jit;stateright/proptestforbidden in the jit/server/runtime non-dev graphs.scripts/test-dependency-isolation.sh:19 controlled-Cargo regression cases invoking the production guard: allowed graph, each forbidden package in each protected root, verifier allowed outside jit, Cargo failure with preserved stderr/exit per root, empty and whitespace-only output, SIGPIPE-style status141 with partial output, and a large graph with an early forbidden entry followed by10,000 dependencies..github/workflows/ci.yml: the isolation step now runs the tested implementation, with the regression suite immediately before it.Verification
OK(FAIL cargo-error-jit: expected exit 42, got 0).Dependency isolation: OK; current default-feature host graphs contain no forbidden dependencies.bash -non both scripts andgit diff --checkpass. A fresh independent source review found no issues.Limits
scripts/audit-deps.shand.claude/hooks/check-deps.share intentionally out of scope.
Confidence Score: 5/5
The PR appears safe to merge; no actionable issues were found.Summary
Moves dependency isolation into a tested script. Cargo errors and empty graphs now fail the check instead of reporting success.
git diff --checkpassed.gabrikexplicitly limits this change to default-feature host graphs; other feature and target combinations remain outside its scope.gabrikexplicitly leaves the existing unsupported queries inscripts/audit-deps.shand.claude/hooks/check-deps.shout of scope.Reviews (1) · Last reviewed commit: "fix(ci): fail dependency isolation on ca..." · Reviewed by Greptile