Skip to content

chore: release v40.0.0 - #2326

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
bob/release-v40.0.0
Aug 7, 2026
Merged

chore: release v40.0.0#2326
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
bob/release-v40.0.0

Conversation

@bwoebi

@bwoebi bwoebi commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Bump for inclusion of telemetry changes in python.

@bwoebi
bwoebi requested a review from a team as a code owner August 6, 2026 14:51
@bwoebi

bwoebi commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 6, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-06 14:53:57 UTC ℹ️ Start processing command /merge

2026-08-06 14:54:04 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

  • Run /code blockers to see what is blocking it.
  • Run /remove to cancel it.

2026-08-06 15:40:15 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 50m (p90).

2026-08-06 16:01:18 UTC ℹ️ MergeQueue: Readding this merge request to the queue because another merge request processed with yours failed. No action is needed from your side.

2026-08-06 16:47:06 UTC ⚠️ MergeQueue: This merge request build was cancelled

bob.weinand@datadoghq.com cancelled this merge request build

@datadog-prod-us1-4

datadog-prod-us1-4 Bot commented Aug 6, 2026 •
edited by datadog-datadog-us1-prod Bot
Loading

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 75.90%

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

@dd-octo-sts

dd-octo-sts Bot commented Aug 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 8.14 MB 8.14 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 88.26 MB 88.26 MB +0% (+1.42 KB) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.96 MB 10.96 MB 0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 99.41 MB 99.41 MB +0% (+2.59 KB) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 26.34 MB 26.34 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 94.26 KB 94.26 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 189.51 MB 189.51 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 987.60 MB 986.92 MB --.06% (-693.97 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 8.61 MB 8.61 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 94.26 KB 94.26 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 25.33 MB 25.33 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 50.45 MB 50.45 MB +0% (+444 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 22.96 MB 22.96 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 95.74 KB 95.74 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 194.30 MB 194.33 MB +.01% (+32.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 976.39 MB 976.27 MB --.01% (-118.86 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.65 MB 6.65 MB +0% (+512 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 95.74 KB 95.74 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 27.24 MB 27.24 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 48.04 MB 48.04 MB +0% (+740 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 78.61 MB 78.61 MB -0% (-664 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 9.05 MB 9.05 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 94.25 MB 94.25 MB -0% (-2.33 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.02 MB 11.02 MB +0% (+24 B) 👌

@pr-commenter

pr-commenter Bot commented Aug 6, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-08-07 03:36:57

Comparing candidate commit 810593f in PR branch bob/release-v40.0.0 with baseline commit 05d785e in branch main.

Found 3 performance improvements and 16 performance regressions! Performance is the same for 121 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:msgpack_decoder::v05/high_sharing/200

  • 🟥 execution_time [+6.995µs; +7.082µs] or [+4.465%; +4.521%]
  • 🟥 throughput [-55233.820op/s; -54561.766op/s] or [-4.326%; -4.274%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_2/8

  • 🟥 execution_time [+22.785ns; +22.972ns] or [+4.879%; +4.919%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_4/8

  • 🟥 execution_time [+19.357ns; +19.559ns] or [+4.878%; +4.929%]

scenario:vec_map/dedup/dup_1_in_10/128

  • 🟥 execution_time [+1.762µs; +1.803µs] or [+28.821%; +29.478%]

scenario:vec_map/dedup/dup_1_in_10/16

  • 🟥 execution_time [+259.786ns; +269.765ns] or [+33.623%; +34.915%]

scenario:vec_map/dedup/dup_1_in_10/64

  • 🟥 execution_time [+792.221ns; +813.349ns] or [+24.696%; +25.355%]

scenario:vec_map/dedup/dup_1_in_10/8

  • 🟥 execution_time [+118.963ns; +124.240ns] or [+30.425%; +31.775%]

scenario:vec_map/dedup/dup_1_in_2/128

  • 🟥 execution_time [+2.694µs; +2.730µs] or [+31.015%; +31.429%]

scenario:vec_map/dedup/dup_1_in_2/16

  • 🟥 execution_time [+361.081ns; +369.095ns] or [+33.053%; +33.787%]

scenario:vec_map/dedup/dup_1_in_2/64

  • 🟥 execution_time [+1.257µs; +1.281µs] or [+28.096%; +28.639%]

scenario:vec_map/dedup/dup_1_in_2/8

  • 🟥 execution_time [+174.034ns; +178.487ns] or [+31.474%; +32.279%]

scenario:vec_map/dedup/dup_1_in_4/128

  • 🟥 execution_time [+2.136µs; +2.170µs] or [+30.204%; +30.688%]

scenario:vec_map/dedup/dup_1_in_4/16

  • 🟥 execution_time [+267.676ns; +275.792ns] or [+30.071%; +30.983%]

scenario:vec_map/dedup/dup_1_in_4/64

  • 🟥 execution_time [+967.491ns; +988.978ns] or [+26.239%; +26.821%]

scenario:vec_map/dedup/dup_1_in_4/8

  • 🟥 execution_time [+136.480ns; +139.569ns] or [+30.222%; +30.906%]

scenario:vec_map/dedup/no_duplicates/64

  • 🟩 execution_time [-143.751ns; -123.616ns] or [-5.349%; -4.599%]

scenario:vec_map/get_mut/8

  • 🟩 execution_time [-9.318ns; -4.134ns] or [-10.628%; -4.715%]
  • 🟩 throughput [+5103658.446op/s; +11252969.708op/s] or [+5.467%; +12.053%]

Benchmark execution time: 2026-08-07 03:50:10

Comparing candidate commit 810593f in PR branch bob/release-v40.0.0 with baseline commit 05d785e in branch main.

Found 7 performance improvements and 1 performance regressions! Performance is the same for 160 metrics, 10 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:alloc_free/system/4096

  • 🟩 execution_time [-6.702ns; -6.555ns] or [-7.243%; -7.084%]

scenario:datadog_sample_span/tag_rule_not_matching/wall_time

  • 🟥 execution_time [+8.743ns; +9.217ns] or [+6.242%; +6.580%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

  • 🟩 execution_time [-21.428ns; -21.394ns] or [-36.728%; -36.670%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

  • 🟩 execution_time [-21.466ns; -21.414ns] or [-36.762%; -36.674%]

scenario:glob_matcher/unicode_pattern_wildcard_match/wall_time

  • 🟩 execution_time [-6.996ns; -6.921ns] or [-5.318%; -5.262%]

scenario:profiler_attached/fast_path_system/4096

  • 🟩 execution_time [-13.568ns; -13.380ns] or [-12.996%; -12.816%]

scenario:trace_buffer/2_senders/no_delay

  • 🟩 execution_time [-93.550µs; -78.312µs] or [-5.734%; -4.800%]
  • 🟩 throughput [+55962.038op/s; +66912.230op/s] or [+5.070%; +6.062%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

@bwoebi

bwoebi commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

/merge -c

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 6, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-06 16:46:57 UTC ℹ️ Start processing command /merge -c

@bwoebi
bwoebi force-pushed the bob/release-v40.0.0 branch from 6563aba to 810593f Compare August 7, 2026 03:02
@bwoebi

bwoebi commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 7, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-07 03:03:48 UTC ℹ️ Start processing command /merge

2026-08-07 03:03:54 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

  • Run /code blockers to see what is blocking it.
  • Run /remove to cancel it.

2026-08-07 04:13:13 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 50m (p90).

2026-08-07 05:06:10 UTC ℹ️ MergeQueue: This merge request was merged

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 33f6862 into main Aug 7, 2026
125 of 126 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the bob/release-v40.0.0 branch August 7, 2026 05:06
bwoebi added a commit that referenced this pull request Aug 7, 2026
@bwoebi
Merge branch 'main' of github.com:DataDog/libdatadog into paullgdc/re…
57704bc 
…mote_config/agentless_fetcher

* 'main' of github.com:DataDog/libdatadog:
  feat(data-pipeline)!: add flush_and_close to the trace buffer (#2313)
  refactor(rc)!: make conversion from RemoteConfigProduct back and forth generally available (#2325)
  chore: release v40.0.0 (#2326)
  feat(datadog-ffe): server-side EVP flagevaluation payload + bincode-safe sidecar delivery (#2117)
  feat(data-pipeline): set structured span values (#2300)
  feat(telemetry)!: Add Installation signature and AppProduct changes payloads (#2213)
  fix(libdd-trace-utils): apply SpanLink flags masking when v0.5 json encoding (#2314)
  feat(data-pipeline): encode structured values (#2304)
  feat(crashtracking): send debug log when no data is received at all (#2321)
  chore: release v39.0.0 (#2324)
  feat(data-pipeline): add span links FFI (#2305)
  fix(crashtracking): check fields and exclude uuid for `has_data` (#2322)
  feat(data-pipeline): add span events FFI (#2301)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hoolioh hoolioh hoolioh approved these changes

Assignees

No one assigned

Labels

mergequeue-status: done run-all-tests

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@bwoebi @hoolioh @morrisonlevi