Skip to content
Hands-on IT IT Drills

Appendix A: Cheat Sheet

State of the book: Renovate CLI 44.153.1 on Node 24 LTS (24.21.0), Forgejo 16.0.6 (rootless, SQLite) in Docker. Names match the lab: org shop, repos shop-api, shop-worker, shop-deploy, shop-mono, preset repo presets/renovate-config.

Lab environment

source ~/renovate-lab/setup/env.sh          # PATH, FORGEJO, ADMIN, RENOVATE_*, GIT_*
docker run -d --name forgejo -p 127.0.0.1:3000:3000 \
  -v forgejo-data:/var/lib/gitea -v forgejo-conf:/etc/gitea \
  --env-file ~/renovate-lab/setup/forgejo.env \
  codeberg.org/forgejo/forgejo:16.0.6-rootless            # Forgejo (0)
docker exec forgejo forgejo admin user create …            # create user (0)
docker exec forgejo forgejo admin user generate-access-token --raw …  # bot token (0)
curl -s -u "$ADMIN" -X DELETE "$FORGEJO/api/v1/repos/shop/shop-api"   # reset (0)
git -C ~/renovate-lab/shop-api push -q forgejo:shop/shop-api.git main
git init -q -b main && git add -A && git commit -qm "Start"    # new repo (0)
git push -q forgejo:shop/<repo>.git main                   # push-to-create
export RENOVATE_GITHUB_COM_TOKEN=$(gh auth token)   # optional, never in files
# Rebuild with a fresh database (the token belongs to the old DB!)
docker rm -f forgejo && docker volume rm forgejo-data forgejo-conf
rm ~/renovate-lab/setup/bot-token                          # then Day 0, Drill 4/5
What Value in the lab
Forgejo web / API http://127.0.0.1:3000 / http://127.0.0.1:3000/api/v1
Container, image forgejo, codeberg.org/forgejo/forgejo:16.0.6-rootless
Admin (lab value) lab-admin / lab-admin-pw-123, in env.sh as $ADMIN
Bot (lab value) renovate-bot, token in ~/renovate-lab/setup/bot-token
Bot scopes write:repository,write:issue,read:user,read:organization,read:package
Renovate npm install --prefix ~/renovate-lab/tools [email protected]
Node ^24.11.0 according to engines; Node 25+ ends with exit 1

Running Renovate

renovate shop/shop-api                         # real run (env from env.sh)
renovate --dry-run=extract shop/shop-api       # only read files
renovate --dry-run=lookup shop/shop-api        # + query registries
renovate --dry-run=full shop/shop-api          # + build branches locally
renovate --dry-run=lookup --onboarding=false --require-config=optional shop/shop-api
renovate --platform=local                      # current directory, never writes
renovate --print-config=true --platform=local --dry-run=extract
renovate --dry-run=extract --report-type=file --report-path=report.json \
  shop/shop-api shop/shop-worker               # JSON report for jq
renovate --pr-hourly-limit=0 shop/shop-tools   # override an option for one run
renovate --autodiscover --autodiscover-filter='shop/*' \
  --write-discovered-repos=repos.json          # write repo list, nothing else
renovate --autodiscover=false lager/lager-app  # autodiscover from config.js off
renovate --checked-branches=renovate/prettier-3.x shop/shop-api   # like a tick
LOG_LEVEL=debug LOG_FORMAT=json renovate shop/shop-api > lauf.json 2>&1
Mode Registries Branches locally Writes to Forgejo
extract no no no
lookup yes no no
full yes yes (incl. lockfile, no PR) no
--platform=local yes (default lookup) never never
  • --print-config otherwise swallows the next argument: always --print-config=true.
  • --platform=local only reads files Git knows about: git add new files first.
  • Renovate splits lists on the command line at the comma: shop/{a,b} only in config.js (Day 9).

Validator

renovate-config-validator                         # repo config in the current dir
renovate-config-validator --strict                # required migration = error (CI!)
renovate-config-validator --no-global renovate.json   # file as repo config
renovate-config-validator config.js               # with file name: global config
renovate-config-validator --no-global *.json platform/*.json   # preset repo
Finding Exit Example
unknown option 1 Invalid configuration option: prHourlyLimt
deprecated option 0, with --strict 1 matchPackagePatterns, fileMatch, prTitle
global option in the repo 1 The "requireConfig" option is a global option
typo in a preset 0 config:recomended – only a run reports it

Environment variables

Every option works as RENOVATE_<OPTION> (prHourlyLimit → RENOVATE_PR_HOURLY_LIMIT). Precedence: config.js < RENOVATE_* < CLI flag (Day 9).

Variable Effect
RENOVATE_PLATFORM, RENOVATE_ENDPOINT forgejo, http://127.0.0.1:3000/api/v1
RENOVATE_TOKEN bot token, without a newline
RENOVATE_GITHUB_COM_TOKEN github.com lookups and release notes
RENOVATE_CONFIG_FILE a path other than ./config.js
RENOVATE_REPOSITORIES repo list (ignored with autodiscover)
RENOVATE_HOST_RULES, RENOVATE_SECRETS JSON array or JSON object
RENOVATE_ALLOWED_COMMANDS regex list for postUpgradeTasks
RENOVATE_BASE_DIR, RENOVATE_CACHE_DIR working and cache directory
RENOVATE_GIT_URL endpoint: clone URL from the endpoint instead of clone_url
LOG_LEVEL, LOG_FORMAT debug/info, json (no prefix!)
LOG_FILE, LOG_FILE_LEVEL additional log file, its level (default debug)

Repo config locations

Renovate takes the first file it finds and silently ignores the others (Day 2): renovate.json, .jsonc, .json5, the same under .github/ and .gitlab/, then .renovaterc, .renovaterc.json, .jsonc, .json5, finally the key renovate in package.json (deprecated). 44.153.1 does not read .forgejo/renovate.json.

Presets

Preset Effect
config:recommended dashboard, monorepo groups, workarounds, ignorePaths
config:best-practices + digests, action SHAs, :configMigration, npm maturity period
config:js-app / config:js-lib pin everything / ranges for libraries
group:allNonMajor all minor/patch in one PR (renovate/all-minor-patch)
schedule:earlyMondays * 0-3 * * 1 (schedule:weekly refers to it)
:dependencyDashboard / :disableDependencyDashboard dashboard on/off
:configMigration PR that rewrites deprecated options
:timezone(Europe/Berlin), :label(deps) presets with a parameter
:disableMajorUpdates major: {enabled: false}
:skipStatusChecks ignoreTests: true – never in production
docker:pinDigests image tags with @sha256:
helpers:pinGitHubActionDigests uses: …@<sha> # v3 (…ToSemver: # v7.0.1)
security:minimumReleaseAgeNpm let npm releases mature for 3 days
security:only-security-updates only security PRs (OSV)
:enableVulnerabilityAlertsWithLabel(security) security PRs with a label
customManagers:dockerfileVersions # renovate: comment above ARG/ENV …_VERSION
customManagers:makefileVersions, …:gitlabPipelineVersions Makefile, GitLab CI

Source code: tools/node_modules/renovate/dist/config/presets/internal/*.preset.js. Defaults: jq '.definitions.<option>.default' on …/renovate/renovate-schema.json. extends applies from left to right, your own keys beat every preset, arrays such as labels are replaced. Deselect individual presets: ignorePresets (Day 15).

packageRules matchers

Matcher Checks Example
matchPackageNames name: exact, glob, /regex/, ! negation ["actions/*", "!actions/cache"]
matchUpdateTypes major, minor, patch, pin, digest … ["minor", "patch"]
matchManagers / matchDatasources manager / datasource ["npm"] / ["docker"]
matchDepTypes / matchFileNames section / file (glob) ["devDependencies"] / ["packages/**"]
matchCurrentVersion current value "<5.0.0"
matchBaseBranches target branch ["/^release\\/.+/"]
  • Within a rule, all matchers must match; within a list, one is enough.
  • All matching rules apply, the later one wins. labels replaces, addLabels adds.
  • matchPackageNames checks packageName, not the displayed depName.
  • Negations only (["!@shop/**"]) match everything that is not excluded.
  • Renamed: matchPackagePatterns/excludePackageNames → matchPackageNames, fileMatch → managerFilePatterns (/…/ = regex), baseBranches → baseBranchPatterns.

Grouping, scheduling, limiting

Option Default Effect
groupName / groupSlug – same branch name = one PR
separateMajorMinor true major gets its own PR, group branch major-…
separateMultipleMajor false a separate PR per major jump
separateMinorPatch false patch separate, group branch patch-…
prHourlyLimit 2 new PRs per running hour (0 = off)
prConcurrentLimit 10 open Renovate PRs
branchConcurrentLimit null (= PR limit) existing Renovate branches
schedule + timezone any time, UTC when new branches are created
updateNotScheduled true maintain existing PRs outside the schedule too
minimumReleaseAge null maturity period, status renovate/stability-days
minimumReleaseAgeBehaviour timestamp-required never mature without a timestamp
internalChecksFilter strict do not propose immature versions at all
dependencyDashboardApproval false branch only after a tick (Day 14)

Cron schedule: minute always * (* 0-5 * * 1 = Mondays 0:00–5:59). The text form (before 6am on monday) still works, but only the validator catches typos in it.

Automerge

{
  "platformAutomerge": false,
  "packageRules": [
    {
      "description": "devDependencies: patch/minor ohne PR, nur bei grünem CI",
      "matchDepTypes": ["devDependencies"],
      "matchUpdateTypes": ["patch", "minor"],
      "automerge": true,
      "automergeType": "branch",
      "automergeSchedule": ["* 0-5 * * *"]
    }
  ]
}
Option Default Remember
automerge false only merges when all statuses are success
automergeType pr branch: fast-forward onto main, PR only on failure
platformAutomerge true Forgejo merges by itself on the first success
automergeSchedule any time only limits the merge
ignoreTests false true = branch always counts as green
internalChecksAsSuccess false only renovate/* checks green = yellow
rebaseWhen auto automerge: behind-base-branch, otherwise conflicted

Forgejo status → Renovate: unknown/pending yellow, success green, the rest red. Per context, the newest status counts. Without platformAutomerge, only the next run merges.

Versions and ranges

rangeStrategy lodash ^4.17.20 (lock 4.17.21) express ^4.18.2 → 5.3.0
auto (npm) like update-lockfile like update-lockfile
update-lockfile lockfile only → 4.18.1 ^5.0.0 (+ lockfile PR 4.x)
bump ^4.18.1 ^5.3.0 (+ ^4.22.3)
replace nothing (within range) ^5.0.0
widen nothing (within range) ^4.18.2 \|\| ^5.0.0
pin first a pin PR 4.17.21, then exact exact
in-range-only lockfile only nothing, major PR closed
Filter Example Remember
allowedVersions "<5", "/^22\\./" holds back permanently, does not filter digests
matchCurrentVersion + enabled: false "<5.0.0" + major resolves itself after the major
ignoreDeps ["prettier"] short form of enabled: false
followTag "latest-4", "next" follows an npm dist-tag, even downwards
pinDigests true node:20.11.0-alpine@sha256:…
versioning "docker", "regex:…" unsupported/unversioned in the log = does not fit

Node images get the node versioning (only LTS as a major target) through workarounds:nodeDockerVersioning; suffixes like -alpine are kept. Bumping the go directive: matchDatasources: ["golang-version"] + rangeStrategy: "bump" (Day 6).

customManagers

{
  "extends": ["config:recommended", "customManagers:dockerfileVersions"],
  "customManagers": [
    {
      "customType": "regex",
      "description": "kubectl im Tool-Image",
      "managerFilePatterns": ["/(^|/)Dockerfile$/"],
      "matchStrings": ["ARG KUBECTL_VERSION=(?<currentValue>\\S+)"],
      "depNameTemplate": "kubernetes/kubernetes",
      "datasourceTemplate": "github-releases"
    },
    {
      "customType": "regex",
      "managerFilePatterns": ["deploy.env"],
      "matchStringsStrategy": "combination",
      "matchStrings": ["DB_IMAGE=(?<depName>\\S+)", "DB_TAG=(?<currentValue>\\S+)"],
      "datasourceTemplate": "docker"
    },
    {
      "customType": "jsonata",
      "fileFormat": "yaml",
      "managerFilePatterns": ["tools.yaml"],
      "matchStrings": ["tools.{ \"depName\": repo, \"currentValue\": version }"],
      "datasourceTemplate": "github-releases"
    }
  ]
}

Comment convention of the customManagers:*Versions presets: fields in the order datasource, depName, packageName, versioning, extractVersion, registryUrl, directly (without a blank line) above the variable:

# renovate: datasource=github-releases depName=kubernetes/kubernetes
ARG KUBECTL_VERSION=v1.29.0
  • Required: depName, currentValue, datasource (group or …Template). currentValue has no template.
  • The regex is RE2 on the entire file content; in JSON, double every backslash.
  • matchStringsStrategy: any (default), recursive, combination.
  • Tags with a prefix (v, kustomize/v): extractVersion=^v(?<version>.*)$.
  • Custom source: customDatasources + datasource=custom.<name>, format {"releases": [{"version": "…"}]}, otherwise transformTemplates (Day 7).
  • The kubernetes manager has no default patterns: "kubernetes": {"managerFilePatterns": ["/(^|/)k8s/.+\\.yaml$/"]}. There is no helm manager, only helmv3 (Chart.yaml) and helm-values (Day 3).

hostRules

These belong in the global config or RENOVATE_HOST_RULES. In the repo only with placeholders, values from the global option secrets (Day 8):

{
  "hostRules": [
    {
      "matchHost": "http://127.0.0.1:3000/api/packages/",
      "hostType": "npm",
      "token": "{{ secrets.FORGEJO_PACKAGES }}"
    },
    {
      "matchHost": "127.0.0.1",
      "hostType": "docker",
      "username": "renovate-bot",
      "password": "{{ secrets.FORGEJO_PACKAGES }}",
      "insecureRegistry": true
    }
  ]
}
matchHost Matches
127.0.0.1 any port, any scheme
127.0.0.1:3000 only https://127.0.0.1:3000… (port without scheme → https!)
http://127.0.0.1:3000/api/packages/ only URLs with exactly this prefix
  • hostType separates rules for the same host (npm, docker, platform). Renovate does not send the platform token to the registry by itself.
  • Docker registry over HTTP only with insecureRegistry: true (lab only).
  • A global npmrc replaces the repo .npmrc completely, unless npmrcMerge: true.
  • Renovate masks secrets values in the log; placeholders are forbidden in branch*, commit*, group*, pr* and semantic* fields.

Global config.js

// config.js – global configuration (Day 9, Day 10, Day 12)
module.exports = {
  platform: 'forgejo',
  endpoint: 'http://127.0.0.1:3000/api/v1',
  token: process.env.RENOVATE_TOKEN,      // never write it into the file
  gitAuthor: 'Renovate Bot <[email protected]>',
  autodiscover: true,
  autodiscoverFilter: ['*/*', '!lager/*'],
  onboardingBranch: 'renovate/onboarding',
  onboardingConfig: {
    $schema: 'https://docs.renovatebot.com/renovate-schema.json',
    extends: ['local>presets/renovate-config'],
  },
  repositoryCache: 'enabled',
  exitCodeForErrors: true,
  allowedCommands: ['^npm ci --ignore-scripts$', '^npm run format$'],
  secrets: { FORGEJO_PACKAGES: process.env.FORGEJO_PACKAGES_TOKEN },
};

In a container or pod, additionally gitUrl: 'endpoint', because Forgejo reports 127.0.0.1 as clone_url (Day 10). Options that only work globally include platform, endpoint, token, gitUrl, autodiscover*, onboarding*, requireConfig, baseDir, cacheDir, repositoryCache, binarySource, allowedCommands, secrets, globalExtends, inheritConfig, internalHostAccess.

requireConfig Repo without config Config in the repo
required (default) onboarding PR applies
optional global config, even after a closed onboarding PR applies
ignored global config is not read (including enabled: false)
Exit Meaning
0 finished, even with a broken repo config or forbidden
1 FATAL at startup (e.g. Authentication failure) or an entry with ERROR
3–8 only with exitCodeForErrors: true, e.g. 5 = config error

Org presets

Reference in extends Loads
local>presets/renovate-config default.json
local>presets/renovate-config:go go.json
local>presets/renovate-config//platform/k8s platform/k8s.json
local>presets/renovate-config:go/x key x in go.json
local>presets/renovate-config#v1.1.0 default.json from Git tag v1.1.0
local>presets/renovate-config:team(team-shop, lab-admin) {{arg0}}, {{arg1}}
  • Each reference needs its own #tag. Without a tag, main applies everywhere immediately.
  • local> reads with the bot token; read access is enough. If it is missing: 404 → “Cannot find preset’s package” → config error issue (Day 11).
  • Onboarding finds <org>/renovate-config with default.json by itself and writes it into the PR without a tag – even before onboardingConfig.
  • globalExtends is resolved before the platform; local> ends up at github.com. Use a URL readable without a token (…/raw/tag/v1.1.0/default.json).
  • inheritConfig: true fetches org-inherited-config.json from {{parentOrg}}/renovate-config, with the bot token.

Monorepos and PR design

{
  "semanticCommits": "enabled",
  "labels": ["deps"],
  "reviewers": ["alice"],
  "baseBranchPatterns": ["main", "/^release\\/.+/"],
  "lockFileMaintenance": { "enabled": true },
  "prBodyNotes": ["Betreut von Team Shop, Fragen im Kanal #shop-deps."],
  "packageRules": [
    {
      "description": "Go-Worker",
      "matchFileNames": ["services/worker/**"],
      "addLabels": ["worker"],
      "additionalBranchPrefix": "{{parentDir}}-",
      "semanticCommitType": "build",
      "semanticCommitScope": "worker",
      "postUpdateOptions": ["gomodTidy"]
    },
    {
      "description": "Release-Branches: nur Patches (Patch sonst im Minor)",
      "matchBaseBranches": ["/^release\\/.+/"],
      "separateMinorPatch": true
    },
    {
      "matchBaseBranches": ["/^release\\/.+/"],
      "matchUpdateTypes": ["major", "minor", "lockFileMaintenance"],
      "enabled": false
    }
  ]
}
  • npm workspaces: one update in several package.json files = one branch; the lockfile always lives in the root directory.
  • Commit/title: commitMessagePrefix commitMessageAction commitMessageTopic commitMessageExtra commitMessageSuffix. Setting prTitle directly is deprecated.
  • {{parentDir}} = worker, {{packageFileDir}} = services/worker.
  • lockFileMaintenance: default schedule before 4am on monday, not for gomod.
  • baseBranchPatterns: branch names with a target prefix, titles with a suffix (main). The config comes from the default branch (otherwise useBaseBranchConfig: "merge").
  • Renovate only sets reviewers and assignees when creating a PR; with automerge only with assignAutomerge: true (Day 13).

Security

{
  "extends": ["config:best-practices"],
  "osvVulnerabilityAlerts": true,
  "dependencyDashboardOSVVulnerabilitySummary": "unresolved",
  "vulnerabilityAlerts": {
    "labels": ["security"],
    "vulnerabilityFixStrategy": "highest"
  }
}
  • OSV only checks direct dependencies, specifically the lockfile version. The offline DB needs around 600 MB unpacked.
  • vulnerabilityAlerts reads platform alerts – only GitHub can do that. Security PRs ignore schedule, limits and minimumReleaseAge.
  • vulnerabilityFixStrategy: lowest (default, smallest fix) or highest.
  • postUpgradeTasks (commands, fileFilters) only run if the global allowedCommands (regex, ^…$) match; without a shell, so no && (Day 12).
  • Bot: no admin, only the necessary scopes, no exception in branch protection (Day 12).

Dependency Dashboard

Ticking via the API: switch the marker in the HTML comment from - [ ] to - [x], write the body back via PATCH (jq -Rs '{body: .}', Day 1). Renovate acts on the next run and unticks it again. Checkboxes override all limits.

Section Cause Marker <typ>-branch=… Bulk checkbox
Repository Problems WARN/ERROR in the run – –
Pending Approval dependencyDashboardApproval approve approve-all-pending-prs
Awaiting Schedule schedule unschedule create-all-awaiting-schedule-prs
Rate-Limited limits unlimit create-all-rate-limited-prs
Errored error in the branch retry –
PR Edited (Blocked) foreign commit in the branch rebase –
Pending Status Checks minimumReleaseAge unpend –
Open open PRs rebase rebase-all-open-prs
PR Closed (Blocked) closed PR recreate –
  • In the PR itself: marker rebase-check, alternatively the label rebase (rebaseLabel) or a title that starts with rebase!.
  • recreateWhen: auto (default, only groups, digests, lockfile maintenance come back), always, never.
  • Renovate finds the dashboard only via dependencyDashboardTitle. Changing the title leaves the old issue orphaned.

Forgejo API one-liners

R="$FORGEJO/api/v1/repos/shop/shop-api"
api() { curl -sf -u "$ADMIN" -H 'Content-Type: application/json' "$@"; }
api "$R/pulls?state=open&limit=50" | jq -r '.[] | "#\(.number) \(.head.ref) \(.title)"'
api "$R/issues?type=issues&state=open" | jq -r '.[] | "#\(.number) \(.title)"'
api "$R/issues/4" | jq -r .body                          # dashboard body
api "$R/raw/renovate.json?ref=renovate/configure"
api -X POST "$R/pulls/2/merge" -d '{"Do":"merge","delete_branch_after_merge":true}'
api -X PATCH "$R/pulls/8" -d '{"state":"closed"}'        # = ignore update
SHA=$(api "$R/branches/renovate%2Fprettier-3.x" | jq -r .commit.id)
api -X POST "$R/statuses/$SHA" -d '{"state":"success","context":"ci/test"}'
api "$R/commits/renovate%2Fprettier-3.x/status" \
  | jq -r '.statuses[] | "\(.context) = \(.status)"'
api -X PATCH "$R" -d '{"has_actions":false}'             # Forgejo Actions off
api -X POST "$R/branch_protections" -d '{"rule_name":"main",
  "enable_status_check":true,"status_check_contexts":["ci/test"]}'
api -X PUT "$R/collaborators/renovate-bot" -d '{"permission":"write"}'
curl -s -H "Authorization: token $RENOVATE_TOKEN" "$R" | jq -c .permissions
curl -s -u renovate-bot:lab-bot-pw-123 \
  "$FORGEJO/api/v1/users/renovate-bot/tokens" | jq -r '.[].scopes | join(",")'

Forgejo numbers issues and PRs together. It silently discards unknown labels; you create org labels under /orgs/shop/labels.

jq recipes for JSON logs

Produce the log with LOG_LEVEL=debug LOG_FORMAT=json renovate … > lauf.json 2>&1.

jq -r .level lauf.json | sort | uniq -c                 # 20 debug … 60 fatal
jq -c 'select(.level >= 40) | {level, branch, msg}' lauf.json        # WARN and up
jq -r 'select(.msg == "packageFiles with updates") | .config[][].deps[]
  | "\(.depName) \(.currentValue) \([.updates[]?.newVersion])"' lauf.json
jq -r 'select(.msg == "branches info extended") | .branchesInformation[]
  | "\(.result) \(.branchName)"' lauf.json
jq -r --arg b renovate/node-24.x 'select(.branch == $b) | .msg' lauf.json
jq -r 'select(.msg == "Repository finished")
  | "\(.repository)\t\(.durationMs) ms\t\(.result)"' lauf.json
jq -r '.. | objects | select(.skipReason?) | "\(.depName): \(.skipReason)"' \
  report.json                                           # --report-type=file

branches results: done, pr-created, needs-approval, not-scheduled, pr-limit-reached, already-existed, pr-edited, error. result in “Repository finished”: done, onboarding, disabled-*, config-validation, forbidden.

Failure patterns

Symptom Cause Remedy
Unsupported node environment, exit 1 Node 25+ or < 24.11 Node 24 LTS (Day 0)
github-token-required no github.com token RENOVATE_GITHUB_COM_TOKEN
Repository is empty - skipping push not processed yet repeat the run
"result": "onboarding" onboarding PR not merged merge it or put the config on main
only 2 PRs, the rest “Rate-Limited” prHourlyLimit 2 (default) set the limit or use the checkbox
Issue “Action Required: Fix Renovate Configuration” JSON, option, preset, secret validator, repair
“Found renovate config warnings” global option in repo config move it to config.js
FATAL: Authentication failure token wrong, with \n or too few scopes GET /api/v1/user with the token
result: forbidden, silent bot without write permission collaborator write
Failed to look up … no-result 401, no hostRules rule with a matching matchHost
-1 https://…/v2/…, wrong version number Docker registry HTTP only insecureRegistry: true
HTTP request to an internal host internalHostAccess=warn hostRules entry
renovate/artifacts: failure tool, E404, peer conflict, allowlist fix on main, rebase-check
No dependencies found in file regex does not match (file does) test the regex with --platform=local
Automerge stuck, Branch status yellow check never finishes (Actions without a runner) has_actions: false or a runner
Update silently missing minimumReleaseAge without timestamp, skipReason timestamp-optional, log
“PR Edited (Blocked)” foreign commit in the Renovate branch rebase-check
PR “- autoclosed” no longer wanted or lookup error (token!) check config, hostRules

Pitfalls

  • Node 25 locally: Renovate runs, but ends with exit 1; RE2 is missing (Day 0).
  • The self-hosted onboarding PR only contains $schema, no config:recommended.
  • Closing a PR = ignoring the entire major line; the block is tied to the title (Day 1).
  • semanticCommits: auto: commits like config: … on main switch PR titles to fix(deps):/chore(deps):; fix triggers a release in semantic-release.
  • ignorePaths is not mergeable: your own list replaces :ignoreModulesAndTests.
  • A config change does not rebuild existing branches; only a rebase or conflict does.
  • Changing the branch prefix (additionalBranchPrefix, separateMinorPatch, baseBranchPatterns) closes all affected PRs as “autoclosed”.
  • platformAutomerge without branch protection: Forgejo merges on the first arbitrary success, even if ci/test is red (Day 5).
  • automergeType: branch with the bot in the push whitelist bypasses required checks.
  • Broken repo config and missing write permission: exit 0 (Day 9, Day 14).
  • autodiscover: repo arguments are not a filter, RENOVATE_REPOSITORIES is ignored – additionally set RENOVATE_AUTODISCOVER=false (Day 9, Day 10).
  • source env.sh sets RENOVATE_ENDPOINT and friends and overrides config.js.
  • concurrencyPolicy: Forbid does not know about manual Jobs (Day 10).
  • A typo in the package name (expresss) often installs foreign code instead of producing a lookup error (Day 14).
  • Deselecting group:monorepos: peer pairs like react/react-dom then need their own group, otherwise ERESOLVE in the lockfile (Day 15).
  • The API’s permissions.push is the user’s permission, not the token’s.