Skip to content

fix(deps): update cargo tracing packages#9818

Open
renovate[bot] wants to merge 1 commit into
devfrom
renovate/cargo-tracing-packages
Open

fix(deps): update cargo tracing packages#9818
renovate[bot] wants to merge 1 commit into
devfrom
renovate/cargo-tracing-packages

Conversation

@renovate

@renovate renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
opentelemetry (source) dev-dependencies minor 0.310.32
opentelemetry (source) dependencies minor 0.310.32
opentelemetry-aws (source) dependencies minor 0.190.20
opentelemetry-datadog (source) dev-dependencies minor 0.190.20
opentelemetry-http (source) dependencies minor 0.310.32
opentelemetry-jaeger-propagator (source) dependencies minor 0.310.32
opentelemetry-otlp (source) dependencies minor 0.310.32
opentelemetry-prometheus (source) dependencies minor 0.310.32
opentelemetry-proto (source) dev-dependencies minor 0.310.32
opentelemetry-semantic-conventions (source) dependencies minor 0.310.32
opentelemetry-stdout (source) dev-dependencies minor 0.310.32
opentelemetry-zipkin (source) dependencies minor 0.310.32
tracing-opentelemetry dev-dependencies minor 0.320.33

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.32.0

Compare Source

Released 2026-May-08

  • Added BoundCounter<T> and BoundHistogram<T> types that cache resolved
    aggregator 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 Clone so a single bound
    state can be shared across threads or modules without re-binding. Also adds
    the SyncInstrument::bind() trait method and BoundSyncInstrument<T> trait
    for SDK implementors; the trait method has a no-op default so custom
    SyncInstrument impls degrade gracefully without panicking. Gated behind the
    experimental_metrics_bound_instruments feature flag.
  • Add reserve method to opentelemetry::propagation::Injector to 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.
  • Breaking Removed the following public fields and methods from the SpanBuilder #​3227:
    • trace_id, span_id, end_time, status, sampling_result
    • with_trace_id, with_span_id, with_end_time, with_status, with_sampling_result
  • Added #[must_use] attribute to opentelemetry::metrics::AsyncInstrumentBuilder to 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.
  • Breaking Moved the following SDK sampling types from opentelemetry::trace to opentelemetry_sdk::trace #​3277:
    • SamplingDecision, SamplingResult
    • These types are SDK implementation details and should be imported from opentelemetry_sdk::trace instead.
  • "spec_unstable_logs_enabled" feature flag is removed. The capability (and the
    backing specification) is now stable and is enabled by default.
    3278
  • Remove the empty "message" field from tracing events emitted via the internal-logs feature
  • Fix panic when calling Context::current() from Drop implementations triggered by ContextGuard cleanup (#​3262).
open-telemetry/opentelemetry-rust-contrib (opentelemetry-aws)

v0.20.0

Released 2026-May-13

Changed
  • Bump opentelemetry and opentelemetry_sdk versions to 0.32.0
open-telemetry/opentelemetry-rust-contrib (opentelemetry-datadog)

v0.20.0

Released 2026-May-13

  • Bump opentelemetry and opentelemetry_sdk versions to 0.32
  • Bump opentelemetry-http and opentelemetry-semantic-conventions versions to 0.32
  • Bump reqwest from 0.12 to 0.13 (required by opentelemetry-http 0.32).
  • Breaking DatadogPipelineBuilder::build_exporter, install_simple, and
    install_batch now return Result<_, opentelemetry_datadog::Error> (previously
    opentelemetry_sdk::trace::TraceError, which was removed upstream in 0.32).
open-telemetry/opentelemetry-rust (opentelemetry-http)

v0.32.0

Compare Source

Released 2026-May-08

  • reqwest's crypto backend has changed from ring to aws-lc-sys.
open-telemetry/opentelemetry-rust (opentelemetry-jaeger-propagator)

v0.32.0

Compare Source

Released 2026-May-08

  • Deprecated: The opentelemetry-jaeger-propagator crate 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.0

Compare Source

Released 2026-May-08

  • Add tls-provider-agnostic feature flag for environments that require a custom crypto backend (e.g., OpenSSL for FIPS compliance). Enables TLS code paths without bundling ring or aws-lc-rs.
  • Add build() directly on SpanExporterBuilder, MetricExporterBuilder, and LogExporterBuilder
    (before selecting a transport), which auto-selects the transport based on the
    OTEL_EXPORTER_OTLP_PROTOCOL environment variable or enabled features.
    #​3394
  • Breaking Removed ExportConfig, HasExportConfig, with_export_config(), HasTonicConfig, HasHttpConfig, TonicConfig, and HttpConfig from public API.
    Use the public WithExportConfig, WithTonicConfig, and WithHttpConfig trait methods instead, which remain unchanged.
  • The gRPC/tonic OTLP exporter's build method now returns an error for all signals (traces, metrics, logs) when
    an https:// endpoint is configured but no TLS feature (tls-ring or tls-aws-lc) is enabled, instead of
    silently sending unencrypted traffic. When a TLS feature is enabled and an https:// endpoint is used without
    an explicit .with_tls_config(), a default ClientTlsConfig is automatically applied.
    #​3182
  • Prevent auth tokens from leaking in export error messages. gRPC and HTTP
    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
  • Surface pre-flight transport error details at ERROR level when grpc-tonic
    OTLP export fails due to a local misconfiguration. When the returned
    tonic::Status wraps a local transport error (invalid URL, connect failure,
    DNS), its source chain (e.g., "transport error: invalid URI") is appended
    to 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
  • Add support for per-signal protocol environment variables:
    OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, OTEL_EXPORTER_OTLP_METRICS_PROTOCOL,
    OTEL_EXPORTER_OTLP_LOGS_PROTOCOL. These allow configuring different transport protocols
    per 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.
  • Transport/protocol mismatch validation: HTTP transport returns InvalidConfig when gRPC protocol
    is requested; gRPC transport returns InvalidConfig when an HTTP protocol is requested.
  • Breaking: Protocol::default() no longer consults the OTEL_EXPORTER_OTLP_PROTOCOL
    environment 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 use
    Protocol::from_env() instead.
  • Add support for OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE environment variable
    to configure metrics temporality. Accepted values: cumulative (default), delta,
    lowmemory (case-insensitive). Programmatic .with_temporality() overrides the env var.
  • Fix NoHttpClient error when multiple HTTP client features are enabled by using priority-based selection (reqwest-client > hyper-client > reqwest-blocking-client). #​2994
  • Add partial success response handling for OTLP exporters (traces, metrics, logs) per OTLP spec. Exporters now log warnings when the server returns partial success responses with rejected items and error messages. #​865
  • Refactor internal-logs feature in opentelemetry-otlp to reduce unnecessary dependencies3191
  • Fixed [#​2777](https://github.com/open-telemetry/opentelemetry rust/issues/2777) to properly handle shutdown_with_timeout() when using grpc-tonic.
  • Deprecate tls feature in favor of explicit tls-ring and tls-aws-lc features.
    Migration: Replace tls with tls-ring (or tls-aws-lc). Users of tls-roots or tls-webpki-roots must now also enable one of these.
  • Prevent logging of header values in OTLP tonic exporter #​3465
open-telemetry/opentelemetry-rust (opentelemetry-prometheus)

v0.32.0

Compare Source

Released 2026-May-08

  • Un-deprecate opentelemetry-prometheus and remove stale discontinuation notices. #​3288
  • Set MSRV to 1.81.0 to match the prometheus dependency requirement.
open-telemetry/opentelemetry-rust (opentelemetry-proto)

v0.32.0

Compare Source

Released 2026-May-08

  • Update proto definitions to v1.10.0.
  • Updated schemars dependency to version 1.0.0.
  • Bug fix: InstrumentationScope version 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.1

Compare Source

Released 2026-Jun-26

  • Update to v1.42.0 of the semantic conventions.

v0.32.0

Compare Source

Released 2026-May-08

open-telemetry/opentelemetry-rust (opentelemetry-stdout)

v0.32.0

Compare Source

Released 2026-May-08

  • ExponentialHistogram supported in stdout
open-telemetry/opentelemetry-rust (opentelemetry-zipkin)

v0.32.0

Compare Source

Released 2026-May-08

  • Deprecated: The opentelemetry-zipkin crate 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 from ring to aws-lc-sys.
tokio-rs/tracing-opentelemetry (tracing-opentelemetry)

v0.33.0

Compare Source

Fixed
  • [breaking] avoid deadlock when entering a span (#​251)
Other

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner July 16, 2026 13:10
@renovate
renovate Bot enabled auto-merge (squash) July 16, 2026 13:10
@apollo-librarian

apollo-librarian Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: f9bc6d927be49427195a6de6
Build Logs: View logs


✅ AI Style Review — No Changes Detected

No MDX files were changed in this pull request.

Review Log: View detailed log

This review is AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.

@github-actions

Copy link
Copy Markdown
Contributor

@renovate[bot], please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

@renovate
renovate Bot force-pushed the renovate/cargo-tracing-packages branch from 45a4bf1 to c4d713c Compare July 16, 2026 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants