[SLES-2907] chore(deps): bump dd-trace-rs to datadog-opentelemetry-v0.5.0#1302
Draft
litianningdatadog wants to merge 3 commits into
Draft
[SLES-2907] chore(deps): bump dd-trace-rs to datadog-opentelemetry-v0.5.0#1302litianningdatadog wants to merge 3 commits into
litianningdatadog wants to merge 3 commits into
Conversation
….5.0 Bumps datadog-opentelemetry from f51cefc4 (pre-v0.3.0) to 50bfea87 (v0.5.0), adding features = ["_unstable_propagation"] since the propagation module bottlecap uses is now feature-gated upstream. Bumps dogstatsd/datadog-fips/datadog-agent-config to the serverless-components commit that carries the matching dd-trace-rs pin (DataDog/serverless-components#144, currently unmerged - rev will be amended to the merged SHA before this PR leaves draft). v0.5.0 adds native B3 (single and multi-header) propagation support, fixing "Unknown trace propagation style: 'b3multi'" errors reported by customers (SLES-2907). Code changes required by the bump: - src/config/propagation_wrapper.rs: implement the new required PropagationConfig::trace_propagation_behavior_extract method (hardcoded to Continue, matching prior implicit behavior; bottlecap does not expose DD_TRACE_PROPAGATION_BEHAVIOR_EXTRACT). - src/traces/propagation/mod.rs: DatadogCompositePropagator::extract now returns ExtractResult instead of Option<SpanContext>; adapted the wrapper to match on it. - src/lifecycle/invocation/triggers/step_function_event.rs: the constants module re-export was removed upstream (moved to libdd-sampling internally); hardcoded the one test-only usage of SAMPLING_DECISION_MAKER_TAG_KEY ("_dd.p.dm") instead of adding a new dependency for it. Verified: cargo check/clippy/fmt clean, cargo test --lib 530/530 pass, dd-rust-license-tool check passes. --features fips hits a pre-existing local-macOS-only dylib issue in libddwaf-sys, confirmed identical on unmodified main.
|
This was referenced Jul 13, 2026
Merged
DataDog/serverless-components#144 merged as 56779dec9f4c9bcc48abcc9833ca4fa4b9d8d627. Re-pin dogstatsd/datadog-fips/datadog-agent-config to that commit instead of the pre-merge draft SHA, and regenerate Cargo.lock. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Bumps
datadog-opentelemetry(dd-trace-rs) fromf51cefc4(pre-v0.3.0) to50bfea87(datadog-opentelemetry-v0.5.0), addingfeatures = ["_unstable_propagation"]since thepropagationmodulebottlecap uses is now feature-gated upstream (was unconditionally public at
our old pin).
Also bumps
dogstatsd/datadog-fips/datadog-agent-configto theserverless-componentscommit that carries the matching dd-trace-rs pin —DataDog/serverless-components#144,
currently unmerged (draft). This PR is opened as draft for the same
reason: the
revfor those three deps will be amended to the merged SHAbefore this leaves draft.
v0.5.0 adds native B3 (single- and multi-header) trace propagation support,
fixing
Failed to parse trace propagation style: Unknown trace propagation style: 'b3multi', ignoringerrors reported by a customer — seeSLES-2907.
Code changes required by the bump
src/config/propagation_wrapper.rs— implements the new requiredPropagationConfig::trace_propagation_behavior_extractmethod (hardcodedto
Continue, matching prior implicit behavior; bottlecap doesn't exposeDD_TRACE_PROPAGATION_BEHAVIOR_EXTRACT).src/traces/propagation/mod.rs—DatadogCompositePropagator::extractnowreturns
ExtractResultinstead ofOption<SpanContext>; adapted thewrapper to match on it (
Continue(ctx) -> Some(ctx), everything else ->None, preserving current behavior).src/lifecycle/invocation/triggers/step_function_event.rs— thedatadog_opentelemetry::constantsre-export was removed upstream (movedto
libdd-samplinginternally); hardcoded the one test-only usage ofSAMPLING_DECISION_MAKER_TAG_KEY("_dd.p.dm") rather than adding a newdependency for it.
Testing
cargo check --all-targets— cleancargo clippy --all-targets -- -D warnings— cleancargo fmt --all -- --check— cleancargo test --lib— 530/530 passdd-rust-license-tool check— passescargo tree --duplicates— no newdatadog-opentelemetry/tonic/prostduplication;
opentelemetry/opentelemetry_sdk/-semantic-conventionsdo pick up a new duplicate version (0.31 direct vs. 0.32 via dd-trace-rs) —
non-blocking, binary-size-only, bottlecap never shares those types across
the
datadog_opentelemetryboundary--features fipshits a pre-existing local-macOS-only dylib loading issuein
libddwaf-sys, confirmed identical on unmodifiedmain(needsLinux/CI, unrelated to this change)
Dependency graph:
