Repository navigation
Upgrade Sentry with ID-only attribution and limited data collection - #66
Merged
Merged
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
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.
Upgrades
@sentry/reactand@sentry/nodeto 11.0.0 together, superseding #61 and #62. Sentry 11 broadens automatic data collection by default, so both SDKs now use explicit restrictive settings while keeping user ID attribution.Validation:
mix precommitpassed (224 Elixir checks and 4 frontend tests, including lint and TypeScript checks);mix assets.buildpassed; the built SSR bundle rendered the login form and captured separate ID-only errors for two users and an anonymous request using an in-memory transport.Migration reference: Sentry 10 to 11 data collection changes.