Update Rspack production test manifest

[vercel-release-bot]

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

[nextjs-bot]

Failing test suites

Commit: a40b8e3 | About building and testing Next.js

pnpm test-dev-turbo test/development/basic/allowed-dev-origins.test.ts (turbopack) (job)

• allowed-dev-origins, basePath: "/docs" > configured allowed origins > should block no-cors requests without a referer even when origins are configured (DD)

Expand output

● allowed-dev-origins, basePath: "/docs" › configured allowed origins › should block no-cors requests without a referer even when origins are configured

expect(received).toContain(expected) // indexOf

Expected substring: "/docs/_next/static/chunks/pages/_app.js"
Received string:    "▲ Next.js 16.2.1-canary.7 (Turbopack)
- Local:         http://localhost:42945
- Network:       http://157.180.14.178:42945
✓ Ready in 639ms
Creating turbopack project {
  dir: '/tmp/next-install-513e37983412840acbb7a277976f229e31a99d6b681c9250228440978e51c509',
  testMode: true
}
- Experiments (use with caution):
  ✓ strictRouteTypes (enabled by `__NEXT_EXPERIMENTAL_STRICT_ROUTE_TYPES`)·
 GET /404 404 in 2.1s (next.js: 2.0s, application-code: 63ms)
"

  89 |   }
  90 | ) {
> 91 |   expect(output).toContain(options.resourcePath)
     |                  ^
  92 |   expect(output).toContain(
  93 |     'Cross-origin access to Next.js dev resources is blocked by default for safety.'
  94 |   )

  at toContain (development/basic/allowed-dev-origins.test.ts:91:18)
  at Object.expectBlockedDevResourceMessage (development/basic/allowed-dev-origins.test.ts:414:9)

pnpm test-dev-turbo test/development/app-dir/instant-navs-devtools/instant-navs-devtools.test.ts (turbopack) (job)

• instant-nav-panel > should show client nav state after clicking Start and navigating (DD)

Expand output

● instant-nav-panel › should show client nav state after clicking Start and navigating

page.waitForSelector: Timeout 10ms exceeded.
Call log:
  - waiting for locator('[data-instant-nav-client]') to be visible

  545 |
  546 |     return this.startChain(async () => {
> 547 |       const el = await page.waitForSelector(selector, {
      |                             ^
  548 |         timeout,
  549 |         state,
  550 |       })

  at waitForSelector (lib/browsers/playwright.ts:547:29)
  at Playwright._chain (lib/browsers/playwright.ts:677:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:658:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:546:17)
  at Playwright.waitForElementByCss (lib/browsers/playwright.ts:439:17)
  at elementByCssInstant (development/app-dir/instant-navs-devtools/instant-navs-devtools.test.ts:41:19)
  at Object.clickStartClientNav (development/app-dir/instant-navs-devtools/instant-navs-devtools.test.ts:107:11)
  at Proxy._chain (lib/browsers/playwright.ts:677:23)
  at Proxy._chain (lib/browsers/playwright.ts:653:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:497:17)
  at click (development/app-dir/instant-navs-devtools/instant-navs-devtools.test.ts:41:68)
  at Object.clickStartClientNav (development/app-dir/instant-navs-devtools/instant-navs-devtools.test.ts:107:11)

pnpm test-start test/e2e/app-dir/nx-handling/nx-handling.test.ts (job)

• app-dir - server-action-period-hash > should have same manifest between continuous two builds (DD)
• app-dir - server-action-period-hash > should have different manifest between two builds with period hash (DD)

Expand output

● app-dir - server-action-period-hash › should have same manifest between continuous two builds

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

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

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

● app-dir - server-action-period-hash › should have different manifest between two builds with period hash

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

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

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

pnpm test-start test/production/app-dir/metadata-static-route-cache/metadata-static-route-cache.test.ts (job)

• segment cache (staleness) > reuses dynamic data up to the staleTimes.dynamic threshold (DD)

Expand output

● segment cache (staleness) › reuses dynamic data up to the staleTimes.dynamic threshold

thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

  50 |       }
  51 |
> 52 |       const result = Reflect.apply(target, thisArg, args)
     |                              ^
  53 |       return typeof result === 'function' ? wrapJestTestFn(result) : result
  54 |     },
  55 |     get(target, prop, receiver) {

  at Object.apply (lib/e2e-utils/index.ts:52:30)
  at it (e2e/app-dir/segment-cache/staleness/segment-cache-stale-time.test.ts:150:3)
  at Object.describe (e2e/app-dir/segment-cache/staleness/segment-cache-stale-time.test.ts:5:1)