Skip to content

[Snyk] Security upgrade react-native from 0.75.3 to 0.76.0 #20

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: main
Choose a base branch
from
Open

[Snyk] Security upgrade react-native from 0.75.3 to 0.76.0 #20

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 @@ -12,7 +12,7 @@
},
"dependencies": {
"react": "18.3.1",
"react-native": "0.75.3"
"react-native": "0.76.0"
Copy link

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

Choose a reason for hiding this comment

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

🔴 react-native bumped to 0.76.0 but @react-native/ devDependencies left at 0.75.3*

The react-native dependency was updated from 0.75.3 to 0.76.0, but the @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config devDependencies at example/package.json:21-23 are still pinned to 0.75.3. These packages are released in lockstep with react-native and must match the major.minor version. Running the example app with react-native 0.76.0 and @react-native/* 0.75.3 can cause build failures or incompatible Metro/Babel configurations.

Prompt for agents 
In example/package.json, update the @react-native/* devDependencies on lines 21-23 to match the react-native 0.76.0 version:

- "@react-native/babel-preset": "0.75.3" -> "0.76.0"
- "@react-native/metro-config": "0.75.3" -> "0.76.0"
- "@react-native/typescript-config": "0.75.3" -> "0.76.0"

These packages are released in lockstep with react-native and their major.minor versions must match.
Open in Devin Review

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

Copy link

@cursor cursor bot Mar 20, 2026

Choose a reason for hiding this comment

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

Mismatched @react-native/* devDependencies after react-native upgrade

High Severity

Upgrading react-native to 0.76.0 without updating the companion @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config packages (still at 0.75.3) creates a version mismatch. These @react-native/* packages are designed to be version-aligned with react-native and have corresponding 0.76.x releases. This mismatch is likely to cause build failures or runtime incompatibilities, especially given that 0.76 enables the New Architecture by default.

Additional Locations (1)
Fix in Cursor Fix in Web

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