docs(ci): clarify setup-vp version pinning

[fengmk2]

Updates the documentation to use exact setup-vp release tags or commit SHAs because the moving v1 tag no longer receives updates. Examples use a placeholder linked to the releases page instead of hard-coding a version.

Related: voidzero-dev/setup-vp#116

[netlify]

✅ Deploy Preview for viteplus-preview canceled.

Name	Link
🔨 Latest commit	d5ce034
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a744a48192c0f0008a9b4c1

[github-actions]

✅ Staging deployment successful!

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

[TheAlexLichter]

@fengmk2 why is it frozen? security?

EDIT: Ah, described in the other issue!

The v1 major tag is frozen at v1.15.0: the voidzero-dev org-level tag ruleset blocks non-fast-forward tag updates, so it can no longer be moved on each release

[fengmk2]

@fengmk2 why is it frozen? security?

EDIT: Ah, described in the other issue!

The v1 major tag is frozen at v1.15.0: the voidzero-dev org-level tag ruleset blocks non-fast-forward tag updates, so it can no longer be moved on each release

Encourage everyone with practical actions pinned GitHub Action version 😭

[github-actions]

Registry bridge build (d5ce034)

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.d5ce0346f8f210ede05fa97dc522e192270b3813
@voidzero-dev/vite-plus-core	0.0.0-commit.d5ce0346f8f210ede05fa97dc522e192270b3813

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

# macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2359 bash

# Windows (PowerShell)
$env:VP_PR_VERSION="2359"; irm https://vite.plus/ps1 | iex

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.d5ce0346f8f210ede05fa97dc522e192270b3813",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.d5ce0346f8f210ede05fa97dc522e192270b3813"
  }
}

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-2359	236MB

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

Quick check:

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

See docs/guide/docker.md for usage.