Upgrade React from c0cd4d5d-20260527 to 557e28fa-20260601

[vercel-release-bot]

diff facebook/react@c0cd4d5d...557e28fa

React upstream changes

• [Fizz] Abort tasks that suspend after aborting during render facebook/react#36585
• [Fizz] Finish abort in a scheduled task facebook/react#36580
• [Fizz] Fix aborts during resumed rendering facebook/react#36584
• [Fizz] Track abort state on Request facebook/react#36583
• [Fizz] model fb bundle's external work scheduling explicitly facebook/react#36576
• [Fizz] Continue reporting aborted task errors after a fatal abort facebook/react#36575
• [Fizz] Do not allow abort reentrancy facebook/react#36574
• [Flight] Avoid main-thread stalls from large debug strings facebook/react#36570
• [ci] Create artifact attestations for builds on backport branches facebook/react#36558
• [Flight] Fix stranded row content under Node stream backpressure facebook/react#36516
• [ci] Allow CI on backport branches facebook/react#36551

[github-actions]

Stats cancelled

Commit: 275dfcc
View workflow run

[github-actions]

Failing test suites

Commit: 275dfcc | About building and testing Next.js

pnpm test-dev test/e2e/app-dir/cache-components-errors/cache-components-errors.test.ts (job)

• Cache Components Errors > Dev > Error Attribution with Sync IO > Unguarded RSC with guarded Client sync IO > should show a collapsed redbox error (DD)

Expand output

● Cache Components Errors › Dev › Error Attribution with Sync IO › Unguarded RSC with guarded Client sync IO › should show a collapsed redbox error

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `Cache Components Errors Dev Error Attribution with Sync IO Unguarded RSC with guarded Client sync IO should show a collapsed redbox error 1`

- Snapshot  - 7
+ Received  + 7

  {
-   "code": "E1272",
-   "description": "Next.js encountered runtime data during prerendering.",
+   "code": "E1266",
+   "description": "Next.js encountered the unstable value new Date() in a Client Component.",
    "environmentLabel": "Server",
    "label": "Blocking Route",
-   "source": "app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (34:18) @ RequestData
- > 34 |   ;(await cookies()).get('foo')
-      |                  ^",
+   "source": "app/sync-attribution/unguarded-async-guarded-clientsync/client.tsx (5:16) @ SyncIO
+ > 5 |   const data = new Date().toISOString()
+     |                ^",
    "stack": [
-     "RequestData app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (34:18)",
-     "Page app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (27:9)",
+     "SyncIO app/sync-attribution/unguarded-async-guarded-clientsync/client.tsx (5:16)",
+     "Page app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (23:11)",
    ],
  }

  2324 |             const browser = await next.browser(pathname)
  2325 |
> 2326 |             await expect(browser).toDisplayCollapsedRedbox(`
       |                                   ^
  2327 |              {
  2328 |                "code": "E1272",
  2329 |                "description": "Next.js encountered runtime data during prerendering.",

  at Object.toDisplayCollapsedRedbox (e2e/app-dir/cache-components-errors/cache-components-errors.test.ts:2326:35)

pnpm test-start test/production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts (job)

• app-dir - server-action-period-hash-custom-key > should have a different manifest if the encryption key from process env is changed (DD)
• app-dir - server-action-period-hash-custom-key > should have the same manifest if the encryption key from process env is same (DD)

Expand output

● app-dir - server-action-period-hash-custom-key › should have a different manifest if the encryption key from process env is changed

can not run export while server is running, use next.stop() first

  253 |   ) {
  254 |     if (this.childProcess) {
> 255 |       throw new Error(
      |             ^
  256 |         `can not run export while server is running, use next.stop() first`
  257 |       )
  258 |     }

  at NextStartInstance.build (lib/next-modes/next-start.ts:255:13)
  at Object.build (production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts:18:16)

● app-dir - server-action-period-hash-custom-key › should have the same manifest if the encryption key from process env is same

can not run export while server is running, use next.stop() first

  253 |   ) {
  254 |     if (this.childProcess) {
> 255 |       throw new Error(
      |             ^
  256 |         `can not run export while server is running, use next.stop() first`
  257 |       )
  258 |     }

  at NextStartInstance.build (lib/next-modes/next-start.ts:255:13)
  at Object.build (production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts:32:16)

pnpm test-start test/production/middleware-prefetch/middleware-prefetch.test.ts (job)

• Middleware Production Prefetch > does not prefetch provided path if it will be rewritten (DD)

Expand output

● Middleware Production Prefetch › does not prefetch provided path if it will be rewritten

expect(received).toBe(expected) // Object.is equality

Expected: false
Received: true

  43 |             src.includes('/ssg-page-2' + (process.env.NEXT_RSPACK ? '-' : ''))
  44 |         )
> 45 |       ).toBe(false)
     |         ^
  46 |     })
  47 |   })
  48 | })

  at toBe (production/middleware-prefetch/middleware-prefetch.test.ts:45:9)
  at retry (lib/next-test-utils.ts:867:14)
  at Object.<anonymous> (production/middleware-prefetch/middleware-prefetch.test.ts:34:5)

pnpm test-dev-turbo test/e2e/app-dir/cache-components-errors/cache-components-errors.test.ts (turbopack) (job)

• Cache Components Errors > Dev > Error Attribution with Sync IO > Unguarded RSC with guarded Client sync IO > should show a collapsed redbox error (DD)

Expand output

● Cache Components Errors › Dev › Error Attribution with Sync IO › Unguarded RSC with guarded Client sync IO › should show a collapsed redbox error

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `Cache Components Errors Dev Error Attribution with Sync IO Unguarded RSC with guarded Client sync IO should show a collapsed redbox error 1`

- Snapshot  - 7
+ Received  + 7

  {
-   "code": "E1272",
-   "description": "Next.js encountered runtime data during prerendering.",
+   "code": "E1266",
+   "description": "Next.js encountered the unstable value new Date() in a Client Component.",
    "environmentLabel": "Server",
    "label": "Blocking Route",
-   "source": "app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (34:18) @ RequestData
- > 34 |   ;(await cookies()).get('foo')
-      |                  ^",
+   "source": "app/sync-attribution/unguarded-async-guarded-clientsync/client.tsx (5:16) @ SyncIO
+ > 5 |   const data = new Date().toISOString()
+     |                ^",
    "stack": [
-     "RequestData app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (34:18)",
-     "Page app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (27:9)",
+     "SyncIO app/sync-attribution/unguarded-async-guarded-clientsync/client.tsx (5:16)",
+     "Page app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx (23:11)",
    ],
  }

  2324 |             const browser = await next.browser(pathname)
  2325 |
> 2326 |             await expect(browser).toDisplayCollapsedRedbox(`
       |                                   ^
  2327 |              {
  2328 |                "code": "E1272",
  2329 |                "description": "Next.js encountered runtime data during prerendering.",

  at Object.toDisplayCollapsedRedbox (e2e/app-dir/cache-components-errors/cache-components-errors.test.ts:2326:35)

pnpm test-start-turbo test/e2e/app-dir/cache-components-errors/cache-components-errors.test.ts (turbopack) (job)

• Cache Components Errors > Build With --prerender-debug > Error Attribution with Sync IO > Unguarded RSC with guarded Client sync IO > should error the build with a reason related dynamic data (DD)
• Cache Components Errors > Build Without --prerender-debug > Error Attribution with Sync IO > Unguarded RSC with guarded Client sync IO > should error the build with a reason related dynamic data (DD)

Expand output

● Cache Components Errors › Build With --prerender-debug › Error Attribution with Sync IO › Unguarded RSC with guarded Client sync IO › should error the build with a reason related dynamic data

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `Cache Components Errors Build With --prerender-debug Error Attribution with Sync IO Unguarded RSC with guarded Client sync IO should error the build with a reason related dynamic data 1`

- Snapshot  - 20
+ Received  + 19

- "Error: Route "/sync-attribution/unguarded-async-guarded-clientsync": Next.js encountered uncached or runtime data during prerendering.
-
- `fetch(...)`, `cookies()`, `headers()`, `params`, `searchParams`, or `connection()` accessed outside of `<Suspense>` prevents the route from being prerendered, blocking the page load and leading to a slower user experience.
-
- Ways to fix this:
-   - Cache the data access with `"use cache"`
-   - Provide a placeholder with `<Suspense fallback={...}>` around the data access
+ "Error: Route "/sync-attribution/unguarded-async-guarded-clientsync": Next.js encountered the unstable value `new Date()` in a Client Component.
+
+ This value would be evaluated during the prerender, instead of recomputed on each visit.
+
+ Ways to fix this:
+   - Wrap the Client Component in `<Suspense fallback={...}>`
-   - If the runtime data is `params` and they're known, prerender them with `generateStaticParams`
-   - Set `export const instant = false` to allow a blocking route
-
- Learn more: https://nextjs.org/docs/messages/blocking-route
-     at RequestData (app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx:34:18)
+   - Move the read into a `useEffect` or event handler
+   - If the value is for telemetry, use a timing API such as `performance.now()`
+
+ Learn more: https://nextjs.org/docs/messages/next-prerender-current-time-client
+     at SyncIO (app/sync-attribution/unguarded-async-guarded-clientsync/client.tsx:5:16)
-     at Page (app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx:27:9)
+     at Page (app/sync-attribution/unguarded-async-guarded-clientsync/page.tsx:23:11)
-   32 |
-   33 | async function RequestData() {
+   3 | export function SyncIO() {
+   4 |   // This is a sync IO access that should not cause an error
- > 34 |   ;(await cookies()).get('foo')
+ > 5 |   const data = new Date().toISOString()
-      |                  ^
+     |                ^
+   6 |
-   35 |   return (
+   7 |   return (
-   36 |     <div>
-   37 |       <h2>Request Data Access</h2>
+   8 |     <main>
  To debug the issue, start the app in development mode by running `next dev`, then open "/sync-attribution/unguarded-async-guarded-clientsync" in your browser to investigate the error.
  Error occurred prerendering page "/sync-attribution/unguarded-async-guarded-clientsync". Read more: https://nextjs.org/docs/messages/prerender-error

  > Export encountered errors on 1 path:
  	/sync-attribution/unguarded-async-guarded-clientsync/page: /sync-attribution/unguarded-async-guarded-clientsync"

  2355 |             if (isTurbopack) {
  2356 |               if (isDebugPrerender) {
> 2357 |                 expect(output).toMatchInlineSnapshot(`
       |                                ^
  2358 |                  "Error: Route "/sync-attribution/unguarded-async-guarded-clientsync": Next.js encountered uncached or runtime data during prerendering.
  2359 |
  2360 |                  \`fetch(...)\`, \`cookies()\`, \`headers()\`, \`params\`, \`searchParams\`, or \`connection()\` accessed outside of \`<Suspense>\` prevents the route from being prerendered, blocking the page load and leading to a slower user experience.

  at Object.toMatchInlineSnapshot (e2e/app-dir/cache-components-errors/cache-components-errors.test.ts:2357:32)

● Cache Components Errors › Build Without --prerender-debug › Error Attribution with Sync IO › Unguarded RSC with guarded Client sync IO › should error the build with a reason related dynamic data

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `Cache Components Errors Build Without --prerender-debug Error Attribution with Sync IO Unguarded RSC with guarded Client sync IO should error the build with a reason related dynamic data 1`

- Snapshot  - 16
+ Received  + 18

- "Error: Route "/sync-attribution/unguarded-async-guarded-clientsync": Next.js encountered uncached or runtime data during prerendering.
-
- `fetch(...)`, `cookies()`, `headers()`, `params`, `searchParams`, or `connection()` accessed outside of `<Suspense>` prevents the route from being prerendered, blocking the page load and leading to a slower user experience.
-
- Ways to fix this:
-   - Cache the data access with `"use cache"`
-   - Provide a placeholder with `<Suspense fallback={...}>` around the data access
+ "Error: Route "/sync-attribution/unguarded-async-guarded-clientsync": Next.js encountered the unstable value `new Date()` in a Client Component.
+
+ This value would be evaluated during the prerender, instead of recomputed on each visit.
+
+ Ways to fix this:
+   - Wrap the Client Component in `<Suspense fallback={...}>`
-   - If the runtime data is `params` and they're known, prerender them with `generateStaticParams`
-   - Set `export const instant = false` to allow a blocking route
-
- Learn more: https://nextjs.org/docs/messages/blocking-route
-     at a (<anonymous>)
-     at main (<anonymous>)
-     at main (<anonymous>)
-     at body (<anonymous>)
-     at html (<anonymous>)
+   - Move the read into a `useEffect` or event handler
+   - If the value is for telemetry, use a timing API such as `performance.now()`
+
+ Learn more: https://nextjs.org/docs/messages/next-prerender-current-time-client
+     at <unknown> (app/sync-attribution/unguarded-async-guarded-clientsync/client.tsx:5:16)
+   3 | export function SyncIO() {
+   4 |   // This is a sync IO access that should not cause an error
+ > 5 |   const data = new Date().toISOString()
+     |                ^
+   6 |
+   7 |   return (
+   8 |     <main>
  To get a more detailed stack trace and pinpoint the issue, try one of the following:
    - Start the app in development mode by running `next dev`, then open "/sync-attribution/unguarded-async-guarded-clientsync" in your browser to investigate the error.
    - Rerun the production build with `next build --debug-prerender` to generate better stack traces.
  Error occurred prerendering page "/sync-attribution/unguarded-async-guarded-clientsync". Read more: https://nextjs.org/docs/messages/prerender-error
  Export encountered an error on /sync-attribution/unguarded-async-guarded-clientsync/page: /sync-attribution/unguarded-async-guarded-clientsync, exiting the build."

  2383 |                 `)
  2384 |               } else {
> 2385 |                 expect(output).toMatchInlineSnapshot(`
       |                                ^
  2386 |                  "Error: Route "/sync-attribution/unguarded-async-guarded-clientsync": Next.js encountered uncached or runtime data during prerendering.
  2387 |
  2388 |                  \`fetch(...)\`, \`cookies()\`, \`headers()\`, \`params\`, \`searchParams\`, or \`connection()\` accessed outside of \`<Suspense>\` prevents the route from being prerendered, blocking the page load and leading to a slower user experience.

  at Object.toMatchInlineSnapshot (e2e/app-dir/cache-components-errors/cache-components-errors.test.ts:2385:32)

Other failing CI jobs

• test cache components prod (5/7) / build