chore: group all Vite+ packages on one Renovate policy - #42
Merged
Conversation
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.
|
✅ Staging deployment successful! Preview: https://vp-setup-staging.void.app/ |
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
1 participant
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.
The
vitecatalog entry is an npm alias for@voidzero-dev/vite-plus-core, so it falls into the preset's generic npm-packages group (3-dayminimumReleaseAge, Monday schedule) whilevite-plusfollows the vite+ rule (0 days, any time). Each Vite+ release then splits across two PRs with mismatched versions: #36 bumpsvite-plusto 0.2.8 and leaves the alias at 0.2.1, while #37 bumps the alias to 0.2.7 and leavesvite-plusat 0.2.1.Add a repo rule so
vite-plusand@voidzero-dev/vite-plus-*share the vite+ group and the same age and schedule.After merging, a Renovate run should fold the alias bump into #36 and drop it from #37.