chore(deps): bump the docker-compose-images group across 1 directory with 7 updates

[dependabot]

Warning

Cooldown could not be applied because no publication date was available from the registry.

Bumps the docker-compose-images group with 7 updates in the / directory:

Package	From	To
elasticsearch	9.5.1	9.5.3
mongo	8.2.12	8.3.11
motoserver/moto	5.2.2	5.2.3
rabbitmq	4.3.4-alpine	4.3.6-alpine
azure-storage/azurite	3.36.0	3.37.0
selenium/standalone-chrome	151.0.7922.108	153.0.8010.47
google/cloud-sdk	580.0.0-emulators	585.0.0-emulators

Updates elasticsearch from 9.5.1 to 9.5.3

Updates mongo from 8.2.12 to 8.3.11

Updates motoserver/moto from 5.2.2 to 5.2.3

Updates rabbitmq from 4.3.4-alpine to 4.3.6-alpine

Updates azure-storage/azurite from 3.36.0 to 3.37.0

Updates selenium/standalone-chrome from 151.0.7922.108 to 153.0.8010.47

Updates google/cloud-sdk from 580.0.0-emulators to 585.0.0-emulators

[datadog-prod-us1-5]

 

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

DataDog/apm-reliability/dd-trace-py | microbenchmarks: [2, errortracking_flask_sqli flask_simple]

View more details · View in GitLab

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🚧 19 tests that failed were ignored due to quarantine

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4521705 | Docs | View more details | Give us feedback!}

[cit-pr-commenter-54b7da]

Circular import analysis

⚠️ Existing circular imports

There are 1 circular imports that already exist on the base branch and have not been changed by this PR.

ddtrace.errortracking._handled_exceptions.bytecode_injector -> ddtrace.errortracking._handled_exceptions.callbacks -> ddtrace.errortracking._handled_exceptions.collector -> ddtrace.errortracking._handled_exceptions.bytecode_reporting -> ddtrace.errortracking._handled_exceptions.bytecode_injector

[cit-pr-commenter-54b7da]

Dependency direction analysis

⚠️ Existing dependency direction violations

There are 210 dependency direction violations that already exist on the base branch and have not been changed by this PR.

Show existing violations (showing 5 of 210 highest severity)

ddtrace.internal.tracemethods -×-> ddtrace.trace  (internal-core -> product:tracing, score=133)
ddtrace.llmobs._integrations.pydantic_ai -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=131)
ddtrace.llmobs._evaluators.runner -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=131)
ddtrace.internal.test_visibility.api -×-> ddtrace.trace  (product:ci_visibility -> product:tracing, score=131)
ddtrace.profiling.scheduler -×-> ddtrace.trace  (product:profiling -> product:tracing, score=131)

To see all violations, download the layers-base.json and layers-pr.json artifacts from this CI job and run:

uv run --script scripts/import-analysis/layers.py compare layers-base.json layers-pr.json

[cit-pr-commenter-54b7da]

Codeowners resolved as

Resolved from the full PR diff against main using the target branch CODEOWNERS file.
CODEOWNERS team requests not listed below are not required by the current file set.

docker-compose.base.yml                                                 @DataDog/python-guild

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-21 03:46:04

Comparing candidate commit 4521705 in PR branch dependabot/docker_compose/docker-compose-images-dda44709e4 with baseline commit fbf13a0 in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 4 performance regressions! Performance is the same for 576 metrics, 10 unstable metrics, 7 known flaky benchmarks, 16 flaky benchmarks without significant changes.

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:httppropagationextract-empty_headers

• 🟥 execution_time [+57.341ns; +76.904ns] or [+8.708%; +11.679%]

scenario:iastaspects-repr_aspect

• 🟥 execution_time [+69.002µs; +73.786µs] or [+19.700%; +21.066%]

scenario:msgpackencoderscenario-simple_one_span

• 🟥 execution_time [+426.775ns; +489.216ns] or [+12.795%; +14.667%]

scenario:otelspan-start

• 🟥 execution_time [+2.255ms; +3.304ms] or [+7.268%; +10.652%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:coreapiscenario-context_with_data_listeners

• unstable execution_time [-687.350ns; +808.510ns] or [-6.171%; +7.259%]

scenario:coreapiscenario-core_dispatch_1_listener

• unstable execution_time [-39.585ns; +25.934ns] or [-6.453%; +4.228%]

scenario:coreapiscenario-core_dispatch_50_listeners

• unstable execution_time [-2040.443ns; +1232.632ns] or [-11.891%; +7.183%]

scenario:coreapiscenario-core_dispatch_exception_listeners

• unstable execution_time [-1156.178ns; +1309.999ns] or [-8.818%; +9.991%]

scenario:coreapiscenario-core_dispatch_listeners

• unstable execution_time [-328.136ns; +317.248ns] or [-8.894%; +8.599%]

scenario:coreapiscenario-core_dispatch_no_args_listeners

• unstable execution_time [-302.817ns; +202.082ns] or [-10.257%; +6.845%]

scenario:coreapiscenario-core_dispatch_with_results_1_listener

• unstable execution_time [-66.704ns; +83.881ns] or [-5.718%; +7.191%]

scenario:coreapiscenario-core_dispatch_with_results_50_listeners

• unstable execution_time [-3932.120ns; +4089.315ns] or [-9.655%; +10.041%]

scenario:coreapiscenario-core_dispatch_with_results_listeners

• unstable execution_time [-781.838ns; +784.103ns] or [-9.551%; +9.578%]

scenario:packagesupdateimporteddependencies-import_many_stdlib_cached

• unstable execution_time [-60.109µs; +52.609µs] or [-10.150%; +8.884%]

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:httppropagationinject-ids_only

• 🟥 execution_time [+2.535µs; +2.702µs] or [+14.926%; +15.905%]

scenario:iastaspects-title_noaspect

• 🟥 execution_time [+20.814µs; +25.319µs] or [+10.780%; +13.113%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+115.420µs; +120.696µs] or [+29.318%; +30.659%]

scenario:iastaspectssplit-rsplit_aspect

• 🟥 execution_time [+24.752µs; +29.253µs] or [+17.671%; +20.885%]

scenario:span-start

• 🟥 execution_time [+1.812ms; +1.954ms] or [+12.859%; +13.868%]

scenario:telemetryaddmetric-1-count-metric-1-times

• 🟥 execution_time [+599.722ns; +641.191ns] or [+21.652%; +23.150%]

scenario:tracer-small

• 🟥 execution_time [+34.035µs; +36.678µs] or [+10.546%; +11.365%]

Known flaky benchmarks without significant changes:

• scenario:errortrackingflasksqli-baseline
• scenario:iastaspects-casefold_aspect
• scenario:iastaspects-casefold_noaspect
• scenario:iastaspects-index_aspect
• scenario:iastaspects-ljust_noaspect
• scenario:iastaspects-lower_aspect
• scenario:iastaspects-replace_aspect
• scenario:iastaspects-rstrip_aspect
• scenario:iastaspects-swapcase_aspect
• scenario:iastaspects-translate_aspect
• scenario:iastaspects-translate_noaspect
• scenario:iastaspects-upper_noaspect
• scenario:packagespackageforrootmodulemapping-cache_off
• scenario:packagespackageforrootmodulemapping-cache_on
• scenario:sethttpmeta-all-enabled
• scenario:telemetryaddmetric-record-100-metrics

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.