release: v1.6.0 (#3426)

Vite+ 1.6.0 caches `vp run` tasks that rewrite files they read, previews
runs with `vp run --dry-run` and JSON output, lets `vp check
--continue-on-error` report every failed check, and sets `VP_USER_AGENT`
for the tools that `vp` starts.

### Features

- `vp run` caches tasks that read files they also write, such as `tsdown
--exports` rewriting `package.json` or `tsc --incremental` reading and
writing `tsconfig.tsbuildinfo`. The files a task writes, and folders
that hold only those files, may be missing on the next run, as on a
fresh clone, and a cache hit restores them with the task's outputs,
including the symbolic links the task created
([docs](https://viteplus.dev/guide/automatic-data-tracking#rebuildable-inputs))
([vite-task#913](voidzero-dev/vite-task#913),
[vite-task#914](voidzero-dev/vite-task#914),
[vite-task#915](voidzero-dev/vite-task#915),
[vite-task#916](voidzero-dev/vite-task#916),
[vite-task#917](voidzero-dev/vite-task#917),
[vite-task#918](voidzero-dev/vite-task#918)), by
@wan9chi.
- `vp run --dry-run` shows each command that a run would start and
whether it would hit the cache, without running anything or writing to
the cache. `vp run --json` prints every package and task in the
workspace, and `vp run --dry-run --json` prints the run plan with each
step's cache status, as one JSON document for scripts, CI, and coding
agents. `vp run -v` lists every change behind a cache miss, including
each changed input file, and `-vv` also lists the unchanged inputs and
the outputs that a hit restores
([docs](https://viteplus.dev/guide/run#dry-runs-and-json-output))
([vite-task#948](voidzero-dev/vite-task#948),
[vite-task#960](voidzero-dev/vite-task#960),
[vite-task#961](voidzero-dev/vite-task#961),
[vite-task#963](voidzero-dev/vite-task#963),
[vite-task#966](voidzero-dev/vite-task#966),
[vite-task#967](voidzero-dev/vite-task#967),
[vite-task#968](voidzero-dev/vite-task#968),
[vite-task#969](voidzero-dev/vite-task#969)), by
@wan9chi.
- `vp check --continue-on-error` runs the remaining enabled checks after
a failure, so one run reports formatting, lint, and type errors
together, and exits with the status of the first failed check. Without
the flag, `vp check` still stops at the first failed check
([#3367](#3367)), by
@chbaefront.
- `vp`, `vpr`, and `vpx` set `VP_USER_AGENT=vp/<version>` for their
child processes, so tools can detect that Vite+ started them. When the
global CLI delegates to a project's local CLI, the local version is
reported ([docs](https://viteplus.dev/guide/global-cli#vp-user-agent))
([#1958](#1958)), by
@fengmk2.
- First part of `VP_ENV_FORBIDDEN=1`, for systems such as NixOS that
provide Node.js and package managers themselves: with it set, Vite+
never downloads a Node.js or package-manager version, shims and `vpx`
use only the system tools on `PATH`, and installers and `vp upgrade` use
the system `node` and `pnpm` for Vite+'s own dependencies. In this
release, commands that delegate to a package manager, such as `vp
install` and `vp run`, fail with `DisabledByEnvForbidden` while it is
set. A follow-up change is planned to cover them and document the
variable ([#3233](#3233)),
by @myuron.
- Upgrade the bundled Oxfmt and Oxlint
([#3416](#3416)), by
@voidzero-guard[bot]:
- `oxfmt@0.76.0` to `oxfmt@0.78.0`. Oxfmt formats Vue files with its own
formatter instead of Prettier, so the output for Vue templates can
change. It also fixes Tailwind class sorting in several layouts, Less
escapes and `%` selectors, and TypeScript in Astro files.
- `oxlint@1.91.0` to `oxlint@1.93.0` and `oxlint-tsgolint@7.0.2005` to
`oxlint-tsgolint@7.0.2006`. `no-redeclare` gets an
`ignoreDeclarationMerge` option, and `promise/prefer-catch` offers a
suggestion.
- Oxlint and Oxfmt resolve an unset or relative `root` in
`vite.config.ts` from the directory of the config file instead of the
current directory, so editor integrations in multi-root workspaces load
the correct project.
- Vite+ installs its own dependencies during setup and `vp upgrade` with
`pnpm@10.34.9` (was `pnpm@10.34.7`).
- The new Oxfmt and Oxlint can flag code that passed before. If your CI
runs `vp check`, run `vp check --fix --continue-on-error` after you
upgrade: it formats files, applies the available lint fixes, formats
again, and reports every error that remains. For example,
`unicorn/prefer-type-error` now also reports a `throw` in an `if` branch
without braces, and this command rewrites it.

### Fixes & Enhancements

- While a Vite+ spinner is visible, such as `Installing global packages`
in `vp install -g`, Vite+ hides the cursor and discards typed keys.
Pressing Enter no longer leaves copies of the spinner row, and typed
text no longer runs in the shell after the command ends. Ctrl+C during a
spinner now ends the command with the usual signal status instead of
exit code 0, and the global package spinners show the elapsed time
([#3373](#3373),
[#3417](#3417)), by
@jong-kyung and @fengmk2.
- `vp run` loads a package's `vite.config.*` only when the run reaches
one of that package's tasks. A run in one package no longer waits for
the configs of other packages, a broken config in another package no
longer fails it, and `vp run <task>` in a package that does not define
the task reports `Task "<task>" not found` instead of another package's
config error
([vite-task#944](voidzero-dev/vite-task#944),
[vite-task#988](voidzero-dev/vite-task#988)), by
@wan9chi.
- `vp run nope#build`, where no workspace package has the name `nope`,
fails with `Package 'nope' not found in the workspace` and exits with
code 1, instead of running nothing and exiting with code 0. A short name
that matches several scoped packages fails as ambiguous
([vite-task#984](voidzero-dev/vite-task#984)),
by @wan9chi.
- Folder listings no longer skip entries named `dist`, so a `dist`
folder that appears or disappears in a folder a task lists makes the
next run a cache miss. Exclusions in a task's `input`, such as
`"!dist/**"`, now also apply to the folders that the task lists. In a
new monorepo from `vp create`, every task hits the cache from the third
`vp run ready`, because the first build creates the `dist` folders
([vite-task#919](voidzero-dev/vite-task#919),
[vite-task#941](voidzero-dev/vite-task#941)), by
@wan9chi.
- Fewer unnecessary cache misses and cache failures in `vp run`: on
Windows, files that a task deletes or moves are no longer among its
inputs. Tasks that read `node_modules/.vite/task-cache`, as Parcel and
Gatsby do, hit the cache. A task that writes outside the workspace
through `..`, like `cp -r dist ../site`, no longer fails with `Cache
update failed`
([vite-task#937](voidzero-dev/vite-task#937),
[vite-task#940](voidzero-dev/vite-task#940),
[vite-task#980](voidzero-dev/vite-task#980)), by
@wan9chi.
- A cache hit restores the symbolic links that a task's `output` globs
match as links, instead of dropping them
([vite-task#885](voidzero-dev/vite-task#885)),
by @jasonkuhrt.
- When several tasks become ready at the same time, `vp run` checks
their cache entries in parallel, so cache hits start sooner
([vite-task#982](voidzero-dev/vite-task#982)),
by @wan9chi.
- On macOS, task commands that use `sh` or `bash` behave as on Linux: a
`while read` loop with a redirect under `set -e` no longer exits the
script, an `EXIT` trap sees the exit status, so a failed task is no
longer reported as successful, and `$BASH` is set
([vite-task#939](voidzero-dev/vite-task#939)),
by @lifeiscontent.
- The helper files that `vp run` writes to the system temp directory go
in one folder that only the current user can write to, such as
`/tmp/vp_run-1000` on Linux. On Linux, a different Vite+ version run by
another user no longer fails
([vite-task#947](voidzero-dev/vite-task#947),
[vite-task#974](voidzero-dev/vite-task#974)), by
@wan9chi.
- A `getEnvs` query from `@voidzero-dev/vite-task-client` that matches
every name (`{ prefix: '' }` or `*`) returns nothing and no longer adds
every environment variable to the cache key
([vite-task#976](voidzero-dev/vite-task#976)),
by @wan9chi.
- `vp migrate` no longer writes package specs that the package manager
cannot resolve, such as a `@vitest/*` `catalog:` reference without a
catalog entry or a top-level catalog on Bun before 1.2.21. Bun projects
with an empty `workspaces` field get catalog references, and child
packages with a plain `vite-plus` range get the same concrete version as
the root when the project cannot use catalogs
([#3397](#3397)), by
@jong-kyung.
- `vp create` uses the package manager version that `VP_PACKAGE_MANAGER`
selects for the generated settings, the installation, and its summary.
Standalone pnpm projects get `packages: ['.']` in an existing
`pnpm-workspace.yaml` only for pnpm before 10.5.0
([#3197](#3197)), by
@evan-lc and @fengmk2.
- `vp` sends a `User-Agent` header on all HTTP requests, so Node.js
mirrors that reject requests without one, such as `mirrors.aliyun.com`,
work ([#3425](#3425)), by
@naokihaba.
- `vp env pin` prints `Updated` when it overwrites an existing
`.node-version` or `.nvmrc` file and `Created` when it writes a new one
([#3377](#3377)), by
@CheHyeonYeong.

### Docs

- Describe rebuildable inputs in the Automatic Data Tracking guide, and
dry runs, JSON output, and `-vv` in the `vp run` guide
([#3419](#3419),
[#3421](#3421)), by
@wan9chi.

### Chore

- Bump vite-task to `cb1ea8d`, with its user-facing changes listed
above, and list `--dry-run`, `--json`, and `-vv` in `vp run --help`
([#3418](#3418)), by
@wan9chi.
- The daily dependency upgrade also updates the pnpm version that the
installers pin, after it checks the release integrity
([#3407](#3407)), by
@fengmk2.
- Warm up the monorepo cache check in the `vp create` CI job under pnpm
and Bun ([#3423](#3423)),
by @wan9chi.
- Remove an unused CI job that the required `done` check did not cover
([#3403](#3403)), by
@jong-kyung.
- Remove an incorrect comment about export pattern order in the CLI
build script
([#3405](#3405)), by
@alexicum.

### Bundled Versions

| Tool | Version | Source | Changelog |
| --------------- | ---------- |
----------------------------------------------------------------------------------------------------
|
-----------------------------------------------------------------------------------------------------------------------------------------------
|
| vite | `8.3.7` |
[`5def936`](vitejs/vite@5def936)
| unchanged |
| rolldown | `1.2.18` |
[`f9a49d6`](rolldown/rolldown@f9a49d6)
| unchanged |
| oxc-node | `1.0.1` |
[`7ff14c3`](oxc-project/oxc-node@7ff14c3)
| unchanged |
| tsdown | `0.23.4` | [npm](https://npmx.dev/package/tsdown/v/0.23.4) |
unchanged |
| vitest | `5.1.0` | [npm](https://npmx.dev/package/vitest/v/5.1.0) |
unchanged |
| oxlint | `1.93.0` | [npm](https://npmx.dev/package/oxlint/v/1.93.0) |
[1.92.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.92.0),
[1.93.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.93.0)
|
| oxlint-tsgolint | `7.0.2006` |
[npm](https://npmx.dev/package/oxlint-tsgolint/v/7.0.2006) |
[7.0.2006](https://github.com/oxc-project/tsgolint/releases/tag/v7.0.2006)
|
| oxfmt | `0.78.0` | [npm](https://npmx.dev/package/oxfmt/v/0.78.0) |
[0.77.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.77.0),
[0.78.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.78.0)
|

### Upgrade

```bash
vp upgrade
```

If `vp upgrade` must download Node.js and `VP_NODE_DIST_MIRROR` points
to a mirror that rejects requests without a `User-Agent` header, such as
`mirrors.aliyun.com`, unset it or point it to another mirror for this
upgrade. The installed `vp` downloads Node.js and does not send the
header yet.

### New Contributors

@alexicum, @evan-lc, @CheHyeonYeong

**Full Changelog**:
v1.5.1...v1.6.0

---

For a stable release, complete the `HomebrewFormula/vp.rb` update after
publication by merging the generated `release/homebrew-v1.6.0` PR.

Merging this PR will trigger the release workflow.

---------

Co-authored-by: voidzero-guard[bot] <278573678+voidzero-guard[bot]@users.noreply.github.com>
Co-authored-by: MK (fengmk2) <fengmk2@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: 3 people

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "vp_global_cli"
-version = "1.5.1"
+version = "1.6.0"
 authors.workspace = true
 edition.workspace = true
 license.workspace = true

crates/vp_global_cli/Cargo.toml

@@ -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.5.1 release, use \`pnpm dlx --package=vite-plus@1.5.1 vp migrate --no-interactive\` or \`npx --package=vite-plus@1.5.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 localMigrationPrompt = `Without a global installation, run the target CLI through the package manager from the workspace root. For the 1.6.0 release, use \`pnpm dlx --package=vite-plus@1.6.0 vp migrate --no-interactive\` or \`npx --package=vite-plus@1.6.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 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.5.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.
+Replace 1.6.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 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.5.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.
+Replace 1.6.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.
 
 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.5.1 release, run \`pnpm dlx --package=vite-plus@1.5.1 vp create\` or \`npx --package=vite-plus@1.5.1 vp create\`. Replace 1.5.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.
+Without a global installation, use a supported Node.js runtime from the compatibility guide. For the 1.6.0 release, run \`pnpm dlx --package=vite-plus@1.6.0 vp create\` or \`npx --package=vite-plus@1.6.0 vp create\`. Replace 1.6.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.
 
 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.
 

docs/.vitepress/theme/data/migration-prompts.ts

@@ -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.5.1` 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.6.0` release:
 
 ::: code-group
 
 ```bash [pnpm]
-pnpm dlx --package=vite-plus@1.5.1 vp migrate --no-interactive
+pnpm dlx --package=vite-plus@1.6.0 vp migrate --no-interactive
 ```
 
 ```bash [npm]
-npx --package=vite-plus@1.5.1 vp migrate --no-interactive
+npx --package=vite-plus@1.6.0 vp migrate --no-interactive
 ```
 
 :::
 
-Replace `1.5.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.
+Replace `1.6.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.
 
 After migration, finish dependency installation and validate with the updated local CLI:
 

docs/guide/migrate.md

@@ -1,6 +1,6 @@
 [package]
 name = "vite-plus-cli"
-version = "1.5.1"
+version = "1.6.0"
 authors.workspace = true
 edition.workspace = true
 license.workspace = true