Skip to content

chore(release): merge release branch to main (proposal for libdd-library-config (#2042))#2044

Open
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
release/libdd-library-config/20260526-153253
Open

chore(release): merge release branch to main (proposal for libdd-library-config (#2042))#2044
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
release/libdd-library-config/20260526-153253

Conversation

@dd-octo-sts
Copy link
Copy Markdown
Contributor

@dd-octo-sts dd-octo-sts Bot commented May 26, 2026

This PR merges the release branch to main

# Release proposal for libdd-library-config and its dependencies

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

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

### ⚠️ major bump forced due to:

- `libdd-trace-protobuf`: ^2.0.0 → ^3.0.2

### Commits

- feat: add Hash trait to TracerMetadata (#1931)
- feat: add PartialEq and Eq traits to TracerMetadata (#1922)
- chore(otel-process-ctx): migrate from rustix to libc (#1859)
- chore(otel-thread-ctx)!: move otel thread ctx in dedicated crate
(#1855)
- feat!: root_span_id handling in otel thread ctx (#1834)
- refactor(otel-thread-ctx)!: gate behind feature (#1843)
- feat!: extend tracer metadata with thread ctx attrbutes (#1831)
- feat(otel_thread_ctx): thread-level ctx publication (#1791)

---------

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
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 26, 2026

📚 Documentation Check Results

⚠️ 150 documentation warning(s) found

📦 libdd-library-config - 150 warning(s)


Updated: 2026-05-26 16:44:36 UTC | Commit: f0521eb | missing-docs job results

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 26, 2026

🔒 Cargo Deny Results

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

📦 libdd-library-config - 1 error(s)

Show output
error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:47:1
   │
47 │ 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-library-config v2.0.0

advisories FAILED, bans ok, sources ok

Updated: 2026-05-26 16:46:46 UTC | Commit: f0521eb | dependency-check job results

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.77%. Comparing base (dd71a87) to head (d82fa71).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2044      +/-   ##
==========================================
+ Coverage   72.75%   72.77%   +0.01%     
==========================================
  Files         458      458              
  Lines       75827    75827              
==========================================
+ Hits        55168    55182      +14     
+ Misses      20659    20645      -14     
Components Coverage Δ
libdd-crashtracker 65.20% <ø> (ø)
libdd-crashtracker-ffi 36.82% <ø> (ø)
libdd-alloc 98.77% <ø> (ø)
libdd-data-pipeline 85.27% <ø> (ø)
libdd-data-pipeline-ffi 70.51% <ø> (ø)
libdd-common 79.89% <ø> (ø)
libdd-common-ffi 74.41% <ø> (ø)
libdd-telemetry 73.34% <ø> (ø)
libdd-telemetry-ffi 31.36% <ø> (ø)
libdd-dogstatsd-client 82.64% <ø> (ø)
datadog-ipc 76.22% <ø> (ø)
libdd-profiling 81.69% <ø> (ø)
libdd-profiling-ffi 64.79% <ø> (ø)
libdd-sampling 97.46% <ø> (ø)
datadog-sidecar 29.19% <ø> (ø)
datdog-sidecar-ffi 10.17% <ø> (ø)
spawn-worker 48.86% <ø> (ø)
libdd-tinybytes 93.16% <ø> (ø)
libdd-trace-normalization 81.71% <ø> (ø)
libdd-trace-obfuscation 87.30% <ø> (ø)
libdd-trace-protobuf 68.25% <ø> (ø)
libdd-trace-utils 88.83% <ø> (ø)
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-5
Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: d82fa71 | Docs | Datadog PR Page | Give us feedback!

@iunanua iunanua marked this pull request as ready for review May 27, 2026 07:23
@iunanua iunanua requested review from a team as code owners May 27, 2026 07:23
@iunanua iunanua requested review from vpellan and removed request for a team May 27, 2026 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant