chore(deps): update opentelemetry

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
opentelemetry	workspace.dependencies	minor	0.27 -> 0.28
opentelemetry-otlp (source)	workspace.dependencies	minor	0.27 -> 0.28
opentelemetry_sdk	workspace.dependencies	minor	0.27 -> 0.28
tracing-opentelemetry	workspace.dependencies	minor	0.28 -> 0.29

---

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

v0.28.0: 0.28.0 Release

Compare Source

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.

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

v0.28.0

Compare Source

Released 2025-Feb-10

• Update opentelemetry dependency version to 0.28.
• Update opentelemetry_sdk dependency version to 0.28.
• Update opentelemetry-http dependency version to 0.28.
• Update opentelemetry-proto dependency version to 0.28.
• Bump msrv to 1.75.0.
• Feature flag "populate-logs-event-name" is removed as no longer relevant.
  LogRecord's event_name() is now automatically populated on the newly added
  "event_name" field in LogRecord proto definition.
• Remove "grpc-tonic" feature from default, and instead add "http-proto" and
  "reqwest-blocking-client" features as default, to align with the
  specification.
  2516
• Remove unnecessarily public trait opentelemetry_otlp::metrics::MetricsClient
  and MetricExporter::new(..) method. Use
  MetricExporter::builder()...build() to obtain MetricExporter.
• The HTTP clients (reqwest, reqwest-blocking, hyper) now support the
  export timeout interval configured in below order
  • Signal specific env variable OTEL_EXPORTER_OTLP_TRACES_TIMEOUT,
    OTEL_EXPORTER_OTLP_LOGS_TIMEOUT or OTEL_EXPORTER_OTLP_TIMEOUT.
  • OTEL_EXPORTER_OTLP_TIMEOUT env variable.
  • with_http().with_timeout() API method of
    LogExporterBuilder and SpanExporterBuilder and MetricsExporterBuilder.
  • The default interval of 10 seconds is used if none is configured.

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

v0.29.0

Compare Source

What's Changed

• Fix the example installing OpenTelemetryLayer into a global subscriber by @​mzabaluev in https://github.com/tokio-rs/tracing-opentelemetry/pull/175
• Update dependencies by @​djc in https://github.com/tokio-rs/tracing-opentelemetry/pull/187
• Use renamed WASI target by @​djc in https://github.com/tokio-rs/tracing-opentelemetry/pull/189
• use the tracing event name as the otel event name by @​zzlk in https://github.com/tokio-rs/tracing-opentelemetry/pull/188
• Update opentelemetry to 0.28 by @​cschramm in https://github.com/tokio-rs/tracing-opentelemetry/pull/193

---

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 is behind base branch, 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.

[rami3l]

@djc It's getting a bit more difficult than it should because we now have to handle shutdown without relying on otel's internal global state... It's against the original code organization. Apart from that I think I've pretty much done most of the migration in https://github.com/rami3l/rustup/tree/deps/bump-otel.