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

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

Changed files:
filename: test/rspack-dev-tests-manifest.json
patch: @@ -6810,66 +6810,87 @@
   "test/e2e/app-dir/ppr-full/ppr-full.test.ts": {
     "passed": [
       "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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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",
@@ -7999,9 +8020,7 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/segment-cache/prefetch-runtime/prefetch-runtime.test.ts": {
-    "passed": [
-      "<Link prefetch={true}> (runtime prefetch) disabled in development"
-    ],
+    "passed": ["runtime prefetching disabled in development"],
     "failed": [],
     "pending": [],
     "flakey": [],
@@ -8039,13 +8058,6 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/e2e/app-dir/segment-cache/segment-prefetch-config/segment-prefetch-config.test.ts": {
-    "passed": ["export const unstable_prefetch = ... disabled in development"],
-    "failed": [],
-    "pending": [],
-    "flakey": [],
-    "runtimeError": false
-  },
   "test/e2e/app-dir/segment-cache/staleness/segment-cache-stale-time.test.ts": {
     "passed": [
       "segment cache (staleness) disabled in development / deployment"
@@ -10819,7 +10831,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",
@@ -10832,7 +10846,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"
     ],