chore(deps): update react monorepo to v19.2.8 - autoclosed - #305
Closed
renovate[bot] wants to merge 1 commit into
Closed
chore(deps): update react monorepo to v19.2.8 - autoclosed#305renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/react-monorepo
branch
3 times, most recently
from
July 28, 2026 17:47
f3198b9 to
f382cf7
Compare
GSTJ
added a commit
that referenced
this pull request
Jul 28, 2026
react and react-dom were open to bumps the SDK does not sanction. The workspace is hoisted, so #305's react 19.2.8 for apps/docs alone won the root node_modules and ran under jest beside the SDK's react-test-renderer 19.2.0, failing three of four suites on the peer assert. react-native-reanimated, react-native-worklets and react-native-screens were only held on the example app side. #306 took reanimated 4.5.3 in packages/modal, which installed a second copy beside the example app's 4.2.3 and asserted on its worklets 0.10.x - 0.11.x peer against the SDK's 0.7.4. Moving worklets up to match fails expo-doctor instead.
renovate
Bot
force-pushed
the
renovate/react-monorepo
branch
from
July 28, 2026 22:15
f382cf7 to
2c585f8
Compare
GSTJ
added a commit
that referenced
this pull request
Jul 28, 2026
…ine (#311) Two Renovate PRs are red on `react-native-magic-modal#test` for the same reason: each moves a version the Expo SDK picks. This adds the rules that stop them being re-proposed. #305 and #306 get closed against it. ## react and react-dom `renovate.json` already holds react-native, and the shared preset already disables react-test-renderer on the grounds that react's version is the SDK's to pick. The preset's Expo rule never lists react or react-dom though, so they stayed open. The workspace is hoisted, so whichever react wins the root `node_modules` is the one packages/modal tests against, whatever any single package.json says. #305 only edits `apps/docs/package.json`: ``` root node_modules/react 19.2.8 <- docs won the root root node_modules/react-test-renderer 19.2.0 <- SDK's, unchanged examples/kitchen-sink/.../react 19.2.0 <- nested, doctor stays quiet ``` @testing-library/react-native asserts the two match, so three of four suites died before running: ``` Incorrect version of "react-test-renderer" detected. Expected "19.2.8", but found "19.2.0". ``` react-test-renderer can't follow it up, since the preset disables it. Holding react costs nothing here. apps/docs is a static export (`next build`, then `serve out`), and 19.2.1 through 19.2.8 are all Server Components and Server Actions changes. ## reanimated, worklets and screens The example-app file rule only reaches `examples/kitchen-sink/package.json`, so Renovate kept proposing these on the packages/modal side alone. #306 took reanimated 4.5.3 there, which installed a second copy beside the example app's 4.2.3 and then asserted on its own peer: ``` reanimated 4.5.3 peers: react-native-worklets 0.10.x - 0.11.x expo 55.0.28 ships: react-native-worklets 0.7.4 [Reanimated] Your installed version of Worklets (0.7.4) is not compatible with installed version of Reanimated (4.5.3). ``` Moving worklets up to 0.10.3 to satisfy it turns the suites green, 36/36. expo-doctor then fails: ``` X Check that packages match versions required by installed Expo SDK package expected found react-native-worklets 0.7.4 0.10.3 ``` Worklets is a native module and isn't on the example app's `expo.install.exclude` list, only reanimated and gesture-handler are. So 4.5.3 cannot land while the repo is on SDK 55. react-native-screens sits in the same position and is held for the same reason. ## Verification Clean `node_modules`, rebased on main: - oxlint straight from `node_modules/.bin` in all three workspaces, exit 0. Planted an unused var first to confirm it exits 1. - format, typecheck, build, doctor 19/19, changelog:check all exit 0 - 36 tests across 4 suites - `renovate-config-validator` accepts the file Config only, so no E2E and no release. Proof, including both reproductions and the worklets experiment: [magic-modal/305-306](https://github.com/GSTJ/pr-assets-dump/tree/magic-modal-305-306-sdk-pins/magic-modal/305-306) | | | |---|---| | [#305 reproduced](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/305.png) | [#306 reproduced](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/306.png) | | [worklets aligned, doctor fails](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/306-worklets.png) | [chain green here](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/green.png) |
renovate
Bot
changed the title
auto-merge was automatically disabled
July 28, 2026 23:07
Pull request was closed
Owner
|
Closing. #311 holds react and react-dom to whatever the Expo SDK picks. The workspace is hoisted, so 19.2.8 landing for |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
19.2.0→19.2.819.2.0→19.2.8Release Notes
react/react (react)
v19.2.8Compare Source
v19.2.7Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable #36566)v19.2.6Compare Source
React Server Components
v19.2.5Compare Source
React Server Components
v19.2.4Compare Source
React Server Components
v19.2.3Compare Source
React Server Components
v19.2.2Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.2.1Compare Source
React Server Components
react/react (react-dom)
v19.2.8Compare Source
v19.2.7Compare Source
React Server Components
FormDataentries in Server Actions which regressed in 19.2.6 (@unstubbable #36566)v19.2.6Compare Source
React Server Components
v19.2.5Compare Source
React Server Components
v19.2.4Compare Source
React Server Components
v19.2.3Compare Source
React Server Components
v19.2.2Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.2.1Compare Source
React Server Components
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.