Bump LZ4 version to latest - #12091
Conversation
There was a problem hiding this comment.
More details
The dependency-only upgrade is internally consistent: the version catalog and all seven affected lockfiles move together from LZ4 1.11.0 to 1.11.1, with no diff-only behavioral hazard identified. Runtime compression tests could not execute because the sandbox lacks the repository-required Java 25 toolchain.
🤖 Datadog Autotest · Commit 4be8fb0 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4be8fb094e
ℹ️ 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".
| javaparser = "3.28.2" | ||
| jctools = "4.0.6" | ||
| lz4 = "1.11.0" | ||
| lz4 = "1.11.1" |
There was a problem hiding this comment.
Regenerate the remaining LZ4 lock
The repo-wide lockfile search still finds at.yawk.lz4:lz4-java:1.11.0 in dd-java-agent/instrumentation/play/play-appsec-2.7/gradle.lockfile:6 for its test* and latestDepTest* configurations. Because this repository commits per-project dependency locks, the checked-in dependency state—and any lockfile-based CVE reporting—continues to include the vulnerable version despite this catalog bump; regenerate that module's lockfile as part of the update.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
no biggie for tests
|
🎯 Code Coverage (details) 🔗 Commit SHA: 4be8fb0 | Docs | Datadog PR Page | Give us feedback! |
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Build pipeline has failing jobs for 994cfcd:
What to do next?
DetailsSince those jobs are not marked as being allowed to fail, the pipeline will most likely fail. |
PerfectSlayer
left a comment
There was a problem hiding this comment.
I would rather have profiling review /ack it before merging to evaluate the impact
I mean, why not, but really this minor release contains only the fix for the CVE, nothing else, so it's pretty safe to say the impact will be none. |
jbachorik
left a comment
There was a problem hiding this comment.
As long as smoke tests are passing, LGTM!
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
97bb5fc
into
master
What Does This Do
bump lz4 version to latest minor (fixes CVE GHSA-xx22-p4ch-683r)
solves #12090
Motivation
Additional Notes
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: [PROJ-IDENT]