Repository navigation
Upgrade React from e84e1492-20261031 to 1620f7b9-20261111 - #101587
Merged
next-js-bot[bot] merged 6 commits intoNov 11, 2026
Merged
Conversation
Contributor
Tests PassedCommit: 0899061 |
unstubbable
approved these changes
Nov 11, 2026
next-js-bot
Bot
deleted the
update/react/19.3.0-canary-1620f7b9-20261111
branch
November 11, 2026 17:22
unstubbable
added a commit
that referenced
this pull request
Nov 12, 2026
PR #101587 includes React's Flight abort fix from react/react#38186. React now handles async iterables, readable streams, and blobs serialized after their abort signal has already fired. Next.js no longer needs to finish metadata accumulators to prevent `--debug-prerender` from hanging. This removes both workaround blocks and simplifies the abort checks. The new e2e suite adapts the reproduction from PR #101356 to cover sync IO during revalidation, including an application iterable that remains pending after abort, in local production and deploy mode. Closes #101356 Closes NAR-810
mischnic
pushed a commit
that referenced
this pull request
Nov 12, 2026
…01642) ### What? Fixes the `pnpm-lock.yaml` entry for `bench/large-app-router` so that `pnpm install --frozen-lockfile` works on canary again. ### Why? Since #101502 was merged, canary CI (`build`, `build-next`, `fetch test timings`, `test devlow package`, …) fails at install with: ``` ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY Broken lockfile: no entry for 'lucide-react@0.554.0(react@19.3.0-canary-e84e1492-20261031)' in pnpm-lock.yaml ``` #101587 upgraded React to `19.3.0-canary-1620f7b9-20261111` while #101502 was open. The lockfile changes merged without a textual conflict. However, the new `bench/large-app-router` importer still referenced the `lucide-react` snapshot that was resolved against the old React version, and #101587 had removed that snapshot. ### How? Point the importer at the existing `lucide-react@0.554.0(react@19.3.0-canary-1620f7b9-20261111)` snapshot. This is a one-line lockfile change. ### Verification - On current canary with this change, `pnpm install --frozen-lockfile` succeeds. - A plain `pnpm install` leaves the lockfile unchanged ("Already up to date"). - `pnpm-lock.yaml` has no remaining references to `e84e1492`. <!-- NEXT_JS_LLM --> <!-- fleet 844a9209-a191-4c7b-904b-5f0ad1e6b91d --> Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
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
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.
diff facebook/react@e84e1492...1620f7b9
React upstream changes