[dependabot]

Updates the requirements on opentelemetry, opentelemetry_sdk, opentelemetry-otlp, tracing-opentelemetry, opentelemetry-proto, axum-tracing-opentelemetry and opentelemetry-instrumentation-actix-web to permit the latest version.
Updates opentelemetry to 0.33.0

Changelog

Sourced from opentelemetry's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates opentelemetry_sdk to 0.33.0

Changelog

Sourced from opentelemetry_sdk's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates opentelemetry-otlp to 0.33.0

Changelog

Sourced from opentelemetry-otlp's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates tracing-opentelemetry to 0.34.0

Changelog

Sourced from tracing-opentelemetry's changelog.

0.34.0 - 2026-09-20

Other

• Upgrade to OpenTelemetry 0.33, see upstream changelog for details (#268)

0.33.0 - 2026-05-18

Fixed

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

Other

• Upgrade to OpenTelemetry 0.32, see upstream changelog for details (#258)
• mimimize package size (#252)

0.32.1 - 2025-12-17

Added

• allow OpenTelemetry context access with SpanRef (#234)
• add event-counting filtering layer for spans (#228)
• publicly export SetParentError

Fixed

• fix panic in multithreaded follows-from

Other

• Remove unwanted dependency on opentelemetry sdk crate (#241)
• update README.md links to use the latest version (#239)
• remove thiserror and unused dependencies (#238)

0.32.0 - 2025-09-29

Added

• Add configuration for including target in spans (#222)

Changed

• OpenTelemetry context activation (#202)
  • Trace ID and span ID can be obtained from OtelData via dedicated functions. Note that these will be available only if the context has already been built. (#233)
• Correctly track entered and exited state for timings (#212)
• Slightly improve error message on version mismatch (#211)
• Remove Lazy for thread_local static (#215)
• Update description of special fields and semantic conventions

... (truncated)

Commits

• See full diff in compare view

Updates opentelemetry-proto to 0.33.0

Changelog

Sourced from opentelemetry-proto's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates axum-tracing-opentelemetry to 0.39.1

Commits

• 47aa02f chore: release (#355)
• bf09a8e docs: add info about differences with tower_http::trace
• 534db47 fix(tracing-opentelemetry-instrumentation-sdk): split server.address/server.p...
• 883291f fix(tracing-opentelemetry-instrumentation-sdk): split server.address/server.p...
• f49b6b5 chore(init-tracing-opentelemetry): release v0.41.0 (#354)
• 1eff3ab chore(init-tracing-opentelemetry): release v0.41.0 (#353)
• 7280ad7 refactor: format
• 1c459e3 fix(ci): syntax error in ci.yml
• 7f01c21 feat(init-tracing-opentelemetry): re-export prometheus crate
• 5a35ad3 docs(init-tracing-opentelemetry): promote direct Meter API over tracing-macro...
• Additional commits viewable in compare view

Updates opentelemetry-instrumentation-actix-web to 0.25.0

Release notes

Sourced from opentelemetry-instrumentation-actix-web's releases.

opentelemetry-instrumentation-actix-web-0.25.0

See CHANGELOG for full history.

Commits

• 964c525 chore: upgrade contrib crates to OpenTelemetry 0.33 (#802)
• fb70cb6 chore(tower): Update tower http server benchmarks to minimize measurement noi...
• 5070699 fix(tower): follow up on the query string redaction review (#800)
• 07c16a0 fix(tower): record the query string of a server request (#789)
• c624338 test(tower): assert no telemetry and context propagation when signals disable...
• 921f5af feat(aws): normalize the behavior and documentation of the Lambda resource de...
• a499720 chore: remove deprecated Stackdriver exporter (#796)
• 1765ce0 chore(deps): update time requirement from >=0.3.47, <0.3.54 to >=0.3.47, <0.3...
• 3fb83ed chore: remove deprecated Datadog exporter (#795)
• 75babcb fix: allow manual_ok_err in detector log helpers when internal-logs is off (#...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[macroscopeapp]

🟡 Medium logfire/Cargo.toml:43

The default OTLP HTTP protobuf exporter now discards any serialized trace, log, or metric batch larger than 64 MiB without sending or retrying it, silently losing telemetry that previously exported successfully. This dependency declaration does not configure a larger request-body limit; configure the exporter limit or otherwise preserve the previous capacity.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @logfire/Cargo.toml around line 43:

The default OTLP HTTP protobuf exporter now discards any serialized trace, log, or metric batch larger than 64 MiB without sending or retrying it, silently losing telemetry that previously exported successfully. This dependency declaration does not configure a larger request-body limit; configure the exporter limit or otherwise preserve the previous capacity.