Skip to content
Hands-on IT IT Drills

Day 4: Grouping, Scheduling, Limiting

Goal: You tame a flood of PRs with groups, time windows, limits, and a minimum maturity period for new releases. · Duration: approx. 120 min · Prerequisite: Day 2

Briefing

  • One PR is created per branch name. Same branch name means same PR – that is exactly what groupName does.
  • schedule (+ timezone) controls when new branches are created. Renovate updates existing PRs outside the window too.
  • prHourlyLimit, prConcurrentLimit, and branchConcurrentLimit cap the volume.
  • minimumReleaseAge lets new releases mature first and sets the status check renovate/stability-days.
  • Whatever is not allowed right now appears in the Dependency Dashboard: “Awaiting Schedule”, “Rate-Limited”, “Pending Status Checks”.
Update found   ─► branch name (groupName?) ─► limit free? ─► in schedule? ─► mature?
                                                  │ no           │ no          │ no
                                                  ▼              ▼             ▼
                                            Rate-Limited  Awaiting Schedule  Pending

Drill 1: The PR flood

Fresh state: recreate shop-api, clone it locally, and load the shortcuts for the day. You only see the GitHub Actions updates with RENOVATE_GITHUB_COM_TOKEN set (Day 0).

source ~/renovate-lab/setup/env.sh
curl -s -o /dev/null -w '%{http_code}\n' -u "$ADMIN" \
  -X DELETE "$FORGEJO/api/v1/repos/shop/shop-api"
git -C ~/renovate-lab/shop-api push -q forgejo:shop/shop-api.git main
mkdir -p ~/renovate-lab/tag04 && cd ~/renovate-lab/tag04
R="$FORGEJO/api/v1/repos/shop/shop-api"
rm -rf shop-api
git clone -q forgejo:shop/shop-api.git
cd shop-api

Expected:

204

Every config change today works the same way: validate, commit, push. Afterwards, one line of curl shows the open PRs with branch and title. Now release all the brakes:

cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended"],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Renovate ohne Limits"
git push -q origin main
renovate shop/shop-api | grep "PR created"
curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[] | "#\(.number) \(.head.ref)  \(.title)"'

Expected:

 INFO: PR created (repository=shop/shop-api, branch=renovate/express-4.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/prettier-3.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/node-20.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/actions-checkout-7.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/actions-setup-node-7.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/express-5.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/node-24.x)
#7 renovate/node-24.x  Update dependency node to v24
#6 renovate/express-5.x  Update dependency express to v5
#5 renovate/actions-setup-node-7.x  Update actions/setup-node action to v7
#4 renovate/actions-checkout-7.x  Update actions/checkout action to v7
#3 renovate/node-20.x  Update Node.js to v20.20.2
#2 renovate/prettier-3.x  Update dependency prettier to v3.9.10
#1 renovate/express-4.x  Update dependency express to v4.22.3

Seven PRs plus the Dashboard for a repo with six dependencies. Scaled up to a real repo with 80 dependencies, nobody wants to review that. Your target versions will be newer – the pattern stays the same.

Which files does PR #7 change?

curl -s -u "$ADMIN" "$R/pulls/7/files" | jq -r '.[].filename'

Expected:

.github/workflows/ci.yml
Dockerfile

Two dependencies are called node (the Docker image and node-version in setup-node). Both major updates result in the branch renovate/node-24.x – and therefore end up in the same PR. That is grouping in its simplest form.

Save your progress? Sign up for free

Drill 2: Groups with groupName

Two rules: all GitHub Actions in one PR, all npm minor and patch updates in another.

cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended"],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0,
  "packageRules": [
    {
      "description": "Alle GitHub Actions in einen PR",
      "matchManagers": ["github-actions"],
      "groupName": "GitHub Actions"
    },
    {
      "description": "npm: Minor und Patch zusammen",
      "matchManagers": ["npm"],
      "matchUpdateTypes": ["minor", "patch"],
      "groupName": "npm non-major"
    }
  ]
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Gruppen per groupName"
git push -q origin main
renovate shop/shop-api | grep -E "PR created|PR updated|Autoclosing"
curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[] | "#\(.number) \(.head.ref)  \(.title)"'
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/major-github-actions") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md

Expected:

 INFO: PR created (repository=shop/shop-api, branch=renovate/npm-non-major)
 INFO: PR created (repository=shop/shop-api, branch=renovate/major-github-actions)
 INFO: PR updated (repository=shop/shop-api, branch=renovate/node-24.x)
 INFO: Autoclosing PR (repository=shop/shop-api)
 INFO: Autoclosing PR (repository=shop/shop-api)
 INFO: Autoclosing PR (repository=shop/shop-api)
 INFO: Autoclosing PR (repository=shop/shop-api)
#10 renovate/major-github-actions  Update GitHub Actions (major)
#9 renovate/npm-non-major  Update npm non-major
#7 renovate/node-24.x  Update Node.js to v24
#6 renovate/express-5.x  Update dependency express to v5
#3 renovate/node-20.x  Update Node.js to v20.20.2
actions/checkout: v3 -> v7
actions/setup-node: v3 -> v7
node: 20 -> 24

Three things stand out:

  • The branch name comes from groupName (lowercase, hyphens) and is renovate/npm-non-major.
  • The Actions group is called major-github-actions. Because of separateMajorMinor: true (default), a group for major updates gets its own branch with major-.
  • Renovate closes the four individual PRs that are now part of groups by itself and deletes their branches. Their title ends with “- autoclosed”.

Warning: A PR closed by a human means “ignore” (Day 1). An “autoclosed” PR, on the other hand, is harmless: Renovate has replaced it.

Save your progress? Sign up for free

Drill 3: Group presets

For standard cases there are ready-made presets. Look inside instead of guessing:

P=~/renovate-lab/tools/node_modules/renovate/dist/config/presets/internal
node -e 'const g = require(process.argv[1]).presets;
console.log(JSON.stringify(g.allNonMajor.packageRules[0]));
console.log("group:recommended:", g.recommended.extends.length,
  "group:monorepos:", g.monorepos.extends.length);' "$P/group.preset.js"

Expected:

{"groupName":"all non-major dependencies","groupSlug":"all-minor-patch",
"matchPackageNames":["*"],"matchUpdateTypes":["minor","patch"]}
group:recommended: 55 group:monorepos: 468
  • group:allNonMajor groups all minor and patch updates, across all managers. groupSlug overrides the branch name.
  • group:monorepos (468 groups) and group:recommended (55 groups) are already part of config:recommended. Packages from a monorepo such as @vitest/* thus automatically end up in one PR.

Replace the npm rule with the preset:

cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended", "group:allNonMajor"],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0,
  "packageRules": [
    {
      "description": "Alle GitHub Actions in einen PR",
      "matchManagers": ["github-actions"],
      "groupName": "GitHub Actions"
    }
  ]
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Gruppen per Preset"
git push -q origin main
renovate shop/shop-api | grep -E "PR created|Autoclosing"
curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[] | "#\(.number) \(.head.ref)  \(.title)"'
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/all-minor-patch") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md

Expected:

 INFO: PR created (repository=shop/shop-api, branch=renovate/all-minor-patch)
 INFO: Autoclosing PR (repository=shop/shop-api)
 INFO: Autoclosing PR (repository=shop/shop-api)
#11 renovate/all-minor-patch  Update all non-major dependencies
#10 renovate/major-github-actions  Update GitHub Actions (major)
#7 renovate/node-24.x  Update Node.js to v24
#6 renovate/express-5.x  Update dependency express to v5
express: 4.18.2 -> 4.22.3
node: 20.11.0-alpine -> 20.20.2-alpine
prettier: 3.0.0 -> 3.9.10

The Docker image node is now included as well – the preset does not care about the manager. Of seven PRs, four are left: one collective PR for the small stuff, one PR per major.

Save your progress? Sign up for free

Drill 4: Separating majors and patches

Three switches control how finely Renovate splits the updates of a package:

Option Default Effect with true
separateMajorMinor true major separate from minor/patch
separateMultipleMajor false each major jump gets its own PR (v4, v5, v6 …)
separateMinorPatch false patch separate from minor

Try out the two non-defaults:

jq '. + {"separateMultipleMajor": true, "separateMinorPatch": true}' renovate.json \
  > tmp.json && mv tmp.json renovate.json
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Majors und Patches trennen"
git push -q origin main
renovate shop/shop-api | grep -c "PR created"
curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[] | "#\(.number) \(.head.ref)  \(.title)"'
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/patch-all-minor-patch") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/major-5-github-actions") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md

Expected:

8
#19 renovate/node-22.x  Update Node.js to v22
#18 renovate/major-7-github-actions  Update GitHub Actions to v7
#17 renovate/major-6-github-actions  Update GitHub Actions to v6
#16 renovate/major-5-github-actions  Update GitHub Actions to v5
#15 renovate/major-4-github-actions  Update GitHub Actions to v4
#14 renovate/major-24-github-actions  Update dependency node to v24
#13 renovate/major-22-github-actions  Update dependency node to v22
#12 renovate/patch-all-minor-patch  Update all non-major dependencies (patch)
#11 renovate/all-minor-patch  Update all non-major dependencies (minor)
#7 renovate/node-24.x  Update Node.js to v24
#6 renovate/express-5.x  Update dependency express to v5
express: 4.18.2 -> 4.18.3
node: 20.11.0-alpine -> 20.11.1-alpine
prettier: 3.0.0 -> 3.0.3
actions/checkout: v3 -> v5
actions/setup-node: v3 -> v5

Eleven PRs – the flood is back. Groups get the prefixes patch- and major-<version>-. separateMultipleMajor is only worth it if you deliberately want to migrate step by step, for example across several Node LTS versions. separateMinorPatch makes sense if patches should be merged automatically (Day 5), but minors should not.

Save your progress? Sign up for free

Drill 5: Limits

For limits you need many individual updates and a clean hourly count. So: reset the repo, without groups.

cd ~/renovate-lab/tag04
curl -s -o /dev/null -w '%{http_code}\n' -u "$ADMIN" \
  -X DELETE "$FORGEJO/api/v1/repos/shop/shop-api"
git -C ~/renovate-lab/shop-api push -q forgejo:shop/shop-api.git main
rm -rf shop-api
git clone -q forgejo:shop/shop-api.git
cd shop-api
cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended"],
  "prHourlyLimit": 2,
  "prConcurrentLimit": 3
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Limits setzen"
git push -q origin main
renovate shop/shop-api | grep "PR created"
curl -s -u "$ADMIN" "$R/issues?type=issues" \
  | jq -r '.[] | select(.title == "Dependency Dashboard") | .body' > dashboard.md
grep -oE 'unlimit-branch=[^ ]+|create-all-rate-limited-prs' dashboard.md

Expected (shortened):

204
 INFO: PR created (repository=shop/shop-api, branch=renovate/express-4.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/prettier-3.x)
unlimit-branch=renovate/node-20.x
unlimit-branch=renovate/actions-checkout-7.x
unlimit-branch=renovate/actions-setup-node-7.x
unlimit-branch=renovate/express-5.x
unlimit-branch=renovate/node-24.x
create-all-rate-limited-prs

Two PRs per hour. A second run in the same hour brings nothing – the debug log says why:

LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -oE "Hourly PRs limit reached|Open PR Count.*Hourly PR Count: [0-9]+" \
  ../debug.log | sort | uniq -c

Expected:

   5 Hourly PRs limit reached
   7 Open PR Count: 2, Existing Branch Count: 2, Hourly PR Count: 2

prHourlyLimit counts PRs created since the start of the current hour. Now limit only the total number:

jq '.prHourlyLimit = 0' renovate.json > tmp.json && mv tmp.json renovate.json
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Kein Stundenlimit"
git push -q origin main
LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -oE "INFO: PR created|[A-Za-z]+ limit reached" ../debug.log | sort | uniq -c

Expected:

   4 Branches limit reached
   1 INFO: PR created

Three PRs, then “Branches limit reached” – not “PRs”. branchConcurrentLimit is empty by default and then inherits the value of prConcurrentLimit. Allow more branches than PRs:

jq '.branchConcurrentLimit = 5' renovate.json > tmp.json && mv tmp.json renovate.json
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Mehr Branches als PRs"
git push -q origin main
LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -oE "INFO: Branch created|[A-Za-z]+ limit reached" ../debug.log | sort | uniq -c
curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[] | "#\(.number) \(.head.ref)  \(.title)"'

Expected:

   2 Branches limit reached
   2 ConcurrentPRs limit reached
   2 INFO: Branch created
#4 renovate/node-20.x  Update Node.js to v20.20.2
#2 renovate/prettier-3.x  Update dependency prettier to v3.9.10
#1 renovate/express-4.x  Update dependency express to v4.22.3

Five branches, three PRs. The two branches without a PR stay under “Rate-Limited” and get their PR as soon as one of the three is merged. Useful with branch automerge (Day 5): the branch already runs through CI without creating review load. If you do not want to wait, tick unlimit-branch in the Dashboard – the checkboxes bypass all limits, including prHourlyLimit (Day 14).

Option Default counts
prHourlyLimit 2 PRs created in the current hour
prConcurrentLimit 10 open Renovate PRs
branchConcurrentLimit empty (= PR limit) existing Renovate branches
commitHourlyLimit 0 commits per hour (0 = no limit)

Save your progress? Sign up for free

Drill 6: Time windows with schedule

On every run, Renovate checks whether “now” is within the window. Without timezone, UTC applies. Our window: Mondays from 0:00 to 5:59 Berlin time. If you happen to be doing the drill early on a Monday, use Tuesday (* 0-5 * * 2).

cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended"],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0,
  "timezone": "Europe/Berlin",
  "schedule": ["* 0-5 * * 1"]
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Nur montags frueh"
git push -q origin main
LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -E "Human-readable|Checking schedule\(" ../debug.log | head -2 | cut -c1-88
grep -oE "Skipping (PR|branch) creation[a-z ]*[a-z]|will update if necessary" \
  ../debug.log | sort | uniq -c

Expected (shortened):

DEBUG: Checking schedule(schedule=* 0-5 * * 1, tz=Europe/Berlin, now=2026-10-12T16:11:27
DEBUG: Human-readable summary for cron:: Every minute, between 12:00 AM and 05:59 AM, on
   2 Skipping branch creation as not within schedule
   2 Skipping PR creation out of schedule
   3 will update if necessary

Three cases: existing PRs keep being maintained, branches without a PR do not get one, and new branches are not created. In the Dashboard:

curl -s -u "$ADMIN" "$R/issues?type=issues" \
  | jq -r '.[] | select(.title == "Dependency Dashboard") | .body' > dashboard.md
grep -oE 'unschedule-branch=[^ ]+' dashboard.md

Expected:

unschedule-branch=renovate/actions-checkout-7.x
unschedule-branch=renovate/actions-setup-node-7.x
unschedule-branch=renovate/express-5.x
unschedule-branch=renovate/node-24.x

Prove “will update if necessary”: on main, change the line that PR #4 touches. The branch then has a conflict and must be rebuilt.

sed -i.bak 's/node:20.11.0-alpine/node:20.12.0-alpine/' Dockerfile && rm Dockerfile.bak
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Node 20.12 von Hand"
git push -q origin main
LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -E "INFO: (Branch|PR)|Branch is conflicted" ../debug.log | cut -c1-88
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/node-20.x") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md

Expected:

DEBUG: Branch is conflicted (repository=shop/shop-api, branch=renovate/node-20.x)
 INFO: Branch updated (repository=shop/shop-api, branch=renovate/node-20.x)
 INFO: PR updated (repository=shop/shop-api, branch=renovate/node-20.x)
node: 20.12.0-alpine -> 20.20.2-alpine

Outside the window, but updated anyway. If you want Renovate to really keep its hands off, set updateNotScheduled: false (preset :noUnscheduledUpdates):

jq '.updateNotScheduled = false' renovate.json > tmp.json && mv tmp.json renovate.json
sed -i.bak 's/node:20.12.0-alpine/node:20.13.0-alpine/' Dockerfile && rm Dockerfile.bak
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Ausserhalb des Fensters nichts anfassen"
git push -q origin main
LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -oE "INFO: (Branch|PR) updated|Skipping branch update[a-z ]*[a-z]" ../debug.log \
  | sort | uniq -c
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/node-20.x") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md

Expected:

   5 Skipping branch update as not within schedule
node: 20.12.0-alpine -> 20.20.2-alpine

PR #4 stays outdated and conflicted until the window opens. For most teams, the default (true) is the better choice.

On syntax: Renovate 44 accepts cron (recommended) and still the old text form. The schedule:* presets provide ready-made windows.

cd ~/renovate-lab/tag04
node -e 'const s = require(process.argv[1]).presets;
for (const k of ["weekly", "earlyMondays", "nonOfficeHours"])
  console.log(k, JSON.stringify(s[k].schedule ?? s[k].extends));' \
  "$P/schedule.preset.js"
for s in "before 6am on monday" "before 6am on mondai" "0 0-5 * * 1"; do
  echo "{\"schedule\": [\"$s\"]}" > s.json
  renovate-config-validator --no-global s.json 2>&1 | grep -E "success|message"
done
rm s.json; cd shop-api

Expected (shortened):

weekly ["schedule:earlyMondays"]
earlyMondays ["* 0-3 * * 1"]
nonOfficeHours ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
 INFO: Config validated successfully against 1 file(s)
           "message": "Invalid schedule: `Invalid schedule: Failed to parse \"before
           "message": "Invalid schedule: `Invalid schedule: \"0 0-5 * * 1\" has cron

Warning: The minute must be *. Renovate does not run to the minute; 0 0-5 * * 1 would almost never match and is therefore rejected. A typo in the text form is only caught by the validator – cron is more robust.

Save your progress? Sign up for free

Drill 7: Maturity period with minimumReleaseAge

Brand-new releases are more often broken or even malicious (Day 12). minimumReleaseAge waits until a release is old enough. Schedule out, group in:

cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended", "group:allNonMajor"],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0,
  "minimumReleaseAge": "3 days"
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Neue Releases 3 Tage reifen lassen"
git push -q origin main
renovate shop/shop-api > /dev/null
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/all-minor-patch") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md
SHA=$(curl -s -u "$ADMIN" "$R/branches/renovate/all-minor-patch" | jq -r .commit.id)
curl -s -u "$ADMIN" "$R/commits/$SHA/status" \
  | jq -r '.statuses[] | "\(.context): \(.status) – \(.description)"'
npm view prettier time --json | jq -r '."3.9.9", ."3.9.10"'

Expected:

express: 4.18.2 -> 4.22.3
prettier: 3.0.0 -> 3.9.9
renovate/stability-days: success – Updates have met minimum release age requirement
2026-09-23T06:31:34.693Z
2026-10-10T08:35:28.472Z

On the test day, prettier 3.9.10 was only two days old. Renovate therefore takes the newest mature version 3.9.9 (internalChecksFilter: "strict", default) and sets the status check renovate/stability-days to green. For you, it will hit other packages.

And where is the Docker image node? It is missing from the group:

LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep -A3 "as pending" ../debug.log | cut -c1-88 | head -4

Expected:

DEBUG: Marking 20 release(s) as pending, as they do not have a releaseTimestamp and we'r
       "depName": "node",
       "versions": [
         "20.20.2",

Warning: In the lab, the Docker datasource returned no publication time for node. With the default minimumReleaseAgeBehaviour: "timestamp-required", such an update counts as never mature and silently disappears from the group. Drill 8 makes this visible.

Save your progress? Sign up for free

Drill 8: Making pending visible

First the counter-check: with internalChecksFilter: "none", Renovate takes the newest version immediately and reports the missing maturity only via a status check.

jq '.internalChecksFilter = "none"' renovate.json > tmp.json \
  && mv tmp.json renovate.json
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Neueste Version sofort"
git push -q origin main
renovate shop/shop-api | grep -E "WARN|PR updated" | cut -c1-88
curl -s -u "$ADMIN" "$R/pulls" \
  | jq -r '.[] | select(.head.ref == "renovate/all-minor-patch") | .body' > pr.md
sed -nE 's/^\| \[([^]]+)\].*`([^`]+)` → `([^`]+)`.*/\1: \2 -> \3/p' pr.md
SHA=$(curl -s -u "$ADMIN" "$R/branches/renovate/all-minor-patch" | jq -r .commit.id)
curl -s -u "$ADMIN" "$R/commits/$SHA/status" \
  | jq -r '.statuses[] | "\(.context): \(.status) – \(.description)"'

Expected:

 WARN: npm `--before` could not be enforced because existing locked packages were publis
 INFO: PR updated (repository=shop/shop-api, branch=renovate/all-minor-patch)
 INFO: PR updated (repository=shop/shop-api, branch=renovate/node-24.x)
express: 4.18.2 -> 4.22.3
node: 20.13.0-alpine -> 20.20.2-alpine
prettier: 3.0.0 -> 3.9.10
renovate/stability-days: pending – Updates have not met minimum release age requirement

The status is pending. If it is registered as a required check in branch protection, it blocks the merge until the maturity period is over – Renovate sets it to success on a later run. Back to strict, with Docker images in a group of their own:

cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended", "group:allNonMajor"],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0,
  "minimumReleaseAge": "3 days",
  "packageRules": [
    {
      "matchDatasources": ["docker"],
      "groupName": "Docker-Images"
    }
  ]
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Docker-Images eigene Gruppe"
git push -q origin main
LOG_LEVEL=debug renovate shop/shop-api > ../debug.log 2>&1
grep "internalChecksFilter was not met" ../debug.log | cut -c8-88
curl -s -u "$ADMIN" "$R/issues?type=issues" \
  | jq -r '.[] | select(.title == "Dependency Dashboard") | .body' > dashboard.md
grep -oE 'unpend-branch=[^ ]+' dashboard.md

Expected:

Branch renovate/docker-images creation is disabled because internalChecksFilter w
Branch renovate/major-docker-images creation is disabled because internalChecksFi
unpend-branch=renovate/docker-images
unpend-branch=renovate/major-docker-images

Now the gap shows up in the Dashboard. If you trust the registry without timestamps, allow the updates specifically for Docker:

jq '.packageRules[0].minimumReleaseAgeBehaviour = "timestamp-optional"' renovate.json \
  > tmp.json && mv tmp.json renovate.json
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Docker ohne Zeitstempel erlauben"
git push -q origin main
renovate shop/shop-api | grep -E "WARN|PR created" | cut -c1-88

Expected:

 WARN: Some release(s) did not have a releaseTimestamp, but as we're running with minimu
 WARN: Some upgrade(s) did not have a releaseTimestamp, but as we're running with minimu
 INFO: PR created (repository=shop/shop-api, branch=renovate/docker-images)
 INFO: PR created (repository=shop/shop-api, branch=renovate/major-docker-images)

The sections of the Dashboard at a glance:

Section Cause Checkbox forces
Awaiting Schedule outside of schedule unschedule-branch
Rate-Limited prHourlyLimit, prConcurrentLimit, branchConcurrentLimit unlimit-branch
Pending Status Checks minimumReleaseAge not met unpend-branch
Pending Approval dependencyDashboardApproval (Day 14) approve-branch

Save your progress? Sign up for free

Checkpoint

The config is valid and contains the collective preset and the maturity period:

cd ~/renovate-lab/tag04/shop-api
R="$FORGEJO/api/v1/repos/shop/shop-api"
renovate-config-validator --no-global renovate.json >/dev/null 2>&1; echo "Exit: $?"
jq -c '.extends' renovate.json
jq -r '.minimumReleaseAge' renovate.json

Expected:

R04_KP1

The collective PR and the Docker group are open:

curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[].head.ref'

Expected:

R04_KP2

The collective PR has passed the maturity test:

SHA=$(curl -s -u "$ADMIN" "$R/branches/renovate/all-minor-patch" | jq -r .commit.id)
curl -s -u "$ADMIN" "$R/commits/$SHA/status" | jq -r '.statuses[].context'
curl -s -u "$ADMIN" "$R/commits/$SHA/status" | jq -r '.statuses[].status'

Expected:

renovate/stability-days
success

Challenge

Build a weekly plan for a fresh shop-api: all minor and patch updates come together, but only on Mondays before 6 a.m. Berlin time. Majors come individually and at any time. Never more than three Renovate PRs are open.

Hint: schedule also works inside a packageRule.

Solution

cd ~/renovate-lab/tag04
curl -s -o /dev/null -w '%{http_code}\n' -u "$ADMIN" \
  -X DELETE "$FORGEJO/api/v1/repos/shop/shop-api"
git -C ~/renovate-lab/shop-api push -q forgejo:shop/shop-api.git main
rm -rf shop-api
git clone -q forgejo:shop/shop-api.git
cd shop-api
cat > renovate.json <<'EOF'
{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended", "group:allNonMajor"],
  "timezone": "Europe/Berlin",
  "prHourlyLimit": 0,
  "prConcurrentLimit": 3,
  "packageRules": [
    {
      "description": "Non-Major nur montags vor 6 Uhr",
      "matchUpdateTypes": ["minor", "patch"],
      "schedule": ["* 0-5 * * 1"]
    }
  ]
}
EOF
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Wochenplan"
git push -q origin main
renovate shop/shop-api | grep "PR created"
curl -s -u "$ADMIN" "$R/issues?type=issues" \
  | jq -r '.[] | select(.title == "Dependency Dashboard") | .body' > dashboard.md
grep -oE '^## [A-Za-z -]+|(unschedule|unlimit)-branch=[^ ]+' dashboard.md

Expected (outside the Monday window):

204
 INFO: PR created (repository=shop/shop-api, branch=renovate/actions-checkout-7.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/actions-setup-node-7.x)
 INFO: PR created (repository=shop/shop-api, branch=renovate/express-5.x)
## Awaiting Schedule
unschedule-branch=renovate/all-minor-patch
## Rate-Limited
unlimit-branch=renovate/node-24.x
## Open
## Detected Dependencies

The majors are there individually, the collective PR waits for Monday, and the fourth major is queued because of the limit. Separate majors are the default (separateMajorMinor: true); you do not need to do anything for that. Early on Monday, the collective PR is still only created if one of the three slots is free – schedule and limit work together.

Save your progress? Sign up for free

Enterprise Note

  • Define groups, windows, and limits centrally as an org preset (Day 11). Teams override only if they have a reason.
  • Plan the schedule window to match the Renovate cadence (Day 10). An hourly CronJob needs a window of at least one hour, otherwise it never hits it.
  • prConcurrentLimit caps per repo, not per organization. For CI load, what counts is the sum across all repos.
  • minimumReleaseAge is a supply chain measure (Day 12). Determine which datasources do not provide timestamps and how to deal with that.
  • Security updates (vulnerabilityAlerts) ignore schedule and limits by default. That is intended, but needs to be explained in change management.