Skip to content

[Snyk] Security upgrade react-native from 0.40.0 to 0.69.12#38

Open
MHxGH-ServiceAccount wants to merge 1 commit into
masterfrom
snyk-fix-8f03815a598565e8bddaf41314814846
Open

[Snyk] Security upgrade react-native from 0.40.0 to 0.69.12#38
MHxGH-ServiceAccount wants to merge 1 commit into
masterfrom
snyk-fix-8f03815a598565e8bddaf41314814846

Conversation

@MHxGH-ServiceAccount

@MHxGH-ServiceAccount MHxGH-ServiceAccount commented Dec 31, 2025

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • examples/TouchIDExample/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-14724253
  170  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

🦉 Allocation of Resources Without Limits or Throttling


Note

Updates dependency in the example app.

  • Bumps react-native in examples/TouchIDExample/package.json from ^0.40.0 to ^0.69.12

Written by Cursor Bugbot for commit 40220b8. This will update automatically on new commits. Configure here.

@MHxGH-ServiceAccount

MHxGH-ServiceAccount commented Dec 31, 2025

Copy link
Copy Markdown
Author

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@MHxGH-ServiceAccount

Copy link
Copy Markdown
Author

Merge Risk: High

This is a massive upgrade across nearly 30 minor versions, representing a complete architectural overhaul of React Native. A direct upgrade is not feasible; this should be treated as a full project migration.

Key Breaking Changes:

  • New Architecture: The legacy bridge is replaced by a new architecture (Fabric renderer and TurboModules) starting around v0.68. This fundamentally changes how JavaScript and native code interact, requiring all native dependencies to be audited and updated for compatibility. [1, 2, 7, 8]
  • Autolinking: The manual react-native link command was replaced by autolinking in v0.60. [11, 14] Native dependencies are now linked automatically via Gradle (Android) and Cocoapods (iOS), requiring a complete change in project setup.
  • Extracted Core Components: Many APIs and UI components (e.g., AsyncStorage, WebView, Slider) have been removed from the core library and must be installed from separate community packages like @react-native-community/async-storage. [16, 26]

Recommendation: Do not attempt an in-place upgrade. The recommended path is to create a new project using react-native@0.69.12 and migrate your application source code, assets, and dependencies incrementally. Use the official React Native Upgrade Helper tool to see the vast configuration changes required. [18, 20]

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

"dependencies": {
"react": "^15.1.0",
"react-native": "^0.40.0",
"react-native": "^0.69.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

React version incompatible with upgraded React Native

Upgrading react-native from 0.40.0 to 0.69.12 creates a dependency incompatibility. React Native 0.69.x requires React 18.x as a peer dependency, but react remains at ^15.1.0. This version mismatch will prevent the example application from building or running correctly. The react dependency needs to be updated to a compatible version (React 18.x) alongside this React Native upgrade.

Fix in Cursor Fix in Web

"dependencies": {
"react": "^15.1.0",
"react-native": "^0.40.0",
"react-native": "^0.69.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Start script uses deprecated CLI path

The start script references node_modules/react-native/local-cli/cli.js, a path that no longer exists in React Native 0.69.x. The CLI was extracted to @react-native-community/cli in earlier versions. With the upgraded react-native dependency, this script will fail to execute. Modern React Native projects typically use npx react-native start or rely on the CLI's auto-discovery.

Fix in Cursor Fix in Web

"dependencies": {
"react": "^15.1.0",
"react-native": "^0.40.0",
"react-native": "^0.69.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrade breaks code using removed AlertIOS API

The react-native upgrade to 0.69.12 removes the AlertIOS API that the example's index.ios.js relies on heavily. AlertIOS was deprecated and then removed from React Native in favor of the cross-platform Alert module. With this upgrade, the example app will crash at runtime when attempting to show alerts because the imported AlertIOS will be undefined.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants