Running Renovate?

Renovate too noisy or too silent? We ship it properly.

Renovate is powerful and opinionated, and most teams that bring us in have either turned every knob or none of them. The symptoms are familiar: a giant dependency dashboard issue that no human reads, a schedule that fires in the middle of a release window, or a prBodyNotes block that was copied from an example and now points at a changelog that does not exist. We rewrite the config until it opens PRs the team actually merges.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

renovate.log

still broken

What it is

Renovate at a glance

Renovate is an automated dependency update tool originally written by Rhys Arkins and now developed under Mend (formerly WhiteSource). It runs as a hosted GitHub App, a free Mend Renovate service, or a self-hosted CLI against GitHub, GitLab, Bitbucket, Azure DevOps and Gitea.

The configuration model is a single renovate.json or renovate.json5 in the repository, with a rich packageRules system for grouping, scheduling, labelling and automerging. It supports more than ninety package managers and ecosystems, including language ones, Docker, Helm, Terraform, Kubernetes manifests, GitHub Actions, GitLab CI includes, and ad hoc regex matchers for anything else that pins a version in a text file.

Type
Multi-platform dependency update automation
First released
2017
License
AGPLv3 open source, commercial Mend add-ons above
Maintained by
Mend (formerly WhiteSource) and community contributors
Typically used for
Dependency bumps across language, container, infra and CI ecosystems on GitHub, GitLab, Bitbucket

The honest version

Renovate pros and cons

No technology is all upside. This is where Renovate earns its place and where it tends to cause trouble.

Where Renovate is strong

  • Works outside GitHub tooFirst class support for GitLab, Bitbucket, Azure DevOps and Gitea means one tool covers teams that split across providers.
  • Package rules are genuinely flexibleYou can group patch updates by ecosystem, pin majors on infrastructure dependencies, auto-merge dev dependencies, and keep tight control over production dependencies, all in one file.
  • Ninety-plus managers out of the boxDocker tags, Helm charts, Terraform providers, Kubernetes manifests, GitHub Actions, regex matchers, and most language package managers are all handled by one tool.
  • Dependency Dashboard surfaceA single issue in the repo lists what is pending, what is rate-limited, and what is ignored, which is the clearest picture of pending debt most teams have ever had.
  • Scheduled runs respect release windowsSchedules can be set to run only during working hours or avoid Fridays, which stops the bot from opening work the team cannot respond to.
  • Hosted or self-hostedThe Mend hosted app is free for most use, and anyone who needs air-gapped or self-hosted operation can run the CLI themselves against their own schedule.

Where Renovate bites

  • The configuration surface is largerenovate.json can get long and clever quickly, and a change that looks small can have surprising effects on grouping and scheduling if you have not followed the inheritance rules.
  • Large queues on big monoreposA monorepo with hundreds of dependencies will sit in a backlog because of concurrent PR limits and lookup budgets, and understanding why a particular package is stuck takes reading the dashboard carefully.
  • prBodyNotes and templating gotchasThe template system is Mustache-like but forgiving, so a typo in a variable name silently renders nothing rather than erroring, which leads to PRs with missing context.
  • Hosted vs self-hosted differencesSome features, especially custom managers and some global config options, behave differently when the bot is hosted by Mend than when you run it yourself.
  • Noisy by defaultWithout packageRules, Renovate opens a PR for every update it finds, which overwhelms a team that was expecting a slow trickle rather than a waterfall.
  • Private registry support needs host ruleshostRules and encrypted credentials cover most cases, but getting the right matchHost value against JFrog, Nexus or a company proxy is a rite of passage.

Sound familiar?

Common Renovate problems we fix

The Renovate problems that bring people to us, and what you have once each one is fixed.

config validation error: unknown option 'matchFiles'

Config will not load after an upgrade

Renovate renamed or removed an option in a newer release, and a config pulled from an older example now fails validation on the version Mend is running.

Config valid on the current release

prConcurrentLimit=20 reached

Pull requests pile up and then stop

A concurrent PR limit that is too low for a repo with many dependencies, leaving everything queued on the Dependency Dashboard without anyone noticing.

Throughput matches the review capacity

FileReadError: .nvmrc not found

Renovate cannot read a file it expects

A manager that was enabled against a path convention the repo does not follow, or a file that was deleted during a reshuffle without disabling the matching manager.

Managers scoped to what the repo really has

prBodyNotes undefined variable

PR bodies render with blank sections

A notes template that uses a variable name that was renamed between Renovate versions, or a Mustache typo where the triple braces do not match.

PR bodies render with useful context

ExternalHostError: 500 from registry

Runs fail because a registry is flaky

A public registry outage, or a private registry behind an intermittent proxy, that returns transient errors Renovate treats as hard failures on the first attempt.

Retries tuned so transient errors recover

config parse error: regex missing slash

A custom manager regex breaks the run

A custom regex manager with an invalid pattern, or a lookahead that is valid in one regex engine but not Renovate's, which fails the entire run until it is fixed.

Custom managers compile and match

GitHub API rate limit remaining 0

The bot stalls on API rate limits

A self-hosted run using a user PAT instead of a GitHub App, or a very large organisation sharing a single PAT across tools that collectively run out of API budget.

Rate budget respected, runs complete

Lookup limit reached: 500 queries

A monorepo blows the per-run lookup budget

A monorepo with too many dependencies to resolve in a single run, leaving half the packages deferred and the dashboard permanently behind.

Lookup budget sized for the repo

What we do

Renovate help, from config to merge strategy

Pick up the phone for a single stuck repo, or hand us the whole update estate.

Rescue
Runs failing, PRs piling up, or a dashboard nobody has looked at in months. We clear the queue first and rewrite the config second.
Configuration
renovate.json rewritten to group patches, schedule outside release windows, keep majors behind manual review, and pin the risky packages your team cares about.
Private registry access
hostRules and encrypted credentials for Nexus, Artifactory, GitHub Packages, Docker Hub and internal proxies, with rotation documented.
Auto-merge strategy
A policy that merges patch bumps on green CI for dev dependencies, holds production and framework updates for review, and prunes merged branches automatically.
Dependabot migration
Repos that have outgrown Dependabot moved across to Renovate with the same or better coverage and a tested rollback window if needed.
Managed Tech
Weekly dashboard review, triage of blocked updates, upgrades of the self-hosted CLI, and a team to call when a Renovate change took a release down.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Renovate alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Renovate questions

Something else? Call+1 737 727 7327

Why does Renovate open so many pull requests?

By default it opens a PR for every update it finds, which is more than most teams can review. Group patches by ecosystem, bundle minors on development dependencies, and schedule the runs to working hours only. Within a sprint the PR count usually drops to something the team can actually get through.

Why is the Dependency Dashboard growing but PRs are not being created?

The bot is hitting the concurrent PR limit, the per-run lookup budget, or a schedule that is more restrictive than the config implies. The dashboard itself labels each item with the reason; the fix is to raise the specific limit, loosen the schedule, or group updates so the backlog clears instead of sitting.

How do we handle a private registry with Renovate?

Add a hostRules entry matching the registry hostname and reference an encrypted credential or a secret depending on whether the bot is hosted or self-hosted. For JFrog, Nexus and Artifactory the matchHost pattern must match the exact proxy path the package manager uses, which is the place most first configs go wrong.

Should we move from Dependabot to Renovate?

Only if you need something Dependabot cannot do: multi-platform support, more complex grouping, custom regex managers, or ecosystems Dependabot does not cover well. For a straightforward GitHub repo, Dependabot is fine and switching for its own sake just adds a config file to maintain.

Can we schedule Renovate to avoid release windows?

Yes. The schedule key accepts cron-like windows and human expressions such as before 5am on monday or every weekend. Combining a weekly schedule on main dependencies with daily runs on dev-only packages gives most teams the balance they want.

How much does Renovate help cost?

The estimate is free. Describe the repository layout and the pain points, and a written quote comes back to you before any time is booked.

Free estimate

Renovate giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.