ref(core): Remove experimental flag from ignoreSentryInternalFrames - #23200
Merged
chargome merged 1 commit intoAug 10, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Member
Author
|
bugbert 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 72b6730. Configure here.
Contributor
size-limit report 📦
|
chargome
marked this pull request as ready for review
August 10, 2026 09:17
nicohrubec
approved these changes
Aug 10, 2026
andreiborza
approved these changes
Aug 10, 2026
chargome
deleted the
cg/third-party-filter-ignore-internal-frames-stable
branch
August 10, 2026 09:20
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
3 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.
Marks the
ignoreSentryInternalFramesoption ofthirdPartyErrorFilterIntegrationas stable and documents its default. No behaviour change.We're keeping it opt-in for now until we get further signal on how it performs in the wild. Detecting the SDK wrapper frame in minified bundles is heuristic, so defaulting it on risks dropping first-party errors under a
drop-*behaviour before we know how often that misfires.closes #18634