fix(mise): skip vercel install on Windows - #26420

Problem

test-go-pg (windows-2022) has been red on main since the Vercel CLI was added to mise.toml. Every PR that runs Windows CI (including #26389) fails at Restore Go cache -> setup-mise -> mise install, and the :x: CI Failure Slack notifications have been firing ~hourly because of it.

The Vercel CLI lives in the top-level [tools] block, so mise tries to install it on every runner. It is installed via the npm:vercel backend, which runs:

C:\Windows\system32\cmd.exe /d /s /c node install.js

as an npm post-install script. mise installs node into its own shim dir; node is not on cmd.exe's PATH at the moment npm spawns the post-install script, so it fails with:

npm error command C:\Windows\system32\cmd.exe /d /s /c node install.js
npm error 'node' is not recognized as an internal or external command,
npm error operable program or batch file.
mise ERROR Failed to install npm:vercel@54.14.0: npm.cmd exited with non-zero status: exit code 1

The whole setup-mise step aborts, so the rest of the job is skipped. Tracked in coder/internal#1596.

Fix

The Vercel CLI is only used to deploy / preview from dogfood workspaces (Linux). Restrict it to linux/macos via the documented os filter:

vercel = { version = "54.14.0", os = ["linux", "macos"] }

On Windows mise will now skip the install entirely. On Linux/macOS behavior is unchanged, the binary still resolves through the same npm:vercel backend.

Lockfile

os is an install-time filter and has no representation in mise.lock. mise lock against the pinned min_version = "2026.5.12" produces no diff, so the lockfile is intentionally left as-is.

Verification

• mise trust && mise ls on Linux still resolves vercel 54.14.0 from mise.toml.
• mise lock against pinned v2026.5.12 is a no-op on mise.lock.
• Windows runners will report (skipped) for vercel and continue past setup-mise.

Fixes coder/internal#1596.

Created on behalf of @kylecarbs.