fix(security): resolve cargo audit dependency advisories - #117
Conversation
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (30)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe pull request upgrades the Cargo development dependency ChangesCriterion upgrade
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 7✅ Passed checks (7 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the Cargo file Comment |
Summary
Resolves #100 by fixing the dependency graph reported by
cargo audit.Changes
Cargo.tomlcriterion constraint from0.5to0.8.2. The lockfile had already selected criterion 0.8.2, but fresh resolution could downgrade it and reintroduce the affected dependency graph.crossbeam-epochfrom0.9.18to0.9.20, resolving RUSTSEC-2026-0204.anyhowfrom1.0.101to1.0.103, resolving RUSTSEC-2026-0190.Verification
cargo metadata --locked --no-deps --format-version 1cargo test --workspace --lockedcargo build --release --workspace --lockedcargo fmt --all -- --checkRUSTFLAGS=-Dwarnings cargo clippy --workspace --locked -- -D warningscargo audit --deny warningscargo audit --deny unmaintainedAll checks pass locally.