chore(release): proposal for libdd-data-pipeline by dd-octo-sts[bot] · Pull Request #2007 · DataDog/libdatadog

dd-octo-sts · 2026-05-18T14:55:38Z

Release proposal for libdd-data-pipeline and its dependencies

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

libdd-dogstatsd-client

Next version: 3.0.0
Semver bump: major
Tag: libdd-dogstatsd-client-v3.0.0

⚠️ major bump forced due to:

libdd-common: ^3.0.2 → ^4.1.0

Commits

fix(crypto): gate libdd-common TLS features in remaining internal crates + add CI guard (fix(crypto): gate libdd-common TLS features in remaining internal crates + add CI guard #1943)

libdd-trace-obfuscation

Next version: 3.0.0
Semver bump: major
Tag: libdd-trace-obfuscation-v3.0.0

⚠️ major bump forced due to:

libdd-common: ^3.0.2 → ^4.1.0
libdd-trace-utils: ^3.0.1 → ^4.0.0

Commits

feat!: integrate obfuscation to the stats exporter [APMSP-2764] (feat!: integrate obfuscation to the stats exporter [APMSP-2764] #1819)
feat!: added regex-lite feature (feat!: added regex-lite feature #1939)
chore: clippy (chore: clippy #1889)
fix(crypto): gate libdd-common TLS features in obfuscation and capabilities-impl (fix(crypto): gate libdd-common TLS features in obfuscation and capabilities-impl #1872)
feat(obfuscation)!: feature parity on span obfuscation [APMSP-2671] (feat(obfuscation)!: feature parity on span obfuscation [APMSP-2671] #1788)
feat(obfuscation/sql): feature parity on sql obfuscation [APMSP-2667] (feat(obfuscation/sql): feature parity on sql obfuscation [APMSP-2667] #1708)

libdd-trace-stats

Next version: 3.0.0
Semver bump: major
Tag: libdd-trace-stats-v3.0.0

⚠️ major bump forced due to:

libdd-trace-utils: ^3.0.1 → ^4.0.0

Commits

perf: pre-compute string messagepack encoding (perf: pre-compute string messagepack encoding #1948)
feat!: integrate obfuscation to the stats exporter [APMSP-2764] (feat!: integrate obfuscation to the stats exporter [APMSP-2764] #1819)
feat(capablities)!: sleep & spawn capabilities (feat(capablities)!: sleep & spawn capabilities #1873)
feat: use ip quantization when aggregating peer tags for trace stats (feat: use ip quantization when aggregating peer tags for trace stats #1944)
fix(crypto): gate libdd-common TLS features in remaining internal crates + add CI guard (fix(crypto): gate libdd-common TLS features in remaining internal crates + add CI guard #1943)
feat(shared_runtime)!: allow worker to be stopped after fork (feat(shared_runtime)!: allow worker to be stopped after fork #1893)
feat(sidecar)!: Add stats computation via SHM (feat(sidecar)!: Add stats computation via SHM #1821)
feat(stats): propagate service source from span meta to client stats payload (feat(stats): propagate service source from span meta to client stats payload #1803)
fix(stats): align with css spec (fix(stats): align with css spec #1790)

libdd-data-pipeline

Next version: 4.0.0
Semver bump: major
Tag: libdd-data-pipeline-v4.0.0

⚠️ major bump forced due to:

libdd-common: ^3.0.2 → ^4.1.0
libdd-telemetry: ^4.0.0 → ^5.0.0
libdd-trace-utils: ^3.0.1 → ^4.0.0

Commits

fix(libdd-telemetry): restore previous Cargo.toml version (fix(libdd-telemetry): restore previous Cargo.toml version #1993)
fix(data-pipeline): remove default-features from of trace-obfuscation (fix(data-pipeline): remove default-features from of trace-obfuscation #1981)
fix(trace_exporter: shared_runtime): unwrap_or being eager is not good (fix(trace_exporter: shared_runtime): unwrap_or being eager is not good #1983)
perf: pre-compute string messagepack encoding (perf: pre-compute string messagepack encoding #1948)
feat!: integrate obfuscation to the stats exporter [APMSP-2764] (feat!: integrate obfuscation to the stats exporter [APMSP-2764] #1819)
feat(capablities)!: sleep & spawn capabilities (feat(capablities)!: sleep & spawn capabilities #1873)
fix(telemetry): avoid trigger loop in telemetry worker (fix(telemetry): avoid trigger loop in telemetry worker #1950)
feat(telemetry)!: include dependencies and integrations in app-extended-heartbeat (feat(telemetry)!: include dependencies and integrations in app-extended-heartbeat #1962)
perf(trace-serializer): pre-allocate serialization buffer (perf(trace-serializer): pre-allocate serialization buffer #1949)
feat!: added regex-lite feature (feat!: added regex-lite feature #1939)
fix(crypto): gate libdd-common TLS features in remaining internal crates + add CI guard (fix(crypto): gate libdd-common TLS features in remaining internal crates + add CI guard #1943)
feat(telemetry): add session id support to trace export (feat(telemetry): add session id support to trace export #1822)
fix(path): missing bench path in data-pipeline (fix(path): missing bench path in data-pipeline #1907)
feat(data-pipeline): port dd-trace-rs trace buffer implementation (feat(data-pipeline): port dd-trace-rs trace buffer implementation #1826)
feat(info_fetcher): add timeout to info fetcher (feat(info_fetcher): add timeout to info fetcher #1890)
feat(shared_runtime)!: allow worker to be stopped after fork (feat(shared_runtime)!: allow worker to be stopped after fork #1893)
feat(sidecar)!: Add stats computation via SHM (feat(sidecar)!: Add stats computation via SHM #1821)
ci(libdd-shared-runtime): downgrade version so publish workflow succeeds (ci(libdd-shared-runtime): downgrade version so publish workflow succeeds #1870)
feat(runtime)!: add shared runtime (feat(runtime)!: add shared runtime #1602)
ci: compilation of libdd-data-pipeline to wasm32 (ci: compilation of libdd-data-pipeline to wasm32 #1830)
feat(capabilities)!: trait architecture http (feat(capabilities)!: trait architecture http #1555)
feat(otel): add support for OTLP trace export (feat(otel): add support for OTLP trace export #1641)
fix(stats): align with css spec (fix(stats): align with css spec #1790)

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

…bumps Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

github-actions · 2026-05-18T14:57:33Z

📚 Documentation Check Results

⚠️ 2549 documentation warning(s) found

📦 `libdd-data-pipeline` - 1032 warning(s)

📦 `libdd-dogstatsd-client` - 166 warning(s)

📦 `libdd-trace-obfuscation` - 656 warning(s)

📦 `libdd-trace-stats` - 695 warning(s)

Updated: 2026-05-18 14:58:01 UTC | Commit: d7d1263 | missing-docs job results

github-actions · 2026-05-18T14:58:55Z

🔒 Cargo Deny Results

⚠️ 17 issue(s) found, showing only errors (advisories, bans, sources)

📦 `libdd-data-pipeline` - 5 error(s)

Show output

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:212:1
    │
212 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── libdd-common v4.1.0
      │   ├── libdd-capabilities-impl v2.0.0
      │   │   ├── libdd-data-pipeline v4.0.0
      │   │   ├── libdd-shared-runtime v1.0.0
      │   │   │   ├── libdd-data-pipeline v4.0.0 (*)
      │   │   │   ├── libdd-telemetry v5.0.0
      │   │   │   │   └── libdd-data-pipeline v4.0.0 (*)
      │   │   │   └── libdd-trace-stats v3.0.0
      │   │   │       └── libdd-data-pipeline v4.0.0 (*)
      │   │   ├── libdd-trace-stats v3.0.0 (*)
      │   │   └── libdd-trace-utils v4.0.0
      │   │       ├── libdd-data-pipeline v4.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v3.0.0
      │   │       │   └── libdd-trace-stats v3.0.0 (*)
      │   │       ├── libdd-trace-stats v3.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v4.0.0 (*)
      │   ├── libdd-data-pipeline v4.0.0 (*)
      │   ├── libdd-dogstatsd-client v3.0.0
      │   │   └── libdd-data-pipeline v4.0.0 (*)
      │   ├── libdd-shared-runtime v1.0.0 (*)
      │   ├── libdd-telemetry v5.0.0 (*)
      │   ├── libdd-trace-obfuscation v3.0.0 (*)
      │   ├── libdd-trace-stats v3.0.0 (*)
      │   └── libdd-trace-utils v4.0.0 (*)
      ├── (dev) libdd-data-pipeline v4.0.0 (*)
      ├── (dev) libdd-trace-normalization v2.0.0
      │   └── libdd-trace-utils v4.0.0 (*)
      ├── (dev) libdd-trace-stats v3.0.0 (*)
      ├── libdd-trace-utils v4.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── libdd-data-pipeline v4.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v4.0.0 (*)

error[vulnerability]: Name constraints for URI names were incorrectly accepted
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:236:1
    │
236 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0098
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
    ├ Name constraints for URI names were ignored and therefore accepted.
      
      Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   ├── libdd-data-pipeline v4.0.0
          │       │   ├── libdd-shared-runtime v1.0.0
          │       │   │   ├── libdd-data-pipeline v4.0.0 (*)
          │       │   │   ├── libdd-telemetry v5.0.0
          │       │   │   │   └── libdd-data-pipeline v4.0.0 (*)
          │       │   │   └── libdd-trace-stats v3.0.0
          │       │   │       └── libdd-data-pipeline v4.0.0 (*)
          │       │   ├── libdd-trace-stats v3.0.0 (*)
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-data-pipeline v4.0.0 (*)
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       │   └── libdd-trace-stats v3.0.0 (*)
          │       │       ├── libdd-trace-stats v3.0.0 (*)
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-data-pipeline v4.0.0 (*)
          │       ├── libdd-dogstatsd-client v3.0.0
          │       │   └── libdd-data-pipeline v4.0.0 (*)
          │       ├── libdd-shared-runtime v1.0.0 (*)
          │       ├── libdd-telemetry v5.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       ├── libdd-trace-stats v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:236:1
    │
236 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0099
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
    ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
      
      This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
      This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   ├── libdd-data-pipeline v4.0.0
          │       │   ├── libdd-shared-runtime v1.0.0
          │       │   │   ├── libdd-data-pipeline v4.0.0 (*)
          │       │   │   ├── libdd-telemetry v5.0.0
          │       │   │   │   └── libdd-data-pipeline v4.0.0 (*)
          │       │   │   └── libdd-trace-stats v3.0.0
          │       │   │       └── libdd-data-pipeline v4.0.0 (*)
          │       │   ├── libdd-trace-stats v3.0.0 (*)
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-data-pipeline v4.0.0 (*)
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       │   └── libdd-trace-stats v3.0.0 (*)
          │       │       ├── libdd-trace-stats v3.0.0 (*)
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-data-pipeline v4.0.0 (*)
          │       ├── libdd-dogstatsd-client v3.0.0
          │       │   └── libdd-data-pipeline v4.0.0 (*)
          │       ├── libdd-shared-runtime v1.0.0 (*)
          │       ├── libdd-telemetry v5.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       ├── libdd-trace-stats v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:236:1
    │
236 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0104
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
    ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
      or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
      `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
      
      This panic is reachable prior to a CRL's signature being verified.
      
      Applications that do not use CRLs are not affected.
      
      Thank you to @tynus3 for the report.
    ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   ├── libdd-data-pipeline v4.0.0
          │       │   ├── libdd-shared-runtime v1.0.0
          │       │   │   ├── libdd-data-pipeline v4.0.0 (*)
          │       │   │   ├── libdd-telemetry v5.0.0
          │       │   │   │   └── libdd-data-pipeline v4.0.0 (*)
          │       │   │   └── libdd-trace-stats v3.0.0
          │       │   │       └── libdd-data-pipeline v4.0.0 (*)
          │       │   ├── libdd-trace-stats v3.0.0 (*)
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-data-pipeline v4.0.0 (*)
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       │   └── libdd-trace-stats v3.0.0 (*)
          │       │       ├── libdd-trace-stats v3.0.0 (*)
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-data-pipeline v4.0.0 (*)
          │       ├── libdd-dogstatsd-client v3.0.0
          │       │   └── libdd-data-pipeline v4.0.0 (*)
          │       ├── libdd-shared-runtime v1.0.0 (*)
          │       ├── libdd-telemetry v5.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       ├── libdd-trace-stats v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Denial of Service via Stack Exhaustion
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:276:1
    │
276 │ time 0.3.41 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0009
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0009
    ├ ## Impact
      
      When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of
      service attack via stack exhaustion is possible. The attack relies on formally deprecated and
      rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary,
      non-malicious input will never encounter this scenario.
      
      ## Patches
      
      A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned
      rather than exhausting the stack.
      
      ## Workarounds
      
      Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of
      the stack consumed would be at most a factor of the length of the input.
    ├ Announcement: https://github.com/time-rs/time/blob/main/CHANGELOG.md#0347-2026-02-05
    ├ Solution: Upgrade to >=0.3.47 (try `cargo update -p time`)
    ├ time v0.3.41
      └── tracing-appender v0.2.3
          └── libdd-log v1.0.0
              └── (dev) libdd-data-pipeline v4.0.0

advisories FAILED, bans ok, sources ok

📦 `libdd-dogstatsd-client` - 4 error(s)

Show output

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:66:1
   │
66 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
   │
   ├ ID: RUSTSEC-2026-0097
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
   ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
     
     - The `log` and `thread_rng` features are enabled
     - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
     - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
     - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
     - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
     
     `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
   ├ Announcement: https://github.com/rust-random/rand/pull/1763
   ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
   ├ rand v0.8.5
     └── (dev) libdd-common v4.1.0
         └── libdd-dogstatsd-client v3.0.0

error[vulnerability]: Name constraints for URI names were incorrectly accepted
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:77:1
   │
77 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0098
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
   ├ Name constraints for URI names were ignored and therefore accepted.
     
     Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
     
     Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
     
     This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
   ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
   ├ rustls-webpki v0.103.10
     └── rustls v0.23.37
         ├── hyper-rustls v0.27.7
         │   └── libdd-common v4.1.0
         │       └── libdd-dogstatsd-client v3.0.0
         ├── libdd-common v4.1.0 (*)
         └── tokio-rustls v0.26.0
             ├── hyper-rustls v0.27.7 (*)
             └── libdd-common v4.1.0 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:77:1
   │
77 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0099
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
   ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
     
     This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
     This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
     
     Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
     
     This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
   ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
   ├ rustls-webpki v0.103.10
     └── rustls v0.23.37
         ├── hyper-rustls v0.27.7
         │   └── libdd-common v4.1.0
         │       └── libdd-dogstatsd-client v3.0.0
         ├── libdd-common v4.1.0 (*)
         └── tokio-rustls v0.26.0
             ├── hyper-rustls v0.27.7 (*)
             └── libdd-common v4.1.0 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:77:1
   │
77 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0104
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
   ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
     or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
     `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
     
     This panic is reachable prior to a CRL's signature being verified.
     
     Applications that do not use CRLs are not affected.
     
     Thank you to @tynus3 for the report.
   ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
   ├ rustls-webpki v0.103.10
     └── rustls v0.23.37
         ├── hyper-rustls v0.27.7
         │   └── libdd-common v4.1.0
         │       └── libdd-dogstatsd-client v3.0.0
         ├── libdd-common v4.1.0 (*)
         └── tokio-rustls v0.26.0
             ├── hyper-rustls v0.27.7 (*)
             └── libdd-common v4.1.0 (*)

advisories FAILED, bans ok, sources ok

📦 `libdd-trace-obfuscation` - 4 error(s)

Show output

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:182:1
    │
182 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v4.1.0
      │   ├── libdd-capabilities-impl v2.0.0
      │   │   └── libdd-trace-utils v4.0.0
      │   │       ├── libdd-trace-obfuscation v3.0.0
      │   │       └── (dev) libdd-trace-utils v4.0.0 (*)
      │   ├── libdd-trace-obfuscation v3.0.0 (*)
      │   └── libdd-trace-utils v4.0.0 (*)
      ├── (dev) libdd-trace-normalization v2.0.0
      │   └── libdd-trace-utils v4.0.0 (*)
      ├── libdd-trace-utils v4.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v4.0.0 (*)

error[vulnerability]: Name constraints for URI names were incorrectly accepted
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:206:1
    │
206 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0098
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
    ├ Name constraints for URI names were ignored and therefore accepted.
      
      Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:206:1
    │
206 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0099
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
    ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
      
      This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
      This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:206:1
    │
206 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0104
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
    ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
      or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
      `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
      
      This panic is reachable prior to a CRL's signature being verified.
      
      Applications that do not use CRLs are not affected.
      
      Thank you to @tynus3 for the report.
    ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

advisories FAILED, bans ok, sources ok

📦 `libdd-trace-stats` - 4 error(s)

Show output

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:189:1
    │
189 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v4.1.0
      │   ├── libdd-capabilities-impl v2.0.0
      │   │   ├── libdd-shared-runtime v1.0.0
      │   │   │   └── libdd-trace-stats v3.0.0
      │   │   ├── libdd-trace-stats v3.0.0 (*)
      │   │   └── libdd-trace-utils v4.0.0
      │   │       ├── libdd-trace-obfuscation v3.0.0
      │   │       │   └── libdd-trace-stats v3.0.0 (*)
      │   │       ├── libdd-trace-stats v3.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v4.0.0 (*)
      │   ├── libdd-shared-runtime v1.0.0 (*)
      │   ├── libdd-trace-obfuscation v3.0.0 (*)
      │   ├── libdd-trace-stats v3.0.0 (*)
      │   └── libdd-trace-utils v4.0.0 (*)
      ├── (dev) libdd-trace-normalization v2.0.0
      │   └── libdd-trace-utils v4.0.0 (*)
      ├── (dev) libdd-trace-stats v3.0.0 (*)
      ├── libdd-trace-utils v4.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v4.0.0 (*)

error[vulnerability]: Name constraints for URI names were incorrectly accepted
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:213:1
    │
213 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0098
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
    ├ Name constraints for URI names were ignored and therefore accepted.
      
      Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   ├── libdd-shared-runtime v1.0.0
          │       │   │   └── libdd-trace-stats v3.0.0
          │       │   ├── libdd-trace-stats v3.0.0 (*)
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       │   └── libdd-trace-stats v3.0.0 (*)
          │       │       ├── libdd-trace-stats v3.0.0 (*)
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-shared-runtime v1.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       ├── libdd-trace-stats v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:213:1
    │
213 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0099
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
    ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
      
      This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
      This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   ├── libdd-shared-runtime v1.0.0
          │       │   │   └── libdd-trace-stats v3.0.0
          │       │   ├── libdd-trace-stats v3.0.0 (*)
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       │   └── libdd-trace-stats v3.0.0 (*)
          │       │       ├── libdd-trace-stats v3.0.0 (*)
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-shared-runtime v1.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       ├── libdd-trace-stats v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:213:1
    │
213 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0104
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
    ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
      or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
      `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
      
      This panic is reachable prior to a CRL's signature being verified.
      
      Applications that do not use CRLs are not affected.
      
      Thank you to @tynus3 for the report.
    ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.1.0
          │       ├── libdd-capabilities-impl v2.0.0
          │       │   ├── libdd-shared-runtime v1.0.0
          │       │   │   └── libdd-trace-stats v3.0.0
          │       │   ├── libdd-trace-stats v3.0.0 (*)
          │       │   └── libdd-trace-utils v4.0.0
          │       │       ├── libdd-trace-obfuscation v3.0.0
          │       │       │   └── libdd-trace-stats v3.0.0 (*)
          │       │       ├── libdd-trace-stats v3.0.0 (*)
          │       │       └── (dev) libdd-trace-utils v4.0.0 (*)
          │       ├── libdd-shared-runtime v1.0.0 (*)
          │       ├── libdd-trace-obfuscation v3.0.0 (*)
          │       ├── libdd-trace-stats v3.0.0 (*)
          │       └── libdd-trace-utils v4.0.0 (*)
          ├── libdd-common v4.1.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.1.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-05-18 14:59:42 UTC | Commit: d7d1263 | dependency-check job results

codecov-commenter · 2026-05-18T15:12:00Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.71%. Comparing base (fef1801) to head (175cdaa).

Additional details and impacted files

@@                               Coverage Diff                               @@
##           release/libdd-data-pipeline/20260518-144622    #2007      +/-   ##
===============================================================================
+ Coverage                                        72.70%   72.71%   +0.01%     
===============================================================================
  Files                                              452      452              
  Lines                                            74845    74845              
===============================================================================
+ Hits                                             54417    54425       +8     
+ Misses                                           20428    20420       -8

Components	Coverage Δ
libdd-crashtracker	`65.31% <ø> (+0.01%)`	⬆️
libdd-crashtracker-ffi	`37.56% <ø> (ø)`
libdd-alloc	`98.77% <ø> (ø)`
libdd-data-pipeline	`86.50% <ø> (+0.49%)`	⬆️
libdd-data-pipeline-ffi	`73.93% <ø> (+2.88%)`	⬆️
libdd-common	`79.81% <ø> (ø)`
libdd-common-ffi	`74.41% <ø> (ø)`
libdd-telemetry	`73.40% <ø> (+0.05%)`	⬆️
libdd-telemetry-ffi	`31.36% <ø> (ø)`
libdd-dogstatsd-client	`82.64% <ø> (ø)`
datadog-ipc	`76.22% <ø> (ø)`
libdd-profiling	`81.60% <ø> (+0.01%)`	⬆️
libdd-profiling-ffi	`64.51% <ø> (ø)`
libdd-sampling	`97.46% <ø> (ø)`
datadog-sidecar	`28.87% <ø> (-0.35%)`	⬇️
datdog-sidecar-ffi	`8.56% <ø> (-1.70%)`	⬇️
spawn-worker	`48.86% <ø> (ø)`
libdd-tinybytes	`93.16% <ø> (ø)`
libdd-trace-normalization	`81.71% <ø> (ø)`
libdd-trace-obfuscation	`87.39% <ø> (ø)`
libdd-trace-protobuf	`68.25% <ø> (ø)`
libdd-trace-utils	`89.59% <ø> (ø)`
libdd-tracer-flare	`86.88% <ø> (ø)`
libdd-log	`74.83% <ø> (ø)`

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

datadog-prod-us1-3 · 2026-05-18T15:15:11Z

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 72.72% (+0.01%)

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

🔗 Commit SHA: 175cdaa | Docs | Datadog PR Page | Give us feedback!}

dd-octo-sts · 2026-05-18T15:23:41Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	81.83 MB	81.83 MB	+0% (+1.38 KB) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	7.57 MB	7.57 MB	0% (0 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	98.03 MB	98.03 MB	+0% (+8.41 KB) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.01 MB	10.01 MB	+0% (+752 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	24.48 MB	24.49 MB	+.02% (+6.50 KB) 🔍
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	79.87 KB	79.87 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	180.22 MB	180.25 MB	+.01% (+32.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	914.05 MB	914.06 MB	+0% (+4.31 KB) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	7.73 MB	7.73 MB	--.01% (-1.50 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	79.87 KB	79.87 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	23.16 MB	23.16 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	45.36 MB	45.35 MB	--.01% (-5.36 KB) 💪

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	21.10 MB	21.10 MB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	81.11 KB	81.11 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	184.44 MB	184.44 MB	-0% (-8.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	900.32 MB	900.34 MB	+0% (+22.37 KB) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	5.99 MB	5.99 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	81.11 KB	81.11 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	24.80 MB	24.80 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	42.85 MB	42.85 MB	+0% (+752 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	72.93 MB	72.93 MB	-0% (-616 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	8.42 MB	8.42 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	90.71 MB	90.71 MB	-0% (-8.25 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.06 MB	10.06 MB	-0% (-480 B) 👌

…-pipeline (#2007)) (#2009) This PR merges the release branch to main Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

github-actions Bot and others added 9 commits May 18, 2026 14:54

chore: Release

baf1d1a

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore: Release

1da614e

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore: Release

b3ec6c3

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore: Release

6e790b3

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore(release): update version for libdd-dogstatsd-client with major …

32cf884

…bumps Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore(release): update CHANGELOG.md for libdd-dogstatsd-client

a800ba1

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore(release): update CHANGELOG.md for libdd-trace-obfuscation

4ec4756

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore(release): update CHANGELOG.md for libdd-trace-stats

edb230b

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

chore(release): update CHANGELOG.md for libdd-data-pipeline

175cdaa

Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

dd-octo-sts Bot added skip-changelog-check skip-metadata-check release-proposal This is a release proposal PR skip-pr-title-semver-check labels May 18, 2026

github-actions Bot added mini-agent data-pipeline labels May 18, 2026

iunanua marked this pull request as ready for review May 18, 2026 15:40

iunanua requested review from a team as code owners May 18, 2026 15:40

iunanua merged commit 1758493 into release/libdd-data-pipeline/20260518-144622 May 18, 2026
108 checks passed

iunanua deleted the release-proposal/libdd-data-pipeline/20260518-144622 branch May 18, 2026 15:41

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(release): proposal for libdd-data-pipeline#2007

chore(release): proposal for libdd-data-pipeline#2007
iunanua merged 9 commits into
release/libdd-data-pipeline/20260518-144622from
release-proposal/libdd-data-pipeline/20260518-144622

dd-octo-sts Bot commented May 18, 2026

Uh oh!

github-actions Bot commented May 18, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 18, 2026 •

edited

Loading

Uh oh!

codecov-commenter commented May 18, 2026

Uh oh!

datadog-prod-us1-3 Bot commented May 18, 2026 •

edited

Loading

Uh oh!

dd-octo-sts Bot commented May 18, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

dd-octo-sts Bot commented May 18, 2026

Release proposal for libdd-data-pipeline and its dependencies

libdd-dogstatsd-client

⚠️ major bump forced due to:

Commits

libdd-trace-obfuscation

⚠️ major bump forced due to:

Commits

libdd-trace-stats

⚠️ major bump forced due to:

Commits

libdd-data-pipeline

⚠️ major bump forced due to:

Commits

Uh oh!

github-actions Bot commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📚 Documentation Check Results

📦 libdd-data-pipeline - 1032 warning(s)

📦 libdd-dogstatsd-client - 166 warning(s)

📦 libdd-trace-obfuscation - 656 warning(s)

📦 libdd-trace-stats - 695 warning(s)

Uh oh!

github-actions Bot commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Cargo Deny Results

📦 libdd-data-pipeline - 5 error(s)

📦 libdd-dogstatsd-client - 4 error(s)

📦 libdd-trace-obfuscation - 4 error(s)

📦 libdd-trace-stats - 4 error(s)

Uh oh!

codecov-commenter commented May 18, 2026

Codecov Report

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Artifact Size Benchmark Report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

github-actions Bot commented May 18, 2026 •

edited

Loading

📦 `libdd-data-pipeline` - 1032 warning(s)

📦 `libdd-dogstatsd-client` - 166 warning(s)

📦 `libdd-trace-obfuscation` - 656 warning(s)

📦 `libdd-trace-stats` - 695 warning(s)

github-actions Bot commented May 18, 2026 •

edited

Loading

📦 `libdd-data-pipeline` - 5 error(s)

📦 `libdd-dogstatsd-client` - 4 error(s)

📦 `libdd-trace-obfuscation` - 4 error(s)

📦 `libdd-trace-stats` - 4 error(s)

datadog-prod-us1-3 Bot commented May 18, 2026 •

edited

Loading

dd-octo-sts Bot commented May 18, 2026 •

edited

Loading