chore: update setup-vp and stabilize pnpm snapshots

[fengmk2]

Update both CI references and SETUP_VP_VERSION to setup-vp release v1.21.1 to include its installation fixes. Generated workflows and vp migrate now select the same release.

pnpm can omit versions from dependency removal summaries when it reads a package manifest after unlinking the package. The snapshot runner now normalizes these summaries when dedupe, link, or prune omits the completion line. Package names, added versions, and manifest contents remain visible.

[github-actions]

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: ac4b1e5

[github-actions]

Registry bridge build (fe3cd95)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package	Version
vite-plus	0.0.0-commit.fe3cd953981e8e6bcbc57f468a5b957a35a69210
@voidzero-dev/vite-plus-core	0.0.0-commit.fe3cd953981e8e6bcbc57f468a5b957a35a69210

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/fe3cd953981e8e6bcbc57f468a5b957a35a69210/packages/cli/install.sh | VP_PR_VERSION=2772 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/fe3cd953981e8e6bcbc57f468a5b957a35a69210/packages/cli/install-legacy.sh bash

# Windows (PowerShell)
$env:VP_PR_VERSION="2772"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/fe3cd953981e8e6bcbc57f468a5b957a35a69210/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/fe3cd953981e8e6bcbc57f468a5b957a35a69210/packages/cli/install.ps1 | iex

Or download the standalone Windows installer built from this commit:

Architecture	Installer
x64	vp-setup-x86_64-pc-windows-msvc.exe
Arm64	vp-setup-aarch64-pc-windows-msvc.exe

GitHub requires you to sign in and downloads each installer as a ZIP artifact. Extract vp-setup.exe, then run it against this preview build:

.\vp-setup.exe --version "0.0.0-commit.fe3cd953981e8e6bcbc57f468a5b957a35a69210" --registry "https://registry-bridge.viteplus.dev/"

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager	Registry config
npm / pnpm / Bun	.npmrc: registry=https://registry-bridge.viteplus.dev/
Yarn (v2+)	.yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/"

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.fe3cd953981e8e6bcbc57f468a5b957a35a69210",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.fe3cd953981e8e6bcbc57f468a5b957a35a69210"
  }
}

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-2772	224MB

# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2772 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2772

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2772 vp --version

See docs/guide/docker.md for usage.

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://chore-update-setup-vp-v1-21-1-viteplus-dev.voidzero-docs.workers.dev (commit ac4b1e5)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://6c6dd3d5-viteplus-dev.voidzero-docs.workers.dev	ac4b1e5	2026-09-21T15:58:49.524Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://fe588e34-viteplus-dev.voidzero-docs.workers.dev	fe3cd95	2026-09-21T14:37:52.384Z	Visit the dashboard ↗