continuwuation/continuwuity
continuwuation/continuwuity
Watch
18
115
Fork
You've already forked continuwuity
 132
Code Issues 137 Pull requests 44 Releases 42 Packages 3 Activity Actions

chore(deps): update opentelemetry-rust monorepo to 0.33.0 - autoclosed #2267

Closed
renovate wants to merge 1 commit from renovate/opentelemetry-rust-monorepo into main
pull from: renovate/opentelemetry-rust-monorepo
merge into: continuwuation:main
Conversation 0 Commits 1 Files changed 2 +33 -19
renovate commented 2026-09-19 05:03:05 +00:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
opentelemetry (source) workspace.dependencies minor 0.32.0 → 0.33.0
opentelemetry-otlp (source) workspace.dependencies minor 0.32.0 → 0.33.0
opentelemetry_sdk (source) workspace.dependencies minor 0.32.0 → 0.33.0

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.33.1

Compare Source

Released 2026-Oct-08

  • Fix a panic when a value stored with Context::with_value() calls
    Context::current() from its Drop implementation.
  • Expand tracing documentation on async context propagation and child spans
    (#​828).
  • Document the panic contract for observable metric callbacks (Callback and
    AsyncInstrumentBuilder::with_callback).
    (#​3640)
  • Fix TraceState::from_str rejecting valid optional whitespace around list members.
    (#​3757)

v0.33.0

Compare Source

Released 2026-Sep-18

  • Fix TraceState accepting more than the 32 list-members the W3C trace-context
    specification allows. from_str, from_key_value and insert now keep at most
    32, dropping members from the end of the list as the specification prescribes, so
    neither a parsed nor a locally built tracestate can exceed the limit.
  • Added experimental support for a global context event observer. A
    ContextObserver can be registered via GlobalContextObserver::set to be
    notified of context transitions through the on_context_enter and
    on_context_exit callbacks. This feature is primarily intended to publish a
    different view of the current context (the ObserverContextView) through
    alternative channels that let external readers (e.g. an eBPF profiler) track
    the current context. See the associated
    OTEP.
    Gated behind the experimental_context_observer feature flag.
  • otel_info!, otel_warn!, otel_debug!, and otel_error! macros now accept quoted-key fields
    (e.g. "otel.component.type" = "value") for dotted attribute names.
  • Added BoundGauge<T> and BoundUpDownCounter<T> types (and the
    corresponding Gauge::bind() / UpDownCounter::bind() methods), completing
    the experimental bound-instrument API across all sync instruments
    (Counter, UpDownCounter, Histogram, Gauge). Gated behind the
    experimental_metrics_bound_instruments feature flag.
open-telemetry/opentelemetry-rust (opentelemetry-otlp)

v0.33.1

Compare Source

Released 2026-Oct-08

  • Declare the OTLP exporters for Logs and Metrics stable after the 0.33.0 release-candidate period. Tracing remains in beta.
  • Update OpenTelemetry dependencies to 0.33.1, including SDK fixes and OTLP/JSON interoperability fixes in opentelemetry-proto.

v0.33.0

Compare Source

Released 2026-Sep-18

  • Exporter builder usage and environment configuration are unchanged.
    Breaking for callers parsing compression strings: Compression::from_str
    (including .parse::<Compression>()) now returns the opaque ParseConfigError
    instead of ExporterBuildError. Update explicit result types and error handling
    that expects ExporterBuildError::UnsupportedCompressionAlgorithm. The new error
    implements Display and std::error::Error; its message is for diagnostics.
    Accepted strings and parsing behavior are unchanged.

    // Before:
let result: Result<Compression, ExporterBuildError> = value.parse();

// After:
let result: Result<Compression, ParseConfigError> = value.parse();
if let Err(error) = result {
    eprintln!("invalid compression configuration: {error}");
}

  • Interpret protocol, compression, and metrics temporality environment values
    case-insensitively. Treat empty values as unset, and warn and ignore invalid,
    non-Unicode, or feature-unavailable enum values so resolution can continue
    to the next environment variable or default. Compression none explicitly
    disables compression, including when a generic compression value is set.
    Programmatic configuration remains strict.

Retry
  • Retries are now enabled by default for OTLP/HTTP and OTLP/gRPC. The default
    policy uses exponential backoff and jitter with up to 3 retries (4 attempts
    total). Use .with_retry_policy(RetryPolicy::disabled()) to disable retries,
    or provide a custom RetryPolicy to change the behavior.
  • Migration for users of the experimental retry features: If your
    Cargo.toml enables experimental-grpc-retry or
    experimental-http-retry, remove those feature flags. No migration action is
    required for users who did not enable them.
    #​3621
  • Breaking Make the retry and retry_classification modules crate-private,
    removing their retry engine, error type, and protocol classifiers from the
    public API. RetryPolicy remains available from the crate root with private
    fields and fluent configuration methods. Replace imports from
    opentelemetry_otlp::retry with opentelemetry_otlp::RetryPolicy, and replace
    struct literals with its with_* methods.
    #​3672
Retry fixes

The following fixes apply to retry behavior that was experimental before this
release:

  • Retry only HTTP status codes 429, 502, 503, and 504, as required by the OTLP
    specification. The exporter now also honors Retry-After on 503 responses.
  • Honor positive gRPC RetryInfo delays returned with Unavailable responses.
  • Continue exponential backoff from server-provided RetryInfo and
    Retry-After delays when subsequent export attempts fail.
Other changes

  • Exporter compression configuration and behavior are unchanged; users of
    .with_compression(...) need no changes. Breaking only for direct conversion
    callers:     removed TryFrom<Compression> for
    tonic::codec::CompressionEncoding. Code explicitly converting between these
    enums must map the variants itself.

  • Return an exporter build error when construction of a built-in reqwest HTTP
    client fails instead of silently falling back to a client without the
    exporter-configured timeout. Failure to spawn the blocking client's setup
    thread, or a panic in that thread, is also returned instead of panicking.

  • Breaking Removed Default from the TonicExporterBuilderSet and
    HttpExporterBuilderSet typestate markers. This also removes Default from
    the transport-selected exporter builders (e.g.
    SpanExporterBuilder<TonicExporterBuilderSet>). Use the intended builder
    flow instead:

    // Before (no longer compiles):
let exporter = SpanExporterBuilder::<TonicExporterBuilderSet>::default().build()?;

// After (use the builder entry point):
let exporter = SpanExporter::builder().with_tonic().build()?;

    Also removed the unused #[doc(hidden)] NoExporterConfig type.

  • Breaking Mark Protocol and Compression as non-exhaustive so new OTLP
    protocols, encodings, and compression algorithms can be added without
    breaking downstream users. External exhaustive matches must add a wildcard
    arm. Constructing existing variants and passing them to exporter builders is
    unchanged.

    let protocol_name = match protocol {
    Protocol::Grpc => "grpc",
    Protocol::HttpBinary => "http/protobuf",
    Protocol::HttpJson => "http/json",
    _ => "unknown", // Required because Protocol is non-exhaustive.
};

  • Breaking Make Protocol::from_env() crate-private. Exporter builders
    already resolve OTEL_EXPORTER_OTLP_PROTOCOL when built; applications that
    need to inspect the raw environment setting should read the variable
    directly.

  • Breaking Remove OTEL_EXPORTER_OTLP_ENDPOINT_DEFAULT, which always held
    the HTTP default (http://localhost:4318) despite gRPC using
    http://localhost:4317. Omit .with_endpoint(...) to let the selected
    transport use its correct default, or provide the appropriate URL explicitly.
    #​3690

  • Breaking Restrict MetricExporterBuilder::with_http() and with_tonic()
    to builders where no transport has been selected, matching the span and log
    exporter builders. Select a transport once; with_temporality() remains
    available before or after transport selection.

  • Breaking Remove the public HttpExporterBuilder and
    TonicExporterBuilder transport-first APIs. Configure transports through the
    signal builders instead:

    • Replace HttpExporterBuilder::default() with the corresponding signal
      exporter builder followed by .with_http(), then replace
      .build_span_exporter() or .build_log_exporter() with .build().
    • Replace .build_metrics_exporter(temporality) with
      .with_temporality(temporality).build().
    • Replace TonicExporterBuilder::default() with the corresponding signal
      exporter builder followed by .with_tonic().
      Transport-specific configuration methods remain available after
      .with_http() or .with_tonic().

  • Breaking Removed the deprecated tls feature alias. Replace tls with
    tls-ring, or select tls-aws-lc or tls-provider-agnostic explicitly.

  • Exporter builder usage is unchanged. Breaking for code matching or constructing
    removed error variants:     Simplified ExporterBuildError to the exhaustive
    InvalidConfiguration(String) and InternalFailure(String) variants.
    The enum is no longer marked #[non_exhaustive].
    Configuration errors such as invalid endpoints, missing HTTP clients,
    transport/protocol mismatches, and missing compression features now use
    InvalidConfiguration. Replace implementation-specific, non-exhaustive
    matches such as:

    match error {
    ExporterBuildError::InvalidUri(_, _)
    | ExporterBuildError::InvalidConfig { .. }
    | ExporterBuildError::NoHttpClient => {
        eprintln!("fix the exporter configuration");
    }
    ExporterBuildError::InternalFailure(message) => {
        eprintln!("exporter initialization failed: {message}");
    }
    _ => {}
}

    with an exhaustive match over the two stable categories:

    match error {
    ExporterBuildError::InvalidConfiguration(message) => {
        eprintln!("fix the exporter configuration: {message}");
    }
    ExporterBuildError::InternalFailure(message) => {
        eprintln!("exporter initialization failed: {message}");
    }
}

    Code that propagates build errors with ? without inspecting their variants
    needs no changes.
    Tonic endpoint errors identify the originating environment variable when
    validating the URI or reporting endpoint-related TLS setup failures.
    #​3691

  • Return an exporter build error for invalid OTLP/HTTP endpoint environment
    variables instead of silently falling back to another endpoint or localhost.
    Empty endpoint environment variables are now treated as unset.

  • Return an exporter build error for invalid OTLP/gRPC endpoint environment
    variables instead of silently falling back to another endpoint or localhost.
    Empty endpoint environment variables are now treated as unset.

  • Add WithHttpConfig::with_max_request_body_size to configure the HTTP request
    body limit. OTLP/HTTP request bodies are now limited to 64 MiB by default, before and
    after compression; oversized requests are discarded without being sent or
    retried.

  • Breaking Seal WithExportConfig, WithHttpConfig, and
    WithTonicConfig. These traits remain public for calling configuration
    methods on OTLP builders, but can no longer be implemented for external
    types.

  • Add support for INSECURE environment variables for gRPC (env-var-only, no builder method, per spec):
    OTEL_EXPORTER_OTLP_INSECURE (generic), OTEL_EXPORTER_OTLP_TRACES_INSECURE,
    OTEL_EXPORTER_OTLP_METRICS_INSECURE, OTEL_EXPORTER_OTLP_LOGS_INSECURE.
    Per the spec, these only apply to gRPC connections. When an endpoint has no explicit scheme,
    INSECURE=true uses http://, INSECURE=false (default) uses https:// with auto-TLS.
    Breaking: Schemeless endpoints (e.g., collector.example.com:4317) now default to https://
    instead of being passed as-is. Set OTEL_EXPORTER_OTLP_INSECURE=true for plaintext connections.
    Endpoints with an explicit scheme (e.g., http://, https://, unix://) are unaffected.
    #​774
    #​984

  • Breaking Removed the serialize feature flag and its implicit serde
    dependency. This feature gated Serialize/Deserialize derives on
    Protocol and Compression, but the derived representations were incorrect
    (Rust variant names instead of spec values) and the feature only covered
    these two enums. The equivalent feature was removed from the core
    opentelemetry crate in 2022.
    Migration: Remove serialize (and serde, if listed) from your feature
    list. If these values are part of serialisable app config, define a local
    config enum or wrapper and convert it to Protocol or Compression when
    building the exporter.
    #​3711

  • Breaking Removed reqwest-rustls-webpki-roots feature. The webpki-roots cargo feature was
    removed from reqwest in v0.13.0, making this feature broken for anyone resolving reqwest >= 0.13.0.
    Migration: Use reqwest-rustls instead (now correctly uses reqwest/rustls with platform native
    trust roots). If you specifically need Mozilla's embedded CA bundle, construct a custom client:

    let root_store = rustls::RootCertStore::from_iter(
    webpki_roots::TLS_SERVER_ROOTS.iter().cloned(),
);
let tls_config = rustls::ClientConfig::builder()
    .with_root_certificates(root_store)
    .with_no_client_auth();
let client = reqwest::Client::builder()
    .tls_backend_preconfigured(tls_config)
    .build()?;
exporter_builder.with_http_client(client)

  • Allow to provide http client wrapped in Arc when configuring HTTP exporter. 3468

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

v0.33.1

Compare Source

Released 2026-Oct-08

  • Emit a one-time internal error diagnostic when the default PeriodicReader
    worker thread panics (such as from an observable metric callback), and document
    the callback panic contract.
    (#​3640)
  • Added Sampler::parent_based(root), returning a ParentBasedSampler that lets
    all 5 branches of the ParentBased sampler spec be configured independently
    (root, and remote/local parent that is/isn't sampled) via with_remote_parent_sampled,
    with_remote_parent_not_sampled, with_local_parent_sampled, and
    with_local_parent_not_sampled. Previously Sampler::ParentBased only let you
    override the root case; the other 4 were fixed to the spec defaults. Unset
    branches keep those same defaults, so this is purely additive.
    (#​3657)
  • Fixed Histogram, Sum, LastValue, and PrecomputedSum aggregators (and
    their bound-instrument handles) silently accepting NaN/Infinity
    measurements. For Histogram and Sum, a single NaN measurement
    permanently corrupted the cumulative sum/total for the rest of the
    process's lifetime (x + NaN == NaN); LastValue and PrecomputedSum
    self-healed on the next valid measurement but still exported one bad value
    in the meantime, and PrecomputedSum under delta temporality corrupted two
    export cycles. Non-finite measurements are now dropped before recording,
    matching ExponentialHistogram's existing behavior.
    (#​3656)
  • Fixed SdkTracer inheriting an invalid parent span context (e.g. a context
    carrying an invalid active span context). Such a parent is now treated as no
    parent: the span gets a freshly generated trace id instead of the parent's
    all-zero one, and is not recorded as a child of it.
    (#​3657)
  • Log metric export failures at ERROR level in PeriodicReader, making
    failures such as an unreachable collector visible without enabling DEBUG
    logging.
    (#​3754)

v0.33.0

Released 2026-Sep-18

  • Publicly export the OTEL_*/OTEL_*_DEFAULT environment variable name and
    default value constants for BatchSpanProcessor (opentelemetry_sdk::trace),
    BatchLogProcessor (opentelemetry_sdk::logs), and PeriodicReader
    (opentelemetry_sdk::metrics), so downstream configuration systems can read
    the SDK's spec-defined defaults programmatically instead of duplicating
    them. As part of this, PeriodicReader's previously-private
    DEFAULT_INTERVAL/METRIC_EXPORT_INTERVAL_NAME constants were renamed
    to OTEL_METRIC_EXPORT_INTERVAL_DEFAULT/OTEL_METRIC_EXPORT_INTERVAL to
    match the naming convention already used elsewhere.
    (#​3623)
  • Added SDK self-observability metrics, feature-gated behind
    experimental_metrics_bound_instruments: otel.sdk.log.created counts log
    records submitted to the SDK; otel.sdk.processor.log.processed and
    otel.sdk.processor.span.processed count records and spans submitted to an
    exporter by batch and simple processors, with error.type reporting items
    dropped before submission; and otel.sdk.processor.log.queue.capacity
    reports the configured BatchLogProcessor queue capacity.
    (#​3514,
    #​3608,
    #​3609,
    #​3611)
  • Made futures-channel, futures-executor, futures-util, and thiserror
    optional, enabling a minimal SDK build. With default-features = false, the
    SDK's only dependency is the opentelemetry API crate.
    (#​3593)
  • Bound instruments are now available for Gauge and UpDownCounter via the
    new BoundGauge<T> and BoundUpDownCounter<T> types exposed by the
    opentelemetry crate. Requires the experimental_metrics_bound_instruments
    feature.
  • Fixed a race in BatchSpanProcessor and BatchLogProcessor where a
    span/log enqueued just before force_flush() or shutdown() could be
    missed by the flush and dropped at shutdown: the pending-item counter is
    now incremented before enqueueing (and reverted if the queue is full), so
    the worker's counter snapshot can no longer under-count items already in
    the queue (#​3453).
  • Default SDK Resource construction now falls back to unknown_service under
    Miri instead of calling std::env::current_exe(), avoiding an abort in Miri
    isolation mode while preserving the normal
    unknown_service:<process.executable.name> fallback outside Miri.
  • Fixed asynchronous counters (ObservableCounter, ObservableUpDownCounter)
    using delta temporality reporting incorrect deltas when observed attributes
    were recorded in an unsorted key order.

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry)) | workspace.dependencies | minor | `0.32.0` → `0.33.0` | | [opentelemetry-otlp](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-otlp) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry-otlp)) | workspace.dependencies | minor | `0.32.0` → `0.33.0` | | [opentelemetry_sdk](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-sdk) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry-sdk)) | workspace.dependencies | minor | `0.32.0` → `0.33.0` | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry)</summary> ### [`v0.33.1`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry/CHANGELOG.md#0331) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-0.33.0...opentelemetry-0.33.1) Released 2026-Oct-08 - Fix a panic when a value stored with `Context::with_value()` calls `Context::current()` from its `Drop` implementation. - Expand tracing documentation on async context propagation and child spans ([#&#8203;828](https://github.com/open-telemetry/opentelemetry-rust/issues/828)). - Document the panic contract for observable metric callbacks (`Callback` and `AsyncInstrumentBuilder::with_callback`). ([#&#8203;3640](https://github.com/open-telemetry/opentelemetry-rust/issues/3640)) - Fix `TraceState::from_str` rejecting valid optional whitespace around list members. ([#&#8203;3757](https://github.com/open-telemetry/opentelemetry-rust/issues/3757)) ### [`v0.33.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry/CHANGELOG.md#0330) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-0.32.0...opentelemetry-0.33.0) Released 2026-Sep-18 - Fix `TraceState` accepting more than the 32 list-members the W3C trace-context specification allows. `from_str`, `from_key_value` and `insert` now keep at most 32, dropping members from the end of the list as the specification prescribes, so neither a parsed nor a locally built `tracestate` can exceed the limit. - **Added** experimental support for a global context event observer. A `ContextObserver` can be registered via `GlobalContextObserver::set` to be notified of context transitions through the `on_context_enter` and `on_context_exit` callbacks. This feature is primarily intended to publish a different view of the current context (the `ObserverContextView`) through alternative channels that let external readers (e.g. an eBPF profiler) track the current context. See the associated [OTEP](https://github.com/open-telemetry/opentelemetry-specification/pull/4947). Gated behind the `experimental_context_observer` feature flag. - `otel_info!`, `otel_warn!`, `otel_debug!`, and `otel_error!` macros now accept quoted-key fields (e.g. `"otel.component.type" = "value"`) for dotted attribute names. - **Added** `BoundGauge<T>` and `BoundUpDownCounter<T>` types (and the corresponding `Gauge::bind()` / `UpDownCounter::bind()` methods), completing the experimental bound-instrument API across all sync instruments (`Counter`, `UpDownCounter`, `Histogram`, `Gauge`). Gated behind the `experimental_metrics_bound_instruments` feature flag. </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry-otlp)</summary> ### [`v0.33.1`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-otlp/CHANGELOG.md#0331) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-otlp-0.33.0...opentelemetry-otlp-0.33.1) Released 2026-Oct-08 - Declare the OTLP exporters for Logs and Metrics stable after the 0.33.0 release-candidate period. Tracing remains in beta. - Update OpenTelemetry dependencies to 0.33.1, including SDK fixes and OTLP/JSON interoperability fixes in `opentelemetry-proto`. ### [`v0.33.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-otlp/CHANGELOG.md#0330) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-otlp-0.32.0...opentelemetry-otlp-0.33.0) Released 2026-Sep-18 - Exporter builder usage and environment configuration are unchanged. **Breaking for callers parsing compression strings:** `Compression::from_str` (including `.parse::<Compression>()`) now returns the opaque `ParseConfigError` instead of `ExporterBuildError`. Update explicit result types and error handling that expects `ExporterBuildError::UnsupportedCompressionAlgorithm`. The new error implements `Display` and `std::error::Error`; its message is for diagnostics. Accepted strings and parsing behavior are unchanged. ```rust // Before: let result: Result<Compression, ExporterBuildError> = value.parse(); // After: let result: Result<Compression, ParseConfigError> = value.parse(); if let Err(error) = result { eprintln!("invalid compression configuration: {error}"); } ``` - Interpret protocol, compression, and metrics temporality environment values case-insensitively. Treat empty values as unset, and warn and ignore invalid, non-Unicode, or feature-unavailable enum values so resolution can continue to the next environment variable or default. Compression `none` explicitly disables compression, including when a generic compression value is set. Programmatic configuration remains strict. ##### Retry - Retries are now enabled by default for OTLP/HTTP and OTLP/gRPC. The default policy uses exponential backoff and jitter with up to 3 retries (4 attempts total). Use `.with_retry_policy(RetryPolicy::disabled())` to disable retries, or provide a custom `RetryPolicy` to change the behavior. - **Migration for users of the experimental retry features:** If your `Cargo.toml` enables `experimental-grpc-retry` or `experimental-http-retry`, remove those feature flags. No migration action is required for users who did not enable them. [#&#8203;3621](https://github.com/open-telemetry/opentelemetry-rust/pull/3621) - **Breaking** Make the `retry` and `retry_classification` modules crate-private, removing their retry engine, error type, and protocol classifiers from the public API. `RetryPolicy` remains available from the crate root with private fields and fluent configuration methods. Replace imports from `opentelemetry_otlp::retry` with `opentelemetry_otlp::RetryPolicy`, and replace struct literals with its `with_*` methods. [#&#8203;3672](https://github.com/open-telemetry/opentelemetry-rust/pull/3672) ##### Retry fixes The following fixes apply to retry behavior that was experimental before this release: - Retry only HTTP status codes 429, 502, 503, and 504, as required by the OTLP specification. The exporter now also honors `Retry-After` on 503 responses. - Honor positive gRPC `RetryInfo` delays returned with `Unavailable` responses. - Continue exponential backoff from server-provided `RetryInfo` and `Retry-After` delays when subsequent export attempts fail. ##### Other changes - Exporter compression configuration and behavior are unchanged; users of `.with_compression(...)` need no changes. **Breaking only for direct conversion callers:** removed `TryFrom<Compression>` for `tonic::codec::CompressionEncoding`. Code explicitly converting between these enums must map the variants itself. - Return an exporter build error when construction of a built-in reqwest HTTP client fails instead of silently falling back to a client without the exporter-configured timeout. Failure to spawn the blocking client's setup thread, or a panic in that thread, is also returned instead of panicking. - **Breaking** Removed `Default` from the `TonicExporterBuilderSet` and `HttpExporterBuilderSet` typestate markers. This also removes `Default` from the transport-selected exporter builders (e.g. `SpanExporterBuilder<TonicExporterBuilderSet>`). Use the intended builder flow instead: ```rust // Before (no longer compiles): let exporter = SpanExporterBuilder::<TonicExporterBuilderSet>::default().build()?; // After (use the builder entry point): let exporter = SpanExporter::builder().with_tonic().build()?; ``` Also removed the unused `#[doc(hidden)]` `NoExporterConfig` type. - **Breaking** Mark `Protocol` and `Compression` as non-exhaustive so new OTLP protocols, encodings, and compression algorithms can be added without breaking downstream users. External exhaustive matches must add a wildcard arm. Constructing existing variants and passing them to exporter builders is unchanged. ```rust let protocol_name = match protocol { Protocol::Grpc => "grpc", Protocol::HttpBinary => "http/protobuf", Protocol::HttpJson => "http/json", _ => "unknown", // Required because Protocol is non-exhaustive. }; ``` - **Breaking** Make `Protocol::from_env()` crate-private. Exporter builders already resolve `OTEL_EXPORTER_OTLP_PROTOCOL` when built; applications that need to inspect the raw environment setting should read the variable directly. - **Breaking** Remove `OTEL_EXPORTER_OTLP_ENDPOINT_DEFAULT`, which always held the HTTP default (`http://localhost:4318`) despite gRPC using `http://localhost:4317`. Omit `.with_endpoint(...)` to let the selected transport use its correct default, or provide the appropriate URL explicitly. [#&#8203;3690](https://github.com/open-telemetry/opentelemetry-rust/issues/3690) - **Breaking** Restrict `MetricExporterBuilder::with_http()` and `with_tonic()` to builders where no transport has been selected, matching the span and log exporter builders. Select a transport once; `with_temporality()` remains available before or after transport selection. - **Breaking** Remove the public `HttpExporterBuilder` and `TonicExporterBuilder` transport-first APIs. Configure transports through the signal builders instead: - Replace `HttpExporterBuilder::default()` with the corresponding signal exporter builder followed by `.with_http()`, then replace `.build_span_exporter()` or `.build_log_exporter()` with `.build()`. - Replace `.build_metrics_exporter(temporality)` with `.with_temporality(temporality).build()`. - Replace `TonicExporterBuilder::default()` with the corresponding signal exporter builder followed by `.with_tonic()`. Transport-specific configuration methods remain available after `.with_http()` or `.with_tonic()`. - **Breaking** Removed the deprecated `tls` feature alias. Replace `tls` with `tls-ring`, or select `tls-aws-lc` or `tls-provider-agnostic` explicitly. - Exporter builder usage is unchanged. **Breaking for code matching or constructing removed error variants:** Simplified `ExporterBuildError` to the exhaustive `InvalidConfiguration(String)` and `InternalFailure(String)` variants. The enum is no longer marked `#[non_exhaustive]`. Configuration errors such as invalid endpoints, missing HTTP clients, transport/protocol mismatches, and missing compression features now use `InvalidConfiguration`. Replace implementation-specific, non-exhaustive matches such as: ```rust match error { ExporterBuildError::InvalidUri(_, _) | ExporterBuildError::InvalidConfig { .. } | ExporterBuildError::NoHttpClient => { eprintln!("fix the exporter configuration"); } ExporterBuildError::InternalFailure(message) => { eprintln!("exporter initialization failed: {message}"); } _ => {} } ``` with an exhaustive match over the two stable categories: ```rust match error { ExporterBuildError::InvalidConfiguration(message) => { eprintln!("fix the exporter configuration: {message}"); } ExporterBuildError::InternalFailure(message) => { eprintln!("exporter initialization failed: {message}"); } } ``` Code that propagates build errors with `?` without inspecting their variants needs no changes. Tonic endpoint errors identify the originating environment variable when validating the URI or reporting endpoint-related TLS setup failures. [#&#8203;3691](https://github.com/open-telemetry/opentelemetry-rust/issues/3691) - Return an exporter build error for invalid OTLP/HTTP endpoint environment variables instead of silently falling back to another endpoint or localhost. Empty endpoint environment variables are now treated as unset. - Return an exporter build error for invalid OTLP/gRPC endpoint environment variables instead of silently falling back to another endpoint or localhost. Empty endpoint environment variables are now treated as unset. - Add `WithHttpConfig::with_max_request_body_size` to configure the HTTP request body limit. OTLP/HTTP request bodies are now limited to 64 MiB by default, before and after compression; oversized requests are discarded without being sent or retried. - **Breaking** Seal `WithExportConfig`, `WithHttpConfig`, and `WithTonicConfig`. These traits remain public for calling configuration methods on OTLP builders, but can no longer be implemented for external types. - Add support for INSECURE environment variables for gRPC (env-var-only, no builder method, per spec): `OTEL_EXPORTER_OTLP_INSECURE` (generic), `OTEL_EXPORTER_OTLP_TRACES_INSECURE`, `OTEL_EXPORTER_OTLP_METRICS_INSECURE`, `OTEL_EXPORTER_OTLP_LOGS_INSECURE`. Per the spec, these only apply to gRPC connections. When an endpoint has no explicit scheme, `INSECURE=true` uses `http://`, `INSECURE=false` (default) uses `https://` with auto-TLS. **Breaking:** Schemeless endpoints (e.g., `collector.example.com:4317`) now default to `https://`\ instead of being passed as-is. Set `OTEL_EXPORTER_OTLP_INSECURE=true` for plaintext connections. Endpoints with an explicit scheme (e.g., `http://`, `https://`, `unix://`) are unaffected. [#&#8203;774](https://github.com/open-telemetry/opentelemetry-rust/issues/774) [#&#8203;984](https://github.com/open-telemetry/opentelemetry-rust/issues/984) - **Breaking** Removed the `serialize` feature flag and its implicit `serde` dependency. This feature gated `Serialize`/`Deserialize` derives on `Protocol` and `Compression`, but the derived representations were incorrect (Rust variant names instead of spec values) and the feature only covered these two enums. The equivalent feature was removed from the core `opentelemetry` crate in 2022. **Migration**: Remove `serialize` (and `serde`, if listed) from your feature list. If these values are part of serialisable app config, define a local config enum or wrapper and convert it to `Protocol` or `Compression` when building the exporter. [#&#8203;3711](https://github.com/open-telemetry/opentelemetry-rust/pull/3711) - **Breaking** Removed `reqwest-rustls-webpki-roots` feature. The `webpki-roots` cargo feature was removed from `reqwest` in v0.13.0, making this feature broken for anyone resolving `reqwest >= 0.13.0`. **Migration**: Use `reqwest-rustls` instead (now correctly uses `reqwest/rustls` with platform native trust roots). If you specifically need Mozilla's embedded CA bundle, construct a custom client: ```rust let root_store = rustls::RootCertStore::from_iter( webpki_roots::TLS_SERVER_ROOTS.iter().cloned(), ); let tls_config = rustls::ClientConfig::builder() .with_root_certificates(root_store) .with_no_client_auth(); let client = reqwest::Client::builder() .tls_backend_preconfigured(tls_config) .build()?; exporter_builder.with_http_client(client) ``` - Allow to provide http client wrapped in Arc when configuring HTTP exporter. [3468](https://github.com/open-telemetry/opentelemetry-rust/pull/3468) </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry_sdk)</summary> ### [`v0.33.1`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-sdk/CHANGELOG.md#0331) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry_sdk-0.33.0...opentelemetry_sdk-0.33.1) Released 2026-Oct-08 - Emit a one-time internal error diagnostic when the default `PeriodicReader` worker thread panics (such as from an observable metric callback), and document the callback panic contract. ([#&#8203;3640](https://github.com/open-telemetry/opentelemetry-rust/issues/3640)) - Added `Sampler::parent_based(root)`, returning a `ParentBasedSampler` that lets all 5 branches of the ParentBased sampler spec be configured independently (root, and remote/local parent that is/isn't sampled) via `with_remote_parent_sampled`, `with_remote_parent_not_sampled`, `with_local_parent_sampled`, and `with_local_parent_not_sampled`. Previously `Sampler::ParentBased` only let you override the root case; the other 4 were fixed to the spec defaults. Unset branches keep those same defaults, so this is purely additive. ([#&#8203;3657](https://github.com/open-telemetry/opentelemetry-rust/issues/3657)) - Fixed `Histogram`, `Sum`, `LastValue`, and `PrecomputedSum` aggregators (and their bound-instrument handles) silently accepting NaN/Infinity measurements. For `Histogram` and `Sum`, a single NaN measurement permanently corrupted the cumulative `sum`/total for the rest of the process's lifetime (`x + NaN == NaN`); `LastValue` and `PrecomputedSum` self-healed on the next valid measurement but still exported one bad value in the meantime, and `PrecomputedSum` under delta temporality corrupted two export cycles. Non-finite measurements are now dropped before recording, matching `ExponentialHistogram`'s existing behavior. ([#&#8203;3656](https://github.com/open-telemetry/opentelemetry-rust/issues/3656)) - Fixed `SdkTracer` inheriting an invalid parent span context (e.g. a context carrying an invalid active span context). Such a parent is now treated as no parent: the span gets a freshly generated trace id instead of the parent's all-zero one, and is not recorded as a child of it. ([#&#8203;3657](https://github.com/open-telemetry/opentelemetry-rust/issues/3657)) - Log metric export failures at ERROR level in `PeriodicReader`, making failures such as an unreachable collector visible without enabling DEBUG logging. ([#&#8203;3754](https://github.com/open-telemetry/opentelemetry-rust/issues/3754)) ### [`v0.33.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-sdk/CHANGELOG.md#0330) Released 2026-Sep-18 - Publicly export the `OTEL_*`/`OTEL_*_DEFAULT` environment variable name and default value constants for `BatchSpanProcessor` (`opentelemetry_sdk::trace`), `BatchLogProcessor` (`opentelemetry_sdk::logs`), and `PeriodicReader` (`opentelemetry_sdk::metrics`), so downstream configuration systems can read the SDK's spec-defined defaults programmatically instead of duplicating them. As part of this, `PeriodicReader`'s previously-private `DEFAULT_INTERVAL`/`METRIC_EXPORT_INTERVAL_NAME` constants were renamed to `OTEL_METRIC_EXPORT_INTERVAL_DEFAULT`/`OTEL_METRIC_EXPORT_INTERVAL` to match the naming convention already used elsewhere. ([#&#8203;3623](https://github.com/open-telemetry/opentelemetry-rust/issues/3623)) - Added SDK self-observability metrics, feature-gated behind `experimental_metrics_bound_instruments`: `otel.sdk.log.created` counts log records submitted to the SDK; `otel.sdk.processor.log.processed` and `otel.sdk.processor.span.processed` count records and spans submitted to an exporter by batch and simple processors, with `error.type` reporting items dropped before submission; and `otel.sdk.processor.log.queue.capacity` reports the configured `BatchLogProcessor` queue capacity. ([#&#8203;3514](https://github.com/open-telemetry/opentelemetry-rust/pull/3514), [#&#8203;3608](https://github.com/open-telemetry/opentelemetry-rust/pull/3608), [#&#8203;3609](https://github.com/open-telemetry/opentelemetry-rust/pull/3609), [#&#8203;3611](https://github.com/open-telemetry/opentelemetry-rust/pull/3611)) - Made `futures-channel`, `futures-executor`, `futures-util`, and `thiserror` optional, enabling a minimal SDK build. With `default-features = false`, the SDK's only dependency is the `opentelemetry` API crate. ([#&#8203;3593](https://github.com/open-telemetry/opentelemetry-rust/pull/3593)) - Bound instruments are now available for `Gauge` and `UpDownCounter` via the new `BoundGauge<T>` and `BoundUpDownCounter<T>` types exposed by the `opentelemetry` crate. Requires the `experimental_metrics_bound_instruments` feature. - Fixed a race in `BatchSpanProcessor` and `BatchLogProcessor` where a span/log enqueued just before `force_flush()` or `shutdown()` could be missed by the flush and dropped at shutdown: the pending-item counter is now incremented before enqueueing (and reverted if the queue is full), so the worker's counter snapshot can no longer under-count items already in the queue ([#&#8203;3453](https://github.com/open-telemetry/opentelemetry-rust/issues/3453)). - Default SDK Resource construction now falls back to `unknown_service` under Miri instead of calling `std::env::current_exe()`, avoiding an abort in Miri isolation mode while preserving the normal `unknown_service:<process.executable.name>` fallback outside Miri. - Fixed asynchronous counters (`ObservableCounter`, `ObservableUpDownCounter`) using delta temporality reporting incorrect deltas when observed attributes were recorded in an unsorted key order. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC44My4yIiwidXBkYXRlZEluVmVyIjoiNDQuMTMzLjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbIkRlcGVuZGVuY2llcyIsIkRlcGVuZGVuY2llcy9SZW5vdmF0ZSJdfQ==-->
chore(deps): update opentelemetry-rust monorepo to 0.33.0
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 3s
Details
Checks / Prek / Check changed files (pull_request) Successful in 5s
Details
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 10s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m7s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m40s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m37s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 7m49s
Details
810667769e
renovate force-pushed renovate/opentelemetry-rust-monorepo from 810667769e
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 3s
Details
Checks / Prek / Check changed files (pull_request) Successful in 5s
Details
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 10s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m7s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m40s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m37s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 7m49s
Details
to 69601849fc
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m22s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m29s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 6m59s
Details
2026-09-21 05:12:23 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from 69601849fc
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m22s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m29s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 6m59s
Details
to 7b0a494a9f
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 11s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m12s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m25s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m12s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 6m18s
Details
2026-09-22 05:05:25 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from 7b0a494a9f
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 11s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m12s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m25s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m12s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 6m18s
Details
to 49ee680bf3
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Checks / Prek / Check changed files (pull_request) Successful in 8s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m8s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m34s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m23s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m57s
Details
2026-09-24 14:01:06 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from 49ee680bf3
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Checks / Prek / Check changed files (pull_request) Successful in 8s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m8s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m34s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m23s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m57s
Details
to b0c6c7308d
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 12s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m10s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 2m29s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 7m47s
Details
2026-09-25 05:03:08 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from b0c6c7308d
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 12s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m10s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 2m29s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 7m47s
Details
to a7ec31436f
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m5s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m23s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m19s
Details
2026-09-28 05:09:05 +00:00 Compare
Jade force-pushed renovate/opentelemetry-rust-monorepo from a7ec31436f
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m5s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m23s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m19s
Details
to 14829e1a88
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 9s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m4s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m50s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m49s
Details
2026-10-04 22:31:42 +00:00 Compare
Jade force-pushed renovate/opentelemetry-rust-monorepo from 14829e1a88
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 9s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m4s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m50s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m49s
Details
to c2815a5992
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 10s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m5s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m8s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m59s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 7m35s
Details
2026-10-04 23:28:51 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from c2815a5992
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 10s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m5s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m8s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m59s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 7m35s
Details
to 7f93a8c020
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 14s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m3s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m11s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 2m28s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m2s
Details
2026-10-05 21:11:01 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from 7f93a8c020
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 14s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m3s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m11s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 2m28s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m2s
Details
to 643614d8de
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m25s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m43s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m50s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 6m35s
Details
2026-10-10 05:04:14 +00:00 Compare
renovate force-pushed renovate/opentelemetry-rust-monorepo from 643614d8de
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m25s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m43s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m50s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 6m35s
Details
to a6ca91a13f
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 9s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m10s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 58s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m26s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 40m48s
Details
2026-10-12 05:16:32 +00:00 Compare
renovate changed title from chore(deps): update opentelemetry-rust monorepo to 0.33.0 to chore(deps): update opentelemetry-rust monorepo to 0.33.0 - autoclosed 2026-10-13 05:20:07 +00:00
renovate closed this pull request 2026-10-13 05:20:07 +00:00
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 9s
Required
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m10s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Required
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 58s
Required
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m26s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 40m48s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Abandoned
This pull request appears to be abandoned by its author.

  
Blocked
This pull request or issue is currently blocked from being merged/closed

  
Bug
Something isn't working as intended

  
Changelog
Added
 Changelog entry added

  
Changelog
Missing
 No changelog when one is needed

  
Changelog
None
 Changelog is unnecesary for this change

  
Cherry-picking
Commits picked from other conduit projects

  
Database
This requires or includes changes to the database

  
Dependencies
Something dependency related

  
Dependencies/Renovate
Automatic dependency upgrades by Renovate

  
Difficulty
Easy
 Low difficulty to implement - touches few parts of the codebase, low complexity

  
Difficulty
Hard
 High difficulty to implement - touches many parts of the codebase, high complexity

  
Difficulty
Medium
 Medium difficulty to implement - touches more parts of the codebase, higher complexity

  
Documentation
Improvements or additions to documentation

  
Enhancement
New feature or request

  
Good first issue
Good for newcomers

  
Help wanted
Additional eyes and keyboards are required for this one

  
Inherited
Issues that have been inhereted from the project pre-fork

  
Matrix/Administration
Features pertaining to homeserver administration

  
Matrix/Appservices
Features pertaining to the appservice API

  
Matrix/Auth
Features pertaining to authentication

  
Matrix/Client
Features pertaining to client-to-server interactions

  
Matrix/Core
Issues relating to core matrix functionality, such as state resolution and PDU formats

  
Matrix/E2EE
Issues related to end to end encryption

  
Matrix/Federation
Features pertaining to server-to-server interactions

  
Matrix/Hydra
Issues related to room version 12 and related changes (temporary label)

  
Matrix/MSC
Features pertaining to unstable matrix features

  
Matrix/Media
Features pertaining to media interactions

  
Matrix/T&S
Changes or issues related to trust & safety tooling

  
Merge
This PR is ready to be merged

  
Merge/Manual
This PR should be manually merged

  
Merge/Squash
This PR should be squashed when it is merged

  
Meta
Related to housekeeping, maintenance, or other repo-meta.

  
Meta/CI
Issues related to CI changes

  
Meta/Packaging
Packaging

  
Priority
Blocking
 This issue is blocking the next release

  
Priority
High
 This issue is very important

  
Priority
Low
 This issue is of a rather low priority

  
Security
This item is related to general security

  
Status
Confirmed
 This issue has enough information and is confirmed

  
Status
Duplicate
 This issue or pull request already exists

  
Status
Invalid
 This issue doesn't seem right

  
Status
Needs Investigation
 This issue needs further investigation

  
Support
Questions or support requests

  
bob the builder
pdu logic rewrite starring nexus nicholson

No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
continuwuation/continuwuity!2267
No description provided.