Leverage VERCEL_CLI_VERSION env for deploy tests (#39823)

This updates our next-e2e test deploy mode to auto pass along the VERCEL_CLI_VERSION env variable to allow testing builder changes easier. cc @nkzawa who encountered this.
vercel · Aug 22, 2022 · b431bd4 · b431bd4
1 parent c172d46
commit b431bd4
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/test/lib/next-modes/next-deploy.ts b/test/lib/next-modes/next-deploy.ts
@@ -74,15 +74,20 @@ export class NextDeployInstance extends NextInstance {
       additionalEnv.push(`${key}=${this.env[key]}`)
     }
 
+    if (process.env.VERCEL_CLI_VERSION) {
+      additionalEnv.push('--build-env')
+      additionalEnv.push(
+        `VERCEL_CLI_VERSION="${process.env.VERCEL_CLI_VERSION}"`
+      )
+    }
+
     const deployRes = await execa(
       'vercel',
       [
         'deploy',
         '--build-env',
         'NEXT_PRIVATE_TEST_MODE=1',
         '--build-env',
-        'FORCE_RUNTIME_TAG=canary',
-        '--build-env',
         'NEXT_TELEMETRY_DISABLED=1',
         ...additionalEnv,
         '--force',