feat(inbound-filters): Update legacy browser versions #5326
Conversation
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
jjbayer
approved these changes
Nov 3, 2025
Member
jjbayer
left a comment
jjbayer
left a comment
There was a problem hiding this comment.
You might also want to update the date mentioned in https://docs.sentry.io/concepts/data-management/filtering/#legacy-browser-filters.
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
roggenkemper
added a commit
to getsentry/sentry
that referenced
this pull request
Dec 9, 2025
…lter (#104250) filter is updated in getsentry/relay#5326, updates the serializer to match.
roggenkemper
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Dec 10, 2025
#15696) updates the date to show that the legacy browser filter will be updated soon getsentry/relay#5326
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
our legacy browser inbound filter has been roughly aligned with NextJS which recently did an update - https://nextjs.org/docs/architecture/supported-browsers. updating our inbound filter to match the versions they support