mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
d470d18941
The weekly `test-e2e-project-reset-cron` workflow never defined `VERCEL_TURBOPACK_TEST_TEAM` or `VERCEL_TURBOPACK_TEST_TOKEN`, even though `run-e2e-test-project-reset.mjs` iterates over all three deploy test teams. Because `resetProject` defaulted `teamId` and `token` to the base team, and a destructuring default fires on an explicit `undefined`, the turbopack iteration silently resolved to `vtest314-next-e2e-tests`. The cron has therefore been deleting and recreating the base team's project twice per run while never resetting the turbopack team's project, and reporting success throughout. This dates back to #89458, which wired the env pair into `build_reusable.yml` and `test_e2e_deploy_release.yml` but missed the cron. This drops the defaults in favor of explicitly passing the team.