-
Notifications
You must be signed in to change notification settings - Fork 503
[Snyk] Security upgrade react-native from 0.81.5 to 0.84.0 #10282
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: x
Are you sure you want to change the base?
Changes from all commits
d196e2c
678011b
93f7e6b
9d368c6
077eaa5
4381922
19199c8
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 |
|---|---|---|
|
|
@@ -114,7 +114,7 @@ | |
| "lottie-react-native": "7.3.4", | ||
| "path-browserify": "^1.0.1", | ||
| "react": "19.1.0", | ||
| "react-native": "0.81.5", | ||
| "react-native": "0.84.0", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔴 Version-specific patch file react-native+0.81.5.patch will not apply to 0.84.0 The repository has a Detailed Explanation
If react-native 0.84.0 is installed, Impact: Loss of custom paste functionality and nil-safety fixes, potentially causing crashes when nil values reach the JSI bridge. Was this helpful? React with 👍 or 👎 to provide feedback.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔴 The Version Alignment DetailThe Impact: Metro bundler may produce bundles incompatible with the react-native 0.84.0 runtime, causing crashes or subtle JS errors at runtime. Prompt for agentsWas this helpful? React with 👍 or 👎 to provide feedback. |
||
| "react-native-aes-crypto": "3.2.1", | ||
| "react-native-awesome-slider": "^2.9.0", | ||
| "react-native-ble-plx": "3.5.1", | ||
|
|
||
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.
🔴 Root workspace resolution still pins react-native to 0.81.5, making the upgrade ineffective or conflicting
The
apps/mobile/package.jsonbumpsreact-nativeto0.84.0, but the rootpackage.jsonhas a Yarnresolutionsfield that pins"react-native": "0.81.5"atpackage.json:329. Yarn resolutions override version specifications across the entire workspace, so the mobile app will still resolve to0.81.5despite requesting0.84.0.Root Cause and Impact
The root
package.jsoncontains:dependencies["react-native"]: "0.81.5"at line 175resolutions["react-native"]: "0.81.5"at line 329Both of these force the entire monorepo to use
0.81.5. The change inapps/mobile/package.jsonto0.84.0is effectively a no-op — the security vulnerability (SNYK-JS-MINIMATCH-15309438) that this PR aims to fix will not actually be remediated.Additionally, if the resolution were somehow bypassed, there would be a version mismatch between what the mobile app uses and what the rest of the monorepo expects, potentially causing runtime crashes from incompatible native modules.
Impact: The stated security fix is not applied. The
package.jsondeclares a version that won't actually be installed, creating a false sense of security.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.