Skip to content

chore(deps): update vite-plus to v0.2.8 - #119

Merged
fengmk2 merged 2 commits into
mainfrom
renovate/vite-plus
Aug 6, 2026
Merged

chore(deps): update vite-plus to v0.2.8#119
fengmk2 merged 2 commits into
mainfrom
renovate/vite-plus

Conversation

@renovate

@renovate renovate Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 0.2.70.2.8 age adoption passing confidence
vite-plus (source) 0.2.70.2.8 age adoption passing confidence

Release Notes

voidzero-dev/vite-plus (vite)

v0.2.8: vite-plus v0.2.8: monorepo target resolution, breaking VP_* environment variable renames, and install fixes

Compare Source

Bare vp dev/build/preview/pack at a monorepo root now resolve a target package instead of silently running against the root, and three Vite+-specific environment variables move to the VP_* prefix without compatibility aliases. Two failures that broke Vite+ before it could run are also fixed: the crash on container images that ship no CA certificates, and the missing Rolldown binding under pnpm's global virtual store.

Breaking Changes
  • Rename three Vite+-specific environment variables to the VP_* prefix, with no compatibility aliases, so the old names stop working (#​2312), by @​jong-kyung:

    Old New
    VITE_LOG VP_LOG
    VITE_GLOBAL_CLI_JS_SCRIPTS_DIR VP_GLOBAL_CLI_JS_SCRIPTS_DIR
    VITE_UPDATE_TASK_TYPES VP_UPDATE_TASK_TYPES

    Update any shell profile, CI job, or Dockerfile that sets the old names.

Highlights
  • Resolve a target package for vp dev, build, preview, and pack at a monorepo root: interactive shells get a fuzzy package picker, non-interactive runs list the candidates and exit 1 instead of building the root, and a new global -C <dir> flag or a defaultPackage setting (a single directory, or an object mapping each of the four commands to its own directory) skips the prompt (#​2031, #​2305), by @​fengmk2
  • Stop aborting with exit 134 on container images that ship no CA certificates (Debian slim, distroless): the shared HTTP client now retries once with the bundled Mozilla root list, like Node's own bundled roots, and reports a real error instead of panicking when it still cannot be built (#​2273, #​2295), by @​jbmusso and @​fengmk2
  • Resolve the bundled Rolldown binding through platform packages instead of an undeclared require back into vite-plus, fixing Cannot find module 'vite-plus/binding' under pnpm enable-global-virtual-store and in standalone @voidzero-dev/vite-plus-core installs (#​2313), by @​fengmk2
  • Add vp pm ci for reproducible frozen-lockfile installs, and vp pm patch / vp pm patch-commit for editing dependencies in place on pnpm, bun, and Yarn Berry (npm and Yarn Classic warn and exit successfully) (#​2082, #​2308), by @​forehalo and @​jong-kyung
Features
  • Upgrade the bundled toolchain: vite 8.1.5 -> 8.2.0, rolldown 1.2.0 -> 1.2.2, oxlint 1.75.0 -> 1.76.0, oxfmt 0.60.0 -> 0.61.0, and Vite DevTools 0.4.5 -> 0.4.10 (#​2302, #​2311), by @​voidzero-guard[bot]. The new oxfmt and oxlint can flag code that passed before, so run vp fmt after upgrading if your CI runs vp check.
  • Read the Node.js version from .nvmrc when no other version source is present (#​2244), by @​BlankParticle
  • Support pnpm v12, which ships as a native binary: Vite+ now downloads the platform-specific @pnpm/exe.* package and generates native shims, so pnpm and pnpx work instead of failing to exec (#​2289), by @​jong-kyung
  • Verify the downloaded bun platform tarball against the registry dist.integrity hash (#​2310), by @​jong-kyung
Fixes & Enhancements
  • Let vp config install the Git hook dispatcher without creating or modifying project hook scripts or staged-file configuration, so a custom .vite-hooks/pre-commit survives (#​2280), by @​TheAlexLichter
  • Nest immutable global package installs under packages/<package>/<uuid> instead of using # in the path, which Node treated as a URL fragment and which broke dynamic imports inside installed packages (#​2222), by @​liangmiQwQ
  • Keep the recorded version spec on global installs, so vp update -g follows a dist tag or range instead of silently resolving back to latest, vp outdated -g reports Wanted versus Latest, and vp update -g --latest explicitly moves packages back to latest (#​2249), by @​TheAlexLichter
  • Stop deleting a managed Node.js runtime that another process is concurrently installing (#​2248), by @​shulaoda
  • Preserve the real exit code when a spawned process is terminated by a signal on Unix (#​2154), by @​liangmiQwQ
  • Honor an explicit vp create --package-manager outside monorepos instead of inheriting the manager from a non-monorepo ancestor directory (#​2226), by @​jong-kyung
  • Scaffold the vite:library template into a directory that contains only .git, while still refusing to overwrite existing user files (#​2287), by @​RSS1102
  • Render help for delegated commands from the local CLI, so vp <command> --help matches the installed toolchain instead of drifting (#​2184), by @​liangmiQwQ
  • Resolve typeAware and typeCheck options inherited through Oxlint extends, so vp check --no-lint runs and classifies type checking correctly (#​2228), by @​jong-kyung
  • Report (no version) instead of unknown when globally installing a local package that has no version field (#​2232), by @​liangmiQwQ
Refactor
  • Rename the Git hooks environment variable to VP_GIT_HOOKS, keeping VITE_GIT_HOOKS working as a deprecated alias (#​2195), by @​dennybiasiolli
  • Consolidate the package manager infrastructure so typed command arguments are the source of truth for per-manager compatibility (#​2140), by @​forehalo
  • Generate the Zed language settings from a language list instead of 17 near-identical blocks (#​2294), by @​jong-kyung
  • Share the agent-file detect and write traversal helpers so both passes apply identical rules (#​2296), by @​jong-kyung
  • Drop redundant clippy allow attributes in the global CLI (#​2235), by @​shulaoda
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.2.0 fa79f9a
rolldown 1.2.2 872b98a
tsdown 0.22.14 npm
vitest 4.1.10 npm
oxlint 1.76.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.61.0 npm
Upgrade
vp upgrade
New Contributors

@​jbmusso, @​Arcadi4, @​dennybiasiolli, @​RSS1102

Full Changelog: voidzero-dev/vite-plus@v0.2.7...v0.2.8

Published Packages
  • @voidzero-dev/vite-plus-core@0.2.8
  • vite-plus@0.2.8
Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.8 vp build

Run any vp command without installing it; see the Docker guide for more.


Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the needs-bundle-rebuild Rebuild dist/ bundle and push to the PR (Renovate bumps to bundled deps) label Aug 5, 2026
@socket-security

socket-security Bot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​voidzero-dev/​vite-plus-core@​0.2.8801007799100
Addedvite-plus@​0.2.879100100100100

View full report

@renovate
renovate Bot force-pushed the renovate/vite-plus branch from 86576d7 to 8503f3f Compare August 6, 2026 03:04
@fengmk2
fengmk2 force-pushed the renovate/vite-plus branch from d2cac9d to 8503f3f Compare August 6, 2026 03:45
fengmk2 added a commit that referenced this pull request Aug 6, 2026
Renovate PR #119 bumped only the `vite-plus` catalog entry and left the
`vite` alias at `@voidzero-dev/vite-plus-core@0.2.7`. The alias resolves
to a different package name, so it matches the preset's generic npm rule
(3-day `minimumReleaseAge`, Monday schedule) instead of the vite+ rule
(0 days, any time). Both 0.2.8 packages were published together on Aug
5, but only `vite-plus` was eligible when Renovate ran 4 hours later.

Set `minimumReleaseAge` and `schedule` on the existing group rule so
every `@voidzero-dev/vite-plus-*` package follows the same policy and
one release lands as one grouped update.

After merging, a Renovate run should add the `vite` alias bump to #119.
@renovate
renovate Bot force-pushed the renovate/vite-plus branch from 8503f3f to cf0548d Compare August 6, 2026 03:56
@renovate renovate Bot changed the title chore(deps): update dependency vite-plus to v0.2.8 chore(deps): update vite-plus to v0.2.8 Aug 6, 2026
@renovate
renovate Bot force-pushed the renovate/vite-plus branch from cf0548d to badd444 Compare August 6, 2026 06:39
@fengmk2 fengmk2 added needs-bundle-rebuild Rebuild dist/ bundle and push to the PR (Renovate bumps to bundled deps) and removed needs-bundle-rebuild Rebuild dist/ bundle and push to the PR (Renovate bumps to bundled deps) labels Aug 6, 2026
fengmk2 added a commit that referenced this pull request Aug 6, 2026
The rebuild-bundle workflow only fired on the `labeled` event, so a
failed rebuild never retried: the label is added once at PR creation,
and later Renovate rebases never re-triggered it. On #119 the first
rebuild crashed during `pnpm install` (vite-plus-core 0.2.7 missing its
rolldown linux binding), and after Renovate rebased to 0.2.8 the stale
`dist/` kept failing the "Verify dist is up to date" check until the
label was manually re-added.

Changes:

- Trigger on `synchronize` as well as `labeled`, gated on the
`needs-bundle-rebuild` label being present (on the `labeled` event the
just-added label is already in the array).
- No loop: the run triggered by our own `dist/` push finds no diff and
exits without pushing, confirmed by today's no-op follow-up run on #119.
@renovate
renovate Bot force-pushed the renovate/vite-plus branch from 3676fe6 to 21be468 Compare August 6, 2026 06:56
@fengmk2
fengmk2 merged commit 030b265 into main Aug 6, 2026
46 checks passed
@fengmk2
fengmk2 deleted the renovate/vite-plus branch August 6, 2026 06:58
@fengmk2 fengmk2 mentioned this pull request Aug 6, 2026
fengmk2 added a commit that referenced this pull request Aug 6, 2026
Bump the version to v1.17.0 in package.json, the README examples, and
the setup-ref / setupRef defaults in the GitLab and Azure templates.

Changes since v1.16.1:

- feat: support disabling Vite+'s Node.js management with node-manager:
false (#115)
- fix: retry sfw vp install when sfw misreports vp as not found on
Windows (#120)
- chore(deps): update vite-plus to v0.2.8 (#119)
- ci: re-run bundle rebuild when Renovate pushes to a labeled PR (#122)
- chore: align Renovate release age for the whole vite-plus group (#121)

After merge, tag the merge commit as v1.17.0 and push the tag.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-bundle-rebuild Rebuild dist/ bundle and push to the PR (Renovate bumps to bundled deps)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant