Skip to content

chore: group all Vite+ packages on one Renovate policy - #628

Merged
fengmk2 merged 2 commits into
mainfrom
renovate-vite-plus-group
Aug 10, 2026
Merged

chore: group all Vite+ packages on one Renovate policy#628
fengmk2 merged 2 commits into
mainfrom
renovate-vite-plus-group

Conversation

@fengmk2

@fengmk2 fengmk2 commented Aug 10, 2026

Copy link
Copy Markdown
Member

The vite catalog entry is an npm alias for @voidzero-dev/vite-plus-core, so it misses the preset's vite+ rule (0-day minimumReleaseAge, any-time schedule) and falls under the generic npm rule (3-day age, Monday schedule). Renovate then bumps vite-plus and leaves the alias behind: main already pairs vite-plus 0.2.4 with core 0.2.2, and #593 would widen that to 0.2.8 vs 0.2.2.

Add a repo rule so vite-plus, @voidzero-dev/vite-plus-*, and vitest share the vite+ group and the same age and schedule. vp pins the vitest override to the version bundled in vite-plus, so a lone vitest bump would desync that pin the same way; vite-task has no vitest today, making the match inert until it does. After merging, a Renovate run should fold the alias bump to 0.2.8 into #593.

Same fix as voidzero-dev/setup-vp#121 and voidzero-dev/setup.viteplus.dev#42, where Renovate folded the alias into the open update PR after the config merged. General write-up in voidzero-dev/vite-plus#2356; the preset-level fix Boshen/renovate#1 is still open, and this rule becomes redundant once it merges.

The vite catalog entry is an npm alias for @voidzero-dev/vite-plus-core,
so it misses the preset's vite+ rule (0-day minimumReleaseAge, any-time
schedule) and falls under the generic npm rule (3-day age, Monday
schedule). Renovate then bumps vite-plus and leaves the alias behind:
main already pairs vite-plus 0.2.4 with core 0.2.2, and #593 would widen
that to 0.2.8 vs 0.2.2.

Add a repo rule so vite-plus and @voidzero-dev/vite-plus-* share the
vite+ group and the same age and schedule. Same fix as
voidzero-dev/setup-vp#121 and voidzero-dev/setup.viteplus.dev#42; see
voidzero-dev/vite-plus#2356 for the general write-up.
vp pins the vitest override to the version bundled in vite-plus, so a
lone vitest bump would desync the pin the same way as the vite alias.
vite-task has no vitest today; the match is inert until it does.
@github-actions

Copy link
Copy Markdown

fspy benchmark

linux

dynamic/launch             change  -0.10%  [ -3.77% ..  +4.94%]  overhead   +65.13%
dynamic/access             change  +0.00%  [ -1.20% ..  +1.84%]  overhead    +7.55%
dynamic/access-relative    change  +0.30%  [ -1.06% ..  +1.29%]  overhead   +46.52%
static/launch              change  +0.69%  [ -3.81% ..  +4.79%]  overhead  +194.91%
static/access              change  +0.26%  [ -0.84% ..  +1.41%]  overhead  +829.35%
static/access-relative     change  +0.25%  [ -1.03% ..  +1.37%]  overhead +1331.54%

macos

dynamic/launch             change  -0.43%  [ -5.11% ..  +4.68%]  overhead  +233.09%
dynamic/access             change  -1.28%  [-15.14% ..  +4.66%]  overhead    +4.29%
dynamic/access-relative    change  -3.13%  [-24.95% ..  +8.99%]  overhead  +237.32%

windows

dynamic/launch             change  -0.00%  [ -2.41% ..  +1.86%]  overhead   +26.62%
dynamic/access             change  -0.19%  [ -1.69% ..  +1.13%]  overhead    +0.96%
dynamic/access-relative    change  -0.18%  [ -1.08% ..  +1.14%]  overhead    +1.15%

@fengmk2
fengmk2 merged commit d068d44 into main Aug 10, 2026
19 checks passed
@fengmk2
fengmk2 deleted the renovate-vite-plus-group branch August 10, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant