Skip to content

chore: prepare crate for publishing - #2466

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
julio/prepare-libdd-data-pipeline-core
Sep 4, 2026
Merged

chore: prepare crate for publishing#2466
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
julio/prepare-libdd-data-pipeline-core

Conversation

@hoolioh

@hoolioh hoolioh commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

Prepare crate for publication.

@hoolioh
hoolioh requested review from a team as code owners September 4, 2026 13:16
@hoolioh
hoolioh force-pushed the julio/prepare-libdd-data-pipeline-core branch from 552f4c8 to 5c3c69a Compare September 4, 2026 13:17
@hoolioh
hoolioh requested a review from a team as a code owner September 4, 2026 13:17
@hoolioh
hoolioh force-pushed the julio/prepare-libdd-data-pipeline-core branch from 5c3c69a to 19ceb98 Compare September 4, 2026 13:17
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Sep 4, 2026 •
edited by datadog-official 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: 77.06% (-0.11%)

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

@dd-octo-sts

dd-octo-sts Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 91.32 MB 91.32 MB +0% (+4.26 KB) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 8.45 MB 8.45 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.38 MB 11.38 MB -0% (-24 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 102.61 MB 102.61 MB -0% (-3.64 KB) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 27.32 MB 27.32 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 96.08 KB 96.08 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 185.42 MB 185.41 MB -0% (-16.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 804.07 MB 803.94 MB --.01% (-135.91 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 9.00 MB 9.00 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 96.08 KB 96.08 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 26.20 MB 26.20 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 52.21 MB 52.21 MB -0% (-28 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 23.82 MB 23.82 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 97.58 KB 97.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 190.44 MB 190.44 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 787.46 MB 786.99 MB --.05% (-480.50 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.96 MB 6.96 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 97.58 KB 97.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 28.18 MB 28.18 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 49.70 MB 49.70 MB +0% (+652 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 81.48 MB 81.48 MB +0% (+4.53 KB) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 9.41 MB 9.41 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 97.21 MB 97.21 MB -0% (-1.55 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.46 MB 11.46 MB +0% (+8 B) 👌

@pr-commenter

pr-commenter Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-09-04 14:01:33

Comparing candidate commit 19ceb98 in PR branch julio/prepare-libdd-data-pipeline-core with baseline commit 48e990d in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 152 metrics, 1 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 ----------------------------------'

Unstable benchmarks

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

scenario:flagevaluation_evp/coalescer/typical/100flags_50users_10fields

  • unstable execution_time [-8.446µs; +11.965µs] or [-4.546%; +6.439%]
Benchmark execution time: 2026-09-04 14:05:34

Comparing candidate commit 19ceb98 in PR branch julio/prepare-libdd-data-pipeline-core with baseline commit 48e990d in branch main.

📊 Benchmarking dashboard

Found 5 performance improvements and 7 performance regressions! Performance is the same for 157 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 [-12.920ns; -12.749ns] or [-13.914%; -13.730%]

scenario:credit_card/is_card_number_no_luhn/ 3782-8224-6310-005

  • 🟩 throughput [+641498.741op/s; +763698.212op/s] or [+4.156%; +4.947%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/wall_time

  • 🟥 execution_time [+1.720ns; +1.742ns] or [+4.667%; +4.726%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

  • 🟥 execution_time [+1.797ns; +1.823ns] or [+4.877%; +4.949%]

scenario:glob_matcher/unicode_exact_match/wall_time

  • 🟩 execution_time [-4.993ns; -4.936ns] or [-6.358%; -6.285%]

scenario:no_profiler/short_circuit/4096

  • 🟩 execution_time [-14.372ns; -14.251ns] or [-13.830%; -13.714%]

scenario:profiler_attached/fast_path_system/256

  • 🟩 execution_time [-2.626ns; -2.543ns] or [-8.950%; -8.669%]

scenario:profiler_attached/slow_path_system/4096

  • 🟥 execution_time [+8.813ns; +8.936ns] or [+5.935%; +6.018%]

scenario:trace_buffer/2_senders/no_delay

  • 🟥 execution_time [+300.164µs; +322.254µs] or [+18.423%; +19.778%]
  • 🟥 throughput [-182879.475op/s; -170635.389op/s] or [-16.543%; -15.435%]

scenario:trace_buffer/4_senders/no_delay

  • 🟥 execution_time [+221.739µs; +237.186µs] or [+6.192%; +6.623%]
  • 🟥 throughput [-62459.460op/s; -58567.891op/s] or [-6.213%; -5.826%]

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 [+514.861%; -514.861%]

scenario:datadog_sample_span/parent_sampled_short_circuit/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+514.808%; -514.838%]

scenario:glob_matcher/ascii_case_insensitive_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+514.900%; -514.878%]

scenario:glob_matcher/ascii_exact_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+516.558%; -515.609%]

scenario:glob_matcher/ascii_exact_miss/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+515.063%; -514.950%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+514.120%; -514.535%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+514.802%; -514.835%]

scenario:glob_matcher/ascii_wildcard_question_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+516.137%; -515.423%]

scenario:glob_matcher/ascii_wildcard_star_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+514.914%; -514.885%]

scenario:glob_matcher/star_short_circuit/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+514.410%; -514.663%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 64ad2ed into main Sep 4, 2026
135 of 137 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the julio/prepare-libdd-data-pipeline-core branch September 4, 2026 14:50
This was referenced Sep 4, 2026
Closed
Closed
Merged
hoolioh added a commit that referenced this pull request Sep 8, 2026
@dd-octo-sts @github-actions @hoolioh
chore(release): proposal for libdd-capabilities-impl, libdd-crashtrac…
7ffbbcb 
…ker, libdd-data-pipeline, li... (#2482)

# Release proposal for libdd-capabilities-impl, libdd-crashtracker,
libdd-data-pipeline, libdd-ddsketch, libdd-ffe, libdd-http-client,
libdd-ipc, libdd-library-config, libdd-live-debugger,
libdd-otel-thread-ctx, libdd-remote-config, libdd-shared-runtime,
libdd-telemetry, libdd-trace-utils, libdd-tracer-flare and their
dependencies

This PR contains version bumps based on public API changes and commits
since last release.


### ⚠️ Crates left out of this proposal affected by its major
bumps

These publishable workspace crates are not part of this release but
their dependency requirement was rewritten on this branch while their
published version still requires the old major. If they are a dependency
on your deployment not including them in the release could result in
duplicate packages or symbol incompatibility.

- `libdd-common` `5.2.0` → `6.0.0` affects: `libdd-profiling`,
`libdd-sampling`
- `libdd-trace-utils` `11.0.0` → `12.0.0` affects: `libdd-sampling`

## libdd-capabilities
**Next version:** `3.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-capabilities-v3.0.1`

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- feat: do not entirely disable connection pooling for periodic
connections (#2440)

## libdd-common
**Next version:** `6.0.0`
**Semver bump:** `major`
**Tag:** `libdd-common-v6.0.0`

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- feat: do not entirely disable connection pooling for periodic
connections (#2440)
- feat(data-pipeline)!: add agentless stats export (#2309)
- feat(data-pipeline): add runtime-independent agentless sending (#2389)
- feat(common)!: add HTTPS_PROXY support for hyper_backend (#2421)

## libdd-ipc-macros
**Next version:** `1.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-ipc-macros-v1.0.1`

### Commits

- feat(sidecar)!: support appsec helper-rust integration with sidecar
(#2310)

## libdd-otel-thread-ctx
**Next version:** `1.1.0`
**Semver bump:** `minor`
**Tag:** `libdd-otel-thread-ctx-v1.1.0`

### Commits

- feat(otel-thread-ctx): add update-and-attach operation (#2443)

## libdd-tinybytes
**Next version:** `1.1.3`
**Semver bump:** `patch`
**Tag:** `libdd-tinybytes-v1.1.3`

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)

## libdd-capabilities-impl
**Next version:** `5.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-impl-v5.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.1.1 → ^6.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- feat: do not entirely disable connection pooling for periodic
connections (#2440)
- feat(data-pipeline): add runtime-independent agentless sending (#2389)

## libdd-http-client
**Next version:** `2.0.0`
**Semver bump:** `major`
**Tag:** `libdd-http-client-v2.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.1.1 → ^6.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- feat(data-pipeline): add runtime-independent agentless sending (#2389)
- feat(common)!: add HTTPS_PROXY support for hyper_backend (#2421)

## libdd-remote-config
**Next version:** `5.0.0`
**Semver bump:** `major`
**Tag:** `libdd-remote-config-v5.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0

### Commits

- fix(remote-config): refresh fetcher identity (#2469)
- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- fix(remote-config): reuse injected sleep capability (#2429)

## libdd-shared-runtime
**Next version:** `4.0.0`
**Semver bump:** `major`
**Tag:** `libdd-shared-runtime-v4.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0

### Commits

- fix(shared-runtime): allow disabling worker fork restart (#2464)

## libdd-trace-utils
**Next version:** `12.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-utils-v12.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0

### Commits

- feat(trace-utils): add v1-native JSON log encoder brick (#2371)
- feat(trace-utils): add v1-native agentless JSON encoder brick (#2370)
- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- fix(trace-stats): read OTel HTTP names for the status and method
dimensions (#2323)
- feat(data-pipeline): emit native trace export telemetry (#2338)
- feat(data-pipeline)!: add agentless stats export (#2309)
- fix(trace-utils): use vec map dedup when serializing (#2422)
- feat(data-pipeline): add runtime-independent agentless sending (#2389)
- fix(compression): align zstd behavior across targets (#2400)
- feat(trace-utils)!: add from owned to SpanText (#2403)

## libdd-ffe
**Next version:** `2.0.0`
**Semver bump:** `major`
**Tag:** `libdd-ffe-v2.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.1.1 → ^6.0.0
- `libdd-remote-config`: ^3.0.0 → ^4.1.0
- `libdd-trace-protobuf`: ^4.0.1 → ^5.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- feat(ffe): support arbitrary semver core parts (#2413)
- feat(ffe)!: send the split serial id on exposure events [EX-3425]
(#2402)
- feat(ffe): expose observeFullEvaluationData config-level FFI getter
(#2373)
- fix(ffe): report rejected flags as parse errors (#2339)
- test: skip/shorten slow miri jobs (#2331)

## libdd-dogstatsd-client
**Next version:** `6.0.0`
**Semver bump:** `major`
**Tag:** `libdd-dogstatsd-client-v6.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)

## libdd-telemetry
**Next version:** `8.0.0`
**Semver bump:** `major`
**Tag:** `libdd-telemetry-v8.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- refactor(telemetry): avoid doing two separate http requests in stop
telemetry (#2435)

## libdd-trace-obfuscation
**Next version:** `8.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-obfuscation-v8.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0
- `libdd-trace-utils`: ^11.0.0 → ^12.0.0

### Commits

- fix(trace-obfuscation): scan all span meta for credit-card obfuscation
(#2472)
- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- feat(data-pipeline)!: Obfuscate v04 spans in agentless context (#2418)

## libdd-tracer-flare
**Next version:** `3.0.0`
**Semver bump:** `major`
**Tag:** `libdd-tracer-flare-v3.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0
- `libdd-trace-utils`: ^11.0.0 → ^12.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)

## libdd-crashtracker
**Next version:** `3.0.0`
**Semver bump:** `major`
**Tag:** `libdd-crashtracker-v3.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- fix(crashtracking): filter out frames above faulting frame (#2428)
- feat(sidecar)!: support appsec helper-rust integration with sidecar
(#2310)
- chore(crashtracking): use RAII remote ptrace API (#2416)
- chore(crashtracking): bump libdd-libunwind-sys to v1.0.3 (#2414)

## libdd-data-pipeline-core
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-data-pipeline-core-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


## libdd-trace-stats
**Next version:** `9.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-stats-v9.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0
- `libdd-trace-obfuscation`: ^7.0.0 → ^8.0.0
- `libdd-trace-utils`: ^11.0.0 → ^12.0.0

### Commits

- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- fix(trace-stats): read OTel HTTP names for the status and method
dimensions (#2323)
- feat(data-pipeline)!: add agentless stats export (#2309)
- feat(trace-utils)!: add from owned to SpanText (#2403)

## libdd-data-pipeline
**Next version:** `10.0.0`
**Semver bump:** `major`
**Tag:** `libdd-data-pipeline-v10.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0
- `libdd-trace-obfuscation`: ^7.0.0 → ^8.0.0
- `libdd-trace-stats`: ^8.0.0 → ^9.0.0
- `libdd-trace-utils`: ^11.0.0 → ^12.0.0

### Commits

- feat(trace-utils): add v1-native JSON log encoder brick (#2371)
- chore: prepare crate for publishing (#2466)
- refactor: migrate HTTP & networking deps to workspace level (phase
4bis) (#2350)
- fix(trace-stats): read OTel HTTP names for the status and method
dimensions (#2323)
- fix(data-pipeline): pass obfuscation config to OTLP stats (#2444)
- feat(data-pipeline): emit native trace export telemetry (#2338)
- feat(data-pipeline): add fork-safe OTLP gRPC trace transport (#2273)
- feat(data-pipeline)!: add agentless stats export (#2309)
- feat(data-pipeline)!: Obfuscate v04 spans in agentless context (#2418)
- feat(data-pipeline): add runtime-independent agentless sending (#2389)
- feat(trace-utils)!: add from owned to SpanText (#2403)

## libdd-ipc
**Next version:** `2.0.0`
**Semver bump:** `major`
**Tag:** `libdd-ipc-v2.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^6.0.0
- `libdd-trace-stats`: ^8.0.0 → ^9.0.0

### Commits

- fix(ipc): drop the signal feature from libdd-ipc (#2431)

## libdd-live-debugger
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-live-debugger-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


[EX-3425]:
https://datadoghq.atlassian.net/browse/EX-3425?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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@paullegranddc paullegranddc paullegranddc approved these changes
@VianneyRuhlmann VianneyRuhlmann VianneyRuhlmann approved these changes

Assignees

No one assigned

Labels

ci-build data-pipeline mergequeue-status: done skip-metadata-check

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hoolioh @paullegranddc @VianneyRuhlmann