chore(deps): update vite-plus to v0.2.8 - #119
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/vite-plus
branch
from
August 6, 2026 03:04
86576d7 to
8503f3f
Compare
fengmk2
force-pushed
the
renovate/vite-plus
branch
from
August 6, 2026 03:45
d2cac9d to
8503f3f
Compare
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
Bot
force-pushed
the
renovate/vite-plus
branch
from
August 6, 2026 03:56
8503f3f to
cf0548d
Compare
renovate
Bot
force-pushed
the
renovate/vite-plus
branch
from
August 6, 2026 06:39
cf0548d to
badd444
Compare
This was referenced 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
Bot
force-pushed
the
renovate/vite-plus
branch
from
August 6, 2026 06:56
3676fe6 to
21be468
Compare
Merged
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.2.7→0.2.80.2.7→0.2.8Release Notes
voidzero-dev/vite-plus (vite)
v0.2.8: vite-plus v0.2.8: monorepo target resolution, breaking VP_* environment variable renames, and install fixesCompare Source
Bare
vp dev/build/preview/packat a monorepo root now resolve a target package instead of silently running against the root, and three Vite+-specific environment variables move to theVP_*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:VITE_LOGVP_LOGVITE_GLOBAL_CLI_JS_SCRIPTS_DIRVP_GLOBAL_CLI_JS_SCRIPTS_DIRVITE_UPDATE_TASK_TYPESVP_UPDATE_TASK_TYPESUpdate any shell profile, CI job, or Dockerfile that sets the old names.
Highlights
vp dev,build,preview, andpackat 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 adefaultPackagesetting (a single directory, or an object mapping each of the four commands to its own directory) skips the prompt (#2031, #2305), by @fengmk2vite-plus, fixingCannot find module 'vite-plus/binding'under pnpmenable-global-virtual-storeand in standalone@voidzero-dev/vite-plus-coreinstalls (#2313), by @fengmk2vp pm cifor reproducible frozen-lockfile installs, andvp pm patch/vp pm patch-commitfor editing dependencies in place on pnpm, bun, and Yarn Berry (npm and Yarn Classic warn and exit successfully) (#2082, #2308), by @forehalo and @jong-kyungFeatures
8.1.5->8.2.0, rolldown1.2.0->1.2.2, oxlint1.75.0->1.76.0, oxfmt0.60.0->0.61.0, and Vite DevTools0.4.5->0.4.10(#2302, #2311), by @voidzero-guard[bot]. The new oxfmt and oxlint can flag code that passed before, so runvp fmtafter upgrading if your CI runsvp check..nvmrcwhen no other version source is present (#2244), by @BlankParticle@pnpm/exe.*package and generates native shims, sopnpmandpnpxwork instead of failing to exec (#2289), by @jong-kyungdist.integrityhash (#2310), by @jong-kyungFixes & Enhancements
vp configinstall the Git hook dispatcher without creating or modifying project hook scripts or staged-file configuration, so a custom.vite-hooks/pre-commitsurvives (#2280), by @TheAlexLichterpackages/<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 @liangmiQwQvp update -gfollows a dist tag or range instead of silently resolving back tolatest,vp outdated -greports Wanted versus Latest, andvp update -g --latestexplicitly moves packages back tolatest(#2249), by @TheAlexLichtervp create --package-manageroutside monorepos instead of inheriting the manager from a non-monorepo ancestor directory (#2226), by @jong-kyungvite:librarytemplate into a directory that contains only.git, while still refusing to overwrite existing user files (#2287), by @RSS1102vp <command> --helpmatches the installed toolchain instead of drifting (#2184), by @liangmiQwQtypeAwareandtypeCheckoptions inherited through Oxlintextends, sovp check --no-lintruns and classifies type checking correctly (#2228), by @jong-kyung(no version)instead ofunknownwhen globally installing a local package that has noversionfield (#2232), by @liangmiQwQRefactor
VP_GIT_HOOKS, keepingVITE_GIT_HOOKSworking as a deprecated alias (#2195), by @dennybiasiolliDocs
vpinstallation step in the onboarding prompt (#2291), by @Arcadi4Chore
vite-pluspeer of oxfmt and oxlint on every install (#2321), by @fengmk2@emnapipeers where@napi-rs/cliis used (#2319), by @jong-kyungrollup-testsfrom the workspace and updatebasic-ftp(#2322), by @fengmk2EnvConfigfields (#2320), by @jong-kyungvpprocess, and kill it before its children, in theenv_install_interruptsnapshot test (#2299, #2316), by @fengmk2vitest_browser_modesnapshot test (#2297), by @fengmk2Bundled Versions
8.2.0fa79f9a1.2.2872b98a0.22.144.1.101.76.07.0.20010.61.0Upgrade
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.8vite-plus@0.2.8Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.8 vp buildRun any
vpcommand without installing it; see the Docker guide for more.Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.