test: enable Relay multi-project deployment coverage (#99403)
## Summary Re-enable deployment coverage for both `relay-graphql-swc-multi-project` projects. Corepack selects the declared pnpm version, and each setup copies a Vercel configuration pointing to its own output directory (`project-a/.next` or `project-b/.next`). Earlier deploy CI for #99192 installed and built both projects, then failed because the harness's post-build script looked for `.next/BUILD_ID` at the fixture root. Remove both blanket `skipDeployment` exclusions together so both page-rendering tests can execute. The two existing compiler-validation checks remain skipped in deploy mode because they run a local executable against the fixture's installation. Dependency versions, build commands, and page assertions are unchanged. ## Verification - All four tests passed locally in production Turbopack mode, both normally and with `__NEXT_CACHE_COMPONENTS=true` and `__NEXT_EXPERIMENTAL_CACHED_NAVIGATIONS=true`. - Checked each generated fixture's copied `vercel.json` against its actual build output: both configured `BUILD_ID` paths are readable, while the root `.next/BUILD_ID` is absent. - Neither setup retains `skipDeployment`. Both normal and cache-components deployment manifests select the suite without excluding cases; actual deployment and page assertions await CI on the updated head. - The repository TypeScript check reports existing shared-`node_modules` build mismatches, with no errors in the changed test. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment