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.pystill sendspayment_method_types
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.
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.
requirements.txt
−stripe==15.6.0
+stripe==16.0.0
billing/checkout.py still sends payment_method_typesbilling/checkout.py
session = stripe.checkout.Session.create(
− payment_method_types=["card"],
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.
| Question | Dependabot and Renovate | patch-it |
|---|---|---|
| What sets it off | A new version of a package is released | The change itself: a changelog entry, an API spec, a shutdown notice, a new major release |
| What the pull request changes | Version numbers in your manifest and lockfile | The code that breaks |
| A breaking change in the new version | Left for you to fix | That's the fix. For package and SDK upgrades it is in testing |
| When there is no version to bump | Nothing happens: there is nothing to bump | It still fires: a shutdown breaks pinned code too |
| Who runs your tests | Your CI, on the pull request | Your CI, on the pull request, like any PR |
| Where it runs | GitHub (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
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.
| Question | A typical hosted bot | patch-it |
|---|---|---|
| Where your code is read | On the vendor's servers, through an app with access to the repo | In your own CI runner |
| Whose model writes the fix | The vendor's, on the vendor's account | Yours, on your key and your bill |
| Setting it up | One click | One workflow file today. One click when the app opens |
| How much it covers | Often a long list | 16 providers today, each marked watched only when a plugin really reads its pages |
| What the vendor holds | Depends on the vendor. Ask them | What you track, and links to pull requests |