Skip to content

Use Cases

This page describes common use cases for Renovate.

Development dependency updates

The original use case, and the most popular one, is for developers to automate dependency updating in their software projects.

Updating of package files

We use the term "package file" to describe files which reference dependencies. Package files are managed by a "package manager".

Example package files include:

  • package.json, managed by npm or Yarn
  • Gemfile, managed by Bundler
  • go.mod, managed by go modules

How Renovate updates a package file


  1. Scans your repositories to find package files and their dependencies
  2. Checks if any newer versions exist
  3. Raises Pull Requests for available updates

The Pull Requests patch the package files directly, and include changelogs for the newer versions (if they are available).

By default:

  • You'll get separate Pull Requests for each dependency
  • Major updates are kept separate from non-major updates

Package managers with lock files

Many package managers support "lock files", which "freeze" the entire dependency tree including transitive dependencies. npm, Yarn, Bundler, Composer, Poetry, Pipenv, and Cargo all support or use lock files.

If you use a lock file then changes to your package file must come with a compatible change to the lock file. Renovate can patch/update package files directly, but can't "reverse engineer" lock files. This is why Renovate lets the package manager do the lock file update. A simplified example:

  1. The repository has a package.json and package-lock.json with version 1.0.0 of a dependency
  2. Renovate sees that version 1.1.0 is available
  3. Renovate patches the package.json to change the dependency's version from 1.0.0 to 1.1.0
  4. Renovate runs npm install to let npm update the package-lock.json
  5. Renovate commits the package.json and package-lock.json
  6. Renovate creates the PR

Custom dependency extraction

Renovate supports 90+ types of package files. By default, Renovate finds most dependencies, but there are exceptions. This can be because:

  • The package manager/file format is not supported, or
  • The file format is not a standard or is proprietary

If your dependencies are not found by default, you can use our custom manager to set your own custom patterns to extract dependencies. You configure the custom manager by telling it:

  • Which file pattern(s) to match
  • How to find the dependency name and version from within the file
  • Which datasource (e.g. Docker registry, npm registry, etc) to use to look up new versions

The end result is that Renovate can keep dependencies in custom file formats up-to-date as long as the dependency datasource is known to Renovate.

DevOps tooling

Renovate is increasingly used for purposes which are traditionally described as DevOps instead of Developer.

DevOps / Infrastructure as Code updates

It's common for repositories to have DevOps-related files like CI/CD configs, or "Infrastructure as Code" (IaC) files. Examples of IaC files are Docker, Kubernetes or Terraform files. Renovate handles IaC files as "package managers" and "package files" and can find and update them.

Docker-compatible images

Docker-compatible images are a key building block of modern software. These images are commonly found in CI/CD pipeline configs or referenced in IaC files. Renovate finds these IaC files and then searches Docker registries to see if there are newer tags or digests.

Tag-based updating

An example of tag-based updating are node images from Docker Hub. The node images use these tag formats:

  • 14.17.4
  • 14.17.4-alpine3.11

Renovate understands both formats and raises updates like these:

  • From 14.17.4 to 14.17.5
  • From 14.17.4-alpine3.11 to 14.17.5-alpine3.11

Docker digests

You can check and update versions like 14.17.4 yourself. But looking up image digests like 341976f40d963a425d627a349a9b0034e1eafffbf4c82a173c1465ee403878d9 and updating them yourself doesn't scale. So let Renovate update your Docker digests.

You can even configure Renovate to "pin" your Docker digests. When you're using tag+digest based images, you'll have immutable builds.

Internal package updates

Your company typically has dozens of repositories, if not hundreds or thousands. These repositories often rely on other repositories and may have upstream or downstream internal dependencies. In such cases, it is best practice to:

  • Update downstream links as soon as possible, and
  • Keep internal version use as consistent as possible

You can use Renovate to follow this best practice. Renovate finds and updates internal dependencies just like external or Open Source dependencies.

Automerge internal dependencies

Renovate's automerge feature is really useful for internal dependencies where you can say "if it passes tests let's merge it".

To learn more about "automerge" read the key concepts, automerge documentation.

Example of automerging internal dependencies

We use these Renovate features to automerge an internal dependency:

Background information

We split our work over two repositories:

  1. The renovatebot/renovate repository, which has the Renovate code, and most of the Markdown documentation files
  2. The renovatebot/ repository, which has a submodule link to the renovatebot/renovate repository
Update process
  1. We edit our documentation files on the main Renovate repository renovatebot/renovate
  2. Renovate sees the change(s) to the renovatebot/renovate Git submodule, and creates an update branch on the documentation build repository
  3. If the tests pass Renovate automerges the update branch into the main branch.
  4. A GitHub Actions workflow runs on main to build the documentation site and push the build live on our GitHub Pages domain

The way we've set things up means we avoid:

  • reviewing PRs
  • manually merging PRs

In fact we don't even get the update PR anymore!

Advanced configuration

The capabilities listed below are commonly needed for all the above use cases.

Batched updates

Renovate defaults to separating each dependency update into its own PR. But you may want to batch or "group" updates together. For example, group all patch updates into one PR or even all non-major updates together (patches and minor updates).

You can configure batched updates by setting a groupName as part of packageRules.

Scheduled updates

You may want to limit the times when Renovate is allowed to raise updates. This reduces "noise" during your working hours, and reduces the chance of CI contention. You can tell Renovate to "not bother you" during times when you're using the CI resources, or want to focus on your work.

You can set the time ranges during which Renovate creates updates in the schedule field.

On-demand updates via Dependency Dashboard

You can use Renovate's "Dependency Dashboard" on platforms which support dynamic Markdown checkboxes:

  • Gitea and Forgejo
  • GitHub
  • GitLab

When you enable the Dependency Dashboard, Renovate creates a "Dependency Dashboard" issue. This issue lists all updates which are pending, in progress, or were previously closed ignored.

If you want to get an update ahead of schedule, or want to retry a previously closed update: select the update's checkbox in the Dependency Dashboard.

Dependency Dashboard Approval

If you enable the Dependency Dashboard you can opt-in to a different workflow for some, or even all of your packages. We call this the "Dependency Dashboard Approval" workflow.

Here's how it works:

  • You tell Renovate which package updates need "Dashboard Approval" by setting a custom packageRule
  • Renovate only raises updates for packages that need "Dashboard Approval" after you select the corresponding checkbox on the dashboard

Benefits of using Dependency Dashboard Approval

Benefits of using Dependency Dashboard Approval:

  • By not raising PRs automatically, it allows you to request updates on-demand when you're ready, and
  • It offers you an alternative to permanently ignoring/disabling certain types of updates, like major updates

When you use the Dependency Dashboard Approval workflow you have full visibility and control over your updates.

Configuration presets

You may run Renovate on many, or even all your repositories. This also means that you might want a similar config for all of your repositories. You can use configuration "presets" to avoid duplicating your configuration across your repositories.

Configuration presets are JSON configuration files which are committed to repositories and then referenced from others. Renovate includes over 100 built-in presets, like the default recommended config:recommended preset.

The typical workflow for a company is:

  • Create a dedicated repository to store the company's default Renovate settings
  • Set that repository as the default extends value when onboarding new repositories

This means that repositories get the centralized config by default, and any changes made to the centralized config repository are propagated to other repositories immediately.

How others use Renovate

You can learn a lot by seeing how others use Renovate. Check out the Swissquote user story.