chore(deps): bump tracing-opentelemetry from 0.32.1 to 0.33.0 in the opentelemetry group

[dependabot]

Bumps the opentelemetry group with 1 update: tracing-opentelemetry.

Updates tracing-opentelemetry from 0.32.1 to 0.33.0

Release notes

Sourced from tracing-opentelemetry's releases.

0.33.0

Fixed

• [breaking] avoid deadlock when entering a span (#251)

Other

• Upgrade to OpenTelemetry 0.32, see upstream changelog for details (#258)
• mimimize package size (#252)

Changelog

Sourced from tracing-opentelemetry's changelog.

0.33.0 - 2026-05-18

Fixed

• [breaking] avoid deadlock when entering a span (#251)

Other

• Upgrade to OpenTelemetry 0.32, see upstream changelog for details (#258)
• mimimize package size (#252)

Commits

• 1d5422f chore: prepare release of 0.33.0
• f67ceb8 fix: use reentrant tracing fix in one more place (#263)
• 07c394b chore: rewirte reentrant tracing checks (#262)
• eb59bda fix!: avoid deadlock when entering a span (#251)
• 44521fa chore: Upgrade to OpenTelemetry 0.32 (#258)
• 91c4faa chore: mimimize package size (#252)
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[rubberduck203]

Why it was broken

Cargo.toml floats all opentelemetry crates with "*", so Cargo.lock is the source of truth for resolved versions. Dependabot bumped only tracing-opentelemetry (0.32.1 → 0.33.0) but left opentelemetry, opentelemetry_sdk, and opentelemetry-otlp at 0.31.x in the lock. tracing-opentelemetry 0.33 requires opentelemetry 0.32, so cargo saw two versions of opentelemetry in the graph and failed to compile with trait impl mismatches.

Fix

Pushed a commit to this branch that regenerates Cargo.lock to bring the entire opentelemetry stack to 0.32 together:

cargo update \
  -p opentelemetry@0.31.0 \
  -p opentelemetry_sdk@0.31.0 \
  -p opentelemetry-otlp@0.31.1 \
  -p opentelemetry-http@0.31.0 \
  -p opentelemetry-proto@0.31.0

cargo build and cargo test both pass after the fix.

Trace verification

Verified that traces still reach Jaeger end-to-end with the upgraded stack. Started a local Jaeger instance (OTLP gRPC on port 14317) and ran two commands:

SCOPE_OTEL_ENDPOINT=http://localhost:14317 scope doctor list
SCOPE_OTEL_ENDPOINT=http://localhost:14317 scope version

Jaeger services endpoint:

$ curl -sf "http://localhost:16686/api/services" | jq '.'
{
  "data": ["jaeger", "scope", "gdev"],
  ...
}

Traces received (2 traces, one per command):

$ curl -sf "http://localhost:16686/api/traces?service=scope&lookback=5m&limit=50" \
  | jq -r '.data[].spans[].operationName' | sort -u
scope doctor list
scope version

--- trace b3c47368 --- (scope doctor list)
  scope doctor list
--- trace 56806027 --- (scope version)
  scope version

The tracing-opentelemetry 0.33 deadlock fix did not break the OTLP gRPC exporter path. Safe to merge once CI is green.

[socket-security]

Caution

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. For more information please check in at #security-help. For License Policy Violations please also tag @Aoife in #security-help.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		License policy violation: cargo webpki-root-certs under CDLA-Permissive-2.0 License: CDLA-Permissive-2.0 - The applicable license policy does not permit this license (5) (webpki-root-certs-1.0.7/Cargo.toml) License: CDLA-Permissive-2.0 - The applicable license policy does not permit this license (5) (webpki-root-certs-1.0.7/LICENSE) From: ? → cargo/opentelemetry-otlp@0.32.0 → cargo/webpki-root-certs@1.0.7 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/webpki-root-certs@1.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report