voidzero-dev · wan9chi · Sep 26, 2026 · Sep 25, 2026 · Sep 25, 2026 · Sep 25, 2026
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/crates/vp_global_cli/Cargo.toml b/crates/vp_global_cli/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "vp_global_cli"
-version = "1.0.0-rc.0"
+version = "1.0.0-rc.1"
 authors.workspace = true
 edition.workspace = true
 license.workspace = true

diff --git a/docs/.vitepress/theme/data/migration-prompts.ts b/docs/.vitepress/theme/data/migration-prompts.ts
@@ -1,4 +1,4 @@
-const localMigrationPrompt = `Without a global installation, run the target CLI through the package manager from the workspace root. For the 1.0.0-rc.0 release, use \`pnpm dlx --package=vite-plus@1.0.0-rc.0 vp migrate --no-interactive\` or \`npx --package=vite-plus@1.0.0-rc.0 vp migrate --no-interactive\`. First run the same command with \`help migrate\` instead of \`migrate --no-interactive\` to read its help. These commands fetch the target CLI without replacing the old project dependencies first.`;
+const localMigrationPrompt = `Without a global installation, run the target CLI through the package manager from the workspace root. For the 1.0.0-rc.1 release, use \`pnpm dlx --package=vite-plus@1.0.0-rc.1 vp migrate --no-interactive\` or \`npx --package=vite-plus@1.0.0-rc.1 vp migrate --no-interactive\`. First run the same command with \`help migrate\` instead of \`migrate --no-interactive\` to read its help. These commands fetch the target CLI without replacing the old project dependencies first.`;
 
 const compatibilityReviewPrompt = `After establishing a passing baseline, try to remove the generated "Vitest v4 compatibility" settings with no code changes or small, localized fixes:
 
@@ -28,7 +28,7 @@ Use the CLI from the target Vite+ 1.0 release or its preview build. Use a suppor
 - With a global vp installation, follow ${__DOCS_ORIGIN__}/guide/upgrade to select the target release and check \`vp toolchain --global\`. Run \`vp help\` and \`vp help migrate\`, then \`vp migrate --no-interactive\` from the workspace root.
 - ${localMigrationPrompt}
 
-Replace 1.0.0-rc.0 with the intended release version. For a preview, use the version from its PR and pass \`--registry=https://registry-bridge.viteplus.dev\` to pnpm or npx before the vp command.
+Replace 1.0.0-rc.1 with the intended release version. For a preview, use the version from its PR and pass \`--registry=https://registry-bridge.viteplus.dev\` to pnpm or npx before the vp command.
 
 Do not run migration with an old project's node_modules/.bin/vp. Migrate monorepos from the workspace root so shared manifests, catalogs, overrides, and lockfiles remain consistent.
 
@@ -64,7 +64,7 @@ Use the CLI from the target Vite+ 1.0 release or its preview build. A global ins
 - With a global vp installation, follow ${__DOCS_ORIGIN__}/guide/upgrade to upgrade it and check \`vp toolchain --global\`. Run \`vp help migrate\`, then \`vp migrate --no-interactive\` from the workspace root.
 - ${localMigrationPrompt}
 
-Replace 1.0.0-rc.0 with the intended release version. For a preview, use the version from its PR and pass \`--registry=https://registry-bridge.viteplus.dev\` to pnpm or npx before the vp command. Do not run migration with the old project's node_modules/.bin/vp. Keep the existing project setup; do not use --full unless I request it.
+Replace 1.0.0-rc.1 with the intended release version. For a preview, use the version from its PR and pass \`--registry=https://registry-bridge.viteplus.dev\` to pnpm or npx before the vp command. Do not run migration with the old project's node_modules/.bin/vp. Keep the existing project setup; do not use --full unless I request it.
 
 Resolve BLOCK findings and rerun migration. Review each REVIEW finding using its documentation link, even if migration exits with success. Preserve test intent and keep the generated Vitest v4 and tsdown <0.23 compatibility settings and comments for the first validation run.
 
@@ -91,7 +91,7 @@ A global installation is optional. To install the global \`vp\` CLI when it is n
 
 Open a new terminal after installation. Follow ${__DOCS_ORIGIN__}/guide/upgrade to select the target release or preview and check \`vp toolchain --global\` before scaffolding.
 
-Without a global installation, use a supported Node.js runtime from the compatibility guide. For the 1.0.0-rc.0 release, run \`pnpm dlx --package=vite-plus@1.0.0-rc.0 vp create\` or \`npx --package=vite-plus@1.0.0-rc.0 vp create\`. Replace 1.0.0-rc.0 with the intended release version. For a preview, use the version from its PR and pass \`--registry=https://registry-bridge.viteplus.dev\` to pnpm or npx before the vp command.
+Without a global installation, use a supported Node.js runtime from the compatibility guide. For the 1.0.0-rc.1 release, run \`pnpm dlx --package=vite-plus@1.0.0-rc.1 vp create\` or \`npx --package=vite-plus@1.0.0-rc.1 vp create\`. Replace 1.0.0-rc.1 with the intended release version. For a preview, use the version from its PR and pass \`--registry=https://registry-bridge.viteplus.dev\` to pnpm or npx before the vp command.
 
 Run \`vp install\`, \`vp check\`, and \`vp test\`, then \`vp build\` for applications or \`vp pack\` for libraries. Without a global CLI, install with the project's package manager and run the local CLI through it, such as \`pnpm exec vp check\` or \`npm exec -- vp check\`. Explain how to use \`vp dev\` for the dev server and \`vp run <task>\` for project scripts or tasks. Report the setup changes, validation results, and any remaining work. Do not commit or push unless I ask.
 

diff --git a/docs/guide/migrate.md b/docs/guide/migrate.md
@@ -95,21 +95,21 @@ Upgrade the [global CLI](./upgrade.md#global-vp) to your target 1.0 release, the
 
 ### Without the Global CLI
 
-Use an existing Node.js runtime that satisfies `^22.18.0 || ^24.11.0 || >=26.0.0`. Run the target migrator through your package manager without adding it to the project first. For the `1.0.0-rc.0` release:
+Use an existing Node.js runtime that satisfies `^22.18.0 || ^24.11.0 || >=26.0.0`. Run the target migrator through your package manager without adding it to the project first. For the `1.0.0-rc.1` release:
 
 ::: code-group
 
 ```bash [pnpm]
-pnpm dlx --package=vite-plus@1.0.0-rc.0 vp migrate --no-interactive
+pnpm dlx --package=vite-plus@1.0.0-rc.1 vp migrate --no-interactive
 ```
 
 ```bash [npm]
-npx --package=vite-plus@1.0.0-rc.0 vp migrate --no-interactive
+npx --package=vite-plus@1.0.0-rc.1 vp migrate --no-interactive
 ```
 
 :::
 
-Replace `1.0.0-rc.0` with your target release. For a preview, use the version from the PR and pass `--registry=https://registry-bridge.viteplus.dev` to `pnpm` or `npx` before the `vp` command. Keep the version in `--package` explicit so you run the target migrator rather than the old local CLI.
+Replace `1.0.0-rc.1` with your target release. For a preview, use the version from the PR and pass `--registry=https://registry-bridge.viteplus.dev` to `pnpm` or `npx` before the `vp` command. Keep the version in `--package` explicit so you run the target migrator rather than the old local CLI.
 
 After migration, finish dependency installation and validate with the updated local CLI:
 

diff --git a/packages/cli/binding/Cargo.toml b/packages/cli/binding/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "vite-plus-cli"
-version = "1.0.0-rc.0"
+version = "1.0.0-rc.1"
 authors.workspace = true
 edition.workspace = true
 license.workspace = true