Skip to content

[TRIVIAL] Update OTel versions#4563

Merged
jmg-duarte merged 1 commit into
mainfrom
jmgd/otel
Jun 26, 2026
Merged

[TRIVIAL] Update OTel versions#4563
jmg-duarte merged 1 commit into
mainfrom
jmgd/otel

Conversation

@jmg-duarte

Copy link
Copy Markdown
Contributor

This update brings the reqwest version into "sync" which will enable setting async DNS resolution for all reqwest callers

This update brings the reqwest version into "sync" which will enable
setting async DNS resolution for all reqwest callers
@jmg-duarte jmg-duarte requested a review from a team as a code owner June 25, 2026 16:46
@jmg-duarte jmg-duarte changed the title Update OTel versions [TRIVIAL] Update OTel versions Jun 25, 2026
@claude

claude Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Claude finished @jmg-duarte's task in 1m 18s —— View job


PR Review: Update OTel versions

  • Read the diff (Cargo.toml, Cargo.lock)
  • Analyze version changes and dependency syncing
  • Check for issues / build implications
  • Post review feedback

Reviewed the dependency bump. This is a clean, low-risk update and the PR description's claim holds up. ✅

What changed

  • opentelemetry, opentelemetry-http, opentelemetry-otlp, opentelemetry_sdk: 0.310.32
  • tracing-opentelemetry: 0.32.10.33.0
  • Cargo.lock regenerated accordingly.

reqwest sync confirmed. Before this PR the tree carried two reqwest versions: 0.12.28 (pulled in by opentelemetry-http/opentelemetry-otlp 0.31) and 0.13.2 (everything else). OTel 0.32 depends on reqwest 0.13, so 0.12.28 is dropped entirely — the lockfile now resolves to a single reqwest 0.13.2. That's the prerequisite for setting async DNS resolution uniformly across all reqwest callers, as described.

Observations

  • No source changes were required, which means the OTel 0.31 → 0.32 API surface used in crates/observe (SpanExporter::builder().with_tonic(), SdkTracerProvider, HeaderExtractor/HeaderInjector, tracing_opentelemetry::layer()) is compatible. Worth confirming the build/clippy CI jobs go green before merge since there's no local source verification possible here.
  • Minor: opentelemetry_sdk resolves to 0.32.1 while the sibling crates are 0.32.0 — semver-compatible with the "0.32" constraint, no concern. The upstream opentelemetry-otlp change (dropped tracing, added tonic-types) is internal to that crate.

No blocking issues found — looks good to merge once CI passes.

@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedopentelemetry@​0.31.0 ⏵ 0.32.09810093100100
Updatedopentelemetry-http@​0.31.0 ⏵ 0.32.010010093100100
Updatedopentelemetry-otlp@​0.31.0 ⏵ 0.32.09710093100100
Updatedopentelemetry_sdk@​0.31.0 ⏵ 0.32.19410093100100
Updatedtracing-opentelemetry@​0.32.1 ⏵ 0.33.0100 +110093100100

View full report

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the OpenTelemetry dependencies (opentelemetry, opentelemetry-http, opentelemetry-otlp, and opentelemetry_sdk) to version 0.32, and tracing-opentelemetry to version 0.33.0. It also standardizes the reqwest dependency version to 0.13.2 across the workspace and adds prost-types and tonic-types. No critical issues found.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@jmg-duarte jmg-duarte added this pull request to the merge queue Jun 26, 2026
Merged via the queue into main with commit 998525b Jun 26, 2026
22 checks passed
@jmg-duarte jmg-duarte deleted the jmgd/otel branch June 26, 2026 10:28
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants