Skip to content

chore(deps): update React Native to v0.87.1 #6607

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

Draft
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
+327 −151
Draft

chore(deps): update React Native to v0.87.1 #6607

Show file tree
Hide file tree
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 dev-packages/e2e-tests/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
"babel-jest": "^29.7.0",
"jest": "^29.7.0",
"react": "19.2.3",
"react-native": "0.86.2",
"react-native": "0.87.1",
"react-native-launch-arguments": "^4.0.2",
"typescript": "4.9.5",
"webdriverio": "^8.27.0"
Expand Down
2 changes: 1 addition & 1 deletion packages/core/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,8 +111,8 @@
"oxfmt": "^0.42.0",
"oxlint": "^1.56.0",
"oxlint-tsgolint": "^0.17.4",
"react": "19.1.0",
"react-native": "0.86.2",
"react-native": "0.87.1",

Check warning on line 115 in packages/core/package.json

View check run for this annotation

@sentry/warden / warden: code-review

[M7G-YAH] React Native 0.87.1 is paired with 0.86.2 Metro and Babel tooling (additional location) 

`performance-tests/TestAppPlain` now uses `react-native` 0.87.1, but its active Babel and Metro integrations remain at 0.86.2. `metro.config.js` directly loads `@react-native/metro-config`, while the React Native 0.87.1 community CLI plugin declares an exact `@react-native/metro-config` 0.87.1 peer. Please align `@react-native/babel-preset` and `@react-native/metro-config` with 0.87.1 to avoid incompatible build tooling; the TypeScript config is not used by this app because it has no tsconfig.

Check warning on line 115 in packages/core/package.json

View check run for this annotation

@sentry/warden / warden: find-bugs

React Native 0.87.1 is installed with an unsupported React version in the core workspace 

The core workspace directly installs `react-native@0.87.1` alongside `react@19.1.0`, but React Native 0.87.1 declares `react: ^19.2.3` as a peer dependency. This leaves the SDK's own build and test environment on an unsupported React/React Native combination. Update `react` and `react-test-renderer` in `packages/core/package.json` to 19.2.3.

@sentry-warden sentry-warden Bot Aug 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

React Native 0.87.1 is paired with incompatible 0.86.2 Metro tooling

Upgrade the explicitly declared @react-native/metro-config packages alongside React Native. React Native 0.87.1 brings @react-native/community-cli-plugin@0.87.1, whose optional peer requires @react-native/metro-config@0.87.1, while the core package and sample apps still install @react-native/metro-config@0.86.2. This can leave react-native start and Metro CLI integration running with an incompatible configuration package. The sample apps also retain @react-native/new-app-screen@0.86.2, whose peer dependency requires React Native exactly 0.86.2.

Evidence
  • react-native@0.87.1 depends on @react-native/community-cli-plugin@0.87.1 in yarn.lock.
  • @react-native/community-cli-plugin@0.87.1 declares @react-native/metro-config: 0.87.1, but no 0.87.x Metro config exists in the lockfile.
  • packages/core, samples/react-native, and both performance apps explicitly resolve @react-native/metro-config@0.86.2 and use it in their Metro configuration or SDK tooling.
  • samples/react-native and performance-tests/TestAppSentry retain @react-native/new-app-screen@0.86.2, whose lockfile peer requires react-native: 0.86.2.
Also found at 1 additional location
  • samples/react-native/package.json:56-56

Identified by Warden · code-review, find-bugs · TBY-FGC

@sentry-warden sentry-warden Bot Aug 27, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Fix attempt detected (commit 8be6162)

The commit upgrades React Native to 0.87.1 and refreshes the lockfile, but leaves the explicitly declared @react-native/metro-config and @react-native/new-app-screen dependencies at 0.86.2 in the sample and performance apps, so the incompatibility persists.

The original issue appears unresolved. Please review and try again.

Evaluated by Warden

@sentry-warden sentry-warden Bot Aug 28, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Fix attempt detected (commit e98296d)

The commit upgraded React Native to 0.87.1 and refreshed related lockfile tooling, but the sample and performance apps still explicitly use @react-native/metro-config@0.86.2 and @react-native/new-app-screen@0.86.2, so the incompatibility remains.

The original issue appears unresolved. Please review and try again.

Evaluated by Warden

@sentry-warden sentry-warden Bot Aug 28, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Fix attempt detected (commit fdea9eb)

The commit upgrades React Native to 0.87.1 and its lockfile entries, but leaves @react-native/metro-config@0.86.2 in the sample and performance app manifests and retains @react-native/new-app-screen@0.86.2, so the incompatibility persists.

The original issue appears unresolved. Please review and try again.

Evaluated by Warden

Comment thread
sentry-warden[bot] marked this conversation as resolved.
"react-test-renderer": "19.1.0",

Check warning on line 116 in packages/core/package.json

View check run for this annotation

@sentry/warden / warden: code-review

Core workspace uses React 19.1.0 with React Native 0.87.1's incompatible peer requirement 

Update `react` in `packages/core/package.json` to `19.2.3` to satisfy `react-native@0.87.1`'s `react` peer dependency. Keep `react-test-renderer` aligned at `19.2.3` as well, since the core workspace uses it for React Native tests.
"rimraf": "^4.1.1",
"ts-jest": "^29.3.1",
Expand Down
2 changes: 1 addition & 1 deletion performance-tests/TestAppPlain/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@
},
"dependencies": {
"react": "19.2.3",
"react-native": "0.86.2"
"react-native": "0.87.1"

Check warning on line 12 in performance-tests/TestAppPlain/package.json

View check run for this annotation

@sentry/warden / warden: code-review

React Native 0.87.1 is paired with 0.86.2 Metro and Babel tooling 

`performance-tests/TestAppPlain` now uses `react-native` 0.87.1, but its active Babel and Metro integrations remain at 0.86.2. `metro.config.js` directly loads `@react-native/metro-config`, while the React Native 0.87.1 community CLI plugin declares an exact `@react-native/metro-config` 0.87.1 peer. Please align `@react-native/babel-preset` and `@react-native/metro-config` with 0.87.1 to avoid incompatible build tooling; the TypeScript config is not used by this app because it has no tsconfig.
},

Check warning on line 13 in performance-tests/TestAppPlain/package.json

View check run for this annotation

@sentry/warden / warden: find-bugs

RN bumped to 0.87.1 but companion @react-native/* packages left on 0.86.2 

Bump `@react-native/babel-preset`, `@react-native/metro-config`, and `@react-native/typescript-config` to 0.87.1 as well; otherwise Metro stays on 0.84 while RN 0.87 expects 0.87 and bundling can break.
"devDependencies": {
"@babel/core": "^7.25.2",
"@babel/preset-env": "^7.25.3",
Expand Down
2 changes: 1 addition & 1 deletion performance-tests/TestAppSentry/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"@react-native/new-app-screen": "0.86.2",
"@sentry/react-native": "8.24.0",
"react": "19.2.3",
"react-native": "0.86.2"
"react-native": "0.87.1"

Check warning on line 14 in performance-tests/TestAppSentry/package.json

View check run for this annotation

@sentry/warden / warden: find-bugs

[8ZF-AKE] RN bumped to 0.87.1 but companion @react-native/* packages left on 0.86.2 (additional location) 

Bump `@react-native/babel-preset`, `@react-native/metro-config`, and `@react-native/typescript-config` to 0.87.1 as well; otherwise Metro stays on 0.84 while RN 0.87 expects 0.87 and bundling can break.
},
"devDependencies": {
"@babel/core": "^7.25.2",
Expand Down
2 changes: 1 addition & 1 deletion samples/expo/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@
"expo-web-browser": "~57.0.0",
"react": "19.2.3",
"react-dom": "19.2.3",
"react-native": "0.86.2",
"react-native": "0.87.1",
"react-native-gesture-handler": "~2.32.0",
"react-native-safe-area-context": "~5.7.0",
"react-native-screens": "~4.25.2",
Expand Down
2 changes: 1 addition & 1 deletion samples/react-native-macos/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@
"@sentry/react-native": "8.24.0",
"delay": "^6.0.0",
"react": "19.1.4",
"react-native": "0.81.6",
"react-native": "0.87.1",
"react-native-gesture-handler": "2.14.0",
"react-native-macos": "0.81.8",

Check failure on line 26 in samples/react-native-macos/package.json

View check run for this annotation

@sentry/warden / warden: code-review

react-native 0.87.1 is incompatible with react-native-macos 0.81.8 

Bump react-native back to the 0.81.x line (or also upgrade react-native-macos and the @react-native/* 0.81.6 tooling) so this sample stays on a matched RN/macOS pair.
"react-native-reanimated": "3.19.5",
"react-native-safe-area-context": "4.8.0",
"react-native-screens": "3.29.0",
Expand Down
2 changes: 1 addition & 1 deletion samples/react-native/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@
"@shopify/flash-list": "^2.0.2",
"delay": "^6.0.0",
"react": "19.2.3",
"react-native": "0.86.2",
"react-native": "0.87.1",

Check warning on line 56 in samples/react-native/package.json

View check run for this annotation

@sentry/warden / warden: find-bugs

[8ZF-AKE] RN bumped to 0.87.1 but companion @react-native/* packages left on 0.86.2 (additional location) 

Bump `@react-native/babel-preset`, `@react-native/metro-config`, and `@react-native/typescript-config` to 0.87.1 as well; otherwise Metro stays on 0.84 while RN 0.87 expects 0.87 and bundling can break.
"react-native-build-config": "^0.3.2",
"react-native-gesture-handler": "^3.0.1",
"react-native-image-picker": "^8.2.1",
Expand Down
Loading
Loading