feat!: Replace skipOpenTelemetrySetup with enableOpenTelemetrySetup - #23199
Merged
Conversation
Contributor
size-limit report 📦
|
andreiborza
marked this pull request as ready for review
August 10, 2026 08:39
andreiborza
requested review from
JPeer264,
mydea,
nicohrubec and
s1gr1d
and removed request for
a team
August 10, 2026 08:39
nicohrubec
approved these changes
Aug 10, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
andreiborza
force-pushed
the
ab/js-3336-enable-opentelemetry-setup
branch
from
August 10, 2026 09:37
7da7955 to
7ae0a89
Compare
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What
Replace the
skipOpenTelemetrySetupoption withenableOpenTelemetrySetup: boolean(inverted meaning, per-package behavior unchanged).@sentry/node,@sentry/cloudflare: defaults tofalse(no Sentry tracer provider)exit@sentry/nextjs,@sentry/sveltekit: passtruesince they own OTel spans by default@sentry/deno,@sentry/vercel-edge: keep OTel setup on by default, so the flag defaults totruethereWhy
Since v11 most server SDKs no longer set up OpenTelemetry by default, so the option is now an opt-in and a positive
enableflag reads clearer than the double negativeskip: false. The nextjs tunnel-drop check only bails on an explicitfalseso edge clients without the merged node default keep processing spans as before.