chore(deps): update opentelemetry

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry-jaeger-propagator (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry-otlp (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry-proto (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry-semantic-conventions (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry-stdout (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry-zipkin (source)	workspace.dependencies	minor	0.28 -> 0.29
opentelemetry_sdk (source)	workspace.dependencies	minor	0.28 -> 0.29
tracing-opentelemetry	workspace.dependencies	minor	0.29 -> 0.30

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.29.0

Compare Source

Released 2025-Mar-21

• Breaking Moved ExportError trait from opentelemetry::trace::ExportError to opentelemetry_sdk::export::ExportError
• Breaking Moved TraceError enum from opentelemetry::trace::TraceError to opentelemetry_sdk::trace::TraceError
• Breaking Moved TraceResult type alias from opentelemetry::trace::TraceResult to opentelemetry_sdk::trace::TraceResult
• Bug Fix: InstrumentationScope implementation for PartialEq and Hash fixed to include Attributes also.
• Breaking changes for baggage users: #​2717
  • Changed value type of Baggage from Value to StringValue
  • Updated Baggage constants to reflect latest standard (MAX_KEY_VALUE_PAIRS - 180 -> 64, MAX_BYTES_FOR_ONE_PAIR - removed) and increased insert performance see #2284.
  • Align Baggage.remove() signature with .get() to take the key as a reference
  • Baggage can't be retrieved from the Context directly anymore and needs to be accessed via context.baggage()
  • with_baggage() and current_with_baggage() override any existing Baggage in the Context
  • Baggage keys can't be empty and only allow ASCII visual chars, except "(),/:;<=>?@&#8203;[\]{} (see RFC7230, Section 3.2.6)
  • KeyValueMetadata does not publicly expose its fields. This should be transparent change to the users.
• Changed Context to use a stack to properly handle out of order dropping of ContextGuard. This imposes a limit of 65535 nested contexts on a single thread. See #2378 and #1887.
• Added additional name: Option<&str> parameter to the event_enabled method on the Logger trait. This allows implementations (SDK, processor, exporters) to leverage this additional information to determine if an event is enabled.

open-telemetry/opentelemetry-rust (opentelemetry-jaeger-propagator)

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29

• Update opentelemetry_sdk dependency version to 0.29

• Update opentelemetry-http dependency version to 0.29

• Update opentelemetry-proto dependency version to 0.29

• The OTEL_EXPORTER_OTLP_TIMEOUT, OTEL_EXPORTER_OTLP_TRACES_TIMEOUT, OTEL_EXPORTER_OTLP_METRICS_TIMEOUT and OTEL_EXPORTER_OTLP_LOGS_TIMEOUT are changed from seconds to miliseconds.

• Fixed .with_headers() in HttpExporterBuilder to correctly support multiple key/value pairs. #​2699

• Fixed #​2770 partially to properly handle shutdown() when using http. (tonic still does not do proper shutdown)

• Breaking ExporterBuilder's build() method now Result with ExporterBuildError being the Error variant. Previously it returned signal specific errors like LogError from the opentelemetry_sdk, which are no longer part of the sdk. No changes required if you were using unwrap/expect. If you were matching on the returning Error enum, replace with the enum ExporterBuildError. Unlike the previous Error which contained many variants unrelated to building an exporter, the new one returns specific variants applicable to building an exporter. Some variants might be applicable only on select features. Also, now unused Error enum is removed.

• Breaking ExportConfig's timeout field is now optional(Option<Duration>)

• Breaking Export configuration done via code is final. ENV variables cannot be used to override the code config. Do not use code based config, if there is desire to control the settings via ENV variables. List of ENV variables and corresponding setting being affected by this change.

  • OTEL_EXPORTER_OTLP_ENDPOINT -> ExportConfig.endpoint
  • OTEL_EXPORTER_OTLP_TIMEOUT -> ExportConfig.timeout

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29
• Update opentelemetry_sdk dependency version to 0.29

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update to v1.31.0 of the semantic conventions.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29.
• Update opentelemetry_sdk dependency version to 0.29.

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

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency version to 0.29.

• Update opentelemetry_sdk dependency version to 0.29.

• Update opentelemetry-http dependency version to 0.29.

• Breaking The ZipkinExporterBuilder::build() method now returns a Result<ZipkinExporter, ExporterBuildError>. The ExporterBuildError enum lists possible failures specific to the Zipkin exporter and was renamed from opentelemetry_zipkin::Error. Previously, this method returned a TraceError from the opentelemetry_sdk crate, which was unrelated to Zipkin builder failures. 2839

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

v0.29.0

Compare Source

Released 2025-Mar-21

• Update opentelemetry dependency to 0.29.
• Update opentelemetry-http dependency to 0.29.
• Breaking: The Runtime trait has been simplified and refined. See the #​2641 for the changes.
• Removed async-std support for Runtime, as async-std crate is deprecated.
• Calls to MeterProviderBuilder::with_resource, TracerProviderBuilder::with_resource, LoggerProviderBuilder::with_resource are now additive (#​2677).
• Moved ExportError trait from opentelemetry::trace::ExportError to opentelemetry_sdk::export::ExportError
• Moved TraceError enum from opentelemetry::trace::TraceError to opentelemetry_sdk::trace::TraceError
• Moved TraceResult type alias from opentelemetry::trace::TraceResult to opentelemetry_sdk::trace::TraceResult
• Breaking: Make force_flush() in PushMetricExporter synchronous
• Breaking: Updated the SpanExporter trait method signature:

  fn export(&mut self, batch: Vec<SpanData>) -> BoxFuture<'static, OTelSdkResult>;

to

  fn export(
    &mut self,
    batch: Vec<SpanData>,
) -> impl std::future::Future<Output = OTelSdkResult> + Send;

This affects anyone who writes custom exporters, as custom implementations of SpanExporter should now define export as an async fn:

  impl trace::SpanExporter for CustomExporter {
    async fn export(&mut self, batch: Vec<trace::SpanData>) -> OTelSdkResult {
        // Implementation here
    }
}

• Breaking The SpanExporter::export() method no longer requires a mutable reference to self. Before:

    async fn export(&mut self, batch: Vec<SpanData>) -> OTelSdkResult
  

  After:

    async fn export(&self, batch: Vec<SpanData>) -> OTelSdkResult
  

  Custom exporters will need to internally synchronize any mutable state, if applicable.

• Bug Fix: BatchLogProcessor now correctly calls shutdown on the exporter when its shutdown is invoked.

• Reduced some info level logs to debug

• Breaking for custom LogProcessor/Exporter authors: Changed name parameter from &str to Option<&str> in event_enabled method on the LogProcessor and LogExporter traits. SdkLogger no longer passes its scope name but instead passes the incoming name when invoking event_enabled on processors.

• Breaking for custom LogExporter authors: shutdown() method in LogExporter trait no longer requires a mutable ref to self. If the exporter needs to mutate state, it should rely on interior mutability. 2764

• Breaking (Affects custom Exporter/Processor authors only) Removed opentelelemetry_sdk::logs::error::{LogError, LogResult}. These were not intended to be public. If you are authoring custom processor/exporters, use opentelemetry_sdk::error::OTelSdkError and opentelemetry_sdk::error::OTelSdkResult. 2790

• Breaking for custom LogProcessor authors: Changed set_resource to require mutable ref. fn set_resource(&mut self, _resource: &Resource) {}

• Breaking: InMemoryExporter's return type change.

  • TraceResult<Vec<SpanData>> to Result<Vec<SpanData>, InMemoryExporterError>
  • MetricResult<Vec<ResourceMetrics>> to Result<Vec<ResourceMetrics>, InMemoryExporterError>
  • LogResult<Vec<LogDataWithResource>> to Result<Vec<LogDataWithResource>, InMemoryExporterError>

tokio-rs/tracing-opentelemetry (tracing-opentelemetry)

v0.30.0

Compare Source

Breaking Changes

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

---

Configuration

📅 Schedule: 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 was generated by Mend Renovate. View the repository job log.

[github-actions[bot]]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ EDITORCONFIG	editorconfig-checker	11		0	0	0.03s
✅ REPOSITORY	checkov	yes		no	no	10.39s
✅ REPOSITORY	dustilock	yes		no	no	0.0s
✅ REPOSITORY	gitleaks	yes		no	no	0.25s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	20.14s
✅ REPOSITORY	secretlint	yes		no	no	0.7s
✅ REPOSITORY	syft	yes		no	no	0.93s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.07s
✅ REPOSITORY	trufflehog	yes		no	no	2.39s

See detailed report in MegaLinter reports Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

[renovate[bot]]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.