ci: publish prompts with npm releases

[fengmk2]

The release workflow builds packages/prompts but omits it from npm releases.

Release preparation now sets its version to match vite-plus. The publish job uses the existing artifact and skips versions that already exist. It waits for npm availability before it creates the GitHub release.

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://ci-publish-prompts-viteplus-dev.voidzero-docs.workers.dev (commit 005b1dc)

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://333f9b1b-viteplus-dev.voidzero-docs.workers.dev	005b1dc	2026-09-15T07:38:05.344Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://35f5cdc7-viteplus-dev.voidzero-docs.workers.dev	59f4170	2026-09-15T07:12:22.240Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://955a282c-viteplus-dev.voidzero-docs.workers.dev	c80fea3	2026-09-15T06:58:35.715Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://84dabc2d-viteplus-dev.voidzero-docs.workers.dev	e9fa53b	2026-09-15T03:03:29.229Z	Visit the dashboard ↗

[github-actions]

Registry bridge build (e9fa53b)

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

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

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

# Windows (PowerShell)
$env:VP_PR_VERSION="2707"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/e9fa53bf2ecd311f18e5c0d873eca852e38be708/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/e9fa53bf2ecd311f18e5c0d873eca852e38be708/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.e9fa53bf2ecd311f18e5c0d873eca852e38be708" --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.e9fa53bf2ecd311f18e5c0d873eca852e38be708",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.e9fa53bf2ecd311f18e5c0d873eca852e38be708"
  }
}

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-2707	223MB

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

Quick check:

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

See docs/guide/docker.md for usage.