Skip to content
Draft
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": "18.3.1",
"react-native": "0.77.1",
"react-native": "0.86.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 @@ -111,7 +111,7 @@
"oxlint": "^1.56.0",
"oxlint-tsgolint": "^0.17.4",
"react": "19.1.0",
"react-native": "0.80.1",
"react-native": "0.86.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 @@ -9,7 +9,7 @@
},
"dependencies": {
"react": "19.2.3",
"react-native": "0.85.1"
"react-native": "0.86.0"

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

View check run for this annotation

@sentry/warden / warden: find-bugs

[VH6-F7K] `react-native` bumped to 0.86.0 while companion `@react-native/*` packages remain at 0.85.1 (additional location)

`react-native` is set to `0.86.0` but the lockstep-released companion packages `@react-native/babel-preset`, `@react-native/metro-config`, `@react-native/typescript-config`, `@react-native/jest-preset`, and `@react-native/new-app-screen` are all still pinned at `0.85.1`. The `@react-native/*` build/tooling packages are versioned in lockstep with `react-native`, so a cross-version mismatch can produce Metro/Babel/codegen build failures. The same inconsistency appears across the changed sample and test app manifests, and the PR title ("update React Native to v0.85.3") does not match the `0.86.0` actually written, suggesting an unintended/incomplete version bump.
},
"devDependencies": {
"@babel/core": "^7.25.2",
Comment thread
sentry-warden[bot] marked this conversation as resolved.
Comment thread
sentry-warden[bot] marked this conversation as resolved.
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.85.1",
"@sentry/react-native": "8.13.0",
"react": "19.2.3",
"react-native": "0.85.1"
"react-native": "0.86.0"

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

View check run for this annotation

@sentry/warden / warden: find-bugs

`react-native` bumped to 0.86.0 while companion `@react-native/*` packages remain at 0.85.1

`react-native` is set to `0.86.0` but the lockstep-released companion packages `@react-native/babel-preset`, `@react-native/metro-config`, `@react-native/typescript-config`, `@react-native/jest-preset`, and `@react-native/new-app-screen` are all still pinned at `0.85.1`. The `@react-native/*` build/tooling packages are versioned in lockstep with `react-native`, so a cross-version mismatch can produce Metro/Babel/codegen build failures. The same inconsistency appears across the changed sample and test app manifests, and the PR title ("update React Native to v0.85.3") does not match the `0.86.0` actually written, suggesting an unintended/incomplete version bump.

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 bumped to 0.86.0 while companion @react-native/* packages remain at 0.85.1

react-native is set to 0.86.0 but the lockstep-released companion packages @react-native/babel-preset, @react-native/metro-config, @react-native/typescript-config, @react-native/jest-preset, and @react-native/new-app-screen are all still pinned at 0.85.1. The @react-native/* build/tooling packages are versioned in lockstep with react-native, so a cross-version mismatch can produce Metro/Babel/codegen build failures. The same inconsistency appears across the changed sample and test app manifests, and the PR title ("update React Native to v0.85.3") does not match the 0.86.0 actually written, suggesting an unintended/incomplete version bump.

Evidence
  • samples/react-native/package.json:56 sets "react-native": "0.86.0", while its devDependencies pin @react-native/babel-preset, @react-native/jest-preset, @react-native/metro-config, and @react-native/typescript-config all to 0.85.1, and @react-native/new-app-screen (dependencies) to 0.85.1.
  • The identical mismatch is present in performance-tests/TestAppPlain/package.json (react-native 0.86.0 vs @react-native/* 0.85.1) — confirmed via grep.
  • packages/core/package.json:114 also sets react-native to 0.86.0 while @react-native/babel-preset (line 88) is 0.80.0, an even larger devDependency skew used for building/testing the SDK.
  • The PR body states the target is v0.85.3, but the written version is 0.86.0, indicating the bump was not applied consistently across the @react-native/* family.
Also found at 2 additional locations
  • performance-tests/TestAppPlain/package.json:12
  • samples/react-native/package.json:56

Identified by Warden find-bugs · VH6-F7K

},
"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": "~56.0.5",
"react": "19.2.3",
"react-dom": "19.2.3",
"react-native": "0.85.3",
"react-native": "0.86.0",
"react-native-gesture-handler": "~2.31.2",
"react-native-safe-area-context": "~5.8.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,7 +21,7 @@
"@sentry/react-native": "8.13.0",
"delay": "^6.0.0",
"react": "18.2.0",
Comment thread
sentry-warden[bot] marked this conversation as resolved.
"react-native": "0.73.9",
"react-native": "0.86.0",
"react-native-gesture-handler": "2.14.0",
"react-native-macos": "0.73.34",
Comment thread
sentry-warden[bot] marked this conversation as resolved.
"react-native-reanimated": "3.8.1",
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.85.1",
"react-native": "0.86.0",

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

View check run for this annotation

@sentry/warden / warden: find-bugs

[VH6-F7K] `react-native` bumped to 0.86.0 while companion `@react-native/*` packages remain at 0.85.1 (additional location)

`react-native` is set to `0.86.0` but the lockstep-released companion packages `@react-native/babel-preset`, `@react-native/metro-config`, `@react-native/typescript-config`, `@react-native/jest-preset`, and `@react-native/new-app-screen` are all still pinned at `0.85.1`. The `@react-native/*` build/tooling packages are versioned in lockstep with `react-native`, so a cross-version mismatch can produce Metro/Babel/codegen build failures. The same inconsistency appears across the changed sample and test app manifests, and the PR title ("update React Native to v0.85.3") does not match the `0.86.0` actually written, suggesting an unintended/incomplete version bump.
"react-native-build-config": "^0.3.2",
"react-native-gesture-handler": "^2.28.0",
"react-native-image-picker": "^8.2.1",
Expand Down
Loading
Loading