Skip to content

feat: ship a Renovate preset and dependency-bot docs for lockstep updates - #2463

Draft
fengmk2 wants to merge 2 commits into
feat/core-version-skew-guardfrom
feat/renovate-preset
Draft

feat: ship a Renovate preset and dependency-bot docs for lockstep updates#2463
fengmk2 wants to merge 2 commits into
feat/core-version-skew-guardfrom
feat/renovate-preset

Conversation

@fengmk2

@fengmk2 fengmk2 commented Aug 16, 2026

Copy link
Copy Markdown
Member

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. This is #2356 idea 1, stacked on the fail-fast guard (#2462).

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 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 passes renovate-config-validator.

Docs: a new "Dependency Update Bots" section in the CI guide documents the preset and an equivalent Dependabot groups config, and the migration guide links to it from the overrides section.

Refs #2356


Stack created with GitHub Stacks CLIGive Feedback 💬

@github-actions

github-actions Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 2021490

@fengmk2
fengmk2 marked this pull request as draft August 16, 2026 10:09
@fengmk2
fengmk2 force-pushed the feat/renovate-preset branch 3 times, most recently from 4b980d0 to 7cfd69a Compare August 16, 2026 12:03
@fengmk2
fengmk2 force-pushed the feat/renovate-preset branch 2 times, most recently from 3117523 to fecc2bb Compare August 17, 2026 08:03
@fengmk2
fengmk2 force-pushed the feat/renovate-preset branch from fecc2bb to 81a4412 Compare August 25, 2026 16:31
@netlify

netlify Bot commented Aug 25, 2026

Copy link
Copy Markdown

Deploy Preview for viteplus-preview ready!

Name Link
🔨 Latest commit 81a4412
🔍 Latest deploy log https://app.netlify.com/projects/viteplus-preview/deploys/6a8dc37a84f91c00082ef27e
😎 Deploy Preview https://deploy-preview-2463--viteplus-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Aug 25, 2026

Copy link
Copy Markdown

Deploy Preview for viteplus-preview canceled.

Name Link
🔨 Latest commit 2021490
🔍 Latest deploy log https://app.netlify.com/projects/viteplus-preview/deploys/6a8dce932ca7b30008e1daf5

…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
fengmk2 force-pushed the feat/renovate-preset branch from 81a4412 to 2021490 Compare August 25, 2026 17:19
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