chore(renovate): group related dependency cohorts - #4423
Merged
Conversation
- Add grouping for analyzers, build tooling, test tooling. - Related packages now arrive in one PR instead of one PR each.
|
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.
What kind of change does this PR introduce?
Chore - Renovate configuration only. No product code, no build files, no dependency versions change.
What is the new behavior?
Adds repo-specific grouping on top of the shared
reactiveui/.githubpreset so related packages arrive as one reviewable PR:analyzersbuild toolingtest toolingThe shared preset holds all of
Microsoft.CodeAnalysis.*on its current major to pin the compiler API.PublicApiAnalyzersandBannedApiAnalyzersship on their own release line and are not part of that toolchain, so their majors are allowed through again. The compiler-API pin is unaffected.What is the current behavior?
These packages are ungrouped, so each one opens its own PR even when it only makes sense to bump them together.
What might this PR break?
Nothing at build time - this file only affects how Renovate batches its own PRs. Any currently-open Renovate PR whose group name changes will be closed and reopened under the new branch name.
Checklist
mainbranchAdditional information
Validated with
renovate-config-validator. Every pattern was checked against this repo's actual package list (no dead rules), and the merged preset+repo rule set was resolved through Renovate'sapplyPackageRulesengine to confirm each package lands in the intended group.