chore: update falcon latest version to 4.4.0

[dd-octo-sts]

Update falcon lockfiles and dependency package lockfiles.
This performs the following updates:

1. Some falcon locks use falcon latest. This updates that package and its dependencies.
2. Some locks pin falcon but use the latest version of another package. This updates those dependencies.

[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-15T07:49:24.366318Z	7b1ac5a	New commits

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

[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.

No remaining files require a CODEOWNERS review.

[cit-pr-commenter-54b7da]

Dependency direction analysis

⚠️ Existing dependency direction violations

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

Show existing violations (showing 5 of 163 highest severity)

ddtrace.internal.tracemethods -×-> ddtrace.trace  (internal-core -> product:tracing, score=121)
ddtrace.internal.test_visibility.api -×-> ddtrace.trace  (product:ci_visibility -> product:tracing, score=119)
ddtrace.llmobs._utils -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=119)
ddtrace.llmobs._integrations.mcp -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=119)
ddtrace.internal.ci_visibility.filters -×-> ddtrace.trace  (product:ci_visibility -> product:tracing, score=119)

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

[datadog-datadog-prod-us1-2]

More details

The updated locks match the Falcon test matrix, preserve pinned 3.x variants, and agree with the published version metadata. The completed static review identified no reportable defect.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit f5e4309}

[datadog-datadog-prod-us1-2]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-10-15 08:17:03

Comparing candidate commit 7b1ac5a in PR branch upgrade-latest-falcon-version with baseline commit e4b09a8 in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 9 performance regressions! Performance is the same for 583 metrics, 10 unstable metrics, 7 known flaky benchmarks, 17 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-tracecontext_headers

• 🟥 execution_time [+3.170µs; +3.376µs] or [+10.156%; +10.817%]

scenario:iastaspects-add_aspect

• 🟥 execution_time [+9.967µs; +12.381µs] or [+11.283%; +14.015%]

scenario:iastaspects-format_map_noaspect

• 🟥 execution_time [+94.130µs; +99.920µs] or [+25.733%; +27.316%]

scenario:iastaspects-lstrip_aspect

• 🟥 execution_time [+101.119µs; +104.318µs] or [+42.559%; +43.906%]

scenario:iastaspectsremodule-re_expand_aspect

• 🟥 execution_time [+86.685µs; +93.368µs] or [+13.825%; +14.891%]

scenario:msgpackencoderscenario-simple_one_span

• 🟥 execution_time [+479.358ns; +566.994ns] or [+12.149%; +14.370%]

scenario:openfeatureflagevaluation-hook-enqueue-typical

• 🟥 execution_time [+1.609µs; +1.739µs] or [+7.444%; +8.045%]

scenario:otelspan-start

• 🟥 execution_time [+2.459ms; +3.327ms] or [+9.468%; +12.809%]

scenario:recursivecomputation-shallow

• 🟥 execution_time [+57.910µs; +61.193µs] or [+8.305%; +8.776%]

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 [-762.108ns; +716.789ns] or [-7.309%; +6.874%]

scenario:coreapiscenario-core_dispatch_1_listener

• unstable execution_time [-36.908ns; +41.404ns] or [-5.564%; +6.241%]

scenario:coreapiscenario-core_dispatch_50_listeners

• unstable execution_time [-1911.146ns; +1914.282ns] or [-9.616%; +9.632%]

scenario:coreapiscenario-core_dispatch_exception_listeners

• unstable execution_time [-1881.920ns; +1800.362ns] or [-9.850%; +9.423%]

scenario:coreapiscenario-core_dispatch_listeners

• unstable execution_time [-393.565ns; +364.596ns] or [-9.229%; +8.550%]

scenario:coreapiscenario-core_dispatch_no_args_listeners

• unstable execution_time [-229.872ns; +225.950ns] or [-8.553%; +8.407%]

scenario:coreapiscenario-core_dispatch_with_results_1_listener

• unstable execution_time [-83.999ns; +101.064ns] or [-6.247%; +7.516%]

scenario:coreapiscenario-core_dispatch_with_results_50_listeners

• unstable execution_time [-5064.738ns; +4290.005ns] or [-10.393%; +8.803%]

scenario:coreapiscenario-core_dispatch_with_results_listeners

• unstable execution_time [-1007.560ns; +890.231ns] or [-9.827%; +8.683%]

scenario:packagesupdateimporteddependencies-import_many_stdlib_cached

• unstable execution_time [-50.586µs; +56.890µs] or [-9.004%; +10.126%]

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.419µs; +2.537µs] or [+17.525%; +18.376%]

scenario:iastaspects-translate_noaspect

• 🟥 execution_time [+50.207µs; +58.103µs] or [+8.434%; +9.761%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+148.015µs; +154.121µs] or [+38.383%; +39.966%]

scenario:iastaspectssplit-rsplit_aspect

• 🟥 execution_time [+25.015µs; +29.378µs] or [+16.201%; +19.028%]

scenario:span-start

• 🟥 execution_time [+1.474ms; +1.775ms] or [+13.324%; +16.040%]

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

• 🟥 execution_time [+237.605ns; +268.578ns] or [+12.516%; +14.147%]

scenario:tracer-small

• 🟥 execution_time [+46.517µs; +47.571µs] or [+19.548%; +19.991%]

Known flaky benchmarks without significant changes:

• scenario:errortrackingflasksqli-baseline
• scenario:flasksimple-iast-get
• 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-title_noaspect
• scenario:iastaspects-translate_aspect
• scenario:iastaspects-upper_noaspect
• scenario:packagespackageforrootmodulemapping-cache_off
• scenario:packagespackageforrootmodulemapping-cache_on
• scenario:sethttpmeta-all-enabled
• scenario:telemetryaddmetric-record-100-metrics

[dubloom]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-15 08:08:54 UTC ℹ️ Start processing command /merge

---

2026-10-15 08:09:06 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-10-15 08:34:09 UTC ℹ️ MergeQueue: merge request added to the queue

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

---

2026-10-15 09:17:54 UTC ℹ️ MergeQueue: This merge request was merged