deps: bump the opentelemetry group with 4 updates

[dependabot]

Bumps the opentelemetry group with 4 updates: opentelemetry, opentelemetry_sdk, opentelemetry-otlp and tracing-opentelemetry.

Updates opentelemetry from 0.27.1 to 0.31.0

Release notes

Sourced from opentelemetry's releases.

0.30.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.30.0 for this release).

This release also upgrades Metrics-SDK to stable!

See summary of release notes: https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.30.md

0.29.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.29.0 for this release).

This release also upgrades

• Logs-SDK to stable
• Logs-Appender-Tracing to stable
• Baggage to RC

And deprecates

• Prometheus exporter is - now deprecated in favor of OTLP exporter.

0.28.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.28.0 for this release).

This release also upgrades

• Logs API to stable
• Logs-SDK, Logs OTLP exporter, Logs-Appender-Tracing to RC
• Metrics-API to stable
• Metrics-SDK, Metrics OTLP exporter to RC.

This release introduces several breaking changes as we progress toward a stable version for logs and metrics. We recommend reviewing the Migration Guide along with the changelogs to ensure a smooth upgrade.

Changelog

Sourced from opentelemetry's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

Commits

• 2b63b75 fix: Panics and exploding memory usage from large cardinality limit (#3290)
• c346d4b feat: Upgrade SDK version to 0.31.0 (#3287)
• 07bb613 feat: Improve support for exponential histogram (#3259)
• 693dcc0 chore: Unify SpanExporter with LogExporter and PushMetricExporter (#3281)
• 65969fd docs: logs enrichment (#3266)
• 627f252 feat: Stabilize Logger Enabled (#3278)
• 4c16d9b fix: Remove unused tracing dependency from opentelemetry-otlp (#3264)
• 759b539 chore(sampling): move sdk types from opentelemetry to opentelemetry_sdk (#3277)
• 483b420 fix: handle shutdown in logs exporter (#3255)
• 53c9f47 chore(deps): bump step-security/harden-runner from 2.13.1 to 2.13.2 (#3273)
• Additional commits viewable in compare view

Updates opentelemetry_sdk from 0.27.1 to 0.31.0

Changelog

Sourced from opentelemetry_sdk's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

Commits

• 285dc92 chore: Prepare for release v0.31.0 (#3179)
• 9cde968 chore: Prepare for release otel-http v0.30.1, Revert part of multi-value key ...
• 5250df2 fix: Suppress telemetry emitted inside of BatchLogProcessor::emit (#3172)
• 9bd2c1b fix: use instrumentation schema URL on scope spans (#3171)
• 159135c feat: Add is_remote flag in exporter for spans and span links (#3153)
• b7ff11b fix: Use path+version dependencies for publishing to crates.io otel-http (#3...
• 24da5c9 fix: Use path+version dependencies for publishing to crates.io (#3167)
• 6f75c58 fix: Add std feature to serde to fix CI linting issues (#3165)
• 80b5dcb chore: Bump opentelemetry-proto to v0.30.1 and opentelemetry-otlp to v0.30.1 ...
• b70771a chore: bump otel-proto to v1.8.0 (#3156)
• Additional commits viewable in compare view

Updates opentelemetry-otlp from 0.27.0 to 0.31.0

Release notes

Sourced from opentelemetry-otlp's releases.

v0.31.0

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.31.0 for this release).

0.30.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.30.0 for this release).

This release also upgrades Metrics-SDK to stable!

See summary of release notes: https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.30.md

0.29.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.29.0 for this release).

This release also upgrades

• Logs-SDK to stable
• Logs-Appender-Tracing to stable
• Baggage to RC

And deprecates

• Prometheus exporter is - now deprecated in favor of OTLP exporter.

0.28.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.28.0 for this release).

This release also upgrades

• Logs API to stable
• Logs-SDK, Logs OTLP exporter, Logs-Appender-Tracing to RC
• Metrics-API to stable
• Metrics-SDK, Metrics OTLP exporter to RC.

This release introduces several breaking changes as we progress toward a stable version for logs and metrics. We recommend reviewing the Migration Guide along with the changelogs to ensure a smooth upgrade.

opentelemetry-0.27.1 patch release

This release has improved internal logging to help with troubleshooting.

opentelemetry_sdk-0.27.1 patch release

Refer to opentelemetry-sdk CHANGELOG for the changes.

Changelog

Sourced from opentelemetry-otlp's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

Commits

• 285dc92 chore: Prepare for release v0.31.0 (#3179)
• 9cde968 chore: Prepare for release otel-http v0.30.1, Revert part of multi-value key ...
• 5250df2 fix: Suppress telemetry emitted inside of BatchLogProcessor::emit (#3172)
• 9bd2c1b fix: use instrumentation schema URL on scope spans (#3171)
• 159135c feat: Add is_remote flag in exporter for spans and span links (#3153)
• b7ff11b fix: Use path+version dependencies for publishing to crates.io otel-http (#3...
• 24da5c9 fix: Use path+version dependencies for publishing to crates.io (#3167)
• 6f75c58 fix: Add std feature to serde to fix CI linting issues (#3165)
• 80b5dcb chore: Bump opentelemetry-proto to v0.30.1 and opentelemetry-otlp to v0.30.1 ...
• b70771a chore: bump otel-proto to v1.8.0 (#3156)
• Additional commits viewable in compare view

Updates tracing-opentelemetry from 0.28.0 to 0.32.0

Release notes

Sourced from tracing-opentelemetry's releases.

0.32.0

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

Breaking Changes

• The attributes code.filepath, code.lineno, and code.namespace have been renamed to code.file.path, and code.line.number, and code.module.name, to align with the opentelemetry semantic conventions for code. (#225)
• Upgrade from opentelemetry to 0.31.0. Refer to the upstream changelog for more information. (#230)
• Hold onto MetricsProvider in MetricsLayer (#224)
• The attribute otel.status_message was changed to otel.status_description to align with the opentelemetry semantic conventions for code. (#209)
• Remove the metrics_gauge_unstable feature.

0.31.0

Breaking Changes

• Upgrade from opentelemetry 0.29.0 to 0.30.0. Refer to the upstream changelog for more information.

Added

• Add OpenTelemetrySpanExt::add_event and OpenTelemetrySpanExt::add_event_with_timestamp functions to allow adding OpenTelemetry events directly to a tracing::Span, enabling the use of dynamic attribute keys and custom event timestamps.

0.30.0

What's Changed

• doc: tracked inactivity default by @​aimericsr in tokio-rs/tracing-opentelemetry#195
• chore: update from opentelemetry-sdk 0.28.0 to 0.29.0 by @​alessandrobologna in tokio-rs/tracing-opentelemetry#196
• chore: prepare for release 0.30.0 by @​tisonkun in tokio-rs/tracing-opentelemetry#197

v0.29.0

What's Changed

... (truncated)

Changelog

Sourced from tracing-opentelemetry's changelog.

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

Breaking Changes

• The attributes code.filepath, code.lineno, and code.namespace have been renamed to code.file.path, and code.line.number, and code.module.name, to align with the opentelemetry semantic conventions for code. (#225)
• Upgrade from opentelemetry to 0.31.0. Refer to the upstream changelog for more information. (#230)
• Hold onto MetricsProvider in MetricsLayer (#224)
• The attribute otel.status_message was changed to otel.status_description to align with the opentelemetry semantic conventions for code. (#209)
• Remove the metrics_gauge_unstable feature.

0.31.0 (June 2, 2025)

Breaking Changes

• Upgrade from opentelemetry 0.29.0 to 0.30.0. Refer to the upstream changelog for more information.

Added

• Add OpenTelemetrySpanExt::add_event and OpenTelemetrySpanExt::add_event_with_timestamp functions to allow adding OpenTelemetry events directly to a tracing::Span, enabling the use of dynamic attribute keys and custom event timestamps.

0.30.0 (March 23, 2025)

Breaking Changes

• Upgrade from opentelemetry 0.28.0 to 0.29.0. Refer to the upstream changelog

... (truncated)

Commits

• f663332 chore: prepare release of 0.32.0
• 0154fa4 chore: fix docs link
• d684c2e chore: delete removed docs.rs feature
• 73a6baf feat: make trace ID and span ID public on OtelData (#233)
• 4ebae2c Upgrade to opentelemetry 0.31 (#230)
• 4fdf560 fix(layer)!: use otel semantic conventions for code (#225)
• 612b5b2 chore: fix clippy lints (#226)
• c4fe96a feat: OpenTelemetry context activation (#202)
• 764cd73 fix(metrics)!: hold onto MetricsProvider in MetricsLayer (#224)
• fd0a58a feat(layer): add configuration for including target in spans (#222)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.