Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
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.0",
"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
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@
"oxlint": "^1.56.0",
"oxlint-tsgolint": "^0.17.4",
"react": "19.1.0",
"react-native": "0.86.2",
"react-native": "0.87.0",
"react-test-renderer": "19.1.0",
"rimraf": "^4.1.1",
"ts-jest": "^29.3.1",
Expand Down
2 changes: 1 addition & 1 deletion performance-tests/TestAppPlain/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,10 @@
"start": "react-native start"
},
"dependencies": {
"react": "19.2.3",

Check failure on line 11 in performance-tests/TestAppPlain/package.json

View check run for this annotation

@sentry/warden / warden: code-review

[ZEY-H6A] React Native companion packages left at 0.86.2 while core updates to 0.87.0 (additional location)

The automated update bumped `react-native` to 0.87.0, but `@react-native/*` monorepo packages remain at 0.86.2 in several changed files. Mismatched React Native framework package versions typically cause Metro, Babel, or Jest failures.
"react-native": "0.86.2"
"react-native": "0.87.0"

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

View check run for this annotation

@sentry/warden / warden: find-bugs

React Native tooling packages not bumped with core package

The `react-native` bump to 0.87.0 is incomplete: related `@react-native/*` packages remain pinned to 0.86.2 across files modified in this PR, which can break builds and tests.
},
"devDependencies": {

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

View check run for this annotation

@sentry/warden / warden: find-bugs

[43C-E6X] React Native tooling packages not bumped with core package (additional location)

The `react-native` bump to 0.87.0 is incomplete: related `@react-native/*` packages remain pinned to 0.86.2 across files modified in this PR, which can break builds and tests.

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 companion packages remain at 0.86.2 after main package bumped to 0.87.0

react-native was bumped to 0.87.0 but @react-native/new-app-screen, @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config stay at 0.86.2.

Evidence
  • performance-tests/TestAppSentry/package.json line 14 bumped react-native to 0.87.0.
  • Lines 11 and 23–25 leave @react-native/new-app-screen, @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config at 0.86.2.
  • yarn.lock shows react-native@0.87.0 depends on monorepo packages at 0.87.0 (e.g., @react-native/codegen, @react-native/gradle-plugin, @react-native/virtualized-lists).
  • Unaligned toolchain packages frequently cause Metro bundling or Babel transform errors during builds.

Identified by Warden · find-bugs · 3BV-5VG

"@babel/core": "^7.25.2",
"@babel/preset-env": "^7.25.3",
"@babel/runtime": "^7.25.0",
Expand Down
2 changes: 1 addition & 1 deletion performance-tests/TestAppSentry/package.json
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.23.0",
"react": "19.2.3",
"react-native": "0.86.2"
"react-native": "0.87.0"

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

View check run for this annotation

@sentry/warden / warden: code-review

[ZEY-H6A] React Native companion packages left at 0.86.2 while core updates to 0.87.0 (additional location)

The automated update bumped `react-native` to 0.87.0, but `@react-native/*` monorepo packages remain at 0.86.2 in several changed files. Mismatched React Native framework package versions typically cause Metro, Babel, or Jest failures.
},
Comment thread
sentry-warden[bot] marked this conversation as resolved.
"devDependencies": {
"@babel/core": "^7.25.2",
Expand Down
2 changes: 1 addition & 1 deletion samples/expo/package.json
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.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Expo sample on unsupported RN

Medium Severity

Flagged per the dependency-update review guidelines: the Expo sample stays on Expo SDK ^57.0.0 (which targets React Native 0.86) while react-native was bumped to 0.87.0. That pairing is outside Expo’s supported matrix and can break prebuild, native modules, or Expo Go / dev-client workflows.

Fix in Cursor Fix in Web

Triggered by project rule: PR Review Guidelines for Cursor Bot

Reviewed by Cursor Bugbot for commit af10bcc. Configure here.

"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
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@
"@sentry/react-native": "8.23.0",
"delay": "^6.0.0",
"react": "19.1.4",
"react-native": "0.81.6",
"react-native": "0.87.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

macOS sample RN version mismatch

High Severity

Flagged per the dependency-update review guidelines: react-native was bumped to 0.87.0 while react-native-macos stays at 0.81.8. Those packages need matching minor versions, so the macOS sample is unlikely to install or build. The updater appears to have applied yarn up react-native across the monorepo, including this intentionally pinned older sample.

Fix in Cursor Fix in Web

Triggered by project rule: PR Review Guidelines for Cursor Bot

Reviewed by Cursor Bugbot for commit af10bcc. Configure here.

"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-macos 0.81.8 incompatible with react-native 0.87.0

react-native-macos 0.81.8 is built for React Native 0.81.x and will fail to build or run against react-native 0.87.0; either bump react-native-macos to a matching version or leave react-native at 0.81.6 in this sample.
"react-native-reanimated": "3.19.5",
Comment on lines 21 to 27

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The react-native-macos version (0.81.8) is incompatible with the updated react-native version (0.87.0), which will cause the macOS sample app build to fail.
Severity: CRITICAL

Suggested Fix

Update the react-native-macos dependency in samples/react-native-macos/package.json to a version compatible with react-native@0.87.0, likely 0.87.0 or a corresponding minor version.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: samples/react-native-macos/package.json#L21-L27

Potential issue: In the `react-native-macos` sample app, the `react-native` dependency
was updated to version `0.87.0`, but the `react-native-macos` dependency was left at
`0.81.8`. These two packages must have matching versions to be compatible. This mismatch
will cause the `build-macos` CI job to fail during either the `pod install` step due to
dependency resolution errors or the Xcode build step due to mismatched native APIs and
symbols. Even if a build were to succeed, the application would likely crash at runtime.

Also affects:

  • yarn.lock:28054~28060

Did we get this right? 👍 / 👎 to inform future reviews.

"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
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.0",

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

View check run for this annotation

@sentry/warden / warden: code-review

React Native companion packages left at 0.86.2 while core updates to 0.87.0

The automated update bumped `react-native` to 0.87.0, but `@react-native/*` monorepo packages remain at 0.86.2 in several changed files. Mismatched React Native framework package versions typically cause Metro, Babel, or Jest failures.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Reanimated peers reject RN 0.87

High Severity

Flagged per the dependency-update review guidelines: react-native is now 0.87.0, but react-native-reanimated@4.4.1 and react-native-worklets@0.9.2 declare peer ranges of react-native: 0.83 - 0.86. RN 0.87 needs Reanimated 4.6.x and Worklets 0.12.x, so the main sample is outside the supported matrix and may fail to build or run animations.

Fix in Cursor Fix in Web

Triggered by project rule: PR Review Guidelines for Cursor Bot

Reviewed by Cursor Bugbot for commit af10bcc. Configure here.

Comment thread
cursor[bot] marked this conversation as resolved.
"react-native-build-config": "^0.3.2",
"react-native-gesture-handler": "^3.0.1",
"react-native-image-picker": "^8.2.1",
Comment on lines 53 to 59

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: Sample apps have a version mismatch between react-native (0.87.0) and pinned dev dependencies like @react-native/metro-config (0.86.2), which may cause Metro bundler failures.
Severity: HIGH

Suggested Fix

Update the versions of @react-native/metro-config, @react-native/babel-preset, and other related @react-native/* dev dependencies in the package.json files of the sample apps to match the react-native version (0.87.0).

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: samples/react-native/package.json#L53-L59

Potential issue: In multiple sample applications, the `react-native` dependency was
updated to `0.87.0`, but related development dependencies like
`@react-native/metro-config` and `@react-native/babel-preset` were left pinned to older
versions (e.g., `0.86.2`). While the package manager will successfully install these due
to an optional peer dependency, a version mismatch will exist at runtime. When the Metro
bundler is started, it will use the mismatched configuration, which is likely to cause
build or runtime failures if there are breaking API changes between versions.

Also affects:

  • performance-tests/TestAppSentry/package.json:11~17

Did we get this right? 👍 / 👎 to inform future reviews.

Expand Down
Loading
Loading