Repository navigation
chore(deps) #386: update sub-workspace Cargo.lock files to resolve Dependabot alerts - #387
Conversation
…pendabot alerts Three standalone example crates had stale pinned dependencies; one orphaned workspace-member lockfile was removed (d-engine-client/Cargo.lock is unused since the crate builds under the parent workspace).
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (5)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What Does This PR Do?
Updates stale
Cargo.lockfiles in three standalone example crates and removesan orphaned lockfile from
d-engine-client(workspace member, never used by Cargo)to clear 30 open Dependabot alerts.
Type:
Why Is This Needed?
30 Dependabot alerts were open against sub-directory
Cargo.lockfiles. The mainworkspace
Cargo.lockwas already clean — the alerts came from stale pinned versionsin standalone example crates and one orphaned lockfile in
d-engine-client/.Packages updated:
astral-tokio-tar0.6.0→0.6.2,rustls-webpki→0.103.13,openssl→0.10.80,rand→0.8.6.Checklist
Required:
make testpassesTesting
How tested:
make testpasses clean (advisory + fmt + clippy + all examples + benchmarks)cargo deny check advisoriesclean on all affected directoriesDoes This Follow d-engine's Principles?
Reviewer Notes
Pure lockfile updates — no production code changed.
d-engine-client/Cargo.lockremoval is safe: the file was never used (Cargo workspace members share the root
lockfile; the sub-directory one was an orphan from initial scaffolding).
Estimated review complexity: