Skip to content

Bump LZ4 version to latest - #12091

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
masterfrom
vandonr-patch-1
Jul 29, 2026
Merged

Bump LZ4 version to latest#12091
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
masterfrom
vandonr-patch-1

Conversation

@vandonr

@vandonr vandonr commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

What Does This Do

bump lz4 version to latest minor (fixes CVE GHSA-xx22-p4ch-683r)
solves #12090

Motivation

Additional Notes

Contributor Checklist

Jira ticket: [PROJ-IDENT]

@vandonr
vandonr marked this pull request as ready for review July 28, 2026 14:03
@vandonr
vandonr requested review from a team as code owners July 28, 2026 14:03
@vandonr
vandonr requested a review from ygree July 28, 2026 14:03
@vandonr vandonr changed the title Vandonr patch 1 Bump LZ4 version to latest Jul 28, 2026

@datadog-datadog-prod-us1 datadog-datadog-prod-us1 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Autotest: PASS

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.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Datadog Autotest · Commit 4be8fb0 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread gradle/libs.versions.toml
javaparser = "3.28.2"
jctools = "4.0.6"
lz4 = "1.11.0"
lz4 = "1.11.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no biggie for tests

@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 57.70% (-0.00%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4be8fb0 | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite Status
Startup 🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results
Scenario Candidate master Δ (95% CI of mean)
startup:insecure-bank:iast:Agent 14.05 s 13.98 s [-0.3%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent 12.88 s 13.03 s [-1.8%; -0.5%] (maybe better)
startup:petclinic:appsec:Agent 17.05 s 16.65 s [+1.2%; +3.5%] (significantly worse)
startup:petclinic:iast:Agent 17.02 s 16.93 s [-0.4%; +1.4%] (no difference)
startup:petclinic:profiling:Agent 16.62 s 16.80 s [-2.3%; +0.1%] (no difference)
startup:petclinic:sca:Agent 17.06 s 16.86 s [+0.4%; +2.1%] (maybe worse)
startup:petclinic:tracing:Agent 16.10 s 16.25 s [-2.0%; +0.2%] (no difference)

Commit: 4be8fb09 · CI Pipeline · Benchmarking Platform UI


Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

@vandonr
vandonr added this pull request to the merge queue Jul 28, 2026
@dd-octo-sts

dd-octo-sts Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jul 28, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-07-28 15:59:13 UTC ℹ️ Start processing command /merge


2026-07-28 15:59:18 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-07-28 16:58:05 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 994cfcd:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jul 28, 2026

@PerfectSlayer PerfectSlayer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather have profiling review /ack it before merging to evaluate the impact

@vandonr

vandonr commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

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.

https://github.com/yawkat/lz4-java/releases/tag/v1.11.1

@jbachorik jbachorik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as smoke tests are passing, LGTM!

@vandonr
vandonr added this pull request to the merge queue Jul 29, 2026
@dd-octo-sts

dd-octo-sts Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jul 29, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-07-29 07:50:30 UTC ℹ️ Start processing command /merge


2026-07-29 07:50:35 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-07-29 09:18:07 UTC ℹ️ MergeQueue: This merge request was merged

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jul 29, 2026
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 97bb5fc into master Jul 29, 2026
592 of 598 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the vandonr-patch-1 branch July 29, 2026 09:18
@github-actions github-actions Bot added this to the 1.65.0 milestone Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants