chore(deps): update dependency @edge-runtime/jest-environment to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@edge-runtime/jest-environment (source)	2.3.10 → 4.0.0

---

Release Notes

vercel/edge-runtime (@​edge-runtime/jest-environment)

v4.0.0

Compare Source

Major Changes

• drop node16 (#​1045)

Patch Changes

• Updated dependencies [b1e3795]:
  • @​edge-runtime/vm@​5.0.0

v3.0.4

Compare Source

Patch Changes

• Updated dependencies []:
  • @​edge-runtime/vm@​4.0.4

v3.0.3

Compare Source

Patch Changes

• Updated dependencies [44aaa5706fb45df468d72531e27930552e882701]:
  • @​edge-runtime/vm@​4.0.3

v3.0.2

Compare Source

Patch Changes

• Updated dependencies []:
  • @​edge-runtime/vm@​4.0.2

v3.0.1

Compare Source

Patch Changes

• Updated dependencies []:
  • @​edge-runtime/vm@​4.0.1

v3.0.0

Compare Source

Major Changes

• use MIT license (#​909)

Patch Changes

• Updated dependencies [892741faf806d5f5a201331fe31e8f26a4816ac6]:
  • @​edge-runtime/vm@​4.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 25afec4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vercel-storage-next-integration-test-suite	Ready	Preview	Mar 21, 2026 4:48am

[vercel]

The updated @edge-runtime/jest-environment@4.0.0 requires Node >=18, but this package specifies engines.node: ">=14.6", creating an incompatible dependency conflict.

View Details

📝 Patch Details

diff --git a/packages/blob/package.json b/packages/blob/package.json
index f66052e..265b5eb 100644
--- a/packages/blob/package.json
+++ b/packages/blob/package.json
@@ -81,6 +81,6 @@
     "tsup": "8.4.0"
   },
   "engines": {
-    "node": ">=16.14"
+    "node": ">=18"
   }
 }
diff --git a/packages/edge-config/package.json b/packages/edge-config/package.json
index 57ade40..af7c22f 100644
--- a/packages/edge-config/package.json
+++ b/packages/edge-config/package.json
@@ -69,6 +69,6 @@
     }
   },
   "engines": {
-    "node": ">=14.6"
+    "node": ">=18"
   }
 }
diff --git a/packages/kv/package.json b/packages/kv/package.json
index 4d127f2..7228df3 100644
--- a/packages/kv/package.json
+++ b/packages/kv/package.json
@@ -63,6 +63,6 @@
     "typescript": "5.7.3"
   },
   "engines": {
-    "node": ">=14.6"
+    "node": ">=18"
   }
 }

Analysis

The package has been updated to use @edge-runtime/jest-environment@4.0.0 (line 50), which requires Node.js version >=18 according to its engine specification in pnpm-lock.yaml. However, this package declares it supports Node >=14.6 in its engines field (line 66). This creates a dependency resolution conflict where:

1. Users with Node 14.6-17.x will be able to install the package (meets package engine requirement) but will fail when trying to install @edge-runtime/jest-environment@4.0.0 (doesn't meet dependency's engine requirement)
2. Package managers may reject the installation entirely due to the conflicting engine requirements
3. Tests using jest --env @edge-runtime/jest-environment (line 38) will fail on supported Node versions

This affects the test script which explicitly uses the @edge-runtime/jest-environment.

---

Recommendation

Either:

1. Recommended: Update the package's Node engine requirement to "node": ">=18" to match the dependency's requirement, or
2. Alternative: Downgrade @edge-runtime/jest-environment to a version that supports Node >=14.6 (likely staying on 2.x series)

If choosing option 1, verify that all features work correctly on Node 18+ and update any CI/deployment configurations accordingly.

[vercel]

The updated @edge-runtime/jest-environment@4.0.0 requires Node >=18, but this package specifies engines.node: ">=14.6", creating an incompatible dependency conflict.

View Details

Analysis

The package has been updated to use @edge-runtime/jest-environment@4.0.0 (line 48), which requires Node.js version >=18 according to its engine specification in pnpm-lock.yaml. However, this package declares it supports Node >=14.6 in its engines field (line 72). This creates a dependency resolution conflict where:

1. Users with Node 14.6-17.x will be able to install the package (meets package engine requirement) but will fail when trying to install @edge-runtime/jest-environment@4.0.0 (doesn't meet dependency's engine requirement)
2. Package managers may reject the installation entirely due to the conflicting engine requirements
3. Tests using jest --env @edge-runtime/jest-environment (line 32) will fail on supported Node versions

This affects the test:common and test:edge scripts which explicitly use the @edge-runtime/jest-environment.

---

Recommendation

Either:

1. Recommended: Update the package's Node engine requirement to "node": ">=18" to match the dependency's requirement, or
2. Alternative: Downgrade @edge-runtime/jest-environment to a version that supports Node >=14.6 (likely staying on 2.x series)

If choosing option 1, verify that all features work correctly on Node 18+ and update any CI/deployment configurations accordingly.