Using Renovate to keep your version dependencies updated
summary
Renovate automates dependency updates on self‑hosted GitLab using Renovate Runner and a scheduled pipeline that finds updates in Dockerfiles, docker‑compose and .gitlab-ci.yml and opens MRs; the demo shows two MRs created and daily auto‑merges for Renovate’s own image via a package rule that succeeds when a renovate token has sufficient scope. Configuration options include centralized onboarding or per‑project renovate.json, presets like config:base, MR grouping, and a caveat that the Docker image is >1 GB which slows pulls.
AI-written summary · about
chapters (10)
- 0:00Introduction to Renovate
- 1:12How Renovate works
- 3:20Package managers and presets
- 5:48Favorite Renovate features
- 10:06Setup components
- 12:16GitLab CI integration
- 14:46Centralized vs standalone setup
- 16:56Tweaking and tuning Renovate
- 20:50Live demo walkthrough
- 28:42Q&A session
related talks
45mHow to Automate Dependency Updates with the Renovate@Roche Bot- 45mHow to Automate Dependency Updates with the Renovate@Roche Bot
16mRenovate to the Rescue
31mRenovate/Dependabot: How to Take Back Control of Dependency Updates
41mRenovate/Dependabot: How to Reclaim Control Over Dependency Updates
50mExtract Dependency Data on Scale with Renovate
15mManaging Third Party Software in your GitOps Setups
11mYou should be using renv