chore(deps): bump opentelemetry-otlp from 0.27.0 to 0.32.0

[dependabot]

Bumps opentelemetry-otlp from 0.27.0 to 0.32.0.

Release notes

Sourced from opentelemetry-otlp's releases.

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

Changelog

Sourced from opentelemetry-otlp'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)

Note

Bump opentelemetry-otlp from 0.27.0 to 0.32.0 in journeys-observability

Updates the opentelemetry-otlp dependency in Cargo.toml from 0.27 to 0.32, keeping the same http-proto and reqwest-client features enabled.

^{Macroscope summarized 2771c77.}

[dependabot]

Labels

The following labels could not be found: rust. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

[codeant-ai]

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​opentelemetry-otlp@​0.27.0 ⏵ 0.32.0

View full report

[kilo-code-bot]

WARNING: OpenTelemetry stack is now split across versions 0.27 and 0.32

Bumping opentelemetry-otlp to 0.32 pulls in opentelemetry 0.32.0 and opentelemetry_sdk 0.32.1 transitively, but this crate still pins opentelemetry = "0.27" (line 14) and opentelemetry-semantic-conventions = "0.27" (line 17), alongside the pre-existing opentelemetry_sdk = "0.32" (line 15). The dependency tree therefore contains both opentelemetry 0.27 and 0.32.

opentelemetry-otlp 0.32 also introduced intentional breaking API changes (per the release notes). Dependabot only updates the version spec, not the crate's usage code, so the observability crate must be confirmed to still compile and pass cargo test/cargo clippy against this exact tree.

Recommend aligning the whole stack to 0.32 (bump opentelemetry and opentelemetry-semantic-conventions accordingly, and verify tracing-opentelemetry 0.28 is compatible), or confirming CI is green before merge.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
crates/phenotype-journeys-observability/Cargo.toml	16	OpenTelemetry stack split across 0.27 and 0.32; otlp 0.32 has breaking changes and the bump must be verified to compile against the rest of the stack

Files Reviewed (2 files)

• crates/phenotype-journeys-observability/Cargo.toml - 1 issue
• Cargo.lock - generated lockfile; no source-level findings (version churn consistent with the otlp bump)

Fix these issues in Kilo Cloud

---

_{Reviewed by hy3-20260706:free · Input: 77.1K · Output: 10.2K · Cached: 150K}