Uh oh!
There was an error while loading. Please reload this page.
feat(deps): Bump OpenTelemetry dependencies to latest - #21988
Merged
Conversation
Bump the SDK's pinned OpenTelemetry versions to latest: - @opentelemetry/core, sdk-trace-base, resources: 2.6.1 to 2.9.0 - @opentelemetry/instrumentation, exporter-trace-otlp-http, instrumentation-http: 0.214.0 to 0.220.0 - @opentelemetry/semantic-conventions: 1.40.0 to 1.41.1 (integration tests only) Peer dependency ranges are intentionally left wide (^1.30.1 || ^2.1.0, >=0.57.1 <1) to preserve consumer compatibility; only the SDK's own pinned dev/runtime resolutions were raised. No source changes were required: - The 2.9.0 BatchSpanProcessor/SimpleSpanProcessor constructor change is absorbed by the sdk-trace-base compat shim, which keeps the positional signature the SDK uses. - The 2.8.0 tracestate set()-time W3C validation does not affect us because the SDK uses its own vendored TraceState. - The 0.220.0 HTTP semconv hardening does not apply; the SDK ships its own vendored HTTP instrumentation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
andreiborza
requested review from
JPeer264, chargome, mydea and nicohrubec
and removed request for
a teamJuly 6, 2026 13:38
andreiborza
commented
Jul 6, 2026
MemberAuthor
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 5bc6c46. Configure here.
nicohrubec
approved these changes
Jul 6, 2026
Contributor
size-limit report 📦
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the SDK's pinned OpenTelemetry dependencies to latest. Peer dependency ranges are intentionally left wide to preserve consumer compatibility; only the SDK's own pinned dev/runtime resolutions were raised.
Versions
@opentelemetry/core,sdk-trace-base,resources:2.6.1→2.9.0@opentelemetry/instrumentation,exporter-trace-otlp-http,instrumentation-http:0.214.0→0.220.0@opentelemetry/semantic-conventions:1.40.0→1.41.1(integration tests only)@opentelemetry/api: already at latest (1.9.1)No source changes required
Upstream shipped breaking changes in this range, but none affect code paths the SDK uses:
BatchSpanProcessor/SimpleSpanProcessorconstructors to an options object.@opentelemetry/sdk-trace-basere-exports them via a compat shim that keeps the old positional signature, which is what the SDK uses.tracestatevalidation intoTraceState.set(). The SDK uses its own vendoredTraceState(ref(opentelemetry): Vendor minimalTraceStateimplementation #21192), so its DSC keys and values are unaffected.Compatibility
The optional OpenTelemetry peer dependency ranges (
^1.30.1 || ^2.1.0,>=0.57.1 <1) already permit these versions and are left unchanged, so consumer compatibility is unaffected.@sentry/node-coreand@sentry/nodebuild cleanly and unit tests pass against the new versions.