Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Renovate is an open-source dependency update bot that works across most git platforms and package managers, with fine-grained control over scheduling, grouping, automerge, and digest pinning.

What Is Renovate?
Renovate is a bot that keeps dependencies up to date. It reads the manifests and lock files in a repository, works out which dependencies have newer versions, and opens pull requests to update them. Rhys Arkins created it, Mend now maintains it, and it is open source and self-hostable as well as available as a managed app.
Its reach is the first reason teams choose it: GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, and Forgejo, with support for well over ninety package managers — npm, pip, Poetry, Bundler, Maven, Gradle, NuGet, Go, Cargo, Composer, Docker, Helm, Terraform, GitHub Actions, pre-commit, and the long tail that matters once you leave the obvious ecosystems.
Configuration goes in renovate.json or .github/renovate.json5, and almost all of it is built from presets and package rules:
{
"extends": [
"config:recommended",
":dependencyDashboard",
"helpers:pinGitHubActionDigests"
],
"timezone": "Europe/London",
"schedule": ["after 9pm every weekday", "every weekend"],
"packageRules": [
{
"matchUpdateTypes": ["patch", "minor"],
"matchDepTypes": ["devDependencies"],
"groupName": "dev dependencies",
"automerge": true
},
{
"matchManagers": ["terraform"],
"schedule": ["before 5am on monday"]
}
],
"vulnerabilityAlerts": { "labels": ["security"], "schedule": ["at any time"] }
}
Two details in that example do most of the practical work. The schedule confines routine updates to evenings and weekends so they are never competing with feature work for continuous integration capacity, while vulnerabilityAlerts overrides the schedule for security advisories so a critical fix arrives immediately. The Dependency Dashboard creates a single issue listing everything pending, which lets you keep open pull requests to a handful without losing visibility of the rest.
The helpers:pinGitHubActionDigests preset rewrites workflow references from uses: acme/action@v4 to a full commit SHA with the version in a comment. This looks fussy until you consider what a mutable tag means for third-party code running inside your pipeline with access to its secrets.
In March 2025 the widely used tj-actions/changed-files action was compromised: its version tags were repointed to a malicious commit that dumped runner process memory, including credentials, into publicly readable build logs. Thousands of repositories were affected, and those that referenced the action by commit digest rather than tag were unaffected. Renovate both applies the pinning and then keeps the pinned digests updated, which is the combination that makes the control sustainable rather than a one-off hardening exercise that rots.
Dependabot is built into GitHub, needs essentially no configuration, and is free. For a small number of repositories on GitHub with ordinary needs, it is the sensible default and there is no reason to add a second bot.
Renovate earns its extra setup when you hit limits: repositories outside GitHub, a package manager Dependabot does not support, monorepos needing per-directory rules, serious grouping and scheduling requirements, automerge policies that differ by dependency type, or a central configuration preset applied across two hundred repositories. The last point is the one that usually decides it — Renovate configuration can be inherited from a shared repository, so a platform team can change update policy everywhere at once.
Automerge is the feature that turns dependency updates from a chore into background noise, and it is also the feature that can merge a malicious package without a human seeing it. Sensible boundaries:
minimumReleaseAge so a brand-new release waits a few days before Renovate proposes it. Most malicious publishes are detected and yanked within that window.For UK organisations, this is the mechanism behind a patching claim rather than the claim itself. Cyber Essentials expects high and critical vulnerabilities to be fixed within 14 days of a patch being released, and an automated updater with security advisories exempt from the schedule is the most reliable way to meet that for software dependencies and to keep supply chain exposure short-lived.
The bot is open source and can be self-hosted at no licence cost, and the hosted Mend Renovate app is free for public repositories and for many private ones. Mend sells enterprise offerings with additional reporting and support. Most teams start with the hosted app and move to self-hosting when they need to reach internal registries or private package feeds.
Dependabot is built into GitHub and requires almost no setup, which makes it the pragmatic default there. Renovate works across GitHub, GitLab, Bitbucket, Azure DevOps, and others, supports far more package managers, and offers much finer control over grouping, scheduling, automerge, and shared configuration presets across many repositories. Renovate costs more configuration effort and repays it at scale.
A tag can be moved. If an action’s maintainer account is compromised, or the tag is repointed to a malicious commit, every workflow referencing that tag runs attacker-controlled code with access to its secrets. That is exactly what happened to tj-actions/changed-files in March 2025. A commit digest cannot be repointed, and Renovate keeps the pinned digests current so the practice does not decay.
For patch and minor updates with solid test coverage, yes, and it is the main way teams stop drowning in update pull requests. Keep major versions, security-sensitive packages, and anything running install scripts under human review. Add a minimum release age so brand-new versions wait a few days, which filters out most malicious publishes before they can be merged automatically.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.