feat: ship a Renovate preset and dependency-bot docs for lockstep updates - #2463
Draft
fengmk2 wants to merge 2 commits into
Draft
feat: ship a Renovate preset and dependency-bot docs for lockstep updates#2463fengmk2 wants to merge 2 commits into
fengmk2 wants to merge 2 commits into
Conversation
Contributor
|
✅ Staging deployment successful! Preview: https://viteplus-staging.void.app/ |
fengmk2
marked this pull request as draft
August 16, 2026 10:09
fengmk2
force-pushed
the
feat/renovate-preset
branch
3 times, most recently
from
August 16, 2026 12:03
4b980d0 to
7cfd69a
Compare
fengmk2
force-pushed
the
feat/renovate-preset
branch
2 times, most recently
from
August 17, 2026 08:03
3117523 to
fecc2bb
Compare
fengmk2
force-pushed
the
feat/renovate-preset
branch
from
August 25, 2026 16:31
fecc2bb to
81a4412
Compare
✅ Deploy Preview for viteplus-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for viteplus-preview canceled.
|
…ates Every vp create / vp migrate project carries vite-plus plus the vite alias (npm:@voidzero-dev/vite-plus-core@<same version>), and vp test projects a pinned vitest override. Dependency bots update each package in its own PR, splitting the lockstep set. The root default.json is a shared Renovate preset, consumed as "extends": ["github>voidzero-dev/vite-plus"]. It groups vite-plus, @voidzero-dev/vite-plus-*, vitest, and @vitest/* into one PR and sets minimumReleaseAge and schedule on the group so no other rule can split member eligibility. The CI guide documents the preset and an equivalent Dependabot groups config, and the migration guide points at it from the overrides section. Refs #2356
The rule-level description restated the preset's top-level description; keep only the fact stated nowhere else (why minimumReleaseAge and schedule are pinned on the group). The CI guide now names all four commands the skew guard fails, not just build and test.
fengmk2
force-pushed
the
feat/renovate-preset
branch
from
August 25, 2026 17:19
81a4412 to
2021490
Compare
jamietanna
reviewed
Sep 2, 2026
Comment on lines
+7
to
+8
| "groupName": "vite+", | ||
| "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*", "vitest", "@vitest/*"], |
There was a problem hiding this comment.
We'd be happy having a "monorepo preset" for these packages in upstream Renovate, if that'd be helpful
jamietanna
reviewed
Sep 2, 2026
| "description": "Explicit minimumReleaseAge and schedule give every member one eligibility policy, so another preset cannot hold one member back and split the group.", | ||
| "groupName": "vite+", | ||
| "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*", "vitest", "@vitest/*"], | ||
| "minimumReleaseAge": "1 day", |
There was a problem hiding this comment.
IMO, users of this preset may be a bit surprised by this (especially if it differs to their existing settings)
Member
Author
There was a problem hiding this comment.
Yes, that's why I haven't continued with this PR either, because I do not want to modify the Renovate configuration.
I'm wondering if renovatebot/renovate#45630 this Renovate PR can solve the Vite+ version upgrade issue, then I can remove this preset. 💌
There was a problem hiding this comment.
Yes, that's the hope 🤞🏼
We do also have renovatebot/renovate#45631 for the Renovate config side, so y'all don't need to maintain that yourselves
15 tasks
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
3 participants
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.
Every
vp create/vp migrateproject carriesvite-plusplus thevitealias (npm:@voidzero-dev/vite-plus-core@<same version>), andvp testprojects a pinnedvitestoverride. Dependency bots update each package in its own PR, splitting the lockstep set. This is #2356 idea 1, stacked on the fail-fast guard (#2462).The root
default.jsonis a shared Renovate preset, consumed as"extends": ["github>voidzero-dev/vite-plus"]. It groupsvite-plus,@voidzero-dev/vite-plus-*,vitest, and@vitest/*into one PR, and setsminimumReleaseAgeandscheduleon the group so no other rule can split member eligibility (the failure mode from voidzero-dev/setup-vp#119; rule shape taken from the merged fixes voidzero-dev/setup-vp#121 and voidzero-dev/setup.viteplus.dev#42). The preset passesrenovate-config-validator.Docs: a new "Dependency Update Bots" section in the CI guide documents the preset and an equivalent Dependabot
groupsconfig, and the migration guide links to it from the overrides section.Refs #2356
Stack created with GitHub Stacks CLI • Give Feedback 💬