chore: align Renovate release age for the whole vite-plus group - #121
Merged
fengmk2 merged 1 commit intoAug 6, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
The vite catalog entry is an npm alias for @voidzero-dev/vite-plus-core, so it matches the preset's generic npm rule (3-day minimumReleaseAge, Monday schedule) instead of the vite+ rule (0 days, any time). When both 0.2.8 packages were published together, only vite-plus was eligible, so the grouped PR bumped one catalog entry and left the alias at 0.2.7. Set minimumReleaseAge and schedule on the group rule so every @voidzero-dev/vite-plus-* package follows the same policy as vite-plus.
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository Renovate configuration so all Vite+ related packages (including the vite catalog alias resolving to @voidzero-dev/vite-plus-*) follow the same release-age and schedule policy, ensuring Renovate groups and proposes synchronized updates together.
Changes:
- Extend the existing vite-plus package rule to set minimumReleaseAge: "0 days" and schedule: ["at any time"] for the whole vite-plus group.
- Clarify the rule’s intent in the description to document why the alias needs the same policy as vite-plus.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
This was referenced Aug 6, 2026
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.
fengmk2
added a commit
to voidzero-dev/vite-task
that referenced
this pull request
Aug 10, 2026
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.
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.
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.