sentry/react-native update 1.3.9#113
Merged
brentvatne merged 1 commit intoexpo:masterfrom May 22, 2020
Merged
Conversation
Member
|
edit: could you link me to a resource with more info about this vulernability? |
Contributor
Author
|
@brentvatne The text of the email is the same as the text written in this issue. |
Member
|
this actually doesn't seem to impact sentry-expo in managed expo applications because we don't use the native sdk, we just use the js portions |
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.
Why
Old @sentry/react-native has security issues. that could potentially lead to access to source map in applications at iOS SDK.
Therefore, it is necessary to update to a benign version.