From 5e29ceca2131088fac6d0df428a7e7c9df5e8cf2 Mon Sep 17 00:00:00 2001
From: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
Date: Thu, 9 Apr 2026 14:25:27 +0200
Subject: [PATCH] [test] Ensure incomplete minimum release age isn't propagate
 to fixture installs

---
 test/lib/create-next-install.js | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/test/lib/create-next-install.js b/test/lib/create-next-install.js
index 490878fd7932..633b7b5d977a 100644
--- a/test/lib/create-next-install.js
+++ b/test/lib/create-next-install.js
@@ -27,7 +27,17 @@ async function installDependencies(cwd, tmpDir) {
   await execa('pnpm', args, {
     cwd,
     stdio: ['ignore', 'inherit', 'inherit'],
-    env: process.env,
+    env: {
+      ...process.env,
+      // pnpm reads this despite claims it ignores `npm_config_*` env variables.
+      // This isn't set in CI but some local environments set this from the
+      // pnpm-workspace.yaml for unknown reasons.
+      // minimumReleaseAgeExclude is not propagated with environment variables
+      // so some installs would just fail.
+      // TODO: ideally every test fixture would run with minimumReleaseAgeExclude but
+      // that requires some work in monorepo test suites.
+      npm_config_minimum_release_age: undefined,
+    },
   })
 }