Repository: vercel/next.js
Pull request: Update Rspack production test manifest

This auto-generated PR updates the production integration test manifest used when testing Rspack.

Changed files:
filename: test/rspack-build-tests-manifest.json
patch: @@ -1845,6 +1845,8 @@
       "Cache Components Errors Build With --prerender-debug Sync IO - Random - Math.random() should error the build if sync IO is used in a Server Component while prerendering",
       "Cache Components Errors Build With --prerender-debug Sync IO - Web Crypto - getRandomValue() should error the build if sync IO is used in a Server Component while prerendering",
       "Cache Components Errors Build With --prerender-debug Sync IO - Web Crypto - randomUUID() should error the build if sync IO is used in a Server Component while prerendering",
+      "Cache Components Errors Build With --prerender-debug With `use cache: private` in `unstable_cache` should error the build",
+      "Cache Components Errors Build With --prerender-debug With `use cache: private` in `use cache` should error the build",
       "Cache Components Errors Build With --prerender-debug With `use cache: private` with `connection()` should not fail the build and show no runtime error (caught in userland)",
       "Cache Components Errors Build With --prerender-debug With `use cache: private` with `headers()` should not fail the build and show no runtime error (caught in userland)",
       "Cache Components Errors Build With --prerender-debug With `use cache: private` without Suspense should error the build",
@@ -1896,10 +1898,7 @@
       "Cache Components Errors Build Without --prerender-debug With `use cache: private` with `headers()` should not fail the build and show no runtime error (caught in userland)",
       "Cache Components Errors Build Without --prerender-debug With `use cache: private` without Suspense should error the build"
     ],
-    "failed": [
-      "Cache Components Errors Build With --prerender-debug With `use cache: private` in `unstable_cache` should error the build",
-      "Cache Components Errors Build With --prerender-debug With `use cache: private` in `use cache` should error the build"
-    ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -3383,10 +3382,10 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/metadata-invalid-image-file/metadata-invalid-image-file.test.ts": {
-    "passed": [],
-    "failed": [
+    "passed": [
       "metadata-invalid-image-file should error on invalid metadata image file"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -4794,81 +4793,102 @@
       "ppr-full HTML Fallback should allow client layouts without postponing fallback if params are not accessed",
       "ppr-full HTML Fallback should postpone in client layout when fallback params are accessed",
       "ppr-full HTML Response for / should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for / should allow soft navigations to and from the / page",
       "ppr-full HTML Response for / should cache the static part",
       "ppr-full HTML Response for / should have correct headers",
       "ppr-full HTML Response for / should resume with dynamic content",
       "ppr-full HTML Response for /dynamic/force-dynamic should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /dynamic/force-dynamic should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /dynamic/force-dynamic should have correct headers",
       "ppr-full HTML Response for /dynamic/force-dynamic should resume with dynamic content",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/a should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /dynamic/force-dynamic/nested/a should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/a should have correct headers",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/a should resume with dynamic content",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/b should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /dynamic/force-dynamic/nested/b should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/b should have correct headers",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/b should resume with dynamic content",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/c should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /dynamic/force-dynamic/nested/c should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/c should have correct headers",
       "ppr-full HTML Response for /dynamic/force-dynamic/nested/c should resume with dynamic content",
       "ppr-full HTML Response for /dynamic/force-static should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /dynamic/force-static should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /dynamic/force-static should have correct headers",
       "ppr-full HTML Response for /dynamic/force-static should not contain dynamic content",
       "ppr-full HTML Response for /loading/a should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /loading/a should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /loading/a should cache the static part",
       "ppr-full HTML Response for /loading/a should have correct headers",
       "ppr-full HTML Response for /loading/a should resume with dynamic content",
       "ppr-full HTML Response for /loading/b should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /loading/b should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /loading/b should cache the static part",
       "ppr-full HTML Response for /loading/b should have correct headers",
       "ppr-full HTML Response for /loading/b should resume with dynamic content",
       "ppr-full HTML Response for /loading/c should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /loading/c should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /loading/c should cache the static part",
       "ppr-full HTML Response for /loading/c should have correct headers",
       "ppr-full HTML Response for /loading/c should resume with dynamic content",
       "ppr-full HTML Response for /metadata should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /metadata should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /metadata should cache the static part",
       "ppr-full HTML Response for /metadata should have correct headers",
       "ppr-full HTML Response for /metadata should resume with dynamic content",
       "ppr-full HTML Response for /nested/a should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /nested/a should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /nested/a should cache the static part",
       "ppr-full HTML Response for /nested/a should have correct headers",
       "ppr-full HTML Response for /nested/a should resume with dynamic content",
       "ppr-full HTML Response for /nested/b should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /nested/b should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /nested/b should cache the static part",
       "ppr-full HTML Response for /nested/b should have correct headers",
       "ppr-full HTML Response for /nested/b should resume with dynamic content",
       "ppr-full HTML Response for /nested/c should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /nested/c should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /nested/c should cache the static part",
       "ppr-full HTML Response for /nested/c should have correct headers",
       "ppr-full HTML Response for /nested/c should resume with dynamic content",
       "ppr-full HTML Response for /no-suspense should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /no-suspense should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /no-suspense should cache the static part",
       "ppr-full HTML Response for /no-suspense should have correct headers",
       "ppr-full HTML Response for /no-suspense should resume with dynamic content",
       "ppr-full HTML Response for /no-suspense/nested/a should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /no-suspense/nested/a should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /no-suspense/nested/a should cache the static part",
       "ppr-full HTML Response for /no-suspense/nested/a should have correct headers",
       "ppr-full HTML Response for /no-suspense/nested/a should resume with dynamic content",
       "ppr-full HTML Response for /no-suspense/nested/b should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /no-suspense/nested/b should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /no-suspense/nested/b should cache the static part",
       "ppr-full HTML Response for /no-suspense/nested/b should have correct headers",
       "ppr-full HTML Response for /no-suspense/nested/b should resume with dynamic content",
       "ppr-full HTML Response for /no-suspense/nested/c should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /no-suspense/nested/c should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /no-suspense/nested/c should cache the static part",
       "ppr-full HTML Response for /no-suspense/nested/c should have correct headers",
       "ppr-full HTML Response for /no-suspense/nested/c should resume with dynamic content",
       "ppr-full HTML Response for /on-demand/a should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /on-demand/a should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /on-demand/a should cache the static part",
       "ppr-full HTML Response for /on-demand/a should have correct headers",
       "ppr-full HTML Response for /on-demand/a should resume with dynamic content",
       "ppr-full HTML Response for /on-demand/b should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /on-demand/b should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /on-demand/b should cache the static part",
       "ppr-full HTML Response for /on-demand/b should have correct headers",
       "ppr-full HTML Response for /on-demand/b should resume with dynamic content",
       "ppr-full HTML Response for /on-demand/c should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /on-demand/c should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /on-demand/c should cache the static part",
       "ppr-full HTML Response for /on-demand/c should have correct headers",
       "ppr-full HTML Response for /on-demand/c should resume with dynamic content",
       "ppr-full HTML Response for /static should allow navigations to and from a pages/ page",
+      "ppr-full HTML Response for /static should allow soft navigations to and from the / page",
       "ppr-full HTML Response for /static should have correct headers",
       "ppr-full HTML Response for /static should not contain dynamic content",
       "ppr-full Metadata should set the right metadata when generateMetadata uses dynamic APIs",
@@ -5658,11 +5678,11 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/scss/compilation-and-prefixing/compilation-and-prefixing.test.ts": {
-    "passed": [],
-    "failed": [
+    "passed": [
       "SCSS Support ({\"sass\": \"1.54.0\"}) Production only CSS Compilation and Prefixing should've compiled and prefixed",
       "SCSS Support ({\"sass-embedded\": \"1.75.0\"}) Production only CSS Compilation and Prefixing should've compiled and prefixed"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -5747,24 +5767,24 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/scss/invalid-global-with-app/invalid-global-with-app.test.ts": {
-    "passed": [],
-    "failed": ["Invalid Global CSS with Custom App should fail to build"],
+    "passed": ["Invalid Global CSS with Custom App should fail to build"],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
   },
   "test/e2e/app-dir/scss/invalid-global/invalid-global.test.ts": {
-    "passed": [],
-    "failed": ["Invalid Global CSS should fail to build"],
+    "passed": ["Invalid Global CSS should fail to build"],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
   },
   "test/e2e/app-dir/scss/invalid-module-document/invalid-module-document.test.ts": {
-    "passed": [],
-    "failed": [
+    "passed": [
       "Invalid SCSS in _document production only should fail to build"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -5977,10 +5997,10 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/scss/valid-and-invalid-global/valid-and-invalid-global.test.ts": {
-    "passed": [],
-    "failed": [
+    "passed": [
       "Valid and Invalid Global CSS with Custom App should fail to build"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -6196,7 +6216,10 @@
       "layout sharing in non-static prefetches navigations should omit layouts that were already prefetched with a full prefetch",
       "layout sharing in non-static prefetches navigations should omit layouts that were prefetched with a runtime prefetch and had no dynamic holes",
       "layout sharing in non-static prefetches runtime prefetches should omit layouts that were already prefetched with a full prefetch",
-      "layout sharing in non-static prefetches runtime prefetches should omit layouts that were already prefetched with a runtime prefetch"
+      "layout sharing in non-static prefetches runtime prefetches should omit layouts that were already prefetched with a runtime prefetch",
+      "layout sharing in non-static prefetches segment-level prefetch config does not unnecessarily use a runtime prefetch for sub-pages of runtime-prefetchable layouts",
+      "layout sharing in non-static prefetches segment-level prefetch config statically prefetches a fully-static page segment if all its runtime-prefetchable parents are available",
+      "layout sharing in non-static prefetches segment-level prefetch config uses a runtime prefetch for sub-pages of runtime-prefetchable layouts if requested"
     ],
     "failed": [],
     "pending": [],
@@ -6205,35 +6228,35 @@
   },
   "test/e2e/app-dir/segment-cache/prefetch-runtime/prefetch-runtime.test.ts": {
     "passed": [
-      "<Link prefetch={true}> (runtime prefetch) cache stale time handling includes private caches with cacheLife(\"seconds\")",
-      "<Link prefetch={true}> (runtime prefetch) cache stale time handling includes public caches with cacheLife(\"seconds\")",
-      "<Link prefetch={true}> (runtime prefetch) cache stale time handling includes short-lived public caches with a long enough staleTime",
-      "<Link prefetch={true}> (runtime prefetch) cache stale time handling omits private caches with a short enough staleTime",
-      "<Link prefetch={true}> (runtime prefetch) cache stale time handling omits short-lived public caches with a short enough staleTime",
-      "<Link prefetch={true}> (runtime prefetch) can completely prefetch a page that is fully static",
-      "<Link prefetch={true}> (runtime prefetch) errors aborts the prerender without logging an error when sync IO is used after awaiting a private cache",
-      "<Link prefetch={true}> (runtime prefetch) errors aborts the prerender without logging an error when sync IO is used after awaiting a quickly-expiring public cache",
-      "<Link prefetch={true}> (runtime prefetch) errors aborts the prerender without logging an error when sync IO is used after awaiting cookies()",
-      "<Link prefetch={true}> (runtime prefetch) errors aborts the prerender without logging an error when sync IO is used after awaiting searchParams",
-      "<Link prefetch={true}> (runtime prefetch) errors should trigger error boundaries for errors that occurred in runtime-prefetched content",
-      "<Link prefetch={true}> (runtime prefetch) in a page can completely prefetch a page that uses cookies and no uncached IO",
-      "<Link prefetch={true}> (runtime prefetch) in a page includes cookies, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a page includes dynamic params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a page includes root params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a page includes search params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a private cache can completely prefetch a page that uses cookies and no uncached IO",
-      "<Link prefetch={true}> (runtime prefetch) in a private cache includes cookies, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a private cache includes dynamic params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a private cache includes root params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) in a private cache includes search params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) passed to a public cache can completely prefetch a page that uses cookies and no uncached IO",
-      "<Link prefetch={true}> (runtime prefetch) passed to a public cache includes cookies, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) passed to a public cache includes dynamic params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) passed to a public cache includes root params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) passed to a public cache includes search params, but not dynamic content",
-      "<Link prefetch={true}> (runtime prefetch) should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a page",
-      "<Link prefetch={true}> (runtime prefetch) should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a private cache",
-      "<Link prefetch={true}> (runtime prefetch) should not cache runtime prefetch responses in the browser cache or server-side private caches should return new results on each request"
+      "runtime prefetching cache stale time handling includes private caches with cacheLife(\"seconds\")",
+      "runtime prefetching cache stale time handling includes public caches with cacheLife(\"seconds\")",
+      "runtime prefetching cache stale time handling includes short-lived public caches with a long enough staleTime",
+      "runtime prefetching cache stale time handling omits private caches with a short enough staleTime",
+      "runtime prefetching cache stale time handling omits short-lived public caches with a short enough staleTime",
+      "runtime prefetching can completely prefetch a page that is fully static",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting a private cache",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting a quickly-expiring public cache",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting cookies()",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting searchParams",
+      "runtime prefetching errors should trigger error boundaries for errors that occurred in runtime-prefetched content",
+      "runtime prefetching in a page can completely prefetch a page that uses cookies and no uncached IO",
+      "runtime prefetching in a page includes cookies, but not dynamic content",
+      "runtime prefetching in a page includes dynamic params, but not dynamic content",
+      "runtime prefetching in a page includes root params, but not dynamic content",
+      "runtime prefetching in a page includes search params, but not dynamic content",
+      "runtime prefetching in a private cache can completely prefetch a page that uses cookies and no uncached IO",
+      "runtime prefetching in a private cache includes cookies, but not dynamic content",
+      "runtime prefetching in a private cache includes dynamic params, but not dynamic content",
+      "runtime prefetching in a private cache includes root params, but not dynamic content",
+      "runtime prefetching in a private cache includes search params, but not dynamic content",
+      "runtime prefetching passed to a public cache can completely prefetch a page that uses cookies and no uncached IO",
+      "runtime prefetching passed to a public cache includes cookies, but not dynamic content",
+      "runtime prefetching passed to a public cache includes dynamic params, but not dynamic content",
+      "runtime prefetching passed to a public cache includes root params, but not dynamic content",
+      "runtime prefetching passed to a public cache includes search params, but not dynamic content",
+      "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a page",
+      "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a private cache",
+      "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side private caches should return new results on each request"
     ],
     "failed": [],
     "pending": [],
@@ -6288,18 +6311,6 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/e2e/app-dir/segment-cache/segment-prefetch-config/segment-prefetch-config.test.ts": {
-    "passed": [
-      "export const unstable_prefetch = ... defaults segments to static if no config is specified",
-      "export const unstable_prefetch = ... does not mark a \"static\" segment that is a child of a \"runtime\" segment as runtime-prefetchable",
-      "export const unstable_prefetch = ... does not mark for segments with prefetch: \"static\" as runtime-prefetchable",
-      "export const unstable_prefetch = ... marks segments with prefetch: \"runtime\" as runtime-prefetchable"
-    ],
-    "failed": [],
-    "pending": [],
-    "flakey": [],
-    "runtimeError": false
-  },
   "test/e2e/app-dir/segment-cache/staleness/segment-cache-stale-time.test.ts": {
     "passed": [
       "segment cache (staleness) caches omitted from the prerender should not affect when the prefetch is expired",
@@ -6465,6 +6476,15 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/e2e/app-dir/sub-shell-generation-middleware/sub-shell-generation-middleware.test.ts": {
+    "passed": [
+      "middleware-static-rewrite should eventually result in a cache hit"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/e2e/app-dir/sub-shell-generation/sub-shell-generation.test.ts": {
     "passed": [
       "sub-shell-generation should serve the correct shell /[lang]/[slug] should serve the correct shell for /es/1",
@@ -6744,6 +6764,7 @@
   },
   "test/e2e/app-dir/use-cache-route-handler-only/use-cache-route-handler-only.test.ts": {
     "passed": [
+      "use-cache-route-handler-only should be able to revalidate prerendered route handlers",
       "use-cache-route-handler-only should cache results in node route handlers"
     ],
     "failed": [],
@@ -9028,6 +9049,16 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/e2e/on-request-error/otel/otel.test.ts": {
+    "passed": [
+      "on-request-error - otel app router should catch app routes error in node runtime",
+      "on-request-error - otel app router should catch server component page error in node runtime"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/e2e/on-request-error/server-action-error/server-action-error.test.ts": {
     "passed": [
       "on-request-error - server-action-error should catch server action error in listener callback in edge runtime",
@@ -9103,7 +9134,9 @@
       "opentelemetry incoming context propagation pages should handle api routes in pages",
       "opentelemetry incoming context propagation pages should handle api routes in pages on edge",
       "opentelemetry incoming context propagation pages should handle getServerSideProps",
+      "opentelemetry incoming context propagation pages should handle getServerSideProps exceptions",
       "opentelemetry incoming context propagation pages should handle getServerSideProps on edge",
+      "opentelemetry incoming context propagation pages should handle getServerSideProps returning notFound",
       "opentelemetry incoming context propagation pages should handle getStaticProps when fallback: 'blocking'",
       "opentelemetry root context app router should handle RSC with fetch",
       "opentelemetry root context app router should handle RSC with fetch in RSC mode",
@@ -9116,7 +9149,9 @@
       "opentelemetry root context pages should handle api routes in pages",
       "opentelemetry root context pages should handle api routes in pages on edge",
       "opentelemetry root context pages should handle getServerSideProps",
+      "opentelemetry root context pages should handle getServerSideProps exceptions",
       "opentelemetry root context pages should handle getServerSideProps on edge",
+      "opentelemetry root context pages should handle getServerSideProps returning notFound",
       "opentelemetry root context pages should handle getStaticProps when fallback: 'blocking'",
       "opentelemetry with disabled fetch tracing root context app router with disabled fetch should handle RSC with disabled fetch"
     ],
@@ -10861,7 +10896,7 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/integration/config-mjs/test/index.test.js": {
+  "test/integration/config-mjs/test/index.test.ts": {
     "passed": [
       "Configuration correctly imports a package that defines `module` but no `main` in package.json",
       "Configuration renders public config on the server only",
@@ -11482,14 +11517,13 @@
   },
   "test/integration/css/test/valid-invalid-css.test.js": {
     "passed": [
-      "Valid Global CSS from npm production mode should've emitted a single CSS file"
-    ],
-    "failed": [
       "Invalid CSS in _document production mode should fail to build",
       "Invalid Global CSS production mode should fail to build",
       "Invalid Global CSS with Custom App production mode should fail to build",
+      "Valid Global CSS from npm production mode should've emitted a single CSS file",
       "Valid and Invalid Global CSS with Custom App production mode should fail to build"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -12437,7 +12471,7 @@
   },
   "test/integration/edge-runtime-dynamic-code/test/index.test.js": {
     "passed": [
-      "Page using eval in development mode does issue dynamic code evaluation warnings"
+      "Page using eval in development mode does not issue dynamic code evaluation warnings"
     ],
     "failed": [
       "Edge route usage of dynamic code evaluation production mode should have middleware warning during build",
@@ -14639,7 +14673,7 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/integration/hydrate-then-render/test/index.test.js": {
+  "test/integration/hydrate-then-render/test/index.test.ts": {
     "passed": [
       "hydrate/render ordering production mode correctly measures hydrate followed by render"
     ],
@@ -15178,6 +15212,7 @@
       "with contentDispositionType inline dev support with next.config.js should fail when q is missing",
       "with contentDispositionType inline dev support with next.config.js should fail when q is not a number",
       "with contentDispositionType inline dev support with next.config.js should fail when q is not an integer",
+      "with contentDispositionType inline dev support with next.config.js should fail when q is not in config",
       "with contentDispositionType inline dev support with next.config.js should fail when url fails to load an image",
       "with contentDispositionType inline dev support with next.config.js should fail when url has file protocol",
       "with contentDispositionType inline dev support with next.config.js should fail when url has ftp protocol",
@@ -15256,6 +15291,7 @@
       "with contentDispositionType inline Production Mode Server support with next.config.js should fail when q is missing",
       "with contentDispositionType inline Production Mode Server support with next.config.js should fail when q is not a number",
       "with contentDispositionType inline Production Mode Server support with next.config.js should fail when q is not an integer",
+      "with contentDispositionType inline Production Mode Server support with next.config.js should fail when q is not in config",
       "with contentDispositionType inline Production Mode Server support with next.config.js should fail when url fails to load an image",
       "with contentDispositionType inline Production Mode Server support with next.config.js should fail when url has file protocol",
       "with contentDispositionType inline Production Mode Server support with next.config.js should fail when url has ftp protocol",
@@ -15337,6 +15373,7 @@
       "with dangerouslyAllowSVG config dev support with next.config.js should fail when q is missing",
       "with dangerouslyAllowSVG config dev support with next.config.js should fail when q is not a number",
       "with dangerouslyAllowSVG config dev support with next.config.js should fail when q is not an integer",
+      "with dangerouslyAllowSVG config dev support with next.config.js should fail when q is not in config",
       "with dangerouslyAllowSVG config dev support with next.config.js should fail when url fails to load an image",
       "with dangerouslyAllowSVG config dev support with next.config.js should fail when url has file protocol",
       "with dangerouslyAllowSVG config dev support with next.config.js should fail when url has ftp protocol",
@@ -15412,6 +15449,7 @@
       "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when q is missing",
       "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when q is not a number",
       "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when q is not an integer",
+      "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when q is not in config",
       "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when url fails to load an image",
       "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when url has file protocol",
       "with dangerouslyAllowSVG config Production Mode Server support with next.config.js should fail when url has ftp protocol",
@@ -15553,6 +15591,7 @@
       "with isrFlushToDisk false config dev support with next.config.js should fail when q is missing",
       "with isrFlushToDisk false config dev support with next.config.js should fail when q is not a number",
       "with isrFlushToDisk false config dev support with next.config.js should fail when q is not an integer",
+      "with isrFlushToDisk false config dev support with next.config.js should fail when q is not in config",
       "with isrFlushToDisk false config dev support with next.config.js should fail when url fails to load an image",
       "with isrFlushToDisk false config dev support with next.config.js should fail when url has file protocol",
       "with isrFlushToDisk false config dev support with next.config.js should fail when url has ftp protocol",
@@ -15694,6 +15733,7 @@
       "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when q is missing",
       "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when q is not a number",
       "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when q is not an integer",
+      "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when q is not in config",
       "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when url fails to load an image",
       "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when url has file protocol",
       "with isrFlushToDisk false config Production Mode Server support with next.config.js should fail when url has ftp protocol",
@@ -15816,6 +15856,7 @@
       "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is missing",
       "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is not a number",
       "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is not an integer",
+      "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is not in config",
       "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url fails to load an image",
       "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url has file protocol",
       "with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url has ftp protocol",
@@ -15894,6 +15935,7 @@
       "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is missing",
       "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is not a number",
       "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is not an integer",
+      "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is not in config",
       "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url fails to load an image",
       "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url has file protocol",
       "with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url has ftp protocol",
@@ -16038,6 +16080,7 @@
       "with latest sharp dev support with next.config.js should fail when q is missing",
       "with latest sharp dev support with next.config.js should fail when q is not a number",
       "with latest sharp dev support with next.config.js should fail when q is not an integer",
+      "with latest sharp dev support with next.config.js should fail when q is not in config",
       "with latest sharp dev support with next.config.js should fail when url fails to load an image",
       "with latest sharp dev support with next.config.js should fail when url has file protocol",
       "with latest sharp dev support with next.config.js should fail when url has ftp protocol",
@@ -16179,6 +16222,7 @@
       "with latest sharp Production Mode Server support with next.config.js should fail when q is missing",
       "with latest sharp Production Mode Server support with next.config.js should fail when q is not a number",
       "with latest sharp Production Mode Server support with next.config.js should fail when q is not an integer",
+      "with latest sharp Production Mode Server support with next.config.js should fail when q is not in config",
       "with latest sharp Production Mode Server support with next.config.js should fail when url fails to load an image",
       "with latest sharp Production Mode Server support with next.config.js should fail when url has file protocol",
       "with latest sharp Production Mode Server support with next.config.js should fail when url has ftp protocol",
@@ -16257,7 +16301,7 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/integration/index-index/test/index.test.js": {
+  "test/integration/index-index/test/index.test.ts": {
     "passed": [
       "nested index.js production mode should 404 on /index/index/index",
       "nested index.js production mode should client render page /",
@@ -16347,11 +16391,11 @@
     "runtimeError": false
   },
   "test/integration/invalid-document-image-import/test/index.test.js": {
-    "passed": [],
-    "failed": [
+    "passed": [
       "Invalid static image import in _document production mode Should fail to build when disableStaticImages in next.config.js",
       "Invalid static image import in _document production mode Should fail to build when no next.config.js"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -17131,15 +17175,15 @@
   "test/integration/next-image-new/app-dir-qualities/test/index.test.ts": {
     "passed": [
       "Image localPatterns config production mode should build correct images-manifest.json",
-      "Image localPatterns config production mode should fail to load img when quality is 100",
+      "Image localPatterns config production mode should coerce quality 100 to closest matching of 88",
       "Image localPatterns config production mode should load img when quality 42",
       "Image localPatterns config production mode should load img when quality 69",
       "Image localPatterns config production mode should load img when quality 88",
       "Image localPatterns config production mode should load img when quality is undefined"
     ],
     "failed": [],
     "pending": [
-      "Image localPatterns config development mode should fail to load img when quality is 100",
+      "Image localPatterns config development mode should coerce quality 100 to closest matching of 88",
       "Image localPatterns config development mode should load img when quality 42",
       "Image localPatterns config development mode should load img when quality 69",
       "Image localPatterns config development mode should load img when quality 88",
@@ -18152,7 +18196,7 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/integration/react-current-version/test/index.test.js": {
+  "test/integration/react-current-version/test/index.test.ts": {
     "passed": [
       "Basics default setting dev hydrates correctly for normal page",
       "Basics default setting dev no warnings for image related link props",
@@ -18623,7 +18667,7 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/integration/script-loader/test/index.test.js": {
+  "test/integration/script-loader/test/index.test.ts": {
     "passed": [
       "Next.js Script - Primary Strategies - Production Mode production mode Does not duplicate inline scripts",
       "Next.js Script - Primary Strategies - Production Mode production mode Error message is shown if Partytown is not installed locally",
@@ -19765,6 +19809,16 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/production/app-dir/resume-data-cache/resume-data-cache.test.ts": {
+    "passed": [
+      "resume-data-cache should have consistent data between static and dynamic renders with fetch cache",
+      "resume-data-cache should have consistent data between static and dynamic renders with use cache"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/production/app-dir/revalidate/revalidate.test.ts": {
     "passed": [
       "app-dir revalidate should be able to revalidate the cache via pages/api"
@@ -20355,6 +20409,16 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/production/next-server-nft/next-server-nft.test.ts": {
+    "passed": [],
+    "failed": [],
+    "pending": [
+      "next-server-nft should not trace too many files in next-minimal-server.js.nft.json",
+      "next-server-nft should not trace too many files in next-server.js.nft.json"
+    ],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/production/optimize-server-react/optimize-server-react.test.ts": {
     "passed": [
       "optimize-server-react should optimize useEffect call on server side",
@@ -20507,10 +20571,11 @@
   },
   "test/production/pnpm-support/index.test.ts": {
     "passed": [
-      "pnpm support should build with dependencies installed via pnpm",
+      "pnpm support should build with dependencies installed via pnpm"
+    ],
+    "failed": [
       "pnpm support should execute client-side JS on each page in output: \"standalone\""
     ],
-    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -20731,6 +20796,7 @@
   "test/production/standalone-mode/required-server-files/required-server-files-ppr.test.ts": {
     "passed": [
       "required server files app router middleware rewrite should work with a dynamic path with Next-Resume",
+      "required server files app router should de-dupe client segment tree revalidate requests",
       "required server files app router should handle RSC requests",
       "required server files app router should handle prefetch RSC requests",
       "required server files app router should handle revalidating the fallback page",
@@ -20741,7 +20807,8 @@
       "required server files app router should properly handle prerender for bot request",
       "required server files app router should properly stream resume with Next-Resume",
       "required server files app router should send cache tags in minimal mode for ISR",
-      "required server files app router should still render when postponed is corrupted with Next-Resume"
+      "required server files app router should still render when postponed is corrupted with Next-Resume",
+      "required server files app router should use the postponed state for the RSC requests"
     ],
     "failed": [],
     "pending": [],