ref(core): Remove otel-based suppressTracing implementation#22574
Draft
mydea wants to merge 3 commits into
Draft
ref(core): Remove otel-based suppressTracing implementation#22574mydea wants to merge 3 commits into
suppressTracing implementation#22574mydea wants to merge 3 commits into
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| getTraceContextForScope, | ||
| } from './trace'; | ||
|
|
||
| export { suppressTracing } from './utils/suppressTracing'; |
There was a problem hiding this comment.
Public export removed without notice
Medium Severity
suppressTracing was removed from @sentry/opentelemetry's public exports without a deprecation period. This violates the PR review rule on breaking changes for publicly exported APIs. Flagged because it was mentioned in the rules file.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit a7c1182. Configure here.
Member
Author
There was a problem hiding this comment.
we do not care about opentelemetry package removals
Contributor
size-limit report 📦
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2ba61a0. Configure here.
mydea
force-pushed
the
fn/suppressTracing
branch
from
July 24, 2026 12:12
2ba61a0 to
e8aa6c4
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
1 participant
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.
Now, by default suppress tracing is async context aware, and we only overwrite this for the stack strategy (in browser) to have special handling (which used to be the default). node, cloudflare, deno can all use the default implementation.