mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Tobias Koppers
05c20cd1fb
### What? Removes the legacy Vercel builder rows from the immutable-assets deployment ID determinism test. Direct `.next` output and Vercel adapter output remain covered, including both the standard and Cache Components fixtures. ### Why? Current `vercel@latest` rejects `_next/static/immutable` output when the Next.js adapter is disabled. Disabling immutable assets is not a valid replacement for these cases: it adds the deployment ID to asset URLs, which intentionally changes content-hashed CSS filenames between builds. This intentionally removes the two legacy-builder deploy-mode cases rather than skipping or weakening their determinism assertions. The current legacy builder no longer supports the immutable-output contract the test verifies. ### How? The Build Output API matrix now exercises only adapter mode, and `NEXT_ENABLE_ADAPTER=1` is applied unconditionally. The shared two-build comparison and all assertions for the retained direct and adapter cases are unchanged. Builder-only mode branching and timeout handling are removed. ### Verification - `pnpm prettier --with-node-modules --ignore-path .prettierignore --check test/production/deterministic-build/deployment-id.test.ts` - `pnpm eslint --config eslint.config.mjs test/production/deterministic-build/deployment-id.test.ts` - `pnpm test-start-turbo test/production/deterministic-build/deployment-id.test.ts` (3 tests passed) <!-- NEXT_JS_LLM --> <!-- fleet 00754f3b-4965-4d6d-bc4c-4dbab7b188e4 --> 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>