Skip to content

[Snyk] Security upgrade react-native from 0.74.1 to 0.76.0 #16

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.

Sign up for GitHub

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

Open
revan-zhang wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade react-native from 0.74.1 to 0.76.0 #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion example/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"jcore-react-native": "^2.3.0",
"jpush-react-native": "^3.2.1",
"react": "18.2.0",
"react-native": "0.74.1"
"react-native": "0.76.0"
Copy link

@devin-ai-integration devin-ai-integration bot Mar 19, 2026

Choose a reason for hiding this comment

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

🟡 devDependencies @react-native/* packages not updated to match new react-native 0.76.0

react-native is bumped from 0.74.1 to 0.76.0, but the @react-native/babel-preset, @react-native/eslint-config, @react-native/metro-config, and @react-native/typescript-config devDependencies remain pinned at 0.74.83. These @react-native/* packages are part of the react-native monorepo and are versioned in lockstep with it. Using 0.74.83 tooling with react-native 0.76.0 will likely cause Metro bundler configuration incompatibilities or build failures in the example app, as each major react-native release expects the matching versions of these companion packages.

Prompt for agents 
In example/package.json, update the @react-native/* devDependencies on lines 22-25 to versions matching react-native 0.76.0. These packages are released in lockstep with react-native from the same monorepo. The correct versions would be the 0.76.x variants, e.g.:

  "@react-native/babel-preset": "0.76.0",
  "@react-native/eslint-config": "0.76.0",
  "@react-native/metro-config": "0.76.0",
  "@react-native/typescript-config": "0.76.0"

Also verify that react 18.2.0 is compatible with react-native 0.76.0 (react-native 0.76 typically expects react 18.3.1).
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link

@cursor cursor bot Mar 19, 2026

Choose a reason for hiding this comment

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

Mismatched React version for React Native 0.76.0

High Severity

react-native was bumped to 0.76.0 but react remains at 18.2.0. React Native 0.76.0 expects react 18.3.1 as its peer dependency. This version mismatch will cause npm peer dependency errors during install and may lead to runtime incompatibilities, since 0.76.0 depends on APIs and deprecation warnings introduced in React 18.3.

Fix in Cursor Fix in Web

Copy link

@cursor cursor bot Mar 19, 2026

Choose a reason for hiding this comment

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

Dev dependencies not updated for React Native 0.76

High Severity

react-native was bumped to 0.76.0 but @react-native/babel-preset, @react-native/eslint-config, @react-native/metro-config, and @react-native/typescript-config all remain pinned at 0.74.83. These packages are versioned in lockstep with react-native and need to be 0.76.x. Notably, the babel preset 0.76 enables the Hermes parser by default, which is required for correct transpilation in 0.76.

Fix in Cursor Fix in Web

},
"devDependencies": {
"@babel/core": "^7.20.0",
Expand Down