chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] - #2318
chore(libdd-data-pipeline): solve cargo deny [APMSP-3884]#2318Eldolfin wants to merge 3 commits into
Conversation
|
🎯 Code Coverage (details) 🔗 Commit SHA: 83d4d85 | Docs | Datadog PR Page | Give us feedback! |
We cannot update `time` before bumping our MSRV. Also we're not affected by this because there is no user provided input
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
BenchmarksComparisonBenchmark execution time: 2026-08-05 13:23:40 Comparing candidate commit 2021264 in PR branch Found 9 performance improvements and 21 performance regressions! Performance is the same for 110 metrics, 0 unstable metrics.
|
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 202126436a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [[package]] | ||
| name = "rand" | ||
| version = "0.8.5" | ||
| version = "0.8.7" |
There was a problem hiding this comment.
Raise the rand lower bounds in Cargo.toml
Updating the lockfile to rand 0.8.7 fixes RUSTSEC-2026-0097 only for this workspace checkout; libdd-data-pipeline and the other publishable crates still declare rand = "0.8.5"/"0.8" in their manifests, so consumer lockfiles that already contain 0.8.5 or minimal-version builds can continue using the affected version. Cargo documents that Cargo.lock “does not affect the consumers of your package, only Cargo.toml does” (https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control), and RustSec marks the 0.8 line patched only from 0.8.6 (https://rustsec.org/advisories/RUSTSEC-2026-0097.html); please raise the manifest lower bounds to at least 0.8.6/0.8.7 where rand is a dependency.
Useful? React with 👍 / 👎.
| [[package]] | ||
| name = "rand" | ||
| version = "0.8.5" | ||
| version = "0.8.7" |
There was a problem hiding this comment.
Raise the rand lower bounds in Cargo.toml
Updating the lockfile to rand 0.8.7 fixes RUSTSEC-2026-0097 only for this workspace checkout; libdd-data-pipeline and the other publishable crates still declare rand = "0.8.5"/"0.8" in their manifests, so consumer lockfiles that already contain 0.8.5 or minimal-version builds can continue using the affected version. Cargo documents that Cargo.lock “does not affect the consumers of your package, only Cargo.toml does that” (https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control), and RustSec marks the 0.8 line patched only from 0.8.6 (https://rustsec.org/advisories/RUSTSEC-2026-0097.html); please raise the manifest lower bounds to at least 0.8.6/0.8.7 where rand is a dependency.
Useful? React with 👍 / 👎.
📚 Documentation Check Results📦
|
🔒 Cargo Deny Results📦
|
What does this PR do?
Solve
cargo denyerrors inlibdd-data-pipelineby updating some dependencies.Motivation
What inspired you to submit this pull request?
Additional Notes
Sadly, updating
timerequires a bump in our MSRV from1.87.0to1.88.0, this can be done in a separate PR.How to test the change?
Describe here in detail how the change can be validated.