lilly/cookied

Watch

Fork 0

Update all non-major dependencies #2

Open

renovatebot wants to merge 1 commit from renovate/all-minor-patch into main

renovatebot commented

2026-03-01 16:08:10 +01:00

Collaborator

This PR contains the following updates:

Package	Type	Update	Change
anyhow	dependencies	patch	`1.0.100` → `1.0.104`
clap	dependencies	minor	`4.5.53` → `4.6.7`
opentelemetry (source)	dependencies	minor	`0.31.0` → `0.33.0`
opentelemetry-otlp (source)	dependencies	minor	`0.31.0` → `0.33.0`
opentelemetry-semantic-conventions (source)	dependencies	minor	`0.31.0` → `0.33.0`
opentelemetry-stdout (source)	dependencies	minor	`0.31.0` → `0.33.0`
opentelemetry_sdk (source)	dependencies	minor	`0.31.0` → `0.33.0`
time (source)	dependencies	patch	`0.3.44` → `0.3.55`
tokio (source)	dependencies	minor	`1.48.0` → `1.53.1`

Release Notes

dtolnay/anyhow (anyhow)

`v1.0.104`

Compare Source

Update syn dev-dependency to version 3

`v1.0.103`

Compare Source

Fix Stacked Borrows violation (UB) in Error::downcast_mut (#451, #452)

`v1.0.102`

Compare Source

Remove backtrace dependency (#438, #439, #440, #441, #442)

`v1.0.101`

Compare Source

Add #[inline] to anyhow::Ok helper (#437, thanks @Ibitier)

clap-rs/clap (clap)

`v4.6.7`

Compare Source

Features

(derive) Add #[command(defer = <bool>)] attribute to opt-in to lazy initialisation of subcommands

`v4.6.6`

Compare Source

Features

Add Command::get_overridden_usage

`v4.6.5`

Compare Source

Fixes

(help) Correctly mark which value_names are optional with num_args

`v4.6.3`

Compare Source

Fixes

(derive) Allow "literal".function() as attribute values

`v4.6.2`

Compare Source

Fixes

(help) Say alias when there is only one

`v4.6.1`

Compare Source

Fixes

(derive) Ensure rebuilds happen when an read env variable is changed

`v4.5.60`

Compare Source

Fixes

(help) Quote empty default values, possible values

`v4.5.59`

Compare Source

Fixes

Command::ignore_errors no longer masks help/version on subcommands

`v4.5.57`

Compare Source

Fixes

Regression from 4.5.55 where having an argument with .value_terminator("--") caused problems with an argument with .last(true)

`v4.5.56`

Compare Source

Fixes

On conflict error, don't show conflicting arguments in the usage

`v4.5.55`

Compare Source

Fixes

Fix inconsistency in precedence between positionals with a value_terminator("--") and escapes (--) where ./foo -- bar means the first arg is empty, rather than escaping future args

`v4.5.54`

Compare Source

Fixes

(help) Move [default] to its own paragraph when PossibleValue::help is present in --help

open-telemetry/opentelemetry-rust (opentelemetry)

`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.
Fix a panic when a value stored with Context::with_value() calls
Context::current() from its Drop implementation.

`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 (opentelemetry-otlp)

`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

`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

`v0.31.1`: opentelemetry-otlp 0.31.1

Compare Source

What's Changed

feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags [patch release v0.31.1] by @lalitb in #3426

Full Changelog: https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-otlp-0.31.1

open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)

`v0.33.0`

Compare Source

Released 2026-Sep-18

`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.33.0`

Compare Source

Released 2026-Sep-18

`v0.32.0`

Compare Source

Released 2026-May-08

ExponentialHistogram supported in stdout

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

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

`v0.32.1`

Released 2026-May-23

BaggagePropagator now enforces the W3C Baggage maximum header length
(8192 bytes) and maximum list-member count (64) when extracting an inbound
baggage header. Headers exceeding 8192 bytes are dropped at the
propagator boundary; headers with more than 64 list members are
truncated to the first 64 entries. The change keeps the propagator from
parsing attacker-controlled input beyond the W3C limits instead of doing
per-entry parse, decode, and allocation work only to discard the excess
on Baggage insert. See https://www.w3.org/TR/baggage/#limits.
Reverted the SimpleSpanProcessor telemetry suppression added in 0.32.0
(see #3494), which caused a RefCell already borrowed panic when a span
was started and dropped inside a get_active_span (or Context::map_current)
closure. Tracked in #3510. A proper fix for the underlying
Context::map_current re-entrancy will be investigated separately, after
which the suppression can be safely re-applied.
View-provided metric stream name (set via Stream::builder().with_name(...))
is no longer validated against the instrument name syntax, per
spec clarification.
unit and other stream parameters continue to be validated.

`v0.32.0`

Compare Source

Released 2026-May-08

SimpleSpanProcessor now suppresses telemetry during export, preventing
telemetry-induced-telemetry feedback loops. This aligns with the existing
behavior in BatchSpanProcessor and SimpleLogProcessor.
Removed SimpleConcurrentLogProcessor and the experimental_logs_concurrent_log_processor
feature flag. The use cases it was designed for (ETW/user_events exporters) are
better served by modeling those exporters as processors directly.
Added Counter::bind() and Histogram::bind() SDK implementations that
return pre-bound measurement handles (BoundCounter<T>, BoundHistogram<T>).
Bound instruments resolve the attribute-to-aggregator mapping once at bind time
and cache the result, eliminating per-call HashMap lookups. View attribute
filtering is applied at bind time so the hot path stays free of per-call
attribute processing. Bound and unbound recordings with the same (post-view)
attribute set always aggregate into the same data point, including the empty
attribute set. Bound entries are never evicted during delta collection while
a handle exists — idle cycles produce no export but the tracker persists. If
bind() is called at the cardinality limit, the handle binds directly to
the overflow tracker — its writes stay on the same direct (no-lookup) hot
path and consistently land in the otel.metric.overflow=true bucket for
the lifetime of the handle. To recover a bound handle after delta collection
frees space, drop the existing handle and call bind() again. Gated behind
the experimental_metrics_bound_instruments feature flag. Benchmarks show
~28x speedup for counter operations and ~9x for histograms.
Delta metrics collection now uses in-place eviction instead of draining the
HashMap on every collect cycle. Stale attribute sets that received no measurements
since the last collection are evicted. Note: recovery from cardinality overflow
now requires 2 collect cycles — the first marks entries as stale, the second
evicts them.
Breaking The SDK testing feature is now runtime agnostic. #3407
- TokioSpanExporter and new_tokio_test_exporter have been renamed to TestSpanExporter and new_test_exporter.
- The following transitive dependencies and features have been removed: tokio/rt, tokio/time, tokio/macros, tokio/rt-multi-thread, tokio-stream, experimental_async_runtime
Store InstrumentationScope in Arc internally in SdkTracer, making tracer clones cheaper (Arc refcount increment instead of deep copy).
Add 32-bit platform support by using portable-atomic for AtomicI64 and AtomicU64 in the metrics module. This enables compilation on 32-bit ARM targets (e.g., armv5te-unknown-linux-gnueabi, armv7-unknown-linux-gnueabihf).
Aggregation enum and StreamBuilder::with_aggregation() are now stable and no longer require the spec_unstable_metrics_views feature flag.
Fix service.name Resource attribute fallback to follow OpenTelemetry
specification by using unknown_service:<process.executable.name> format when
service name is not explicitly configured. Previously, it only used
unknown_service.
Fix SpanExporter::shutdown() default timeout from 5 nanoseconds to 5 seconds.
Breaking SpanExporter trait methods shutdown, shutdown_with_timeout, and force_flush now take &self instead of &mut self for consistency with LogExporter and PushMetricExporter. Implementers using interior mutability (e.g., Mutex, AtomicBool) require no changes.
Added Resource::get_ref(&self, key: &Key) -> Option<&Value> to allow retrieving a reference to a resource value without cloning.
Breaking Removed the following public hidden methods from the SdkTracer #3227:
- id_generator, should_sample
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.
StreamBuilder::build() now rejects usize::MAX as a cardinality limit
with a validation error. #3506
Fix Histogram boundaries being ignored in the presence of views #3312
TracerProviderBuilder::with_sampler allows to pass boxed instance of ShouldSample [#3313][3313]
Fix ObservableCounter and ObservableUpDownCounter now correctly report only data points from the current measurement cycle, removing stale attribute combinations that are no longer observed. #3248
Fix panic when SpanProcessor::on_end calls Context::current() (#3262).
- Updated SpanProcessor::on_end documentation to clarify that Context::current() returns the parent context, not the span's context
Fix traceparent headers with unknown flags (e.g. W3C random-trace-id flag 0x02) being incorrectly rejected. Unknown flags are now accepted and zeroed out as required by the W3C trace-context spec. #3435
Breaking InMemoryExporterError has been removed and replaced by OTelSdkError, and a new JaegerRemoteSamplerBuildError introduced to replace last uses of TraceError. #3458
"spec_unstable_logs_enabled" feature flag is removed. The capability (and the
backing specification) is now stable and is enabled by default. #3278

time-rs/time (time)

`v0.3.55`

Compare Source

Fixed

Avoid underflow in DateIter::nth, ensuring correct behavior.
Avoid overflow when deserializing timestamps.
Handle out-of-bounds data when deserializing.
Don't assume that the format being deserialized was generated by the serializer; this previously
led to some valid values being parsed incorrectly and others being rejected.
No longer silence errors when deserializing UtcOffset.
OffsetDateTime::from_unix_timestamp_nanos and UtcDateTime::from_unix_timestamp_nanos correctly
return None for all out-of-range values, rather than unexpectedly panicking in some situations.
OffsetDateTime::checked_to_offset and UtcDateTime::checked_to_offset correctly return None
for all out-of-range values, rather than unexpectedly panicking in some situations.

`v0.3.54`

Compare Source

Added

PrimitiveDateTime has been renamed to PlainDateTime.
Duration has been renamed to SignedDuration.
Iteration is now possible over Date, Month, and Weekday. Relevant iterator methods have been
overridden to ensure maximum performance.

For both PlainDateTime and SignedDuration, a non-deprecated type alias has been added for
backwards compatibility. The new names should be preferred.

Changed

The associated metadata type (for powerfmt implementations) for various types has been changed
to () and made public. This guarantees that no additional metadata will be present.

Performance

More gains when parsing RFC 2822.

`v0.3.53`

Compare Source

There are no publicly-facing changes in this release. It solely works around the cookie crate
relying on an implementation detail of time that was never part of the public API (and thus
subject to semver guarantees). The internal API has been reverted to the extent necessary for
cookie to compile. This measure is temporary; the internal change will be re-applied in an
yet-to-be-determined future release.

`v0.3.52`

Compare Source

Fixed

Subsecond values in the time! macro are parsed using the textual representation, ensuring
accuracy. Previously, they were parsed using the floating point representation, which could result
in a loss of precision and even invalid values.
The date! macro could previously create an invalid value that would then panic at compile time.
The macro now emits a proper error instead.
When parsing an invalid format description, an edge case would inadvertently panic. This now
returns an error as intended.

Added

Support default values when parsing

`v0.3.51`

Compare Source

Fixed

time compiles with macros enabled. This version is otherwise identical to v0.3.50.

`v0.3.50`

Compare Source

Fixed

time compiles with macros enabled. This version is otherwise identical to v0.3.50.

`v0.3.49`

Compare Source

Fixed

Due to a long-standing bug in the Rust compiler, v0.3.48 caused a number of crates to stop
compiling. A patch has been added that avoids triggering the bug.

`v0.3.48`

Compare Source

Security

The number of digits parsed by [subsecond digits:1+] is capped at 32 to avoid parsing unbounded
user input. Digits after the 9^th have no semantic meaning.
Explicitly specify #[repr] for Weekday. The value of the variants is relied upon in multiple
locations for soundness. The practical effect of this change is nothing, as Rust has always mapped
C-like enums to 0..N in memory.

Compatibility

Non-UTF-8 formatting and parsing is deprecated without replacement. It is recommended to only
format and parse valid UTF-8.
format_description::parse is deprecated. It is recommended to use
format_description::parse_borrowed::<3> or format_description::parse_owned::<3>.

Added

All types in the unit module have a generic parameter, though this is currently not used for
much. Usage will be expanded in the future.
Comparisons between types in the unit module and the generic Unit type are permitted.
Support for rand 0.10
Version 3 format descriptions
- Only UTF-8 is supported. As a side effect of this, [ignore] requires that the remaining input
  not begin mid-codepoint.
- Representation is deliberately opaque to allow for arbitrary changes going forward.
- format:false is supported on [optional] components. This is not possible in version 1 and
  version 2 format descriptions due to API compatibility.
- The time::serde::format_description! macro uses a new, clearer syntax for version 3.
  - time::serde::format_description!(mod foo [Date] = "[year]-[month]-[day]");
  - Unlike version 1 and version 2 format descriptions, the type is not automatically brought into
    scope. You must import it yourself.
- Nonsensical combinations of modifiers are rejected. For example, you cannot specify
  case-sensitivity when parsing a numerical month.
- [year] defaults to range:standard
- Components and modifiers are case sensitive (and always lowercase).

Changed

The convert module has been renamed to unit.

Fixed

Macro hygiene has been improved by specifying re-exports.
Fix handling of T in ISO 8601
Support parsing the full range of UTC offset hours
Version 1 nested format descriptions may now start with a component. Previously, a lexer bug
unintentionally prohibited this.
Error when ISO week date overflows the max year. This would previously panic.
Error when padding is specified in strftime format descriptions but the component is not. This
would previously panic.

Performance

Huge performance gains across multiple areas, including:

optimizing equality checks for Duration
optimizing Display impls for all major types
optimizing the formatting of components and well-known formats
precomputing metadata when formatting, reducing allocations
adding fast path for typical RFC 2822 usage
optimizing strftime parsing
refactoring format description parsing

Depending on the area, gains range from 3× to even 11×.

`v0.3.47`

Compare Source

Security

The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been
eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now,
the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable
limit.

This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format.

Compatibility

Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will
error at compile time if the type being formatted does not provide sufficient information. This
would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is
only configured for parsing (i.e. Iso8601::PARSING) will error at compile time.

Added

Builder methods for format description modifiers, eliminating the need for verbose initialization
when done manually.
date!(2026-W01-2) is now supported. Previously, a space was required between W and 01.
[end] now has a trailing_input modifier which can either be prohibit (the default) or
discard. When it is discard, all remaining input is ignored. Note that if there are components
after [end], they will still attempt to be parsed, likely resulting in an error.

Changed

More performance gains when parsing.

Fixed

If manually formatting a value, the number of bytes written was one short for some components.
This has been fixed such that the number of bytes written is always correct.
The possibility of integer overflow when parsing an owned format description has been effectively
eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the
depth as u8, it is stored as u32. This would require multiple gigabytes of nested input to
overflow, at which point we've got other problems and trivial mitigations are available by
downstream users.

`v0.3.46`

Compare Source

Added

All possible panics are now documented for the relevant methods.
The need to use #[serde(default)] when using custom serde formats is documented. This applies
only when deserializing an Option<T>.
Duration::nanoseconds_i128 has been made public, mirroring
std::time::Duration::from_nanos_u128.
Various methods for truncating components have been added, avoiding the need to call the fallible
replace methods multiple times.

For PrimitiveDateTime, UtcDateTime, and OffsetDateTime:
- truncate_to_day
For Time, PrimitiveDateTime, UtcDateTime, and OffsetDateTime:
- truncate_to_hour
- truncate_to_minute
- truncate_to_second
- truncate_to_millisecond
- truncate_to_microsecond

Changed

The minimum supported Rust version is now 1.88.0.
Significant performance gains in numerous locations. No public APIs were changed or removed as
part of this.
The size of error::ComponentRange, along with types that contain it, has been significantly
reduced.

Fixed

The PartialOrd and Ord implementations of UtcOffset now return the expected result.

`v0.3.45`

Compare Source

Added

time::format_description::StaticFormatDescription type alias for &'static [BorrowedFormatItem<'static>]. This is the type returned by the
time::macros::format_description! macro.

Changed

The minimum supported Rust version is now 1.83.0.
All floating point methods on Duration are now const fn.
All setters on Parsed are now const fn.
The serde dependency has been replaced with serde_core, This reduces compile times by not
including unused parts of serde.
Date::from_julian_day uses a new algorithm, resulting in an approximately 16% performance
improvement. This method is used internally by numerous other methods.
util::is_leap_year uses a new algorithm, resulting in an approximately 8% performance
improvement.

tokio-rs/tokio (tokio)

`v1.53.1`: Tokio v1.53.1

Compare Source

1.53.1 (July 20th, 2026)

Fixed

signal: restore MSRV by removing OnceLock::wait from the Windows handler (#8300)

Fixed (unstable)

time: fix alt timer cancellation and insertion race (#8252)

Documented

runtime: remove dead link definition in Runtime::block_on (#8301)

`v1.53.0`: Tokio v1.53.0

Compare Source

1.53.0 (July 17th, 2026)

Added

fs: implement From<OwnedFd> and From<OwnedHandle> for File (#8266)
metrics: add task schedule latency metric (#7986)
net: add SocketAddr methods to Unix sockets (#8144)

Changed

io: add #[inline] to IO trait impls for in-memory types (#8242)
net: implement UCred::pid on FreeBSD (#8086)
net: support Nuttx target os (#8259)
signal: refactor global variables on Windows (#8231)
sync: mpsc::{Receiver,UnboundedReceiver} now drops waker on drop, even if there are still senders (#8095)
taskdump: support taskdumps on s390x (#8192)
time: add #[track_caller] to timeout_at() (#8077)
time: consolidate mutex locks on spurious poll (#8124)
time: defer waker clone on spurious poll (#8107)
time: move lazy-registration state into Sleep (#8132)
tracing: remove unnecessary span clone (#8126)

Fixed

io: do not treat zero-length reads as EOF in Chain (#8251)
net: use getpeereid for QNX peer credentials (#8270)
runtime: avoid illegal state in FastRand (#8078)
sync: wake mpsc receiver when a queued reserve[_many] returns permits (#8260)
taskdump: skip double wake on Trace::capture/Trace::trace_with (#8043)
time: avoid stack overflow in runtime constructor (#8093)
time (alt timer): ensure timers stay in the same runtime after .reset() (#8169)

IO uring (unstable)

fs: use io-uring for fs::try_exists (#8080)
fs: use io-uring for renaming files (#7800)
rt: flush io-uring CQE in case of CQE overflow (#8277)

Documented

docs: clarify cancel safety wording (#8181)
fs: clarify create_dir_all succeeds if path exists (#8149)
io: add warning about stdout reordering with multiple handles (#8276)
net: document pipe try_read*/try_write* readiness behavior (#8032)
runtime: document interaction with fork() (#8202)
sync: clarify broadcast lagging semantics (#8239)
sync: document memory ordering guarantees for Semaphore (#8119)
task: explain why yield_now defers its waker (#8254)
time: add panic docs to timeout_at() (#8077)
time: fix reversed poll order in timeout doc (#8214)

`v1.52.4`: Tokio v1.52.4

Compare Source

1.52.4 (July 16th, 2026)

Fixed

runtime: don't skip the driver when before_park schedules work (#8222)

Fixed (unstable)

taskdump: remove crate disambiguators from output (#8264)

`v1.52.3`: Tokio v1.52.3

Compare Source

1.52.3 (May 8th, 2026)

Fixed

sync: fix underflow in mpsc channel len() (#8062)
sync: notify receivers in mpsc OwnedPermit::release() method (#8075)
sync: require that an RwLock has max_readers != 0 (#8076)
sync: return Empty from try_recv() when mpsc is closed with outstanding permits (#8074)

`v1.52.2`: Tokio v1.52.2

Compare Source

1.52.2 (May 4th, 2026)

This release reverts the LIFO slot stealing change introduced in 1.51.0 (#7431), due to its performance impact. (#8100)

`v1.52.1`: Tokio v1.52.1

Compare Source

1.52.1 (April 16th, 2026)

Fixed

runtime: revert #7757 to fix a regression that causes spawn_blocking to hang (#8057)

`v1.52.0`: Tokio v1.52.0

Compare Source

1.52.0 (April 14th, 2026)

Added

io: AioSource::register_borrowed for I/O safety support (#7992)
net: add try_io function to unix::pipe sender and receiver types (#8030)

Added (unstable)

runtime: Builder::enable_eager_driver_handoff setting enable eager hand off of the I/O and time drivers before polling tasks (#8010)
taskdump: add trace_with() for customized task dumps (#8025)
taskdump: allow impl FnMut() in trace_with instead of just fn() (#8040)
fs: support io_uring in AsyncRead for File (#7907)

Changed

runtime: improve spawn_blocking scalability with sharded queue (#7757)
runtime: use compare_exchange_weak() in worker queue (#8028)

Fixed

runtime: overflow second half of tasks when local queue is filled instead of first half (#8029)

Documented

docs: fix typo in oneshot::Sender::send docs (#8026)
docs: hide #[tokio::main] attribute in the docs of sync::watch (#8035)
net: add docs on ConnectionRefused errors with UDP sockets (#7870)

`v1.51.4`: Tokio v1.51.4

Compare Source

1.51.4 (July 16th, 2026)

Fixed

runtime: don't skip the driver when before_park schedules work (#8222)

`v1.51.3`: Tokio v1.51.3

Compare Source

1.51.3 (May 8th, 2026)

Fixed

sync: fix underflow in mpsc channel len() (#8062)
sync: notify receivers in mpsc OwnedPermit::release() method (#8075)
sync: require that an RwLock has max_readers != 0 (#8076)
sync: return Empty from try_recv() when mpsc is closed with outstanding permits (#8074)

`v1.51.2`: Tokio v1.51.1

Compare Source

1.51.2 (May 4th, 2026)

This release reverts the LIFO slot stealing change introduced in 1.51.0 (#7431), due to its performance impact. (#8100)

`v1.51.1`: Tokio v1.51.1

Compare Source

1.51.1 (April 8th, 2026)

Fixed

sync: fix semaphore reopens after forget (#8021)
net: surface errors from SO_ERROR on recv for UDP sockets on Linux (#8001)

Fixed (unstable)

metrics: fix worker_local_schedule_count test (#8008)
rt: do not leak fd when cancelling io_uring open operation (#7983)

`v1.51.0`: Tokio v1.51.0

Compare Source

1.51.0 (April 3rd, 2026)

Added

net: implement get_peer_cred on Hurd (#7989)
runtime: add tokio::runtime::worker_index() (#7921)
runtime: add runtime name (#7924)
runtime: stabilize LocalRuntime (#7557)
wasm: add wasm32-wasip2 networking support (#7933)

Changed

runtime: steal tasks from the LIFO slot (#7431)

Fixed

docs: do not show "Available on non-loom only." doc label (#7977)
macros: improve overall macro hygiene (#7997)
sync: fix notify_waiters priority in Notify (#7996)
sync: fix panic in Chan::recv_many when called with non-empty vector on closed channel (#7991)

`v1.50.0`: Tokio v1.50.0

Compare Source

1.50.0 (Mar 3rd, 2026)

Added

net: add TcpStream::set_zero_linger (#7837)
rt: add is_rt_shutdown_err (#7771)

Changed

io: add optimizer hint that memchr returns in-bounds pointer (#7792)
io: implement vectored writes for write_buf (#7871)
runtime: panic when event_interval is set to 0 (#7838)
runtime: shorten default thread name to fit in Linux limit (#7880)
signal: remember the result of SetConsoleCtrlHandler (#7833)
signal: specialize windows Registry (#7885)

Fixed

io: always cleanup AsyncFd registration list on deregister (#7773)
macros: remove (most) local use declarations in tokio::select! (#7929)
net: fix GET_BUF_SIZE constant for target_os = "android" (#7889)
runtime: avoid redundant unpark in current_thread scheduler (#7834)
runtime: don't park in current_thread if before_park defers waker (#7835)
io: fix write readiness on ESP32 on short writes (#7872)
runtime: wake deferred tasks before entering block_in_place (#7879)
sync: drop rx waker when oneshot receiver is dropped (#7886)
runtime: fix double increment of num_idle_threads on shutdown (#7910, #7918, #7922)

Unstable

fs: check for io-uring opcode support (#7815)
runtime: avoid lock acquisition after uring init (#7850)

Documented

docs: update outdated unstable features section (#7839)
io: clarify the behavior of AsyncWriteExt::shutdown() (#7908)
io: explain how to flush stdout/stderr (#7904)
io: fix incorrect and confusing AsyncWrite documentation (#7875)
rt: clarify the documentation of Runtime::spawn (#7803)
rt: fix missing quotation in docs (#7925)
runtime: correct the default thread name in docs (#7896)
runtime: fix event_interval doc (#7932)
sync: clarify RwLock fairness documentation (#7919)
sync: clarify that recv returns None once closed and no more messages (#7920)
task: clarify when to use spawn_blocking vs dedicated threads (#7923)
task: doc that task drops before JoinHandle completion (#7825)
signal: guarantee that listeners never return None (#7869)
task: fix task module feature flags in docs (#7891)
task: fix two typos (#7913)
task: improve the docs of Builder::spawn_local (#7828)
time: add docs about auto-advance and when to use sleep (#7858)
util: fix typo in docs (#7926)

`v1.49.0`: Tokio v1.49.0

Compare Source

1.49.0 (January 3rd, 2026)

Added

net: add support for TCLASS option on IPv6 (#7781)
runtime: stabilize runtime::id::Id (#7125)
task: implement Extend for JoinSet (#7195)
task: stabilize the LocalSet::id() (#7776)

Changed

net: deprecate {TcpStream,TcpSocket}::set_linger (#7752)

Fixed

macros: fix the hygiene issue of join! and try_join! (#7766)
runtime: revert "replace manual vtable definitions with Wake" (#7699)
sync: return TryRecvError::Disconnected from Receiver::try_recv after Receiver::close (#7686)
task: remove unnecessary trait bounds on the Debug implementation (#7720)

Unstable

fs: handle EINTR in fs::write for io-uring (#7786)
fs: support io-uring with tokio::fs::read (#7696)
runtime: disable io-uring on EPERM (#7724)
time: add alternative timer for better multicore scalability (#7467)

Documented

docs: fix a typos in bounded.rs and park.rs (#7817)
io: add SyncIoBridge cross-references to copy and copy_buf (#7798)
io: doc that AsyncWrite does not inherit from std::io::Write (#7705)
metrics: clarify that num_alive_tasks is not strongly consistent (#7614)
net: clarify the cancellation safety of the TcpStream::peek (#7305)
net: clarify the drop behavior of unix::OwnedWriteHalf (#7742)
net: clarify the platform-dependent backlog in TcpSocket docs (#7738)
runtime: mention LocalRuntime in new_current_thread docs (#7820)
sync: add missing period to mpsc::Sender::try_send docs (#7721)
sync: clarify the cancellation safety of oneshot::Receiver (#7780)
sync: improve the docs for the errors of mpsc (#7722)
task: add example for spawn_local usage on local runtime (#7689)

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.

👻 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 has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [anyhow](https://github.com/dtolnay/anyhow) | dependencies | patch | `1.0.100` → `1.0.104` | | [clap](https://github.com/clap-rs/clap) | dependencies | minor | `4.5.53` → `4.6.7` | | [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry)) | dependencies | minor | `0.31.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)) | dependencies | minor | `0.31.0` → `0.33.0` | | [opentelemetry-semantic-conventions](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-semantic-conventions) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry-semantic-conventions)) | dependencies | minor | `0.31.0` → `0.33.0` | | [opentelemetry-stdout](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-stdout) ([source](https://github.com/open-telemetry/opentelemetry-rust/tree/HEAD/opentelemetry-stdout)) | dependencies | minor | `0.31.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)) | dependencies | minor | `0.31.0` → `0.33.0` | | [time](https://time-rs.github.io) ([source](https://github.com/time-rs/time)) | dependencies | patch | `0.3.44` → `0.3.55` | | [tokio](https://tokio.rs) ([source](https://github.com/tokio-rs/tokio)) | dependencies | minor | `1.48.0` → `1.53.1` | --- ### Release Notes <details> <summary>dtolnay/anyhow (anyhow)</summary> ### [`v1.0.104`](https://github.com/dtolnay/anyhow/releases/tag/1.0.104) [Compare Source](https://github.com/dtolnay/anyhow/compare/1.0.103...1.0.104) - Update `syn` dev-dependency to version 3 ### [`v1.0.103`](https://github.com/dtolnay/anyhow/releases/tag/1.0.103) [Compare Source](https://github.com/dtolnay/anyhow/compare/1.0.102...1.0.103) - Fix Stacked Borrows violation (UB) in `Error::downcast_mut` ([#451](https://github.com/dtolnay/anyhow/issues/451), [#452](https://github.com/dtolnay/anyhow/issues/452)) ### [`v1.0.102`](https://github.com/dtolnay/anyhow/releases/tag/1.0.102) [Compare Source](https://github.com/dtolnay/anyhow/compare/1.0.101...1.0.102) - Remove backtrace dependency ([#438](https://github.com/dtolnay/anyhow/issues/438), [#439](https://github.com/dtolnay/anyhow/issues/439), [#440](https://github.com/dtolnay/anyhow/issues/440), [#441](https://github.com/dtolnay/anyhow/issues/441), [#442](https://github.com/dtolnay/anyhow/issues/442)) ### [`v1.0.101`](https://github.com/dtolnay/anyhow/releases/tag/1.0.101) [Compare Source](https://github.com/dtolnay/anyhow/compare/1.0.100...1.0.101) - Add #\[inline] to anyhow::Ok helper ([#437](https://github.com/dtolnay/anyhow/issues/437), thanks [@Ibitier](https://github.com/Ibitier)) </details> <details> <summary>clap-rs/clap (clap)</summary> ### [`v4.6.7`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#467---2026-09-14) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.6...v4.6.7) ##### Features - *(derive)* Add `#[command(defer = <bool>)]` attribute to opt-in to lazy initialisation of subcommands ### [`v4.6.6`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#466---2026-08-06) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.5...v4.6.6) ##### Features - Add `Command::get_overridden_usage` ### [`v4.6.5`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#465---2026-07-31) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.4...v4.6.5) ##### Fixes - *(help)* Correctly mark which `value_names` are optional with `num_args` ### [`v4.6.4`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#464---2026-07-21) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.3...v4.6.4) ##### Internal - Update to syn v3 ### [`v4.6.3`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#463---2026-07-20) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.2...v4.6.3) ##### Fixes - *(derive)* Allow `"literal".function()` as attribute values ### [`v4.6.2`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#462---2026-07-15) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.1...v4.6.2) ##### Fixes - *(help)* Say `alias` when there is only one ### [`v4.6.1`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#461---2026-04-15) [Compare Source](https://github.com/clap-rs/clap/compare/v4.6.0...v4.6.1) ##### Fixes - *(derive)* Ensure rebuilds happen when an read env variable is changed ### [`v4.6.0`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#460---2026-03-12) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.61...v4.6.0) ##### Compatibility - Update MSRV to 1.85 ### [`v4.5.61`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4561---2026-03-12) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.60...v4.5.61) ##### Internal - Update dependencies ### [`v4.5.60`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4560---2026-02-19) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.59...v4.5.60) ##### Fixes - *(help)* Quote empty default values, possible values ### [`v4.5.59`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4559---2026-02-16) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.58...v4.5.59) ##### Fixes - `Command::ignore_errors` no longer masks help/version on subcommands ### [`v4.5.58`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4558---2026-02-11) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.57...v4.5.58) ### [`v4.5.57`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4557---2026-02-03) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.56...v4.5.57) ##### Fixes - Regression from 4.5.55 where having an argument with `.value_terminator("--")` caused problems with an argument with `.last(true)` ### [`v4.5.56`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4556---2026-01-29) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.55...v4.5.56) ##### Fixes - On conflict error, don't show conflicting arguments in the usage ### [`v4.5.55`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4555---2026-01-27) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.54...v4.5.55) ##### Fixes - Fix inconsistency in precedence between positionals with a `value_terminator("--")` and escapes (`--`) where `./foo -- bar` means the first arg is empty, rather than escaping future args ### [`v4.5.54`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4554---2026-01-02) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.53...v4.5.54) ##### Fixes - *(help)* Move `[default]` to its own paragraph when `PossibleValue::help` is present in `--help` </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry)</summary> ### [`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. - Fix a panic when a value stored with `Context::with_value()` calls `Context::current()` from its `Drop` implementation. ### [`v0.32.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry/CHANGELOG.md#0320) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-0.32.0) 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][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][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](https://github.com/open-telemetry/opentelemetry-rust/pull/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][3262]). [3227]: https://github.com/open-telemetry/opentelemetry-rust/pull/3227 [3262]: https://github.com/open-telemetry/opentelemetry-rust/pull/3262 [3277]: https://github.com/open-telemetry/opentelemetry-rust/pull/3277 </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry-otlp)</summary> ### [`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. [#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. [#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. [#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. [#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. [#774](https://github.com/open-telemetry/opentelemetry-rust/issues/774) [#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. [#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) ### [`v0.32.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-otlp/CHANGELOG.md#0320) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-otlp-0.31.1...opentelemetry-otlp-0.32.0) 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](https://github.com/open-telemetry/opentelemetry-rust/pull/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](https://github.com/open-telemetry/opentelemetry-rust/issues/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](https://github.com/open-telemetry/opentelemetry-rust/issues/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](https://github.com/open-telemetry/opentelemetry-rust/issues/3021). [#3331](https://github.com/open-telemetry/opentelemetry-rust/issues/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](https://github.com/open-telemetry/opentelemetry-rust/issues/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](https://github.com/open-telemetry/opentelemetry-rust/issues/865) - Refactor `internal-logs` feature in `opentelemetry-otlp` to reduce unnecessary dependencies[3191](https://github.com/open-telemetry/opentelemetry-rust/pull/3192) - Fixed \[[#2777](https://github.com/open-telemetry/opentelemetry-rust/issues/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](https://github.com/open-telemetry/opentelemetry-rust/pull/3465) ### [`v0.31.1`](https://github.com/open-telemetry/opentelemetry-rust/releases/tag/opentelemetry-otlp-0.31.1): opentelemetry-otlp 0.31.1 [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-otlp-0.31.1) #### What's Changed - feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags \[patch release v0.31.1] by [@lalitb](https://github.com/lalitb) in [#3426](https://github.com/open-telemetry/opentelemetry-rust/pull/3426) **Full Changelog**: <https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-otlp-0.31.1> </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)</summary> ### [`v0.33.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-semantic-conventions/CHANGELOG.md#0330) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-semantic-conventions-0.32.1...opentelemetry-semantic-conventions-0.33.0) Released 2026-Sep-18 ### [`v0.32.1`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-semantic-conventions/CHANGELOG.md#0321) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-semantic-conventions-0.32.0...opentelemetry-semantic-conventions-0.32.1) Released 2026-Jun-26 - Update to [v1.42.0](https://github.com/open-telemetry/semantic-conventions/releases/tag/v1.42.0) of the semantic conventions. ### [`v0.32.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-semantic-conventions/CHANGELOG.md#0320) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-semantic-conventions-0.32.0) Released 2026-May-08 </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry-stdout)</summary> ### [`v0.33.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-stdout/CHANGELOG.md#0330) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/opentelemetry-stdout-0.32.0...opentelemetry-stdout-0.33.0) Released 2026-Sep-18 ### [`v0.32.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-stdout/CHANGELOG.md#0320) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-stdout-0.32.0) Released 2026-May-08 - ExponentialHistogram supported in stdout </details> <details> <summary>open-telemetry/opentelemetry-rust (opentelemetry_sdk)</summary> ### [`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. ([#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. ([#3514](https://github.com/open-telemetry/opentelemetry-rust/pull/3514), [#3608](https://github.com/open-telemetry/opentelemetry-rust/pull/3608), [#3609](https://github.com/open-telemetry/opentelemetry-rust/pull/3609), [#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. ([#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 ([#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. ### [`v0.32.1`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-sdk/CHANGELOG.md#0321) Released 2026-May-23 - `BaggagePropagator` now enforces the W3C Baggage maximum header length (8192 bytes) and maximum list-member count (64) when extracting an inbound `baggage` header. Headers exceeding 8192 bytes are dropped at the propagator boundary; headers with more than 64 list members are truncated to the first 64 entries. The change keeps the propagator from parsing attacker-controlled input beyond the W3C limits instead of doing per-entry parse, decode, and allocation work only to discard the excess on `Baggage` insert. See <https://www.w3.org/TR/baggage/#limits>. - Reverted the `SimpleSpanProcessor` telemetry suppression added in 0.32.0 (see [#3494](https://github.com/open-telemetry/opentelemetry-rust/issues/3494)), which caused a `RefCell already borrowed` panic when a span was started and dropped inside a `get_active_span` (or `Context::map_current`) closure. Tracked in [#3510](https://github.com/open-telemetry/opentelemetry-rust/issues/3510). A proper fix for the underlying `Context::map_current` re-entrancy will be investigated separately, after which the suppression can be safely re-applied. - View-provided metric stream `name` (set via `Stream::builder().with_name(...)`) is no longer validated against the instrument name syntax, per [spec clarification](https://github.com/open-telemetry/opentelemetry-specification/pull/5094). `unit` and other stream parameters continue to be validated. ### [`v0.32.0`](https://github.com/open-telemetry/opentelemetry-rust/blob/HEAD/opentelemetry-sdk/CHANGELOG.md#0320) [Compare Source](https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry_sdk-0.32.0) Released 2026-May-08 - `SimpleSpanProcessor` now suppresses telemetry during export, preventing telemetry-induced-telemetry feedback loops. This aligns with the existing behavior in `BatchSpanProcessor` and `SimpleLogProcessor`. - Removed `SimpleConcurrentLogProcessor` and the `experimental_logs_concurrent_log_processor` feature flag. The use cases it was designed for (ETW/user\_events exporters) are better served by modeling those exporters as processors directly. - **Added** `Counter::bind()` and `Histogram::bind()` SDK implementations that return pre-bound measurement handles (`BoundCounter<T>`, `BoundHistogram<T>`). Bound instruments resolve the attribute-to-aggregator mapping once at bind time and cache the result, eliminating per-call HashMap lookups. View attribute filtering is applied at bind time so the hot path stays free of per-call attribute processing. Bound and unbound recordings with the same (post-view) attribute set always aggregate into the same data point, including the empty attribute set. Bound entries are never evicted during delta collection while a handle exists — idle cycles produce no export but the tracker persists. If `bind()` is called at the cardinality limit, the handle binds directly to the overflow tracker — its writes stay on the same direct (no-lookup) hot path and consistently land in the `otel.metric.overflow=true` bucket for the lifetime of the handle. To recover a bound handle after delta collection frees space, drop the existing handle and call `bind()` again. Gated behind the `experimental_metrics_bound_instruments` feature flag. Benchmarks show \~28x speedup for counter operations and \~9x for histograms. - Delta metrics collection now uses in-place eviction instead of draining the HashMap on every collect cycle. Stale attribute sets that received no measurements since the last collection are evicted. Note: recovery from cardinality overflow now requires 2 collect cycles — the first marks entries as stale, the second evicts them. - **Breaking** The SDK `testing` feature is now runtime agnostic. [#3407][3407] - `TokioSpanExporter` and `new_tokio_test_exporter` have been renamed to `TestSpanExporter` and `new_test_exporter`. - The following transitive dependencies and features have been removed: `tokio/rt`, `tokio/time`, `tokio/macros`, `tokio/rt-multi-thread`, `tokio-stream`, `experimental_async_runtime` - Store `InstrumentationScope` in `Arc` internally in `SdkTracer`, making tracer clones cheaper (Arc refcount increment instead of deep copy). - Add 32-bit platform support by using `portable-atomic` for `AtomicI64` and `AtomicU64` in the metrics module. This enables compilation on 32-bit ARM targets (e.g., `armv5te-unknown-linux-gnueabi`, `armv7-unknown-linux-gnueabihf`). - `Aggregation` enum and `StreamBuilder::with_aggregation()` are now stable and no longer require the `spec_unstable_metrics_views` feature flag. - Fix `service.name` Resource attribute fallback to follow OpenTelemetry specification by using `unknown_service:<process.executable.name>` format when service name is not explicitly configured. Previously, it only used `unknown_service`. - Fix `SpanExporter::shutdown()` default timeout from 5 nanoseconds to 5 seconds. - **Breaking** `SpanExporter` trait methods `shutdown`, `shutdown_with_timeout`, and `force_flush` now take `&self` instead of `&mut self` for consistency with `LogExporter` and `PushMetricExporter`. Implementers using interior mutability (e.g., `Mutex`, `AtomicBool`) require no changes. - Added `Resource::get_ref(&self, key: &Key) -> Option<&Value>` to allow retrieving a reference to a resource value without cloning. - **Breaking** Removed the following public hidden methods from the `SdkTracer` [#3227][3227]: - `id_generator`, `should_sample` - **Breaking** Moved the following SDK sampling types from `opentelemetry::trace` to `opentelemetry_sdk::trace` [#3277][3277]: - `SamplingDecision`, `SamplingResult` - These types are SDK implementation details and should be imported from `opentelemetry_sdk::trace` instead. - `StreamBuilder::build()` now rejects `usize::MAX` as a cardinality limit with a validation error. [#3506][3506] - Fix Histogram boundaries being ignored in the presence of views [#3312][3312] - `TracerProviderBuilder::with_sampler` allows to pass boxed instance of `ShouldSample` \[[#3313](https://github.com/open-telemetry/opentelemetry-rust/issues/3313)]\[3313] - Fix ObservableCounter and ObservableUpDownCounter now correctly report only data points from the current measurement cycle, removing stale attribute combinations that are no longer observed. [#3248][3248] - Fix panic when `SpanProcessor::on_end` calls `Context::current()` ([#3262][3262]). - Updated `SpanProcessor::on_end` documentation to clarify that `Context::current()` returns the parent context, not the span's context - Fix `traceparent` headers with unknown flags (e.g. W3C random-trace-id flag `0x02`) being incorrectly rejected. Unknown flags are now accepted and zeroed out as required by the W3C trace-context spec. [#3435][3435] - **Breaking** `InMemoryExporterError` has been removed and replaced by `OTelSdkError`, and a new `JaegerRemoteSamplerBuildError` introduced to replace last uses of `TraceError`. [#3458][3458] - "spec\_unstable\_logs\_enabled" feature flag is removed. The capability (and the backing specification) is now stable and is enabled by default. [#3278][3278] [3227]: https://github.com/open-telemetry/opentelemetry-rust/pull/3227 [3277]: https://github.com/open-telemetry/opentelemetry-rust/pull/3277 [3278]: https://github.com/open-telemetry/opentelemetry-rust/pull/3278 [3312]: https://github.com/open-telemetry/opentelemetry-rust/pull/3312 [3248]: https://github.com/open-telemetry/opentelemetry-rust/pull/3248 [3262]: https://github.com/open-telemetry/opentelemetry-rust/pull/3262 [3407]: https://github.com/open-telemetry/opentelemetry-rust/pull/3407 [3435]: https://github.com/open-telemetry/opentelemetry-rust/issues/3435 [3458]: https://github.com/open-telemetry/opentelemetry-rust/pull/3458 [3506]: https://github.com/open-telemetry/opentelemetry-rust/pull/3506 </details> <details> <summary>time-rs/time (time)</summary> ### [`v0.3.55`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0355-2026-08-01) [Compare Source](https://github.com/time-rs/time/compare/v0.3.54...v0.3.55) ##### Fixed - Avoid underflow in `DateIter::nth`, ensuring correct behavior. - Avoid overflow when deserializing timestamps. - Handle out-of-bounds data when deserializing. - Don't assume that the format being deserialized was generated by the serializer; this previously led to some valid values being parsed incorrectly and others being rejected. - No longer silence errors when deserializing `UtcOffset`. - `OffsetDateTime::from_unix_timestamp_nanos` and `UtcDateTime::from_unix_timestamp_nanos` correctly return `None` for all out-of-range values, rather than unexpectedly panicking in some situations. - `OffsetDateTime::checked_to_offset` and `UtcDateTime::checked_to_offset` correctly return `None` for all out-of-range values, rather than unexpectedly panicking in some situations. ### [`v0.3.54`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0354-2026-07-20) [Compare Source](https://github.com/time-rs/time/compare/v0.3.53...v0.3.54) ##### Added - `PrimitiveDateTime` has been renamed to `PlainDateTime`. - `Duration` has been renamed to `SignedDuration`. - Iteration is now possible over `Date`, `Month`, and `Weekday`. Relevant iterator methods have been overridden to ensure maximum performance. For both `PlainDateTime` and `SignedDuration`, a non-deprecated type alias has been added for backwards compatibility. The new names should be preferred. ##### Changed - The associated metadata type (for `powerfmt` implementations) for various types has been changed to `()` and made public. This guarantees that no additional metadata will be present. ##### Performance - More gains when parsing RFC 2822. ### [`v0.3.53`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0353-2026-07-01) [Compare Source](https://github.com/time-rs/time/compare/v0.3.52...v0.3.53) There are no publicly-facing changes in this release. It solely works around the `cookie` crate relying on an implementation detail of `time` that was never part of the public API (and thus subject to semver guarantees). The internal API has been reverted to the extent necessary for `cookie` to compile. This measure is temporary; the internal change will be re-applied in an yet-to-be-determined future release. ### [`v0.3.52`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0352-2026-06-30) [Compare Source](https://github.com/time-rs/time/compare/v0.3.51...v0.3.52) ##### Fixed - Subsecond values in the `time!` macro are parsed using the textual representation, ensuring accuracy. Previously, they were parsed using the floating point representation, which could result in a loss of precision and even invalid values. - The `date!` macro could previously create an invalid value that would then panic at compile time. The macro now emits a proper error instead. - When parsing an invalid format description, an edge case would inadvertently panic. This now returns an error as intended. ##### Added - Support default values when parsing ### [`v0.3.51`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0351-2026-06-22) [Compare Source](https://github.com/time-rs/time/compare/v0.3.50...v0.3.51) ##### Fixed - `time` compiles with `macros` enabled. This version is otherwise identical to v0.3.50. ### [`v0.3.50`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0351-2026-06-22) [Compare Source](https://github.com/time-rs/time/compare/v0.3.49...v0.3.50) ##### Fixed - `time` compiles with `macros` enabled. This version is otherwise identical to v0.3.50. ### [`v0.3.49`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0349-2026-06-13) [Compare Source](https://github.com/time-rs/time/compare/v0.3.48...v0.3.49) ##### Fixed - Due to a long-standing bug in the Rust compiler, v0.3.48 caused a number of crates to stop compiling. A patch has been added that avoids triggering the bug. ### [`v0.3.48`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0348-2026-06-12-YANKED) [Compare Source](https://github.com/time-rs/time/compare/v0.3.47...v0.3.48) ##### Security - The number of digits parsed by `[subsecond digits:1+]` is capped at 32 to avoid parsing unbounded user input. Digits after the 9<sup>th</sup> have no semantic meaning. - Explicitly specify `#[repr]` for `Weekday`. The value of the variants is relied upon in multiple locations for soundness. The practical effect of this change is nothing, as Rust has always mapped C-like `enum`s to 0..N in memory. ##### Compatibility - Non-UTF-8 formatting and parsing is deprecated without replacement. It is recommended to only format and parse valid UTF-8. - `format_description::parse` is deprecated. It is recommended to use `format_description::parse_borrowed::<3>` or `format_description::parse_owned::<3>`. ##### Added - All types in the `unit` module have a generic parameter, though this is currently not used for much. Usage will be expanded in the future. - Comparisons between types in the `unit` module and the generic `Unit` type are permitted. - Support for `rand` 0.10 - Version 3 format descriptions - Only UTF-8 is supported. As a side effect of this, `[ignore]` requires that the remaining input not begin mid-codepoint. - Representation is deliberately opaque to allow for arbitrary changes going forward. - `format:false` is supported on `[optional]` components. This is not possible in version 1 and version 2 format descriptions due to API compatibility. - The `time::serde::format_description!` macro uses a new, clearer syntax for version 3. - `time::serde::format_description!(mod foo [Date] = "[year]-[month]-[day]");` - Unlike version 1 and version 2 format descriptions, the type is not automatically brought into scope. You must import it yourself. - Nonsensical combinations of modifiers are rejected. For example, you cannot specify case-sensitivity when parsing a numerical month. - `[year]` defaults to `range:standard` - Components and modifiers are case sensitive (and always lowercase). ##### Changed - The `convert` module has been renamed to `unit`. ##### Fixed - Macro hygiene has been improved by specifying re-exports. - Fix handling of `T` in ISO 8601 - Support parsing the full range of UTC offset hours - Version 1 nested format descriptions may now start with a component. Previously, a lexer bug unintentionally prohibited this. - Error when ISO week date overflows the max year. This would previously panic. - Error when padding is specified in `strftime` format descriptions but the component is not. This would previously panic. ##### Performance Huge performance gains across multiple areas, including: - optimizing equality checks for `Duration` - optimizing `Display` impls for all major types - optimizing the formatting of components and well-known formats - precomputing metadata when formatting, reducing allocations - adding fast path for typical RFC 2822 usage - optimizing `strftime` parsing - refactoring format description parsing Depending on the area, gains range from 3× to even 11×. ### [`v0.3.47`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0347-2026-02-05) [Compare Source](https://github.com/time-rs/time/compare/v0.3.46...v0.3.47) ##### Security - The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now, the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable limit. This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format. ##### Compatibility - Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will error at compile time if the type being formatted does not provide sufficient information. This would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is only configured for parsing (i.e. `Iso8601::PARSING`) will error at compile time. ##### Added - Builder methods for format description modifiers, eliminating the need for verbose initialization when done manually. - `date!(2026-W01-2)` is now supported. Previously, a space was required between `W` and `01`. - `[end]` now has a `trailing_input` modifier which can either be `prohibit` (the default) or `discard`. When it is `discard`, all remaining input is ignored. Note that if there are components after `[end]`, they will still attempt to be parsed, likely resulting in an error. ##### Changed - More performance gains when parsing. ##### Fixed - If manually formatting a value, the number of bytes written was one short for some components. This has been fixed such that the number of bytes written is always correct. - The possibility of integer overflow when parsing an owned format description has been effectively eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the depth as `u8`, it is stored as `u32`. This would require multiple gigabytes of nested input to overflow, at which point we've got other problems and trivial mitigations are available by downstream users. ### [`v0.3.46`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0346-2026-01-23) [Compare Source](https://github.com/time-rs/time/compare/v0.3.45...v0.3.46) ##### Added - All possible panics are now documented for the relevant methods. - The need to use `#[serde(default)]` when using custom `serde` formats is documented. This applies only when deserializing an `Option<T>`. - `Duration::nanoseconds_i128` has been made public, mirroring `std::time::Duration::from_nanos_u128`. - Various methods for truncating components have been added, avoiding the need to call the fallible `replace` methods multiple times. For `PrimitiveDateTime`, `UtcDateTime`, and `OffsetDateTime`: - `truncate_to_day` For `Time`, `PrimitiveDateTime`, `UtcDateTime`, and `OffsetDateTime`: - `truncate_to_hour` - `truncate_to_minute` - `truncate_to_second` - `truncate_to_millisecond` - `truncate_to_microsecond` ##### Changed - The minimum supported Rust version is now 1.88.0. - Significant performance gains in numerous locations. No public APIs were changed or removed as part of this. - The size of `error::ComponentRange`, along with types that contain it, has been significantly reduced. ##### Fixed - The `PartialOrd` and `Ord` implementations of `UtcOffset` now return the expected result. ### [`v0.3.45`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0345-2026-01-13) [Compare Source](https://github.com/time-rs/time/compare/v0.3.44...v0.3.45) ##### Added - `time::format_description::StaticFormatDescription` type alias for `&'static [BorrowedFormatItem<'static>]`. This is the type returned by the `time::macros::format_description!` macro. ##### Changed - The minimum supported Rust version is now 1.83.0. - All floating point methods on `Duration` are now `const fn`. - All setters on `Parsed` are now `const fn`. - The `serde` dependency has been replaced with `serde_core`, This reduces compile times by not including unused parts of `serde`. - `Date::from_julian_day` uses a new algorithm, resulting in an approximately 16% performance improvement. This method is used internally by numerous other methods. - `util::is_leap_year` uses a new algorithm, resulting in an approximately 8% performance improvement. </details> <details> <summary>tokio-rs/tokio (tokio)</summary> ### [`v1.53.1`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.53.1): Tokio v1.53.1 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.53.0...tokio-1.53.1) ### 1.53.1 (July 20th, 2026) ##### Fixed - signal: restore MSRV by removing `OnceLock::wait` from the Windows handler ([#8300]) ##### Fixed (unstable) - time: fix alt timer cancellation and insertion race ([#8252]) ##### Documented - runtime: remove dead link definition in Runtime::block\_on ([#8301]) [#8252]: https://github.com/tokio-rs/tokio/pull/8252 [#8300]: https://github.com/tokio-rs/tokio/pull/8300 [#8301]: https://github.com/tokio-rs/tokio/pull/8301 ### [`v1.53.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.53.0): Tokio v1.53.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.52.4...tokio-1.53.0) ### 1.53.0 (July 17th, 2026) ##### Added - fs: implement `From<OwnedFd>` and `From<OwnedHandle>` for `File` ([#8266]) - metrics: add task schedule latency metric ([#7986]) - net: add `SocketAddr` methods to Unix sockets ([#8144]) ##### Changed - io: add `#[inline]` to IO trait impls for in-memory types ([#8242]) - net: implement UCred::pid on FreeBSD ([#8086]) - net: support Nuttx target os ([#8259]) - signal: refactor global variables on Windows ([#8231]) - sync: `mpsc::{Receiver,UnboundedReceiver}` now drops waker on drop, even if there are still senders ([#8095]) - taskdump: support taskdumps on s390x ([#8192]) - time: add `#[track_caller]` to `timeout_at()` ([#8077]) - time: consolidate mutex locks on spurious poll ([#8124]) - time: defer waker clone on spurious poll ([#8107]) - time: move lazy-registration state into `Sleep` ([#8132]) - tracing: remove unnecessary span clone ([#8126]) ##### Fixed - io: do not treat zero-length reads as EOF in `Chain` ([#8251]) - net: use getpeereid for QNX peer credentials ([#8270]) - runtime: avoid illegal state in `FastRand` ([#8078]) - sync: wake mpsc receiver when a queued `reserve[_many]` returns permits ([#8260]) - taskdump: skip double wake on `Trace::capture`/`Trace::trace_with` ([#8043]) - time: avoid stack overflow in runtime constructor ([#8093]) - time (alt timer): ensure timers stay in the same runtime after `.reset()` ([#8169]) ##### IO uring (unstable) - fs: use io-uring for `fs::try_exists` ([#8080]) - fs: use io-uring for renaming files ([#7800]) - rt: flush io-uring CQE in case of CQE overflow ([#8277]) ##### Documented - docs: clarify cancel safety wording ([#8181]) - fs: clarify `create_dir_all` succeeds if path exists ([#8149]) - io: add warning about stdout reordering with multiple handles ([#8276]) - net: document pipe `try_read*`/`try_write*` readiness behavior ([#8032]) - runtime: document interaction with fork() ([#8202]) - sync: clarify broadcast lagging semantics ([#8239]) - sync: document memory ordering guarantees for Semaphore ([#8119]) - task: explain why `yield_now` defers its waker ([#8254]) - time: add panic docs to `timeout_at()` ([#8077]) - time: fix reversed poll order in timeout doc ([#8214]) [#7800]: https://github.com/tokio-rs/tokio/pull/7800 [#7986]: https://github.com/tokio-rs/tokio/pull/7986 [#8032]: https://github.com/tokio-rs/tokio/pull/8032 [#8043]: https://github.com/tokio-rs/tokio/pull/8043 [#8077]: https://github.com/tokio-rs/tokio/pull/8077 [#8078]: https://github.com/tokio-rs/tokio/pull/8078 [#8080]: https://github.com/tokio-rs/tokio/pull/8080 [#8086]: https://github.com/tokio-rs/tokio/pull/8086 [#8093]: https://github.com/tokio-rs/tokio/pull/8093 [#8095]: https://github.com/tokio-rs/tokio/pull/8095 [#8107]: https://github.com/tokio-rs/tokio/pull/8107 [#8119]: https://github.com/tokio-rs/tokio/pull/8119 [#8124]: https://github.com/tokio-rs/tokio/pull/8124 [#8126]: https://github.com/tokio-rs/tokio/pull/8126 [#8132]: https://github.com/tokio-rs/tokio/pull/8132 [#8144]: https://github.com/tokio-rs/tokio/pull/8144 [#8149]: https://github.com/tokio-rs/tokio/pull/8149 [#8169]: https://github.com/tokio-rs/tokio/pull/8169 [#8181]: https://github.com/tokio-rs/tokio/pull/8181 [#8192]: https://github.com/tokio-rs/tokio/pull/8192 [#8193]: https://github.com/tokio-rs/tokio/pull/8193 [#8202]: https://github.com/tokio-rs/tokio/pull/8202 [#8214]: https://github.com/tokio-rs/tokio/pull/8214 [#8231]: https://github.com/tokio-rs/tokio/pull/8231 [#8239]: https://github.com/tokio-rs/tokio/pull/8239 [#8242]: https://github.com/tokio-rs/tokio/pull/8242 [#8251]: https://github.com/tokio-rs/tokio/pull/8251 [#8254]: https://github.com/tokio-rs/tokio/pull/8254 [#8259]: https://github.com/tokio-rs/tokio/pull/8259 [#8260]: https://github.com/tokio-rs/tokio/pull/8260 [#8266]: https://github.com/tokio-rs/tokio/pull/8266 [#8270]: https://github.com/tokio-rs/tokio/pull/8270 [#8276]: https://github.com/tokio-rs/tokio/pull/8276 [#8277]: https://github.com/tokio-rs/tokio/pull/8277 ### [`v1.52.4`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.52.4): Tokio v1.52.4 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.52.3...tokio-1.52.4) ### 1.52.4 (July 16th, 2026) ##### Fixed - runtime: don't skip the driver when `before_park` schedules work ([#8222]) ##### Fixed (unstable) - taskdump: remove crate disambiguators from output ([#8264]) [#8264]: https://github.com/tokio-rs/tokio/pull/8264 [#8222]: https://github.com/tokio-rs/tokio/pull/8222 ### [`v1.52.3`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.52.3): Tokio v1.52.3 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.52.2...tokio-1.52.3) ### 1.52.3 (May 8th, 2026) ##### Fixed - sync: fix underflow in mpsc channel `len()` ([#8062]) - sync: notify receivers in mpsc `OwnedPermit::release()` method ([#8075]) - sync: require that an `RwLock` has `max_readers != 0` ([#8076]) - sync: return `Empty` from `try_recv()` when mpsc is closed with outstanding permits ([#8074]) [#8062]: https://github.com/tokio-rs/tokio/pull/8062 [#8074]: https://github.com/tokio-rs/tokio/pull/8074 [#8075]: https://github.com/tokio-rs/tokio/pull/8075 [#8076]: https://github.com/tokio-rs/tokio/pull/8076 ### [`v1.52.2`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.52.2): Tokio v1.52.2 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.52.1...tokio-1.52.2) ### 1.52.2 (May 4th, 2026) This release reverts the LIFO slot stealing change introduced in 1.51.0 ([#7431]), due to [its performance impact][#8065]. ([#8100]) [#7431]: https://github.com/tokio-rs/tokio/pull/7431 [#8065]: https://github.com/tokio-rs/tokio/pull/8065 [#8100]: https://github.com/tokio-rs/tokio/pull/8100 ### [`v1.52.1`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.52.1): Tokio v1.52.1 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.52.0...tokio-1.52.1) ### 1.52.1 (April 16th, 2026) #### Fixed - runtime: revert [#7757] to fix [a regression][#8056] that causes `spawn_blocking` to hang ([#8057]) [#7757]: https://github.com/tokio-rs/tokio/pull/7757 [#8056]: https://github.com/tokio-rs/tokio/pull/8056 [#8057]: https://github.com/tokio-rs/tokio/pull/8057 ### [`v1.52.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.52.0): Tokio v1.52.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.51.4...tokio-1.52.0) ### 1.52.0 (April 14th, 2026) #### Added - io: `AioSource::register_borrowed` for I/O safety support ([#7992]) - net: add `try_io` function to `unix::pipe` sender and receiver types ([#8030]) #### Added (unstable) - runtime: `Builder::enable_eager_driver_handoff` setting enable eager hand off of the I/O and time drivers before polling tasks ([#8010]) - taskdump: add `trace_with()` for customized task dumps ([#8025]) - taskdump: allow `impl FnMut()` in `trace_with` instead of just `fn()` ([#8040]) - fs: support `io_uring` in `AsyncRead` for `File` ([#7907]) #### Changed - runtime: improve `spawn_blocking` scalability with sharded queue ([#7757]) - runtime: use `compare_exchange_weak()` in worker queue ([#8028]) #### Fixed - runtime: overflow second half of tasks when local queue is filled instead of first half ([#8029]) #### Documented - docs: fix typo in `oneshot::Sender::send` docs ([#8026]) - docs: hide #\[tokio::main] attribute in the docs of `sync::watch` ([#8035]) - net: add docs on `ConnectionRefused` errors with UDP sockets ([#7870]) [#7757]: https://github.com/tokio-rs/tokio/pull/7757 [#7870]: https://github.com/tokio-rs/tokio/pull/7870 [#7907]: https://github.com/tokio-rs/tokio/pull/7907 [#7992]: https://github.com/tokio-rs/tokio/pull/7992 [#8010]: https://github.com/tokio-rs/tokio/pull/8010 [#8025]: https://github.com/tokio-rs/tokio/pull/8025 [#8026]: https://github.com/tokio-rs/tokio/pull/8026 [#8028]: https://github.com/tokio-rs/tokio/pull/8028 [#8029]: https://github.com/tokio-rs/tokio/pull/8029 [#8030]: https://github.com/tokio-rs/tokio/pull/8030 [#8035]: https://github.com/tokio-rs/tokio/pull/8035 [#8040]: https://github.com/tokio-rs/tokio/pull/8040 ### [`v1.51.4`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.51.4): Tokio v1.51.4 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.51.3...tokio-1.51.4) ### 1.51.4 (July 16th, 2026) ##### Fixed - runtime: don't skip the driver when `before_park` schedules work ([#8222]) [#8222]: https://github.com/tokio-rs/tokio/pull/8222 ### [`v1.51.3`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.51.3): Tokio v1.51.3 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.51.2...tokio-1.51.3) ### 1.51.3 (May 8th, 2026) ##### Fixed - sync: fix underflow in mpsc channel `len()` ([#8062]) - sync: notify receivers in mpsc `OwnedPermit::release()` method ([#8075]) - sync: require that an `RwLock` has `max_readers != 0` ([#8076]) - sync: return `Empty` from `try_recv()` when mpsc is closed with outstanding permits ([#8074]) [#8062]: https://github.com/tokio-rs/tokio/pull/8062 [#8074]: https://github.com/tokio-rs/tokio/pull/8074 [#8075]: https://github.com/tokio-rs/tokio/pull/8075 [#8076]: https://github.com/tokio-rs/tokio/pull/8076 ### [`v1.51.2`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.51.2): Tokio v1.51.1 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.51.1...tokio-1.51.2) ### 1.51.2 (May 4th, 2026) This release reverts the LIFO slot stealing change introduced in 1.51.0 ([#7431]), due to [its performance impact][#8065]. ([#8100]) [#7431]: https://github.com/tokio-rs/tokio/pull/7431 [#8065]: https://github.com/tokio-rs/tokio/pull/8065 [#8100]: https://github.com/tokio-rs/tokio/pull/8100 ### [`v1.51.1`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.51.1): Tokio v1.51.1 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.51.0...tokio-1.51.1) ### 1.51.1 (April 8th, 2026) ##### Fixed - sync: fix semaphore reopens after forget ([#8021]) - net: surface errors from `SO_ERROR` on `recv` for UDP sockets on Linux ([#8001]) ##### Fixed (unstable) - metrics: fix `worker_local_schedule_count` test ([#8008]) - rt: do not leak fd when cancelling io\_uring open operation ([#7983]) [#7983]: https://github.com/tokio-rs/tokio/pull/7983 [#8001]: https://github.com/tokio-rs/tokio/pull/8001 [#8008]: https://github.com/tokio-rs/tokio/pull/8008 [#8021]: https://github.com/tokio-rs/tokio/pull/8021 ### [`v1.51.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.51.0): Tokio v1.51.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.50.0...tokio-1.51.0) ### 1.51.0 (April 3rd, 2026) ##### Added - net: implement `get_peer_cred` on Hurd ([#7989]) - runtime: add `tokio::runtime::worker_index()` ([#7921]) - runtime: add runtime name ([#7924]) - runtime: stabilize `LocalRuntime` ([#7557]) - wasm: add wasm32-wasip2 networking support ([#7933]) ##### Changed - runtime: steal tasks from the LIFO slot ([#7431]) ##### Fixed - docs: do not show "Available on non-loom only." doc label ([#7977]) - macros: improve overall macro hygiene ([#7997]) - sync: fix `notify_waiters` priority in `Notify` ([#7996]) - sync: fix panic in `Chan::recv_many` when called with non-empty vector on closed channel ([#7991]) [#7431]: https://github.com/tokio-rs/tokio/pull/7431 [#7557]: https://github.com/tokio-rs/tokio/pull/7557 [#7921]: https://github.com/tokio-rs/tokio/pull/7921 [#7924]: https://github.com/tokio-rs/tokio/pull/7924 [#7933]: https://github.com/tokio-rs/tokio/pull/7933 [#7977]: https://github.com/tokio-rs/tokio/pull/7977 [#7989]: https://github.com/tokio-rs/tokio/pull/7989 [#7991]: https://github.com/tokio-rs/tokio/pull/7991 [#7996]: https://github.com/tokio-rs/tokio/pull/7996 [#7997]: https://github.com/tokio-rs/tokio/pull/7997 ### [`v1.50.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.50.0): Tokio v1.50.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.49.0...tokio-1.50.0) ### 1.50.0 (Mar 3rd, 2026) ##### Added - net: add `TcpStream::set_zero_linger` ([#7837]) - rt: add `is_rt_shutdown_err` ([#7771]) ##### Changed - io: add optimizer hint that `memchr` returns in-bounds pointer ([#7792]) - io: implement vectored writes for `write_buf` ([#7871]) - runtime: panic when `event_interval` is set to 0 ([#7838]) - runtime: shorten default thread name to fit in Linux limit ([#7880]) - signal: remember the result of `SetConsoleCtrlHandler` ([#7833]) - signal: specialize windows `Registry` ([#7885]) ##### Fixed - io: always cleanup `AsyncFd` registration list on deregister ([#7773]) - macros: remove (most) local `use` declarations in `tokio::select!` ([#7929]) - net: fix `GET_BUF_SIZE` constant for `target_os = "android"` ([#7889]) - runtime: avoid redundant unpark in current\_thread scheduler ([#7834]) - runtime: don't park in `current_thread` if `before_park` defers waker ([#7835]) - io: fix write readiness on ESP32 on short writes ([#7872]) - runtime: wake deferred tasks before entering `block_in_place` ([#7879]) - sync: drop rx waker when oneshot receiver is dropped ([#7886]) - runtime: fix double increment of `num_idle_threads` on shutdown ([#7910], [#7918], [#7922]) ##### Unstable - fs: check for io-uring opcode support ([#7815]) - runtime: avoid lock acquisition after uring init ([#7850]) ##### Documented - docs: update outdated unstable features section ([#7839]) - io: clarify the behavior of `AsyncWriteExt::shutdown()` ([#7908]) - io: explain how to flush stdout/stderr ([#7904]) - io: fix incorrect and confusing `AsyncWrite` documentation ([#7875]) - rt: clarify the documentation of `Runtime::spawn` ([#7803]) - rt: fix missing quotation in docs ([#7925]) - runtime: correct the default thread name in docs ([#7896]) - runtime: fix `event_interval` doc ([#7932]) - sync: clarify RwLock fairness documentation ([#7919]) - sync: clarify that `recv` returns `None` once closed and no more messages ([#7920]) - task: clarify when to use `spawn_blocking` vs dedicated threads ([#7923]) - task: doc that task drops before `JoinHandle` completion ([#7825]) - signal: guarantee that listeners never return `None` ([#7869]) - task: fix task module feature flags in docs ([#7891]) - task: fix two typos ([#7913]) - task: improve the docs of `Builder::spawn_local` ([#7828]) - time: add docs about auto-advance and when to use sleep ([#7858]) - util: fix typo in docs ([#7926]) [#7771]: https://github.com/tokio-rs/tokio/pull/7771 [#7773]: https://github.com/tokio-rs/tokio/pull/7773 [#7792]: https://github.com/tokio-rs/tokio/pull/7792 [#7803]: https://github.com/tokio-rs/tokio/pull/7803 [#7815]: https://github.com/tokio-rs/tokio/pull/7815 [#7825]: https://github.com/tokio-rs/tokio/pull/7825 [#7828]: https://github.com/tokio-rs/tokio/pull/7828 [#7833]: https://github.com/tokio-rs/tokio/pull/7833 [#7834]: https://github.com/tokio-rs/tokio/pull/7834 [#7835]: https://github.com/tokio-rs/tokio/pull/7835 [#7837]: https://github.com/tokio-rs/tokio/pull/7837 [#7838]: https://github.com/tokio-rs/tokio/pull/7838 [#7839]: https://github.com/tokio-rs/tokio/pull/7839 [#7850]: https://github.com/tokio-rs/tokio/pull/7850 [#7858]: https://github.com/tokio-rs/tokio/pull/7858 [#7869]: https://github.com/tokio-rs/tokio/pull/7869 [#7871]: https://github.com/tokio-rs/tokio/pull/7871 [#7872]: https://github.com/tokio-rs/tokio/pull/7872 [#7875]: https://github.com/tokio-rs/tokio/pull/7875 [#7879]: https://github.com/tokio-rs/tokio/pull/7879 [#7880]: https://github.com/tokio-rs/tokio/pull/7880 [#7885]: https://github.com/tokio-rs/tokio/pull/7885 [#7886]: https://github.com/tokio-rs/tokio/pull/7886 [#7889]: https://github.com/tokio-rs/tokio/pull/7889 [#7891]: https://github.com/tokio-rs/tokio/pull/7891 [#7896]: https://github.com/tokio-rs/tokio/pull/7896 [#7904]: https://github.com/tokio-rs/tokio/pull/7904 [#7908]: https://github.com/tokio-rs/tokio/pull/7908 [#7910]: https://github.com/tokio-rs/tokio/pull/7910 [#7913]: https://github.com/tokio-rs/tokio/pull/7913 [#7918]: https://github.com/tokio-rs/tokio/pull/7918 [#7919]: https://github.com/tokio-rs/tokio/pull/7919 [#7920]: https://github.com/tokio-rs/tokio/pull/7920 [#7922]: https://github.com/tokio-rs/tokio/pull/7922 [#7923]: https://github.com/tokio-rs/tokio/pull/7923 [#7925]: https://github.com/tokio-rs/tokio/pull/7925 [#7926]: https://github.com/tokio-rs/tokio/pull/7926 [#7929]: https://github.com/tokio-rs/tokio/pull/7929 [#7932]: https://github.com/tokio-rs/tokio/pull/7932 ### [`v1.49.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.49.0): Tokio v1.49.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.48.0...tokio-1.49.0) ### 1.49.0 (January 3rd, 2026) ##### Added - net: add support for `TCLASS` option on IPv6 ([#7781]) - runtime: stabilize `runtime::id::Id` ([#7125]) - task: implement `Extend` for `JoinSet` ([#7195]) - task: stabilize the `LocalSet::id()` ([#7776]) ##### Changed - net: deprecate `{TcpStream,TcpSocket}::set_linger` ([#7752]) ##### Fixed - macros: fix the hygiene issue of `join!` and `try_join!` ([#7766]) - runtime: revert "replace manual vtable definitions with Wake" ([#7699]) - sync: return `TryRecvError::Disconnected` from `Receiver::try_recv` after `Receiver::close` ([#7686]) - task: remove unnecessary trait bounds on the `Debug` implementation ([#7720]) ##### Unstable - fs: handle `EINTR` in `fs::write` for io-uring ([#7786]) - fs: support io-uring with `tokio::fs::read` ([#7696]) - runtime: disable io-uring on `EPERM` ([#7724]) - time: add alternative timer for better multicore scalability ([#7467]) ##### Documented - docs: fix a typos in `bounded.rs` and `park.rs` ([#7817]) - io: add `SyncIoBridge` cross-references to `copy` and `copy_buf` ([#7798]) - io: doc that `AsyncWrite` does not inherit from `std::io::Write` ([#7705]) - metrics: clarify that `num_alive_tasks` is not strongly consistent ([#7614]) - net: clarify the cancellation safety of the `TcpStream::peek` ([#7305]) - net: clarify the drop behavior of `unix::OwnedWriteHalf` ([#7742]) - net: clarify the platform-dependent backlog in `TcpSocket` docs ([#7738]) - runtime: mention `LocalRuntime` in `new_current_thread` docs ([#7820]) - sync: add missing period to `mpsc::Sender::try_send` docs ([#7721]) - sync: clarify the cancellation safety of `oneshot::Receiver` ([#7780]) - sync: improve the docs for the `errors` of mpsc ([#7722]) - task: add example for `spawn_local` usage on local runtime ([#7689]) [#7125]: https://github.com/tokio-rs/tokio/pull/7125 [#7195]: https://github.com/tokio-rs/tokio/pull/7195 [#7305]: https://github.com/tokio-rs/tokio/pull/7305 [#7467]: https://github.com/tokio-rs/tokio/pull/7467 [#7614]: https://github.com/tokio-rs/tokio/pull/7614 [#7686]: https://github.com/tokio-rs/tokio/pull/7686 [#7689]: https://github.com/tokio-rs/tokio/pull/7689 [#7696]: https://github.com/tokio-rs/tokio/pull/7696 [#7699]: https://github.com/tokio-rs/tokio/pull/7699 [#7705]: https://github.com/tokio-rs/tokio/pull/7705 [#7720]: https://github.com/tokio-rs/tokio/pull/7720 [#7721]: https://github.com/tokio-rs/tokio/pull/7721 [#7722]: https://github.com/tokio-rs/tokio/pull/7722 [#7724]: https://github.com/tokio-rs/tokio/pull/7724 [#7738]: https://github.com/tokio-rs/tokio/pull/7738 [#7742]: https://github.com/tokio-rs/tokio/pull/7742 [#7752]: https://github.com/tokio-rs/tokio/pull/7752 [#7766]: https://github.com/tokio-rs/tokio/pull/7766 [#7776]: https://github.com/tokio-rs/tokio/pull/7776 [#7780]: https://github.com/tokio-rs/tokio/pull/7780 [#7781]: https://github.com/tokio-rs/tokio/pull/7781 [#7786]: https://github.com/tokio-rs/tokio/pull/7786 [#7798]: https://github.com/tokio-rs/tokio/pull/7798 [#7817]: https://github.com/tokio-rs/tokio/pull/7817 [#7820]: https://github.com/tokio-rs/tokio/pull/7820 </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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] 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).

renovatebot force-pushed renovate/all-minor-patch from 9c5c8448d6 to b5bc42f235

2026-03-03 11:01:16 +01:00

Compare

renovatebot force-pushed renovate/all-minor-patch from b5bc42f235 to 3729b86e4c

2026-03-12 18:17:00 +01:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 3729b86e4c to dc5c8ef2ce

2026-03-12 20:16:20 +01:00

Compare

renovatebot force-pushed renovate/all-minor-patch from dc5c8ef2ce to c5aa84e19f

2026-03-25 19:17:15 +01:00

Compare

renovatebot force-pushed renovate/all-minor-patch from c5aa84e19f to c51f380918

2026-04-03 11:01:43 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from c51f380918 to 9b04b6501a

2026-04-08 13:01:47 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 9b04b6501a to 4657a8e498

2026-04-14 21:16:18 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 4657a8e498 to c240fe6ff7

2026-04-15 21:16:51 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from c240fe6ff7 to 6007b379eb

2026-04-17 00:01:45 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 6007b379eb to f21ffc752c

2026-05-04 15:01:39 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from f21ffc752c to 04caccf4af

2026-05-08 15:31:36 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 04caccf4af to b12df3bde4

2026-05-09 01:46:21 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from b12df3bde4 to 003a348438

2026-05-09 02:31:22 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 003a348438 to 364f3d508c

2026-06-02 09:02:44 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 364f3d508c to 4abb2133f2

2026-06-09 17:17:13 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 4abb2133f2 to 447117e9a7

2026-06-12 10:16:29 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 447117e9a7 to 56b19c59ce

renovate/artifacts Artifact file update failure

2026-06-13 01:31:20 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 56b19c59ce

renovate/artifacts Artifact file update failure

to dba3d84a1c

2026-06-13 01:46:17 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from dba3d84a1c to 65c1f217f9

2026-06-14 00:16:17 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 65c1f217f9 to a3f43386a9

2026-06-22 08:16:37 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from a3f43386a9 to c3686865bd

2026-06-22 08:46:27 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from c3686865bd to f0d4f439ad

2026-06-22 09:31:33 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from f0d4f439ad to 3f60dec698

2026-06-25 23:01:23 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 3f60dec698 to 72641cba7e

2026-06-30 11:16:27 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 72641cba7e to 4ed7b96ea3

2026-07-01 08:16:36 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 4ed7b96ea3 to b57ad63b41

2026-07-15 21:46:50 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from b57ad63b41 to 7917f76cef

2026-07-16 15:46:31 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 7917f76cef to b59c5bcbbc

2026-07-17 10:46:43 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from b59c5bcbbc to ac4e02f580

2026-07-18 23:16:24 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from ac4e02f580 to ad9f355137

2026-07-20 10:46:40 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from ad9f355137 to 67c785984b

2026-07-20 16:31:40 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 67c785984b to 25cd21e05d

2026-07-20 19:31:41 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 25cd21e05d to 9591f16e9b

2026-07-22 00:16:37 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 8749e43e35 to 9c46d99ac7

2026-08-06 16:16:26 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from 9c46d99ac7 to ed215dc239

renovate/artifacts Artifact file update failure

2026-09-03 16:45:48 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from ed215dc239

renovate/artifacts Artifact file update failure

to afefd0e9c1

2026-09-03 17:07:55 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from afefd0e9c1 to a3f7a065b4

2026-09-14 21:16:40 +02:00

Compare

renovatebot force-pushed renovate/all-minor-patch from a3f7a065b4 to 6f79e0b841

2026-09-18 20:02:49 +02:00

Compare

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/all-minor-patch:renovate/all-minor-patch

git switch renovate/all-minor-patch

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff renovate/all-minor-patch

git switch renovate/all-minor-patch

git rebase main

git switch main

git merge --ff-only renovate/all-minor-patch

git switch renovate/all-minor-patch

git rebase main

git switch main

git merge --no-ff renovate/all-minor-patch

git switch main

git merge --squash renovate/all-minor-patch

git switch main

git merge --ff-only renovate/all-minor-patch

git switch main

git merge renovate/all-minor-patch

git push origin main

No reviewers

No labels

No milestone

No assignees

1 participant

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

lilly/cookied!2

No description provided.

Rows
Columns

Update all non-major dependencies #2

Release Notes

Features

Features

Fixes

Internal

Fixes

Fixes

Fixes

Compatibility

Internal

Fixes

Fixes

Fixes

Fixes

Fixes

Fixes

Retry

Retry fixes

Other changes

v0.31.1: opentelemetry-otlp 0.31.1

What's Changed

Fixed

Added

Changed

Performance

Fixed

Added

Fixed

Fixed

Fixed

Security

Compatibility

Added

Changed

Fixed

Performance

Security

Compatibility

Added

Changed

Fixed

Added

Changed

Fixed

Added

Changed

v1.53.1: Tokio v1.53.1

1.53.1 (July 20th, 2026)

Fixed

Fixed (unstable)

Documented

v1.53.0: Tokio v1.53.0

1.53.0 (July 17th, 2026)

Added

Changed

Fixed

IO uring (unstable)

Documented

v1.52.4: Tokio v1.52.4

1.52.4 (July 16th, 2026)

Fixed

Fixed (unstable)

v1.52.3: Tokio v1.52.3

1.52.3 (May 8th, 2026)

Fixed

v1.52.2: Tokio v1.52.2

1.52.2 (May 4th, 2026)

v1.52.1: Tokio v1.52.1

1.52.1 (April 16th, 2026)

Fixed

v1.52.0: Tokio v1.52.0

1.52.0 (April 14th, 2026)

Added

Added (unstable)

Changed

Fixed

Documented

v1.51.4: Tokio v1.51.4

1.51.4 (July 16th, 2026)

`v0.31.1`: opentelemetry-otlp 0.31.1

`v1.53.1`: Tokio v1.53.1

`v1.53.0`: Tokio v1.53.0

`v1.52.4`: Tokio v1.52.4

`v1.52.3`: Tokio v1.52.3

`v1.52.2`: Tokio v1.52.2

`v1.52.1`: Tokio v1.52.1

`v1.52.0`: Tokio v1.52.0

`v1.51.4`: Tokio v1.51.4

`v1.51.3`: Tokio v1.51.3

`v1.51.2`: Tokio v1.51.1

`v1.51.1`: Tokio v1.51.1

`v1.51.0`: Tokio v1.51.0

`v1.50.0`: Tokio v1.50.0

`v1.49.0`: Tokio v1.49.0