Guides
How to roll out base image updates safely
A base image update breaks builds across many repositories at once.
5 min read
A base image update breaks builds across many repositories at once.
Why it happens
Updates land everywhere simultaneously because nothing is pinned.
How to fix it
- Pin base images by digest and update through a pull request
- Roll out to a canary repository first
- Use Dependabot or Renovate so updates are visible and reviewable
- Keep the previous image available for fast rollback
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.