release: v1.0.0-rc.1: task cache settings move under cache

[voidzero-guard]

Task cache settings now live under cache, and vp migrate moves existing task settings for you. vp lint and vp fmt run from a package directory now pick the same config as your editor, and piped vp output exits cleanly.

Breaking Changes

Task cache settings in run.tasks now go inside cache (#2813, #2814, vite-task#749), by @wan9chi.

Old (top level of a task)	New
env	cache.env
untrackedEnv	cache.untrackedEnv
input	cache.input
output	cache.output

cache: true is the same as cache: {}. After upgrading, a task that still uses the old top-level fields fails with an error that points to vp migrate. Run vp migrate to move the fields in vite.config.* for the workspace root and every package. It warns about any task it cannot rewrite safely so you can update that task by hand. Projects whose tasks do not use these fields need no changes. See the task cache migration rules and the cache reference.

Highlights

• vp lint and vp fmt run from a package directory now use the same config as Oxlint, Oxfmt, and the language server, so results match your editor. vp check still applies the workspace-root settings (#2807), by @fengmk2.
• Global vp commands now exit cleanly when piped into a command that closes early, such as vp --version | head -n 1, instead of aborting with exit code 134 (#2785, #2793), by @naokihaba.
• Cached tasks on macOS no longer intermittently fail with oils I/O error (main): No such process (vite-task#703), by @lifeiscontent.

Features

• The bundled tools update vite@8.3.0 -> vite@8.3.1, rolldown@1.2.9 -> rolldown@1.2.11, and oxlint-tsgolint@7.0.2002 -> oxlint-tsgolint@7.0.2003 (#2805, #2812), by @voidzero-guard[bot].

Fixes & Enhancements

• Async defineConfig callbacks now type-check lint and format options, such as 'warn' rule severities, the same way as synchronous callbacks, so configs updated by vp migrate no longer fail with TS2769 (#2803), by @TheAlexLichter.
• vp test --help now lists the Vitest 5 options --repeats, --injectCjsGlobals, --fsModuleCache, --fsModuleCachePath, and --sharedViteServer (#2809), by @Marve10s.
• On Windows, vp run now matches environment variable names regardless of letter case (vite-task#747), by @wan9chi.

Docs

• The copy prompt dialog no longer nests scroll areas and shows clearer copy feedback (#2794, #2799), by @liangmiQwQ and @Boshen.

Chore

• Snapshot tests share prepared packages and one Chromium process, run faster on every platform, and no longer read the live npm registry in the standalone npm fallback case (#2771, #2786, #2797), by @fengmk2 and @voidzero-guard[bot].
• The standalone install workflow loads the generated environment before running vp env doctor (#2790), by @naokihaba.

Bundled Versions

Tool	Version	Source
vite	8.3.1	39ddf7c
rolldown	1.2.11	8df4219
tsdown	0.23.0	npm
vitest	5.0.1	npm
oxlint	1.85.0	npm
oxlint-tsgolint	7.0.2003	npm
oxfmt	0.70.0	npm

Upgrade

vp upgrade

New Contributors

@Marve10s

Full Changelog: v1.0.0-rc.0...v1.0.0-rc.1

---

Merging this PR will trigger the release workflow.

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://release-v1-0-0-rc-1-viteplus-dev.voidzero-docs.workers.dev (commit 73ce44e)

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://3ec28dbe-viteplus-dev.voidzero-docs.workers.dev	73ce44e	2026-09-25T13:20:29.005Z	Visit the dashboard ↗
Build: In progress 🔵 View logs ↗		8252f48	2026-09-25T13:17:51.595Z	View logs ↗

[github-actions]

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 73ce44e

[github-actions]

CLI artifact sizes (73ce44e)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.
The dist rows use the Linux build. The core total excludes .node files to match the release artifact.

Artifact	Format	Base	PR	Change
packages/cli/dist	Directory total	2.35 MiB	2.35 MiB	0 B (0.00%)
packages/core/dist	Directory total	3.96 MiB	3.96 MiB	0 B (0.00%)
Combined package dist	Directory total	6.31 MiB	6.31 MiB	0 B (0.00%)
vp (Linux x64)	Binary	11.29 MiB	11.29 MiB	0 B (0.00%)
vp (Linux x64)	gzip -9	4.88 MiB	4.88 MiB	-2.02 KiB (-0.04%)
NAPI (Linux x64)	Binary	32.24 MiB	32.24 MiB	0 B (0.00%)
NAPI (Linux x64)	gzip -9	12.78 MiB	12.78 MiB	+1.11 KiB (+0.01%)
vp (macOS ARM64)	Binary	8.41 MiB	8.41 MiB	0 B (0.00%)
vp (macOS ARM64)	gzip -9	4.26 MiB	4.25 MiB	-2.37 KiB (-0.05%)
NAPI (macOS ARM64)	Binary	39.85 MiB	39.85 MiB	0 B (0.00%)
NAPI (macOS ARM64)	gzip -9	17.09 MiB	17.09 MiB	+720 B (+0.00%)
vp (Windows x64)	Binary	9.15 MiB	9.15 MiB	0 B (0.00%)
vp (Windows x64)	gzip -9	4.00 MiB	4.00 MiB	-106 B (-0.00%)
NAPI (Windows x64)	Binary	27.19 MiB	27.19 MiB	0 B (0.00%)
NAPI (Windows x64)	gzip -9	10.89 MiB	10.89 MiB	-101 B (-0.00%)
Trampoline (Windows x64)	Binary	13.50 KiB	13.50 KiB	0 B (0.00%)
Trampoline (Windows x64)	gzip -9	7.08 KiB	7.08 KiB	0 B (0.00%)
Installer (Windows x64)	Binary	4.56 MiB	4.56 MiB	0 B (0.00%)
Installer (Windows x64)	gzip -9	2.13 MiB	2.13 MiB	0 B (0.00%)

[github-actions]

Registry bridge build (73ce44e)

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

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

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

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

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

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

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

Quick check:

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

See docs/guide/docker.md for usage.