chore: bump libdatadog

[Leiyks]

Description

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[datadog-official]

 

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 11 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-php | ASAN Opcache tests: [8.5]     

DataDog/apm-reliability/dd-trace-php | ASAN test_c with multiple observers: [8.3]     

DataDog/apm-reliability/dd-trace-php | ASAN test_c with multiple observers: [8.4]     

View all 11 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 54.12% (-0.01%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 522d1e4 | Docs | Datadog PR Page | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6e2a163344

ℹ️ 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".

[chatgpt-codex-connector]

Update the renamed remote-config dependency

This submodule bump points at a libdatadog revision where datadog-remote-config has been renamed to libdd-remote-config, but the PHP Rust workspace still has components-rs/Cargo.toml:19 depending on ../libdatadog/datadog-remote-config and the root Cargo.lock still references the old package name. With this gitlink checked out, any cargo metadata/Rust build of components-rs fails before compiling because that path no longer exists, so the bump needs to update the local dependency name/path and lockfile together.

Useful? React with 👍 / 👎.

[typotter]

upgrade lgtm, in theory. pending Green CI

[pr-commenter]

Benchmarks [ tracer ]

Benchmark execution time: 2026-06-09 17:11:30

Comparing candidate commit 522d1e4 in PR branch leiyks/bump-libdatadog with baseline commit 0f53344 in branch master.

Found 2 performance improvements and 0 performance regressions! Performance is the same for 192 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:SamplingRuleMatchingBench/benchRegexMatching4

• 🟩 execution_time [-123.811ns; -38.789ns] or [-7.597%; -2.380%]

scenario:SamplingRuleMatchingBench/benchRegexMatching4-opcache

• 🟩 execution_time [-151.937ns; -60.863ns] or [-8.809%; -3.529%]