From 278a954719bb45e2a0908289fe98145a0e1f1c3f Mon Sep 17 00:00:00 2001 From: MK Date: Thu, 6 Aug 2026 11:47:55 +0800 Subject: [PATCH] chore: group all Vite+ packages on one Renovate policy The vite catalog entry is an npm alias for @voidzero-dev/vite-plus-core, so it falls into the preset's generic npm-packages group (3-day minimumReleaseAge, Monday schedule) while vite-plus follows the vite+ rule (0 days, any time). Each Vite+ release then splits across two PRs with mismatched versions: the vite+ PR bumps vite-plus and leaves the alias behind, and the npm-packages PR bumps the alias and leaves vite-plus behind. Add a repo rule so vite-plus and @voidzero-dev/vite-plus-* share the vite+ group and the same age and schedule. --- .github/renovate.json | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/.github/renovate.json b/.github/renovate.json index 6eea32f..22ceae3 100644 --- a/.github/renovate.json +++ b/.github/renovate.json @@ -1,4 +1,13 @@ { "$schema": "https://docs.renovatebot.com/renovate-schema.json", - "extends": ["github>Boshen/renovate"] + "extends": ["github>Boshen/renovate"], + "packageRules": [ + { + "description": "Group all Vite+ packages into a single PR; they are published together at the same version. minimumReleaseAge and schedule keep @voidzero-dev/vite-plus-* (the vite catalog alias) on the same policy as vite-plus; the preset's generic npm rule would otherwise hold the alias behind a 3-day age gate and a Monday schedule.", + "groupName": "vite+", + "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*"], + "minimumReleaseAge": "0 days", + "schedule": ["at any time"] + } + ] }