[Snyk] Security upgrade react-native from 0.20.0 to 0.69.12#29
[Snyk] Security upgrade react-native from 0.20.0 to 0.69.12#29MHxGH-ServiceAccount wants to merge 1 commit intomasterfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MINIMATCH-15309438
|
This is a massive upgrade across approximately 49 major versions, representing a complete project migration rather than a simple dependency update. Manually upgrading by changing the version number in Recommendation: Do not attempt a manual upgrade. The only supported method is to use the official React Native Upgrade Helper. This tool generates a diff of all the file changes between your current version and the target version, which you must apply incrementally. For older or heavily customized projects, creating a new project with the target version and migrating your source code is often a safer approach. Key Breaking Changes Include:
Source: React Native Upgrade Helper
|
⛔ Snyk checks have failed. 2 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| }, | ||
| "dependencies": { | ||
| "react-native": "0.20.0", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
Missing required react peer dependency for RN 0.69
High Severity
Upgrading react-native to 0.69.12 requires react@18.0.0 as a peer dependency, but react is not listed in dependencies. In RN 0.20, React was bundled inside react-native, so a separate react dependency wasn't needed. Starting from RN 0.44+, react became a required peer dependency. Without it, npm install will fail or produce broken installs, and the app will not run.
| }, | ||
| "dependencies": { | ||
| "react-native": "0.20.0", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
Start script references removed local-cli/cli.js path
High Severity
The start script references node_modules/react-native/local-cli/cli.js, which was removed from react-native as part of the Lean Core effort. In RN 0.69.x the CLI lives in the separate @react-native-community/cli package. This script will fail with a "module not found" error. The path was valid for RN 0.20 but is broken after the version bump to 0.69.12.


Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
examples/SampleRN20/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-MINIMATCH-15309438
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
Note
High Risk
Large major-version jump in
react-nativefor the sample app, which is likely to introduce build/runtime incompatibilities even though the code change is small.Overview
Upgrades the
examples/SampleRN20app’sreact-nativedependency from0.20.0to0.69.12(Snyk-driven security bump), leaving the rest of the sample app dependencies unchanged.Written by Cursor Bugbot for commit 7a42515. This will update automatically on new commits. Configure here.