Repository navigation
Conversation
The @nestjs group had no update-types filter, so Dependabot bundled the Nest 11 -> 12 major (#1781) together with pending minor/patch updates — the group PR fails CI and would hold back security fixes until a major migration happens. Restrict the group to minor/patch (continuously mergeable) and route majors to a separate nestjs-major group deferred until a migration is scheduled. Signed-off-by: Ajay Jadhav <ajay@ayanworks.com>
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|



Follow-up to #1779's grouping rule. The
nestjsgroup had noupdate-typesfilter, so Dependabot bundled the Nest 11 → 12 major (all 20@nestjs/*packages) into #1781 — which fails CI, and would hold back any pending minor/patch/security fixes until a major migration is done.Change
nestjsgroup →update-types: [minor, patch]— stays continuously mergeable (incl. security-driven minors)nestjs-majorgroup →update-types: [major]— one deferred PR (what chore(deps): bump the nestjs group across 1 directory with 20 updates #1781 will become on its next run), migrated when schedulednestjs-securitygroup unchanged — security updates flow regardless of bump typeValidation
.github/dependabot.ymlcheck on this PR is the authoritative gateSummary by CodeRabbit