Update LZ4 dependency to 1.11.4

[mcculls]

Motivation

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

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-12T15:26:20.881035Z	0e7dc07	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0e7dc07727

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[datadog-datadog-prod-us1]

More details

The LZ4 1.11.4 catalog and lockfile updates are consistent with the existing shading configuration and call sites. Runtime compatibility remains unverified.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit a538e1f}

[dd-octo-sts]

🟢 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	13.97 s	13.95 s	[-0.5%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.85 s	12.91 s	[-1.2%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	17.06 s	16.94 s	[-0.0%; +1.4%] (no difference)
startup:petclinic:iast:Agent	16.83 s	17.07 s	[-2.3%; -0.6%] (maybe better)
startup:petclinic:profiling:Agent	16.62 s	16.75 s	[-2.0%; +0.5%] (no difference)
startup:petclinic:sca:Agent	17.11 s	17.15 s	[-1.0%; +0.6%] (no difference)
startup:petclinic:tracing:Agent	16.10 s	16.23 s	[-1.7%; +0.1%] (no difference)

Commit: a538e1f9 · 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.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-12 16:43:24 UTC ℹ️ Start processing command /merge

---

2026-10-12 16:43:28 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-10-12 17:48:22 UTC ℹ️ MergeQueue: This merge request was merged