chore: move all remaining external deps to workspace-level dependencies

[yannham]

What does this PR do?

Follow-up of #2350. Migrate all of the remaining external dependencies to the workspace level. duplicate was used with incompatible major versions. Mostly the macro syntax changed. Files are updated to use the latest version's syntax.

Motivation

As for the other workspace-level deps: use a single source of truth and version, for each dependency, in the whole workspace. Force leaf crates to opt-in features they need instead of blindly enabling default features.

[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-09-10T14:56:58.630897Z	ff44675	Manual request

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

[datadog-official]

More details

Source inspection finds no reportable defect in the dependency changes, feature selections, or macro syntax updates.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 737075e · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-official]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 50.00%
• Overall Coverage: 77.67% (-0.15%)

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

[dd-octo-sts]

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	9.02 MB	9.02 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	95.91 MB	95.96 MB	+.05% (+51.14 KB) 🔍

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.18 MB	12.18 MB	+.01% (+2.17 KB) 🔍
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	107.26 MB	107.36 MB	+.09% (+102.97 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change

libdatadog-x86-windows

Artifact	Baseline	Commit	Change

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	85.88 MB	85.93 MB	+.05% (+48.33 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	10.02 MB	10.03 MB	+.03% (+4.00 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	101.82 MB	101.82 MB	+0% (+1.79 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.25 MB	12.25 MB	+0% (+200 B) 👌

[pr-commenter]

Benchmarks

Comparison

Benchmark execution time: 2026-09-10 15:57:16

Comparing candidate commit 4eba699 in PR branch yannham/all-workspace-deps with baseline commit 513a0ae in branch main.

📊 Benchmarking dashboard

Found 15 performance improvements and 3 performance regressions! Performance is the same for 147 metrics, 11 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:glob_matcher/ascii_exact_miss/wall_time

• 🟩 execution_time [-0.858ns; -0.788ns] or [-7.014%; -6.444%]

scenario:glob_matcher/ascii_pattern_unicode_subject/wall_time

• 🟩 execution_time [-12.403ns; -12.315ns] or [-8.220%; -8.162%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/wall_time

• 🟩 execution_time [-20.271ns; -20.244ns] or [-35.231%; -35.185%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/wall_time

• 🟩 execution_time [-14.595ns; -14.550ns] or [-26.185%; -26.105%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

• 🟩 execution_time [-20.221ns; -20.192ns] or [-35.413%; -35.364%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

• 🟩 execution_time [-17.587ns; -17.567ns] or [-32.273%; -32.235%]

scenario:glob_matcher/unicode_exact_match/wall_time

• 🟩 execution_time [-17.701ns; -17.634ns] or [-19.321%; -19.249%]

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

• 🟩 execution_time [-3.969ns; -3.819ns] or [-4.204%; -4.045%]

scenario:glob_matcher/unicode_pattern_wildcard_match/wall_time

• 🟩 execution_time [-18.753ns; -18.672ns] or [-13.176%; -13.119%]

scenario:normalization/normalize_service/normalize_service/[empty string]

• 🟥 execution_time [+1.629µs; +1.660µs] or [+4.484%; +4.570%]
• 🟥 throughput [-1203547.923op/s; -1180723.063op/s] or [-4.372%; -4.289%]

scenario:profiler_attached/fast_path_system/4096

• 🟩 execution_time [-10.447ns; -10.293ns] or [-9.874%; -9.729%]

scenario:profiler_attached/slow_path_system/4096

• 🟥 execution_time [+6.880ns; +7.045ns] or [+4.587%; +4.697%]

scenario:sql/obfuscate_sql_string

• 🟩 execution_time [-17.674µs; -17.492µs] or [-5.713%; -5.654%]

scenario:tags/replace_trace_tags

• 🟩 execution_time [-267.885ns; -259.746ns] or [-9.161%; -8.883%]

scenario:tags/replace_trace_tags_v04

• 🟩 execution_time [-271.501ns; -240.437ns] or [-8.774%; -7.770%]

scenario:trace_buffer/4_senders/no_delay

• 🟩 execution_time [-247.736µs; -236.330µs] or [-6.470%; -6.172%]
• 🟩 throughput [+61961.337op/s; +64932.994op/s] or [+6.590%; +6.906%]

Unstable benchmarks

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

scenario:datadog_sample_span/parent_not_sampled_short_circuit/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+557.868%; -556.740%]

scenario:datadog_sample_span/parent_sampled_short_circuit/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+557.284%; -556.464%]

scenario:flagevaluation_evp/coalescer/typical/100flags_50users_10fields

• unstable execution_time [-11388.854ns; +11659.917ns] or [-6.067%; +6.212%]

scenario:glob_matcher/ascii_case_insensitive_match/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+562.535%; -558.947%]

scenario:glob_matcher/ascii_exact_match/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+563.148%; -559.238%]

scenario:glob_matcher/ascii_exact_miss/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+532.326%; -544.865%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+774.584%; -667.037%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+698.436%; -626.876%]

scenario:glob_matcher/ascii_wildcard_question_match/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+750.104%; -654.008%]

scenario:glob_matcher/ascii_wildcard_star_match/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+755.839%; -657.051%]

scenario:glob_matcher/star_short_circuit/allocated_bytes

• unstable execution_time [-0.000ns; +0.000ns] or [+559.228%; -557.382%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

[typotter]

lgtm for FFE

[datadog-official]

More details

The workspace dependency move keeps each leaf crate's feature choice. The required duplicate, priority-queue, and elf API changes match the new dependency versions.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit c56110d · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[yannham]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: ff44675275

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