fix(deps): update cargo tracing packages#9818
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: f9bc6d927be49427195a6de6 ✅ AI Style Review — No Changes DetectedNo MDX files were changed in this pull request. Review Log: View detailed log
|
Contributor
|
@renovate[bot], please consider creating a changeset entry in |
renovate
Bot
force-pushed
the
renovate/cargo-tracing-packages
branch
from
July 16, 2026 19:38
45a4bf1 to
c4d713c
Compare
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.
This PR contains the following updates:
0.31→0.320.31→0.320.19→0.200.19→0.200.31→0.320.31→0.320.31→0.320.31→0.320.31→0.320.31→0.320.31→0.320.31→0.320.32→0.33Release Notes
open-telemetry/opentelemetry-rust (opentelemetry)
v0.32.0Compare Source
Released 2026-May-08
BoundCounter<T>andBoundHistogram<T>types that cache resolvedaggregator references for a fixed attribute set. Created via
Counter::bind()and
Histogram::bind(), bound instruments bypass per-call attribute lookup,providing significant performance improvements for hot paths where the same
attributes are used repeatedly. Both types implement
Cloneso a single boundstate can be shared across threads or modules without re-binding. Also adds
the
SyncInstrument::bind()trait method andBoundSyncInstrument<T>traitfor SDK implementors; the trait method has a no-op default so custom
SyncInstrumentimpls degrade gracefully without panicking. Gated behind theexperimental_metrics_bound_instrumentsfeature flag.reservemethod toopentelemetry::propagation::Injectorto hint at the number of elements that will be added to avoid multiple resize operations of the underlying data structure. Has an empty default implementation.SpanBuilder#3227:trace_id,span_id,end_time,status,sampling_resultwith_trace_id,with_span_id,with_end_time,with_status,with_sampling_result#[must_use]attribute toopentelemetry::metrics::AsyncInstrumentBuilderto add compile time warning when.build()is not called on observable instrument builders, preventing silent failures where callbacks are never registered and metrics are never reported.opentelemetry::tracetoopentelemetry_sdk::trace#3277:SamplingDecision,SamplingResultopentelemetry_sdk::traceinstead.backing specification) is now stable and is enabled by default.
3278
tracingevents emitted via theinternal-logsfeatureContext::current()fromDropimplementations triggered byContextGuardcleanup (#3262).open-telemetry/opentelemetry-rust-contrib (opentelemetry-aws)
v0.20.0Released 2026-May-13
Changed
open-telemetry/opentelemetry-rust-contrib (opentelemetry-datadog)
v0.20.0Released 2026-May-13
reqwestfrom 0.12 to 0.13 (required byopentelemetry-http0.32).DatadogPipelineBuilder::build_exporter,install_simple, andinstall_batchnow returnResult<_, opentelemetry_datadog::Error>(previouslyopentelemetry_sdk::trace::TraceError, which was removed upstream in 0.32).open-telemetry/opentelemetry-rust (opentelemetry-http)
v0.32.0Compare Source
Released 2026-May-08
reqwest's crypto backend has changed fromringtoaws-lc-sys.open-telemetry/opentelemetry-rust (opentelemetry-jaeger-propagator)
v0.32.0Compare Source
Released 2026-May-08
opentelemetry-jaeger-propagatorcrate is now deprecated. The Jaeger propagation format is deprecated per the OpenTelemetry specification. Use W3C TraceContext propagation instead. This crate will be removed in a future release.open-telemetry/opentelemetry-rust (opentelemetry-otlp)
v0.32.0Compare Source
Released 2026-May-08
tls-provider-agnosticfeature flag for environments that require a custom crypto backend (e.g., OpenSSL for FIPS compliance). Enables TLS code paths without bundlingringoraws-lc-rs.build()directly onSpanExporterBuilder,MetricExporterBuilder, andLogExporterBuilder(before selecting a transport), which auto-selects the transport based on the
OTEL_EXPORTER_OTLP_PROTOCOLenvironment variable or enabled features.#3394
ExportConfig,HasExportConfig,with_export_config(),HasTonicConfig,HasHttpConfig,TonicConfig, andHttpConfigfrom public API.Use the public
WithExportConfig,WithTonicConfig, andWithHttpConfigtrait methods instead, which remain unchanged.an
https://endpoint is configured but no TLS feature (tls-ringortls-aws-lc) is enabled, instead ofsilently sending unencrypted traffic. When a TLS feature is enabled and an
https://endpoint is used withoutan explicit
.with_tls_config(), a defaultClientTlsConfigis automatically applied.#3182
exporter errors no longer include potentially sensitive server responses
(e.g., authentication tokens echoed back). Error messages returned to SDK
processors contain only the gRPC status code or HTTP status code. Full
details are logged at DEBUG level only.
#3021
grpc-tonicOTLP export fails due to a local misconfiguration. When the returned
tonic::Statuswraps a local transport error (invalid URL, connect failure,DNS), its source chain (e.g.,
"transport error: invalid URI") is appendedto the returned error so SDK processors surface it at ERROR without
requiring DEBUG logging. Server-returned gRPC status messages remain
DEBUG-only to preserve the auth-token leak safeguards from
#3021.
#3331
OTEL_EXPORTER_OTLP_TRACES_PROTOCOL,OTEL_EXPORTER_OTLP_METRICS_PROTOCOL,OTEL_EXPORTER_OTLP_LOGS_PROTOCOL. These allow configuring different transport protocolsper signal type. Signal-specific vars take precedence over generic
OTEL_EXPORTER_OTLP_PROTOCOL.The auto-select
build()method on each exporter builder now respects the full priority chain:signal-specific env var > generic env var > feature-based default.
InvalidConfigwhen gRPC protocolis requested; gRPC transport returns
InvalidConfigwhen an HTTP protocol is requested.Protocol::default()no longer consults theOTEL_EXPORTER_OTLP_PROTOCOLenvironment variable. It now returns only the feature-based default (http-json > http-proto >
grpc-tonic). Protocol resolution from environment variables is handled internally by the
exporter builders. Users who relied on
Protocol::default()to read env vars should useProtocol::from_env()instead.OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCEenvironment variableto configure metrics temporality. Accepted values:
cumulative(default),delta,lowmemory(case-insensitive). Programmatic.with_temporality()overrides the env var.NoHttpClienterror when multiple HTTP client features are enabled by using priority-based selection (reqwest-client>hyper-client>reqwest-blocking-client). #2994internal-logsfeature inopentelemetry-otlpto reduce unnecessary dependencies3191shutdown_with_timeout()when usinggrpc-tonic.tlsfeature in favor of explicittls-ringandtls-aws-lcfeatures.Migration: Replace
tlswithtls-ring(ortls-aws-lc). Users oftls-rootsortls-webpki-rootsmust now also enable one of these.open-telemetry/opentelemetry-rust (opentelemetry-prometheus)
v0.32.0Compare Source
Released 2026-May-08
opentelemetry-prometheusand remove stale discontinuation notices. #3288prometheusdependency requirement.open-telemetry/opentelemetry-rust (opentelemetry-proto)
v0.32.0Compare Source
Released 2026-May-08
schemarsdependency to version 1.0.0.InstrumentationScopeversion and attributes are now preserved when logs have a target set. Previously, setting a log target would discard the scope's version and attributes. (#3276)open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)
v0.32.1Compare Source
Released 2026-Jun-26
v0.32.0Compare Source
Released 2026-May-08
open-telemetry/opentelemetry-rust (opentelemetry-stdout)
v0.32.0Compare Source
Released 2026-May-08
open-telemetry/opentelemetry-rust (opentelemetry-zipkin)
v0.32.0Compare Source
Released 2026-May-08
opentelemetry-zipkincrate is now deprecated. Use the OTLP exporter (opentelemetry-otlp) instead. Zipkin supports native OTLP ingestion. This crate will be removed in a future release.reqwest's crypto backend has changed fromringtoaws-lc-sys.tokio-rs/tracing-opentelemetry (tracing-opentelemetry)
v0.33.0Compare Source
Fixed
Other
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.