Day 2: Understanding Configuration
Goal: You read, check, and test a Renovate configuration before it takes effect, and control individual updates precisely with
packageRules. · Duration: approx. 90 min · Prerequisite: Day 1
Briefing
- The repo config is a file in the default branch. Renovate takes the first one it finds from a fixed list of locations and silently ignores all others.
extendsloads presets from left to right. Later ones override earlier ones, and your own keys in the file override all presets.- All
packageRulesare checked. Every matching rule is applied, and a later one overrides the same option of an earlier one. - Checking without risk:
renovate-config-validator,--dry-run,--platform=local.
Renovate defaults ─► extends[0] ─► extends[1] ─► … ─► your own keys
│
per update: packageRules[0] ─► packageRules[1] ─► … ─────┘ (only if all
match* fields match)
Drill 1: Starting point
You start with a fresh shop-api and put the config
directly on main. If there is a config in the default
branch, the repo counts as onboarded and there is no onboarding PR.
source ~/renovate-lab/setup/env.sh
export RENOVATE_GITHUB_COM_TOKEN=$(gh auth token) # optional, see Day 0
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/tag02 && cd ~/renovate-lab/tag02
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"]
}
EOF
git add renovate.json
git commit -qm "Renovate-Konfiguration"
git push -q
git log --onelineExpected (hashes differ):
204
2340402 Renovate-Konfiguration
a8b2fdb Initialer Stand
The DELETE removes the repo along with the PRs and
issues from Day 1. The commit messages are deliberately chosen without
the type: text pattern; Drill 7 shows why.
Save your progress? Sign up for free
Drill 2: config:recommended broken down
Presets are not magic, but JavaScript objects in the installed package. Read the definition where your Renovate version actually takes it from.
P=~/renovate-lab/tools/node_modules/renovate/dist/config/presets/internal
awk '/^\trecommended: \{/,/\]/' $P/config.preset.js | expand -t2 | cut -c1-80
awk '/^\tdependencyDashboard: \{/,/\}/' $P/default.preset.js | expand -t2Expected:
recommended: {
description: "Recommended configuration for most users. It does not matter w
extends: [
":dependencyDashboard",
":semanticPrefixFixDepsChoreOthers",
":ignoreModulesAndTests",
"group:monorepos",
"group:recommended",
"mergeConfidence:age-confidence-badges",
"replacements:all",
"workarounds:all",
"helpers:forgejoDigestChangelogs",
"helpers:giteaDigestChangelogs",
"helpers:githubDigestChangelogs",
"helpers:gitlabDigestChangelogs",
"helpers:goXPackagesChangelogLink",
"helpers:goXPackagesNameLink",
"helpers:renovateChangelog"
]
dependencyDashboard: {
dependencyDashboard: true,
description: "Enable Renovate Dependency Dashboard creation."
},
Presets without a prefix (:name) live in
default.preset.js, group: in
group.preset.js, and so on. What remains of them after
resolution is shown by --print-config. You do the
comparison with an empty config locally: changing
renovate.json in the working directory is enough, no commit
needed.
LOG_FORMAT=json renovate --platform=local --dry-run=extract --print-config=true \
> print.json 2>&1
jq -c 'select(.config.packageRules) | .config.dependencyDashboard' print.json
jq -c 'select(.config.packageRules) | .config.packageRules | length' print.jsonExpected:
true
729
select(.config.packageRules) finds the one line in the
JSON log with the resolved config; after it comes the field you are
interested in. Now with an empty config:
echo '{}' > renovate.json
LOG_FORMAT=json renovate --platform=local --dry-run=extract --print-config=true \
> print.json 2>&1
jq -c 'select(.config.packageRules) | .config.dependencyDashboard' print.json
jq -c 'select(.config.packageRules) | .config.packageRules | length' print.json
git checkout -q renovate.jsonExpected:
false
0
729 rules hide behind one line, counted live: 523 with
groupName (from group:*), 155 replacements
(replacements:all), the rest from
workarounds:*, helpers:*, and
:semanticPrefixFixDepsChoreOthers.
| Building block | Effect |
|---|---|
:dependencyDashboard |
“Dependency Dashboard” issue (Day 14) |
:semanticPrefixFixDepsChoreOthers |
fix for dependencies, otherwise
chore – only with semantic commits |
:ignoreModulesAndTests |
ignorePaths for node_modules,
vendor, test, examples … |
group:monorepos, group:recommended |
well-known package families end up in one PR (Day 4) |
replacements:all |
PRs for renamed or replaced packages |
workarounds:all |
fixes for packages with odd versions |
mergeConfidence:age-confidence-badges |
Age/Confidence columns in the PR text |
helpers:*Changelogs, helpers:*Link |
better changelog and source links |
Warning:
--print-config shop/shop-apifails with “Invalid boolean value: expected ‘true’ or ‘false’, but got ‘shop/shop-api’”. The option swallows the next argument. Write--print-config=true.
Save your progress? Sign up for free
Drill 3: extends – order and overriding
Four variants, the same tool.
:disableDependencyDashboard sets
dependencyDashboard: false, :label(…) is a
preset with a parameter.
for c in '{"extends":["config:recommended",":disableDependencyDashboard"]}' \
'{"extends":[":disableDependencyDashboard","config:recommended"]}' \
'{"extends":["config:recommended",":label(deps)"]}' \
'{"extends":[":label(deps)"],"labels":["eigenes"],"dependencyDashboard":true}'; do
echo "$c" > renovate.json
LOG_FORMAT=json renovate --platform=local --dry-run=extract --print-config=true \
> print.json 2>&1
jq -c 'select(.config.packageRules) | .config | {dependencyDashboard, labels}' \
print.json
done
git checkout -q renovate.jsonExpected:
{"dependencyDashboard":false,"labels":[]}
{"dependencyDashboard":true,"labels":[]}
{"dependencyDashboard":true,"labels":["deps"]}
{"dependencyDashboard":true,"labels":["eigenes"]}
Line 2 is the trap: config:recommended comes last and
turns the Dashboard back on. Line 4 shows the rule “file beats preset”.
Arrays like labels are replaced in the process, not
extended.
Save your progress? Sign up for free
Drill 4: Config locations and their priority
--platform=local reads only files that Git knows about
(git ls-files). A git add is enough; you do
not have to commit. You create all candidates and remove them from the
index one by one.
cd ~/renovate-lab/tag02 && rm -rf prio && cp -R shop-api prio && cd prio
mkdir -p .github .gitlab .forgejo
for f in renovate.json5 .github/renovate.json .gitlab/renovate.json \
.renovaterc .forgejo/renovate.json; do echo '{}' > $f; done
git add -A
for f in renovate.json renovate.json5 .github/renovate.json .gitlab/renovate.json \
.renovaterc .forgejo/renovate.json; do
printf '%-24s -> ' "$f"
LOG_LEVEL=debug renovate --platform=local --dry-run=extract 2>&1 \
| grep -oE "Found .* config file|No renovate config file found"
git rm -q --cached $f
doneExpected:
renovate.json -> Found renovate.json config file
renovate.json5 -> Found renovate.json5 config file
.github/renovate.json -> Found .github/renovate.json config file
.gitlab/renovate.json -> Found .gitlab/renovate.json config file
.renovaterc -> Found .renovaterc config file
.forgejo/renovate.json -> No renovate config file found
No renovate config file found
The complete list in 44.153.1 (from
dist/config/app-strings.js): renovate.json,
renovate.jsonc, renovate.json5, the same under
.github/ and .gitlab/,
.renovaterc, .renovaterc.json,
.renovaterc.jsonc, .renovaterc.json5, and
finally the renovate key in package.json.
jq '. + {renovate: {extends: ["config:recommended"]}}' package.json > p.json
mv p.json package.json
LOG_LEVEL=debug renovate --platform=local --dry-run=extract 2>&1 \
| grep -E "Found .* config file|deprecated" | cut -c1-80
cd ~/renovate-lab/tag02 && rm -rf prioExpected:
WARN: Using package.json for Renovate config is deprecated - please use a dedic
DEBUG: Found package.json config file (repository=local)
"⚠️ WARN: Using package.json for Renovate config is deprecated - please
Warning:
.github/renovate.jsonand.gitlab/renovate.jsonapply on every platform, including Forgejo..forgejo/renovate.json, on the other hand, is not read by 44.153.1, not even withRENOVATE_PLATFORM=forgejo(checked live: “Repo is not onboarded”). If there are two configs in the repo, the first one in the list wins – without a warning.
Save your progress? Sign up for free
Drill 5: JSON5 and renovate-config-validator
JSON5 allows comments, keys without quotes, and trailing commas. Ideal for explaining rules. First a deliberately broken file:
mkdir -p ~/renovate-lab/tag02/kaputt && cd ~/renovate-lab/tag02/kaputt
cat > renovate.json5 <<'EOF'
{
// Deliberately broken
extends: ["config:recommended"],
prHourlyLimt: 4,
packageRules: [
{
matchPackagePatterns: ["^@types/"],
labels: ["types"],
},
],
}
EOF
renovate-config-validator 2>&1 | grep -E '^ ?[A-Z]+:|^ +[-+] |"message"'
echo "exit=${PIPESTATUS[0]}"Expected:
INFO: Validating renovate.json5
WARN: Config migration necessary
WARN: Config migration diff:
- "matchPackagePatterns": [
- "^@types/"
- ],
+ ],
+ "matchPackageNames": [
+ "/^@types//"
ERROR: Found errors in configuration
"message": "Invalid configuration option: prHourlyLimt"
exit=1
Two findings: the typo is an error, the deprecated option only a
warning with a migration suggestion (/…/ means regex, Drill
7). Without arguments, the validator checks all locations from Drill 4
in the current directory. Now fix the typo:
sed -i.bak 's/prHourlyLimt/prHourlyLimit/' renovate.json5 && rm renovate.json5.bak
renovate-config-validator >/dev/null 2>&1; echo "normal: exit=$?"
renovate-config-validator --strict >/dev/null 2>&1; echo "--strict: exit=$?"
echo '{"extends": ["config:recomended"]}' > tippfehler.json
renovate-config-validator --no-global tippfehler.json; echo "exit=$?"Expected:
normal: exit=0
--strict: exit=1
INFO: Validating tippfehler.json as repo config
INFO: Config validated successfully against 1 file(s)
exit=0
--strict turns a required migration into an error –
exactly right for CI. If you pass file names, the validator checks them
as a global config. --no-global switches
to repo config. It does not see the preset typo
config:recomended, because it does not resolve presets.
Only a real run can do that:
mkdir -p ~/renovate-lab/tag02/preset-test && cd ~/renovate-lab/tag02/preset-test
git init -q && cp ../kaputt/tippfehler.json renovate.json && git add renovate.json
renovate --platform=local --dry-run=extract 2>&1 | grep -E "validationError|DRY-RUN"
cd ~/renovate-lab/tag02 && rm -rf preset-testExpected:
"validationError": "Cannot find preset's package (config:recomended)"
"validationError": "Cannot find preset's package (config:recomended)",
INFO: DRY-RUN: Would ensure configuration error issue (repository=local)
"validationError": "Cannot find preset's package (config:recomended)",
On Forgejo this would be an issue “Action Required: Fix Renovate Configuration”, and Renovate stops creating PRs until the config is fixed.
Save your progress? Sign up for free
Drill 6: –dry-run=extract|lookup|full and –platform=local
Three stages, each does one step more. The time breakdown in the debug log shows what really happened.
cd ~/renovate-lab/tag02
for m in extract lookup full; do
LOG_LEVEL=debug renovate --dry-run=$m shop/shop-api > dry-$m.log 2>&1
printf '%-8s %s DRY-RUN-Zeilen: %s\n' $m \
"$(grep -o '"lookup": [0-9]*, "update": [0-9]*' dry-$m.log)" \
"$(grep -c '^ INFO: DRY-RUN' dry-$m.log)"
done
grep -h '^ INFO: DRY-RUN' dry-full.log | cut -c1-70 | head -3Expected (milliseconds vary):
extract "lookup": 0, "update": 0 DRY-RUN-Zeilen: 0
lookup "lookup": 4860, "update": 0 DRY-RUN-Zeilen: 0
full "lookup": 356, "update": 3368 DRY-RUN-Zeilen: 9
INFO: DRY-RUN: Would commit files to branch renovate/express-4.x. See
INFO: DRY-RUN: Would commit files to branch renovate/prettier-3.x. Se
INFO: DRY-RUN: Would commit files to branch renovate/node-20.x. See d
| Mode | Queries registries | Builds branches locally | Writes to Forgejo |
|---|---|---|---|
extract |
no | no | no |
lookup |
yes | no | no |
full |
yes | yes (incl. lockfile) | no |
All three need Forgejo for cloning. --platform=local
works with no platform at all and takes the current directory:
cd ~/renovate-lab/tag02/shop-api
renovate --platform=local 2>&1 | sed -n '/extraction complete/,/total/p'
LOG_LEVEL=debug renovate --platform=local --dry-run=full 2>&1 \
| grep -o '"lookup": [0-9]*, "update": [0-9]*'Expected:
INFO: Dependency extraction complete (repository=local, baseBranch=)
"stats": {
"managers": {
"dockerfile": {"fileCount": 1, "depCount": 1},
"github-actions": {"fileCount": 1, "depCount": 4},
"npm": {"fileCount": 1, "depCount": 3}
},
"total": {"fileCount": 3, "depCount": 8}
"lookup": 293, "update": 0
local never writes: without an option it runs as
lookup, and even --dry-run=full ends with
"update": 0. No token, no clone, no issues. Good for
pre-commit checks and for trying out a config before you push it.
Save your progress? Sign up for free
Drill 7: packageRules with a visible effect
Now every matcher gets a rule whose effect you can see on the PR.
Forgejo only attaches labels that exist in the repo (or in the org), so
create them first. The config is also available at
~/renovate-lab/code/tag02/renovate.json5.
for l in npm:1d76db web:0e8a16 ci:5319e7 docker:0052cc major:d93f0b; do
curl -sf -u "$ADMIN" -H 'Content-Type: application/json' -X POST \
"$FORGEJO/api/v1/repos/shop/shop-api/labels" \
-d "{\"name\":\"${l%%:*}\",\"color\":\"#${l##*:}\"}" | jq -r .name
done
cd ~/renovate-lab/tag02/shop-api && git rm -q renovate.json
cat > renovate.json5 <<'EOF'
{
$schema: "https://docs.renovatebot.com/renovate-schema.json",
extends: ["config:recommended"],
prHourlyLimit: 0, // Lab: alle PRs in einem Lauf (Details: Tag 4)
packageRules: [
{
description: "Manager: alle npm-Updates",
matchManagers: ["npm"],
labels: ["npm"],
},
{
description: "exakter Name: express bekommt zusätzlich web",
matchPackageNames: ["express"],
addLabels: ["web"],
},
{
description: "Glob: alle Actions der Org actions",
matchPackageNames: ["actions/*"],
labels: ["ci"],
},
{
description: "Regex + Datei + Datasource: Basis-Image im Dockerfile",
matchFileNames: ["Dockerfile"],
matchDatasources: ["docker"],
matchPackageNames: ["/^node$/"],
labels: ["docker"],
},
{
description: "Majors außer Actions: überschreibt labels von oben",
matchUpdateTypes: ["major"],
matchPackageNames: ["!actions/*"],
labels: ["major"],
},
{
description: "devDependencies vorerst aus",
matchDepTypes: ["devDependencies"],
enabled: false,
},
],
}
EOF
renovate-config-validator --strict && git add -A \
&& git commit -qm "packageRules als JSON5" && git push -q
renovate shop/shop-api 2>&1 | grep -cE "PR created"
curl -s -u "$ADMIN" "$FORGEJO/api/v1/repos/shop/shop-api/pulls?state=open" \
| jq -r '.[] | "#\(.number) [\([.labels[].name]|join(","))] \(.title)"'Expected (your target versions will be newer):
npm
web
ci
docker
major
INFO: Validating renovate.json5
INFO: Config validated successfully against 1 file(s)
6
#6 [ci,major] Update dependency node to v24
#5 [major,web] Update dependency express to v5
#4 [ci] Update actions/setup-node action to v7
#3 [ci] Update actions/checkout action to v7
#2 [docker] Update Node.js to v20.20.2
#1 [npm,web] Update dependency express to v4.22.3
This is how you read the result:
- #1 matches rule 1 (
npm) and rule 2 (addLabelsaddsweb). - #5 additionally matches rule 5.
labelsis not mergeable, somajorreplacesnpm.addLabelsis mergeable, sowebstays. - #3/#4 stay
cibecause the negation!actions/*excludes them from rule 5. - #6 bundles
nodein theDockerfileandnode-versioninci.yml(same branchrenovate/node-24.x). The labels of all updates in the branch are merged. Where doescicome from? The matcher checks thepackageName, not the displayed name. - prettier is missing; rule 6 turned it off.
- If
RENOVATE_GITHUB_COM_TOKENis missing, Renovate skips the Actions and the Node version in the workflow (github-token-required). Then #3, #4, and theci.ymlhalf of #6 are missing.
LOG_LEVEL=debug renovate --dry-run=lookup shop/shop-api 2>&1 \
| grep -E '"packageName": "actions/node-versions"|prettier, is disabled'Expected:
DEBUG: Dependency: prettier, is disabled (repository=shop/shop-api)
"packageName": "actions/node-versions",
The matchers at a glance:
| Matcher | checks | Example |
|---|---|---|
matchPackageNames |
package name: exact, glob, /regex/, !
negation |
["actions/*", "!actions/cache"] |
matchUpdateTypes |
major, minor, patch,
pin, digest … |
["major"] |
matchManagers / matchDatasources |
manager / datasource | ["npm"] / ["docker"] |
matchDepTypes / matchFileNames |
section / file (glob) | ["devDependencies"] / ["Dockerfile"] |
Within a rule, all matchers must match (AND); within
a list, one is enough (OR). Globs are case-insensitive, and
* alone matches everything.
Tip: Look at the PR titles after you have pushed a few commits like
fix: ….semanticCommitsis set toauto: if messages following thetype: textpattern dominate the most recent commits onmain, Renovate writesfix(deps): update …fordependenciesandchore(deps): …for everything else. That is:semanticPrefixFixDepsChoreOthersfrom Drill 2. Observed live: even messages likeRenovate: neue Regelcount.
Save your progress? Sign up for free
Drill 8: Deprecated options and configMigration
Renovate migrates old options internally on every run. With
:configMigration it also opens a PR that rewrites the file.
You deliberately put in the old syntax.
cd ~/renovate-lab/tag02/shop-api
sed -i.bak -e 's/"config:recommended"\]/"config:recommended", ":configMigration"]/' \
-e 's/matchPackageNames: \["express"\]/matchPackagePatterns: ["^express$"]/' \
renovate.json5 && rm renovate.json5.bak
grep -nE 'extends|matchPackagePatterns' renovate.json5
renovate-config-validator >/dev/null 2>&1 \
&& git commit -qam "Alte Option" && git push -q
renovate shop/shop-api 2>&1 | grep -i "migration"
git fetch -q
git diff main origin/renovate/migrate-config | grep -E '^[-+] ' | head -8
curl -s -u "$ADMIN" "$FORGEJO/api/v1/repos/shop/shop-api/pulls?state=open" \
| jq -r '.[] | select(.head.ref=="renovate/migrate-config") | .body' \
| grep -o 'JSON5 config file migrated.*removed.'Expected:
3: extends: ["config:recommended", ":configMigration"],
13: matchPackagePatterns: ["^express$"],
INFO: Migration PR created (repository=shop/shop-api)
- $schema: "https://docs.renovatebot.com/renovate-schema.json",
- extends: ["config:recommended", ":configMigration"],
- prHourlyLimit: 0, // Lab: alle PRs in einem Lauf (Details: Tag 4)
+ $schema: 'https://docs.renovatebot.com/renovate-schema.json',
+ extends: [
+ 'config:recommended',
+ ':configMigration',
+ ],
+ prHourlyLimit: 0,
JSON5 config file migrated! All comments & trailing commas were removed.
The PR “Migrate Renovate config” (#8; #7 is the Dependency Dashboard: in Forgejo, issues and PRs share their numbers) would delete your comments. Better: migrate by hand. Renovate then closes the PR by itself.
sed -i '' 's|matchPackagePatterns: \["^express\$"\]|matchPackageNames: ["express"]|' \
renovate.json5
renovate-config-validator --strict >/dev/null 2>&1; echo "Exit: $?"
git commit -qam "Migration von Hand"
git push -q
renovate shop/shop-api 2>&1 | grep -E "Autoclosing"
curl -s -u "$ADMIN" "$FORGEJO/api/v1/repos/shop/shop-api/pulls?state=closed" \
| jq -r '.[] | "#\(.number) \(.title)"'Expected:
Exit: 0
INFO: Autoclosing PR (repository=shop/shop-api)
#8 Migrate Renovate config - autoclosed
There is no preset config:migration. The option is
called configMigration, the preset
:configMigration, and it is part of
config:best-practices, not of
config:recommended.
Save your progress? Sign up for free
Checkpoint
The config lives in renovate.json5, and the validator
has nothing to report:
cd ~/renovate-lab/tag02/shop-api
git pull -q
ls renovate.json*
renovate-config-validator --strict >/dev/null 2>&1; echo "Exit: $?"Expected:
renovate.json5
Exit: 0
The express v5 PR carries major and web,
and no prettier PR is open:
API="$FORGEJO/api/v1/repos/shop/shop-api"
curl -s -u "$ADMIN" "$API/pulls" | jq -r '.[] | "\(.title) \([.labels[].name])"'Expected:
R02_KP1
The migration PR is closed:
curl -s -u "$ADMIN" "$API/pulls?state=closed" | jq -r '.[].title'Expected:
Migrate Renovate config - autoclosed
Challenge
Change the config so that updates of devDependencies are
no longer turned off, but get the additional label dev
instead, and so that major updates do not come at all for now. Prove via
the API that a prettier PR with dev exists and that the
major PRs have been closed.
Hint: A rule can also set
enabled: false for an update type, and Forgejo silently
drops a missing label.
Solution
Create the label first. Renovate sets labels only when it creates a
PR or when the configured labels change. A label created afterwards is
not added later. The solution is at
~/renovate-lab/code/tag02/challenge/renovate.json5.
cd ~/renovate-lab/tag02/shop-api
curl -sf -u "$ADMIN" -H 'Content-Type: application/json' -X POST \
"$FORGEJO/api/v1/repos/shop/shop-api/labels" \
-d '{"name":"dev","color":"#fbca04"}' | jq -r .name
cat > renovate.json5 <<'EOF'
{
$schema: "https://docs.renovatebot.com/renovate-schema.json",
extends: ["config:recommended", ":configMigration"],
prHourlyLimit: 0, // Lab: alle PRs in einem Lauf (Details: Tag 4)
packageRules: [
{
description: "Manager: alle npm-Updates",
matchManagers: ["npm"],
labels: ["npm"],
},
{
description: "exakter Name: express bekommt zusätzlich web",
matchPackageNames: ["express"],
addLabels: ["web"],
},
{
description: "Glob: alle Actions der Org actions",
matchPackageNames: ["actions/*"],
labels: ["ci"],
},
{
description: "Regex + Datei + Datasource: Basis-Image im Dockerfile",
matchFileNames: ["Dockerfile"],
matchDatasources: ["docker"],
matchPackageNames: ["/^node$/"],
labels: ["docker"],
},
{
description: "devDependencies: zusätzlich Label dev",
matchDepTypes: ["devDependencies"],
addLabels: ["dev"],
},
{
description: "Majors: vorerst keine (steht hinten, gewinnt immer)",
matchUpdateTypes: ["major"],
enabled: false,
},
],
}
EOF
renovate-config-validator --strict >/dev/null 2>&1 && git commit -qam "Challenge" \
&& git push -q
renovate shop/shop-api 2>&1 | grep -cE "Autoclosing PR"
curl -s -u "$ADMIN" "$FORGEJO/api/v1/repos/shop/shop-api/pulls?state=all&limit=20" \
| jq -r '.[] | "#\(.number) \(.state) [\([.labels[].name]|join(","))] \(.title)"'Expected:
dev
4
#9 open [dev,npm] Update dependency prettier to v3.9.10
#8 closed [] Migrate Renovate config - autoclosed
#6 closed [ci,major] Update dependency node to v24 - autoclosed
#5 closed [major,web] Update dependency express to v5 - autoclosed
#4 closed [ci] Update actions/setup-node action to v7 - autoclosed
#3 closed [ci] Update actions/checkout action to v7 - autoclosed
#2 open [docker] Update Node.js to v20.20.2
#1 open [npm,web] Update dependency express to v4.22.3
Renovate closes PRs whose update is no longer wanted, adds the suffix “autoclosed”, and deletes the branch. If a major is allowed again later, it opens a new PR.
Save your progress? Sign up for free
Enterprise Note
- Run
renovate-config-validator --strictin the CI of every repo that contains a Renovate config. Only a run with--platform=localcatches preset typos. - Establish conventions: one config location (usually
renovate.json5or.github/renovate.json5), comments and adescriptionfor every rule. - Create labels centrally as org labels, otherwise Forgejo/Gitea silently drops them. GitHub and GitLab, on the other hand, create missing labels themselves.
- Pin the Renovate version in operation. New versions migrate options,
and
config:recommendedchanges its content with every release. - Recurring rules belong in an org preset (Day 11), not copied into every repo.