-
-
Notifications
You must be signed in to change notification settings - Fork 237
[Snyk] Security upgrade react-native from 0.83.0 to 0.84.0 #553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,7 +13,7 @@ | |
| "dependencies": { | ||
| "@react-native/new-app-screen": "0.83.0", | ||
| "react": "19.2.3", | ||
| "react-native": "0.83.0", | ||
| "react-native": "0.84.0", | ||
| "react-native-nitro-modules": "0.31.10", | ||
|
Comment on lines
14
to
17
|
||
| "react-native-safe-area-context": "^5.6.2" | ||
| }, | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This bumps
react-nativeto 0.84.0 in the workspace manifest, but the repo’syarn.lockstill resolvesreact-nativeto 0.83.0 (including forreact-native-sensitive-info-example@workspace:example). As-is, CI/builds that rely on the committed lockfile won’t actually pick up 0.84.0 and the vulnerability fix may not apply. Please runyarn install(or the project’s standard install command) and commit the updatedyarn.lockso it resolvesreact-native@0.84.0for the example workspace (and ensure workspace constraints, e.g. rootpackage.json, don’t keep it pinned to 0.83.x).