patch-itUse patch-it

Next to the tools you already use.

Two comparisons. The first is with version bots, which stop at the version number. The second is with hosted bots that do a similar job a different way, where the honest answer is that it depends on what you care about.

Version bots bump the version. patch-it changes the code that breaks.

Dependabot and Renovate open a pull request with a new version number and stop there. When the bump breaks your code, the checks fail and the pull request waits for an engineer. patch-it writes the code change, and it also fires when there is no version to bump.

dependabot bot

Bump stripe from 15.6.0 to 16.0.0

requirements.txt

−stripe==15.6.0

+stripe==16.0.0

  • CI passes
  • Checkout fails once it ships: billing/checkout.py still sends payment_method_types
patch-it bot

Remove payment_method_types from Checkout create

billing/checkout.py

session = stripe.checkout.Session.create(

− payment_method_types=["card"],

  • CI passes
  • Checkout keeps working on stripe 16

An example, modeled on a real one: in flathub-infra/website, Dependabot's bump to stripe 16.0.0 passed their CI while their PaymentIntent call still sent the removed parameter. patch-it's pull request had the fix; a maintainer made the same change by hand.

QuestionDependabot and Renovatepatch-it
What sets it offA new version of a package is releasedThe change itself: a changelog entry, an API spec, a shutdown notice, a new major release
What the pull request changesVersion numbers in your manifest and lockfileThe code that breaks
A breaking change in the new versionLeft for you to fixThat's the fix. For package and SDK upgrades it is in testing
When there is no version to bumpNothing happens: there is nothing to bumpIt still fires: a shutdown breaks pinned code too
Who runs your testsYour CI, on the pull requestYour CI, on the pull request, like any PR
Where it runsGitHub (Dependabot) or your own setup (Renovate)Your CI, with your own model key

An example of the gap: when a provider shuts a model down, no package has a new version. Nothing gets bumped, and the code that names the model starts failing anyway. What patch-it notices and fixes today

Hosted bots read your repo on their servers. patch-it reads it on yours.

Several hosted services also open pull requests when something you depend on changes. They are easier to start with. The trade is where your code goes.

QuestionA typical hosted botpatch-it
Where your code is readOn the vendor's servers, through an app with access to the repoIn your own CI runner
Whose model writes the fixThe vendor's, on the vendor's accountYours, on your key and your bill
Setting it upOne clickOne workflow file today. One click when the app opens
How much it coversOften a long list16 providers today, each marked watched only when a plugin really reads its pages
What the vendor holdsDepends on the vendor. Ask themWhat you track, and links to pull requests

A hosted bot is the better pick when

  • you want it running in one click, today;
  • you depend on many providers patch-it doesn't watch yet;
  • a vendor reading your repo is fine under your rules.

patch-it is the better pick when

  • your code can't leave your own infrastructure;
  • you want the model calls on your own key and bill;
  • you'd rather have every watched provider tied to its own source than a long list on trust.

How the private part works and what's watched today