refactor: migrate to workspace dependencies, phase 4 by yannham · Pull Request #2296 · DataDog/libdatadog

yannham · 2026-07-29T14:00:51Z

Follow up of #2283.

What does this PR do?

Moves the dev/test and specialized tooling dependencies to [workspace.dependencies]: tempfile, clap, criterion, bolero, allocator-api2, chrono, elf and cxx-build. This is phase 4 of the workspace dependency migration plan.

Version decisions, resolving the pre-existing skew:

Dependency	Before	Workspace version
`tempfile`	`3`, `3.3`, `3.3.0`, `3.8`, `3.10`, `3.13`	`3.13`
`clap`	`4.0`, `4.3.21`	`4.3.21`
`criterion`	`0.5`, `0.5.1`	`0.5.1`
`bolero`	`0.13`, `0.13.4`	`0.13.4`
`allocator-api2`	`0.2`, `0.2.21`	`0.2.21`
`chrono`	`0.4`, `0.4.31`, `0.4.38`	`0.4.38`
`elf`	`0.7`	`0.7`
`cxx-build`	`1.0`	`1.0`

For tempfilenothing had to be downgraded, and libdd-crashtracker keeps working on it.

Motivation

Single source of truth per dependency version, no accidental skew, shorter leaf-crate manifests.

Additional Notes

Three documented deviations from the `default-features = false` policy

The policy says workspace entries must carry default-features = false and let leaf crates opt in. Three of these dependencies declare a baseline feature set at the workspace level instead, because dropping their defaults degrades behaviour silently rather than failing to compile — so the "compile and escalate only on failure" rule would have quietly regressed them:

tempfile → getrandom. Without it tempfile seeds its temp-name RNG weakly, and its own docs flag that an attacker may then be able to predict the generated file names.
criterion → default. Without cargo_bench_support the harness refuses to run under a plain cargo bench; the other two produce the report plots.

Each is annotated with a comment in the root Cargo.toml explaining why. This follows the libc precedent from phase 3.

Behaviour changes worth a look

Cargo.lock loses exactly one thing: chrono's wasmbind edge (js-sys, wasm-bindgen). datadog-sidecar was pulling it in via implicit default features (chrono = "0.4.31"); it is not built for wasm32, so this is dead weight. No package is added or removed, hence LICENSE-3rdparty.csv is unchanged (regenerated to confirm).
elf needed an explicit features = ["std"] in both consumers — its Error impl for ParseError is behind std, which anyhow::Context requires.
libdd-trace-protobuf's fuzzing feature needed an explicit features = ["std"] on bolero: the TypeGenerator impl for HashMap lives behind std. Note this one is invisible to --all-features (feature unification across the workspace turns bolero/std on anyway) — it only shows up when checking that crate alone.

How to test the change?

cargo deny check was not run locally (cargo-deny isn't installed on this machine); since the resolved package set is byte-for-byte identical to main, its verdict should be unchanged, and CI covers it.

🤖 Generated with Claude Code

datadog-datadog-prod-us1 · 2026-07-29T14:14:09Z

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 74.83% (+0.02%)

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: 9b58363 | Docs | Datadog PR Page | Give us feedback!}

dd-octo-sts · 2026-07-29T14:45:02Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.01 MB	8.01 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	87.33 MB	87.32 MB	-0% (-1.82 KB) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.78 MB	10.78 MB	-0% (-960 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	98.56 MB	98.55 MB	-0% (-7.19 KB) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.05 MB	26.05 MB	-0% (-2.00 KB) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	89.60 KB	89.60 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	188.12 MB	188.10 MB	-0% (-16.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	981.00 MB	980.77 MB	--.02% (-240.67 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.49 MB	8.49 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	89.60 KB	89.60 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.10 MB	25.10 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	49.93 MB	49.93 MB	-0% (-626 B) 👌

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	22.69 MB	22.69 MB	+0% (+512 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	91.00 KB	91.00 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	192.89 MB	192.86 MB	--.01% (-32.00 KB) 💪
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	968.83 MB	969.41 MB	+.05% (+587.97 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.56 MB	6.56 MB	-0% (-512 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	91.00 KB	91.00 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	26.97 MB	26.97 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	47.53 MB	47.53 MB	+0% (+566 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	77.86 MB	77.87 MB	+.01% (+8.39 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	8.93 MB	8.93 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	93.35 MB	93.36 MB	+0% (+6.09 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.87 MB	10.87 MB	+0% (+632 B) 👌

pr-commenter · 2026-07-29T14:56:36Z

Benchmarks

Comparison

Benchmark execution time: 2026-07-30 15:24:05

Comparing candidate commit 9b58363 in PR branch yannham/workspace-deps-phase-4 with baseline commit 9614b20 in branch main.

Found 8 performance improvements and 24 performance regressions! Performance is the same for 110 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 [+8.735µs; +8.871µs] or [+5.532%; +5.618%]
🟥 throughput [-67412.165op/s; -66373.990op/s] or [-5.322%; -5.240%]

scenario:msgpack_decoder::v05/low_sharing/10000

🟩 execution_time [-1.092ms; -1.086ms] or [-5.988%; -5.956%]
🟩 throughput [+34738.729op/s; +34931.352op/s] or [+6.334%; +6.369%]

scenario:msgpack_decoder::v05/low_sharing/200

🟩 execution_time [-17.874µs; -17.659µs] or [-4.909%; -4.850%]
🟩 throughput [+28007.548op/s; +28358.110op/s] or [+5.099%; +5.162%]

scenario:msgpack_decoder::v05/low_sharing/2000

🟩 execution_time [-205.926µs; -204.591µs] or [-5.654%; -5.617%]
🟩 throughput [+32688.037op/s; +32905.358op/s] or [+5.953%; +5.992%]

scenario:otlp/e2e_json/1x1000

🟥 execution_time [+341.263µs; +349.540µs] or [+8.287%; +8.488%]

scenario:otlp/encode_json/1x1000

🟥 execution_time [+352.841µs; +353.390µs] or [+19.579%; +19.609%]

scenario:otlp/encode_protobuf/1x1000

🟩 execution_time [-99.905µs; -99.460µs] or [-8.621%; -8.583%]

scenario:profile_serialize_compressed_pprof_timestamped_x1000

🟥 execution_time [+49.062µs; +49.932µs] or [+5.297%; +5.391%]

scenario:profiles_dictionary/profile_string_inserts/threads/1

🟥 execution_time [+13.845µs; +15.350µs] or [+4.565%; +5.062%]
🟥 throughput [-163099.140op/s; -147030.587op/s] or [-4.830%; -4.354%]

scenario:vec_map/as_deduped_map/already_deduped/16

🟥 execution_time [+0.961ns; +0.980ns] or [+4.087%; +4.167%]

scenario:vec_map/as_deduped_map/already_deduped/8

🟥 execution_time [+0.941ns; +0.957ns] or [+6.782%; +6.899%]

scenario:vec_map/get_hit/128

🟥 execution_time [+4.310µs; +4.321µs] or [+34.744%; +34.830%]
🟥 throughput [-2666008.868op/s; -2659744.868op/s] or [-25.839%; -25.778%]

scenario:vec_map/get_hit/16

🟥 execution_time [+36.861ns; +37.064ns] or [+17.313%; +17.409%]
🟥 throughput [-11148256.891op/s; -11086054.862op/s] or [-14.834%; -14.752%]

scenario:vec_map/get_hit/64

🟥 execution_time [+1.002µs; +1.006µs] or [+29.629%; +29.739%]
🟥 throughput [-4339016.091op/s; -4322876.302op/s] or [-22.932%; -22.847%]

scenario:vec_map/get_hit/8

🟥 execution_time [+4.610ns; +4.751ns] or [+7.473%; +7.702%]
🟥 throughput [-9302197.428op/s; -9005709.662op/s] or [-7.173%; -6.944%]

scenario:vec_map/get_miss/16

🟩 execution_time [-1.030ns; -0.938ns] or [-9.914%; -9.030%]

scenario:vec_map/get_miss/8

🟥 execution_time [+1.432ns; +1.489ns] or [+23.682%; +24.617%]

scenario:vec_map/iter/128

🟥 execution_time [+8.171ns; +8.338ns] or [+7.860%; +8.021%]
🟥 throughput [-91502402.517op/s; -89693266.126op/s] or [-7.431%; -7.284%]

scenario:vec_map/iter/16

🟥 execution_time [+0.598ns; +0.608ns] or [+4.576%; +4.651%]
🟥 throughput [-54432616.999op/s; -53549900.852op/s] or [-4.446%; -4.374%]

scenario:vec_map/iter/8

🟥 execution_time [+0.546ns; +0.551ns] or [+8.160%; +8.244%]
🟥 throughput [-91170847.961op/s; -90186744.036op/s] or [-7.622%; -7.540%]

Benchmark execution time: 2026-07-30 15:37:00

Comparing candidate commit 9b58363 in PR branch yannham/workspace-deps-phase-4 with baseline commit 9614b20 in branch main.

Found 4 performance improvements and 4 performance regressions! Performance is the same for 159 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 [-13.260ns; -13.113ns] or [-14.252%; -14.094%]

scenario:glob_matcher/ascii_pattern_unicode_subject/wall_time

🟥 execution_time [+5.795ns; +5.862ns] or [+4.122%; +4.169%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/wall_time

🟩 execution_time [-2.465ns; -2.440ns] or [-6.222%; -6.159%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/wall_time

🟩 execution_time [-2.841ns; -2.824ns] or [-6.494%; -6.455%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

🟩 execution_time [-3.483ns; -3.448ns] or [-8.715%; -8.628%]

scenario:profiler_attached/fast_path_system/4096

🟥 execution_time [+8.471ns; +8.626ns] or [+8.842%; +9.004%]

scenario:trace_buffer/4_senders/no_delay

🟥 execution_time [+102.648µs; +134.859µs] or [+4.475%; +5.880%]
🟥 throughput [-90121.173op/s; -68190.718op/s] or [-5.731%; -4.336%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

Move the dev/test and specialized tooling dependencies to workspace-level dependencies: tempfile, clap, criterion, bolero, allocator-api2, chrono, elf and cxx-build. Phase 4 of the workspace migration plan. Version decisions, resolving the pre-existing skew: - tempfile: 3.13 (the highest requirement already in the workspace) - clap: 4.3.21, criterion: 0.5.1, bolero: 0.13.4 - allocator-api2: 0.2.21, chrono: 0.4.38 Per the migration policy, workspace entries carry `default-features = false` and leaf crates opt into the features they need. criterion and tempfile declare a baseline feature set at the workspace level instead, because turning those defaults off would silently degrade behaviour rather than fail to compile: tempfile/getrandom (predictable temp file names without it), criterion/cargo_bench_support+plotters+rayon (`cargo bench` refuses to run without it). clap keeps `default-features = false` at the workspace level with no features listed there, since its default set (help, usage, color, error-context, suggestions) is exactly what the leaf crates want; each of the three clap consumers (tools, libdd-data-pipeline, datadog-profiling-replayer) sets `default-features = true` itself instead of duplicating that list. Cargo.lock only loses chrono's `wasmbind` edge (js-sys, wasm-bindgen), which datadog-sidecar was pulling in via implicit default features; that crate is not built for wasm32. No package is added or removed, so LICENSE-3rdparty.csv is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…er-flare (#2332) # Release proposal for libdd-ffe, libdd-http-client, libdd-tracer-flare and their dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-capabilities **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-capabilities-v3.0.0` ### Commits - fix(telemetry)!: stop sending Connection: close to the Agent (#2286) - feat(capabilities)!: Add streaming to http capabilities (#2251) - feat: added file capability [APMSP-3780] (#2240) - feat: added environment capability [APMSP-3780] (#2239) ## libdd-common **Next version:** `5.1.1` **Semver bump:** `patch` **Tag:** `libdd-common-v5.1.1` ### Commits - feat(telemetry)!: Add Installation signature and AppProduct changes payloads (#2213) - refactor: migrate to workspace dependencies, phase 4 (#2296) - refactor: migrate to workspace dependencies, phase 3 (#2283) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - test: stabilize flaky tests (#2256) - fix(sidecar): don't double-encode file:// telemetry endpoints (#2230) - fix: last new clippy lint (#2221) ## libdd-tinybytes **Next version:** `1.1.2` **Semver bump:** `patch` **Tag:** `libdd-tinybytes-v1.1.2` ### Commits - chore: moving to workspace-level dependencies, phase 2 (#2270) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) ## libdd-trace-protobuf **Next version:** `4.0.1` **Semver bump:** `patch` **Tag:** `libdd-trace-protobuf-v4.0.1` ### Commits - refactor: migrate to workspace dependencies, phase 4 (#2296) - chore: moving to workspace-level dependencies, phase 2 (#2270) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - feat(stats)!: implement additional metric tags in libdd-trace-stats (#2170) ## libdd-capabilities-impl **Next version:** `4.0.0` **Semver bump:** `major` **Tag:** `libdd-capabilities-impl-v4.0.0` ### ⚠️ major bump forced due to: - `libdd-capabilities`: ^2.1.0 → ^3.0.0 ### Commits - feat(telemetry)!: Add Installation signature and AppProduct changes payloads (#2213) - refactor: migrate to workspace dependencies, phase 4 (#2296) - fix(telemetry)!: stop sending Connection: close to the Agent (#2286) - fix(remote-config)!: Expose HttpClientCapability in remote config (#2252) - feat(capabilities)!: Add streaming to http capabilities (#2251) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - feat: added file capability [APMSP-3780] (#2240) - feat(telemetry)!: make telemetry worker wasm-compatible for the TraceExporter (#2172) - feat: added environment capability [APMSP-3780] (#2239) ## libdd-http-client **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-http-client-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. ## libdd-trace-normalization **Next version:** `3.0.1` **Semver bump:** `patch` **Tag:** `libdd-trace-normalization-v3.0.1` ### Commits - refactor: migrate to workspace dependencies, phase 4 (#2296) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) ## libdd-remote-config **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-remote-config-v3.0.0` ### Commits - refactor(rc)!: make conversion from RemoteConfigProduct back and forth generally available (#2325) - fix(wasm)!: finish the WASM port of remote-config (#2315) - refactor: migrate to workspace dependencies, phase 3 (#2283) - feat(rc): Handle expired config status (#2274) - feat(remote-config)!: add AsmRawResponseBody capability (#2278) - chore: moving to workspace-level dependencies, phase 2 (#2270) - fix(remote-config)!: Expose HttpClientCapability in remote config (#2252) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - fix(rc): Make Target fields available again after eaf5ad0 (#2232) - fix: new clippy lints (#2219) ## libdd-trace-utils **Next version:** `10.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-utils-v10.0.0` ### ⚠️ major bump forced due to: - `libdd-capabilities`: ^2.1.0 → ^3.0.0 ### Commits - refactor(rc)!: make conversion from RemoteConfigProduct back and forth generally available (#2325) - fix(libdd-trace-utils): apply SpanLink flags masking when v0.5 json encoding (#2314) - refactor: migrate to workspace dependencies, phase 4 (#2296) - feat(data-pipeline)!: add compression option for agentless export (#2205) - refactor: migrate to workspace dependencies, phase 3 (#2283) - refactor(trace-utils)!: split generic TracerHeaderTags (#2279) - chore(lint): update nightly (#2281) - chore: moving to workspace-level dependencies, phase 2 (#2270) - fix(remote-config)!: Expose HttpClientCapability in remote config (#2252) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - feat(stats)!: implement additional metric tags in libdd-trace-stats (#2170) - feat(trace-utils)!: add v1 decoder (#2174) - feat(trace-utils)!: add encoder v1 to v04 + refactor (#2145) - feat(otlp): add instrumentation scope metadata (#2235) - fix(trace-utils)!: serialize v0.5 span links and events into meta (#980) ## libdd-ffe **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-ffe-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. ## libdd-tracer-flare **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-tracer-flare-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. [APMSP-3780]: https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [APMSP-3780]: https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [APMSP-3780]: https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: hoolioh <107922352+hoolioh@users.noreply.github.com>

github-actions Bot added telemetry mini-agent sidecar common data-pipeline crashtracker sampling labels Jul 29, 2026

yannham force-pushed the yannham/workspace-deps-phase-4 branch from 8477a40 to 7bda4b0 Compare July 30, 2026 09:17

yannham marked this pull request as ready for review July 30, 2026 09:28

yannham requested review from a team as code owners July 30, 2026 09:28

yannham requested review from hoolioh, mabdinur, pavlokhrebto and typotter and removed request for a team July 30, 2026 09:28

hoolioh approved these changes Jul 30, 2026

View reviewed changes

yannham and others added 2 commits July 30, 2026 16:50

chore: update comments in Cargo.toml, use default-features for criterion

9b58363

yannham force-pushed the yannham/workspace-deps-phase-4 branch from 9727c00 to 9b58363 Compare July 30, 2026 14:50

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: waiting mergequeue-status: queued mergequeue-status: in_progress and removed mergequeue-status: waiting mergequeue-status: queued labels Jul 30, 2026

gh-worker-dd-mergequeue-cf854d Bot merged commit 3c4c095 into main Jul 30, 2026
116 checks passed

gh-worker-dd-devflow-36fce6 Bot removed the mergequeue-status: in_progress label Jul 30, 2026

gh-worker-dd-mergequeue-cf854d Bot deleted the yannham/workspace-deps-phase-4 branch July 30, 2026 16:24

gh-worker-dd-devflow-36fce6 Bot added the mergequeue-status: done label Jul 30, 2026

dd-octo-sts Bot mentioned this pull request Aug 7, 2026

chore(release): proposal for libdd-ffe, libdd-http-client, libdd-tracer-flare #2332

Merged

Navigation Menu

Uh oh!

refactor: migrate to workspace dependencies, phase 4 - #2296

refactor: migrate to workspace dependencies, phase 4#2296
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
mainfrom
yannham/workspace-deps-phase-4

yannham commented Jul 29, 2026 •

edited

Loading

Uh oh!

datadog-datadog-prod-us1 Bot commented Jul 29, 2026 •

edited by datadog-datadog-us1-prod Bot

Loading

Uh oh!

dd-octo-sts Bot commented Jul 29, 2026 •

edited

Loading

Uh oh!

pr-commenter Bot commented Jul 29, 2026 •

edited

Loading

Explanation

More details about the CI and significant changes

Explanation

More details about the CI and significant changes

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

yannham commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Motivation

Additional Notes

Three documented deviations from the default-features = false policy

Behaviour changes worth a look

How to test the change?

Uh oh!

datadog-datadog-prod-us1 Bot commented Jul 29, 2026 • edited by datadog-datadog-us1-prod Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dd-octo-sts Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Artifact Size Benchmark Report

Uh oh!

pr-commenter Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Comparison

Explanation

More details about the CI and significant changes

scenario:msgpack_decoder::v05/high_sharing/200

scenario:msgpack_decoder::v05/low_sharing/10000

scenario:msgpack_decoder::v05/low_sharing/200

scenario:msgpack_decoder::v05/low_sharing/2000

scenario:otlp/e2e_json/1x1000

scenario:otlp/encode_json/1x1000

scenario:otlp/encode_protobuf/1x1000

scenario:profile_serialize_compressed_pprof_timestamped_x1000

scenario:profiles_dictionary/profile_string_inserts/threads/1

scenario:vec_map/as_deduped_map/already_deduped/16

scenario:vec_map/as_deduped_map/already_deduped/8

scenario:vec_map/get_hit/128

scenario:vec_map/get_hit/16

scenario:vec_map/get_hit/64

scenario:vec_map/get_hit/8

scenario:vec_map/get_miss/16

scenario:vec_map/get_miss/8

scenario:vec_map/iter/128

scenario:vec_map/iter/16

scenario:vec_map/iter/8

Explanation

More details about the CI and significant changes

scenario:alloc_free/system/4096

scenario:glob_matcher/ascii_pattern_unicode_subject/wall_time

scenario:glob_matcher/ascii_wildcard_backtrack_match/wall_time

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/wall_time

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

scenario:profiler_attached/fast_path_system/4096

scenario:trace_buffer/4_senders/no_delay

Candidate

Baseline

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

yannham commented Jul 29, 2026 •

edited

Loading

Three documented deviations from the `default-features = false` policy

datadog-datadog-prod-us1 Bot commented Jul 29, 2026 •

edited by datadog-datadog-us1-prod Bot

Loading

dd-octo-sts Bot commented Jul 29, 2026 •

edited

Loading

pr-commenter Bot commented Jul 29, 2026 •

edited

Loading