chore(renovate): group by scenario, weekly with 3-day delay#357
Merged
Conversation
Replaces per-manager grouping (npm-dev/npm-prod/composer/pip/upstream-*) with per-scenario grouping: one PR per scenario covering its npm, docker, composer, pip, and pinned image deps. Root npm collapses into a single npm-web PR. github-actions stays as one weekly PR. All groups inherit a Monday 09:00 schedule and 3-day minimumReleaseAge; security alerts override both with "at any time" + no release-age gate.
This was referenced May 22, 2026
This was referenced May 22, 2026
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
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.
Summary
npm-webPR;github-actionsstays as one weekly PRminimumReleaseAge; security alerts still fire immediatelyEffect
A quiet week is now bounded at ~19 PRs (1 web + 1 actions + up to 17 scenarios) instead of one PR per dep. Most weeks should open 2–4 PRs.
When merged, the next renovate cycle will close the ~50 currently-open ungrouped PRs and replace them with the new grouped ones.
Test plan
RENOVATE_FORCEoverriding schedule + PR limits