Foreword
Read little, type a lot. This book shows how Renovate keeps your
dependencies up to date without your team drowning in pull requests.
Everything runs on your laptop: a local Forgejo in Docker, the Renovate
CLI on Node 24, and a small demo application shop-api whose
versions are deliberately outdated. Every pull request, every issue, and
every status check you see in the book really happens on your
machine.
Why Forgejo and not GitHub? Because here you run Renovate yourself: you see every run, every log, and every option, without a cloud account, without installing an app, and without disturbing anyone else’s repositories. Whatever is different on GitHub or GitLab is covered in a note each time and on Day 10.
The book is for platform engineers, DevOps, and security people who want to introduce or tame Renovate in an organization: from the first onboarding PR through groups, schedules, and automerge to running it as a CronJob with org presets and supply chain guardrails.
The Training Rules
- Type, don’t copy. Every command once by yourself.
- Compare with Expected. After every drill you will find what you should see. If it differs, that is where the real lesson is.
- Pass the checkpoint. Only when every command shows what is expected do you move on.
- Solve the challenge on your own. First the hint, then the solution.
- Lab values stay in the lab.
lab-admin-pw-123, the bot token in~/renovate-lab/setup/bot-token, and all otherlab-…values are practice data.
Warning: Renovate releases new versions several times a day, and the packages in the demo application get new releases all the time. The target versions in your update PRs (for example “Update dependency express to v4.22.3”) will therefore be newer than in the book. That is not a bug, it is exactly what Renovate is there for.
Structure of Each Training Day
| Section | Purpose |
|---|---|
| Briefing | The essentials in a few bullet points |
| Drills | Commands with expected output |
| Checkpoint | Check script: did everything work? |
| Challenge | A task without instructions |
| Enterprise Note | What is different in production |
The Training Plan
| Part | Day | Unit |
|---|---|---|
| Training ground | 0 | Node 24, Renovate CLI, Forgejo, bot team, demo repo, push-to-create |
| A – Basics | 1 | The first run: onboarding, update PRs, dashboard |
| 2 | Understanding configuration: presets, packageRules,
validator |
|
| 3 | Managers and datasources: npm, Go, Docker, Helm, Kubernetes | |
| B – Control | 4 | Grouping, scheduling, limiting |
| 5 | Automerge and status checks | |
| 6 | Versions and ranges | |
| 7 | Your own dependencies with customManagers |
|
| 8 | Private registries and credentials | |
| C – Operations | 9 | Running self-hosted: global configuration |
| 10 | Renovate as a service: CronJob, GitLab CI, GitHub Actions | |
| 11 | Org presets | |
| 12 | Security and supply chain | |
| D – Practice | 13 | Monorepos, lockfiles, and PR design |
| 14 | Dependency Dashboard and troubleshooting | |
| 15 | Competition: disaster drills | |
| Appendix | A | Cheat Sheet |
| B | Final Exam |
Part A shows what Renovate does and why. Part B turns the PR generator into a tool that fits your team. Part C brings Renovate into operation for many repositories. Part D trains everyday work and emergencies.
Tip: Tested with Renovate 44.153.1 on Node 24.21.0, Forgejo 16.0.6 (image
codeberg.org/forgejo/forgejo:16.0.6-rootless), Docker 29.5, kind 0.33 (Kubernetes 1.37), kubectl 1.37, and Helm 4.3. If an option differs: the configuration reference atdocs.renovatebot.comandrenovate-config-validator.
The Companion Code
All files from this book are publicly available on GitHub: https://github.com/thomaszachmann/renovate-zum-anfassen. Day 0 shows how to get them.
Let’s go.
Thomas Zachmann, October 2026