fix(deps): update dependency @vercel/style-guide to v6

[renovate]

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

---

This PR contains the following updates:

Package	Change	Age	Confidence
@vercel/style-guide	5.2.0 -> 6.0.0

---

Release Notes

vercel/style-guide (@​vercel/style-guide)

v6.0.0

Compare Source

Features

• eslint: update @typescript-eslint/* dependencies (#​102) (dd7004d)
• deps: update dependencies and require Node >=18.18 (#​97) (4efc908)
• eslint: accept @next/eslint-plugin-next@canary as peer dep (#​89) (55508ac)
• eslint: add vitest config (#​96) (325b65a)
• eslint: remove jest/require-top-level-describe (#​93) (e09a147)
• eslint: remove no-await-in-loop (#​95) (2b0ce9d)
• eslint: remove react/jsx-sort-props (#​87) (0088457)
• eslint: remove deprecated no-return-await (#​94) (1ea97f4)
• eslint: update eslint-plugin-playwright (#​98) (4b89216)

BREAKING CHANGES

• deps: Node 18.18 is now the minimum required version.
• eslint: Contains changes to @typescript-eslint/* enabled rules and configuration.
• eslint: Enabled rules for eslint-plugin-playwright have changed.
• eslint: no-await-in-loop has been removed.
• eslint: no-return-await is deprecated and has been removed.
• eslint: jest/require-top-level-describe has been removed.

---

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 these updates again.

---

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

---

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

[vercel]

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

Project	Deployment	Preview	Updated (UTC)
vercel-storage-next-integration-test-suite	Ready	Preview	Sep 29, 2025 2:54pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 88a438f

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 project's Node version requirement (>=18) is less strict than what @vercel/style-guide 6.0.0 requires (>=18.18), potentially causing runtime issues for users with Node 18.0-18.17.

View Details

📝 Patch Details

diff --git a/package.json b/package.json
index d1bcd69..4831161 100644
--- a/package.json
+++ b/package.json
@@ -44,6 +44,6 @@
   },
   "packageManager": "[email protected]",
   "engines": {
-    "node": ">=18"
+    "node": ">=18.18"
   }
 }

Analysis

The update to @vercel/style-guide 6.0.0 introduces a more restrictive Node.js version requirement (>=18.18) than what the project currently specifies in its engines field (>=18). This version mismatch creates a compatibility gap where the project claims to support Node.js 18.0.0 and above, but the @vercel/style-guide dependency actually requires Node.js 18.18.0 or later.

This discrepancy can lead to runtime failures if users attempt to run the project with Node versions 18.0.0 through 18.17.x, which satisfy the project's stated requirements but fail the dependency's requirements. The fix is to update the project's Node version requirement to match or exceed the most restrictive dependency requirement: "node": ">=18.18".