Running Dependabot?

Dependabot flooding or failing silently? We sort it out.

Dependabot is good at opening pull requests and bad at being a product plan. The usual trouble is a repo where dozens of its PRs sit for weeks, a private registry the bot cannot reach, or a lockfile the resolver gives up on because an indirect dependency pins something incompatible. We cut the scope to what the team will actually merge and make the rest of the PRs reliable.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

dependabot.log

still broken

What it is

Dependabot at a glance

Dependabot is GitHub's built-in dependency update tool, acquired from an independent project in 2019 and now embedded into the platform. It checks dependency manifests on a schedule, opens pull requests to upgrade to newer versions, and runs security updates automatically when a known advisory lands.

The configuration lives at .github/dependabot.yml and covers package ecosystems from npm, Yarn, pnpm, Bundler, Composer, pip, Poetry, Go modules, Cargo, Maven, Gradle, and more, plus GitHub Actions and Docker base images. There is also a security-only mode that ignores regular version bumps and only reacts to vulnerability advisories, which is a cleaner fit for many teams than the full version update firehose.

Type
Automated dependency update bot
First released
2017 as Dependabot, acquired by GitHub 2019
License
MIT core, closed service on github.com
Maintained by
GitHub, a subsidiary of Microsoft
Typically used for
Routine version bumps, security advisory updates, Actions and Docker base image pins

The honest version

Dependabot pros and cons

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

Where Dependabot is strong

  • Zero to running in one commitA short dependabot.yml at the repo root is all it takes to start getting updates, with no server to run or token to rotate.
  • Security updates separate from version noiseAdvisory-driven updates can be enabled on their own, so you get the alerts that matter without a wall of patch bumps you did not ask for.
  • Deep ecosystem coveragenpm, Yarn, pnpm, Bundler, Composer, pip, Poetry, Go, Cargo, Maven, Gradle, Terraform, Docker and GitHub Actions are all first class, which beats most self-hosted alternatives for breadth.
  • Grouped updates reduce PR floodGrouping rules let you fold related patch and minor bumps into a single PR, which is often enough to make the review load bearable.
  • GitHub-native permissions modelThe bot uses GitHub tokens and permissions, so approvals, reviewers and branch protection just work without additional identity plumbing.
  • Free on public and included on privateThere is no separate SKU on github.com; it is included with the plan, which keeps budget discussions short.

Where Dependabot bites

  • No pause or snoozeIf a release weekend starts and Dependabot is still opening PRs, there is no clean way to tell it to stop other than editing the config, which feels crude.
  • Grouping is limited compared to RenovateGroup by ecosystem and dependency type exists, but you cannot build the detailed matchers Renovate supports, so complex monorepos outgrow the config quickly.
  • Private registry support can be fragileAuthentication to GitHub Packages works easily; authentication to Nexus, Artifactory or a company npm proxy needs careful secrets and sometimes IP allowlisting.
  • Resolution failures are opaqueA rejected update often says only that the bump is not possible, without naming the conflicting peer or indirect dependency that caused it.
  • Review bottleneck is realTeams who do not set a merge policy end up with hundreds of open PRs, which teaches everyone to ignore the bot entirely.
  • Reviewer and permission quirksDependabot PRs cannot assign themselves to code owner reviewers in every configuration, and workflow runs on them follow stricter token scopes which can trip CI.

Sound familiar?

Common Dependabot problems we fix

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

DependencyFileNotResolvable

A version bump cannot be applied

An indirect dependency that pins an incompatible range, a peer dependency that has not released a compatible version yet, or a lockfile that includes multiple copies of the same package.

Update merges with the full dependency tree

private_source_authentication_failure

Dependabot cannot reach a private registry

A missing credential on the Dependabot configuration, an IP allowlist on Nexus or Artifactory that does not include GitHub's egress, or a GitHub Packages scope that expired.

Private packages resolved and updated

update_not_possible: react version conflict

A shared peer dependency blocks an update

A library that locks React to one version and an app that would like a newer one, with no release yet from the library that lifts the peer range.

Conflict resolved or documented

47 open pull requests from dependabot

The repo is drowning in open bot PRs

A default config that opens a separate PR for every bump and no grouping, and no merge automation to handle the patch-level noise.

PR volume matches what the team will merge

Lockfile integrity check failed

Dependabot rebases keep breaking the lockfile

Two concurrent rebases racing on the same lockfile, or a package manager version mismatch between what Dependabot runs and what CI runs.

Lockfiles rebuild cleanly on rebase

token lacks workflow:write

Reviewers or labels cannot be assigned

A permissions boundary on the Dependabot token that does not allow writing to workflow files, labels or reviewers, which is a common surprise after a repo settings change.

Bot permissions aligned with policy

run exceeded 45 minute timeout

Dependabot jobs time out on a large monorepo

A monorepo being updated as one job, a package manager that reinstalls everything on each attempted update, or a slow private registry adding latency to every fetch.

Jobs finish within budget

rebase failed: merge conflict

Rebases fail when humans edit the lockfile

A developer committing a lockfile change in parallel with the bot, leaving Dependabot's branch unable to rebase without a human.

Rebase strategy agreed with the team

What we do

Dependabot help, from config to merge policy

Call in on one noisy repo, or let us set Dependabot up across the org.

Rescue
Hundreds of open bot PRs, lockfiles broken on rebase, or a private registry Dependabot cannot reach. We get it back under control and keep it there.
Configuration
dependabot.yml tuned per repo, with grouped updates for patch and minor bumps, ignored breaking releases flagged, and reasonable schedules.
Private registries
Credentials and allowlisting for Nexus, Artifactory, GitHub Packages, JFrog and private npm proxies, documented and rotated on a schedule.
Merge automation
Auto-merge on green CI for patch bumps where the risk is low, with manual review preserved for majors and production dependencies.
Renovate migration
Honest advice on whether a repo has outgrown Dependabot and should move to Renovate, and the migration done without a gap in coverage.
Managed Tech
Weekly review of outstanding updates, triage of security advisories, and a team to call when a Dependabot change broke something in production.

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 Dependabot alongside something else?

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

Questions

Dependabot questions

Something else? Call+1 737 727 7327

Why can Dependabot not resolve this update?

In most cases a peer dependency has not released a compatible version yet, or an indirect dependency pins a range that excludes the new one. The error message does not name the culprit; the quickest route is to run the update locally and watch the resolver output, which identifies the exact conflict and whether it can be side-stepped with an override.

How do we stop Dependabot from drowning us in pull requests?

Group patch and minor bumps into a single PR per ecosystem, set the schedule to weekly rather than daily, and enable auto-merge on green CI for low-risk updates. The combination usually cuts the open PR count by an order of magnitude without missing any updates that matter.

Why can Dependabot not reach our private npm or Maven registry?

Either the registries entry in dependabot.yml is missing or has an incorrect credential reference, or the private registry has an IP allowlist that does not include GitHub's outbound range. Both show up as authentication failures; the remedy depends on which it is, and we check them in that order.

Should we use Dependabot or Renovate?

Dependabot is a strong default on GitHub for straightforward repos. Renovate is the better fit once you need complex grouping, custom package rules, multiple ecosystems treated differently, or support for Bitbucket and GitLab in the same workflow. We will say plainly which one suits a given repo rather than defaulting to either.

Why do Dependabot rebases keep failing?

Usually a human committed a lockfile edit in parallel with the bot, or the package manager version in the bot environment differs from what CI uses. Agree a policy that humans do not touch lockfiles during the update window, and pin the package manager version in CI and in dependabot.yml so they rebuild identically.

How much does Dependabot help cost?

The initial estimate is on the house. Point us at the repository and tell us where the bot is causing pain, and we come back with a price before any engineering work begins.

Free estimate

Dependabot 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.