[Snyk] Security upgrade react-native from 0.20.0 to 0.69.12#30
[Snyk] Security upgrade react-native from 0.20.0 to 0.69.12#30MHxGH-ServiceAccount wants to merge 1 commit intomasterfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MINIMATCH-15353389
|
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 version 18.0.0 as a peer dependency, but react is not listed in dependencies at all. In RN 0.20.0, React was bundled with React Native, but since RN 0.60+, react must be explicitly declared. Without it, npm install will fail or produce warnings, 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 path incompatible with RN 0.69
Medium Severity
The start script still references node node_modules/react-native/local-cli/cli.js start, which is the entry point for RN 0.20.0. Since RN 0.60+, the CLI moved to @react-native-community/cli, and the standard start script for RN 0.69 is "react-native start". This path may not exist or may not function correctly in RN 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-15353389
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:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.
Note
High Risk
Upgrading
react-nativefrom 0.20.0 to 0.69.12 is a major version jump and may break theSampleRN20example app due to large React Native API/build tooling changes, despite being isolated to an example package.Overview
Updates the
examples/SampleRN20example app dependency onreact-nativefrom0.20.0to0.69.12(Snyk-driven security upgrade), leaving other dependencies unchanged.Written by Cursor Bugbot for commit 5093ec5. This will update automatically on new commits. Configure here.