deps: bump opentelemetry from 0.27.1 to 0.32.0

[dependabot]

Bumps opentelemetry from 0.27.1 to 0.32.0.

Release notes

Sourced from opentelemetry's releases.

0.32.0

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

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 in open-telemetry/opentelemetry-rust#3426

Full Changelog: open-telemetry/opentelemetry-rust@v0.31.0...opentelemetry-otlp-0.31.1

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

OpenTelemetry Rust 0.32 continues to drive the Logs, Metrics, and Distributed Tracing components forward. The Logs and Metrics API and SDK remain stable, with no breaking changes in this release. The OTLP Exporters and the Distributed Tracing API/SDK remain in pre-stable states (Release-Candidate and Beta respectively), and this release introduces a small number of intentional breaking changes in those areas to prepare them for stabilization.

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

1. Bound instruments (experimental): Added Counter::bind() and Histogram::bind() returning 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 on the hot path. Benchmarks show ~28x speedup for counter operations and ~9x for histograms. Gated behind the experimental_metrics_bound_instruments feature flag.

2. Delta collection efficiency: 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.

3. Stable Aggregation API: Aggregation and StreamBuilder::with_aggregation() are now stable and no longer require the spec_unstable_metrics_views feature flag.

Logs

1. Tracing-span attribute enrichment (experimental): The opentelemetry-appender-tracing crate can now copy attributes from active tracing spans onto each emitted log record. ("Span" here refers to tracing::span!, not an opentelemetry::trace::Span.) Enrichment is disabled by default with zero per-span overhead, and is gated behind the new experimental_span_attributes cargo feature.

2. spec_unstable_logs_enabled removed: The capability (and the backing specification) is now stable and is enabled by default. The feature flag has been removed.

Distributed Tracing (Beta)

The Distributed Tracing API and SDK remain in beta. This release contains intentional breaking changes to clean up the public surface ahead of

... (truncated)

Commits

• ec289cb chore: Prepare for release v0.32.0 (#3508)
• 3ddb386 fix(metrics): reject usize::MAX as cardinality limit (#3506)
• bad0a1b feat(appender-tracing): re-gate span attribute enrichment behind experimental...
• f744509 docs: update README status table and remove deprecated crates (#3502)
• 81d5a06 chore(prometheus): restore crate to workspace (#3500)
• 5a07ce1 ci: close stale pull requests (#3499)
• cc87dd9 feat(appender-tracing): stabilize span attribute propagation (#3482)
• f290595 docs(metrics): document experimental bound instruments (#3495)
• a79eb76 fix(sdk): suppress telemetry in SimpleSpanProcessor during export (#3494)
• aa3bda3 chore(zipkin): deprecate opentelemetry-zipkin crate (#3492)
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[nitecon]

Eventic automated review — CI failure diagnosis

Bumping opentelemetry from 0.27.1 → 0.32.0 is a major-version jump in the 0.x series (semver-breaking). CI fails to compile because the OpenTelemetry API contract changed:

• SdkMeterProvider no longer implements opentelemetry::metrics::MeterProvider (use the SDK-side MeterProvider trait or as_meter_provider).
• PeriodicReaderBuilder::with_interval(...) trait bounds changed.

This is the same upstream migration required by PR #18 (opentelemetry-otlp 0.27.0 → 0.31.0) and PR #50 (opentelemetry_sdk 0.27.1 → 0.32.0). The three crates ship together — bumping any one in isolation will not compile.

Suggested path:

• Migrate lnc-metrics/src/otlp.rs (and any other call sites) to the new OTel builder/exporter API in a single commit covering all three crates.
• Once the migration lands on main, close PRs deps: bump opentelemetry-otlp from 0.27.0 to 0.31.0 #18 / deps: bump opentelemetry_sdk from 0.27.1 to 0.32.0 #50 / deps: bump opentelemetry from 0.27.1 to 0.32.0 #51 in favor of a fresh combined Dependabot run.

No automated fix applied — major-version dep migration needs manual API adaptation per project guidelines. Tracked in /opt/eventic/.eventic-todo.md ([nitecon/lance] Migrate opentelemetry-otlp to 0.31.0 API (PR #18)).

[nitecon]

Eventic auto-merge skipped — major version bump with CI failures.

Why

• This is a major version bump for opentelemetry (0.27.1 → 0.32.0) — five minor versions of breaking changes (0.28 / 0.29 / 0.30 / 0.31 / 0.32 release notes all call out breaking changes for the tracing API + OTLP exporter feature flags). Sub-flow B reserves major bumps for manual review.
• Multiple CI checks are failing: Clippy, Clippy Strict, Test (ubuntu+macos), Build Release (ubuntu+macos), Build and Test, Documentation.

Root cause of the build failure

The PR bumps only the core opentelemetry crate. opentelemetry_sdk and opentelemetry-otlp stay at 0.27, so the workspace now has two coexisting versions of opentelemetry (see Cargo.lock diff — opentelemetry 0.27.1 and opentelemetry 0.32.0).

The compiler error is the consequence:

error[E0277]: the trait bound
  `opentelemetry_sdk::metrics::SdkMeterProvider:
   opentelemetry::metrics::MeterProvider`
  is not satisfied

SdkMeterProvider is still the 0.27 type, but our code now refers to MeterProvider from opentelemetry 0.32 — the two versions' traits don't unify.

How to land this

The opentelemetry-rust workspace cuts all crates on the same version cadence, so the bump has to be coordinated:

1. Combine with PR deps: bump opentelemetry_sdk from 0.27.1 to 0.32.0 #50 (opentelemetry_sdk 0.32.0) and a matching opentelemetry-otlp 0.32 bump in one branch.
2. Migrate to the 0.28–0.32 breaking changes (notably the tracing-API surface and OTLP feature-flag renames tls-ring / tls-aws-lc / tls-provider-agnostic introduced in 0.31.1).
3. Verify the rand transitive pin clears — opentelemetry_sdk 0.27 was the reason rand was stuck at 0.8.5 in this repo.

Holding for manual review.