Alternatives · Dependency bots

Cheer vs Dependabot and Renovate

Dependabot and Renovate open pull requests for every update they find. Cheer’s refresh builds and checks each upgrade first and opens a PR only when it would pass. If your Monday starts with a dozen dependency PRs, this page is for you.

What the bots do well

Both are free, both are widely used, and both are good at noticing that a new version exists. Dependabot alerts and the dependency graph are free on every GitHub plan and worth keeping on. Renovate’s grouping and scheduling rules are mature. The problem isn’t that they open PRs. It is that nothing has been built or tested when they do.

Where the differences show up in practice

When a PR opens
Dependabot and RenovateA PR opens for each update, or each group. Whether it builds is found out by CI on the PR, and whether it breaks anything is found out in review.
CheerThe refresh applies the upgrade in a sandbox, builds it, runs the tests and checks it against your policy. A PR opens only if the result would be cleared.
Which updates
Dependabot and RenovateEvery update the rules allow, on a schedule. Choosing what matters is left to whoever triages the queue.
CheerUpgrades that clear an open finding or an end-of-life check. If nothing would change, nothing is opened.
What you already decided
Dependabot and RenovateIgnore rules per dependency, per repo, with no expiry. A dismissed alert on one repo is new on the next.
CheerAn waiver has a name, a reason and an expiry, and carries across every version. Waived findings don’t come back as new.
What broke
Dependabot and RenovateA failing PR sits in the queue with red checks until someone closes it.
CheerAn upgrade that broke the build stays out of your queue, with the log, and is retried next week.
Across the estate
Dependabot and RenovatePer repo. To see every component that carries a package, you grep lockfiles or run a report.
CheerAsk what a package reaches and get the components, what has been done on each, and which haven’t been scanned.
Where it runs
Dependabot and RenovateBuilds and tests happen in your CI, on each PR.
CheerThe refresh runs in Cheer’s sandbox. Your CI runs once, on the PR that was already built and checked.

Side by side

CheerDependabot / Renovate
Updates
Notices new versionsYesYes
Opens a PR for every updateNo, only ones that would passYes
Builds and tests before the PR opensYesNo
Checks the result against your policyYesNo
Grouping and scheduling rulesOne refresh a week per componentYes
Decisions
Waiver with a name and an expiryYesIgnore rules, no expiry
Decision carries across repos and versionsYesPer repo
Lapsing waivers land in an InboxYesNo
Reach
Which components carry a packageYesPer repo
End-of-life for runtimes and dependenciesYesNo
Cost
PriceRuns and minutes on your planFree
CI minutes spent on failed upgrade PRsNoneEvery PR

Drowning in dependency PRs?

Keep Dependabot alerts on. Turn on the refresh for one component and see what Monday looks like with two PRs instead of twelve.

Refresh · Monday 03:0031 components
payments-api · 9 upgrades, clears 3 findingsPR opened
notify-svc · axios 2.0 broke the buildLeft out
27 components had nothing to do.