chore(renovate): group related dependency cohorts - #471
Conversation
- Add grouping for analyzers, build tooling, TUnit, test tooling. - Related packages now arrive in one PR instead of one PR each.
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s Renovate configuration to add repo-specific dependency grouping rules on top of the shared reactiveui/.github preset, so Renovate opens fewer, more coherent update PRs (especially for coupled test dependencies like TUnit + Verify.TUnit).
Changes:
- Expanded
extendsinto a multiline array (no functional change). - Added
packageRulesto group related NuGet dependencies into four cohorts: analyzers, build tooling, TUnit (+ Verify.*), and test tooling.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #471 +/- ##
=======================================
Coverage 62.16% 62.16%
=======================================
Files 75 75
Lines 4105 4105
Branches 572 572
=======================================
Hits 2552 2552
Misses 1385 1385
Partials 168 168 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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 toolingTUnittest toolingVerify.TUnitis compiled against a specific TUnit version, but the shared preset put TUnit in its own group andVerify.*in the .NET test stack - so a matched pair could land in two separate PRs and red the build. They are now grouped together.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.