patch-itUse patch-it

Four steps, every night.

patch-it notices what changed on its own, finds where your code uses it, and leaves you a pull request with the fix an AI model wrote on your key. Below is one real change followed through, on an example repo. The clock is one example night.

  1. 02:14 Notice
  2. 02:15 Find
  3. 02:16 Fix
  4. 09:03 Merge
02:14

Notice

It notices the change on its own.

Every night patch-it reads each provider's own pages: changelogs, API specs, shutdown notices, migration guides, release feeds. Nobody assigns an alert or opens a ticket, and it fires even when there is no version to bump. No blogs, no rumours. A change with no source is not a change.

docs.stripe.com/changelog

2026-09-30.endive

Removes payment_method_types from Checkout Session create.

− Breaking

02:15

Find

It finds the exact line that breaks.

Only code that really uses what changed, at the version you pinned. Lookalikes are left alone, like an Azure deployment that happens to be named gpt-4.

billing/checkout.pyexample repo
21def start_checkout(items, customer):
22 session = stripe.checkout.Session.create(
23 mode="payment",
24 customer=customer.stripe_id,
−25 payment_method_types=["card"],
26 line_items=items,
27 )

billing/checkout.py:25 uses the removed parameter

02:16

Fix

An AI model writes the fix, on your key.

A small pull request that says what broke and when, where, the fix, what wasn't run, and how it was found. When patch-it isn't sure, it opens an issue instead. When the change doesn't touch your code, it says nothing.

Where the fix is written, and what never leaves your CI

Remove payment_method_types from Checkout createexample

What broke: Stripe 2026-09-30.endive removed payment_method_types.

Where: billing/checkout.py:25

− payment_method_types=["card"],

Not run: your tests; your CI will.

[^^] patch-it · the night shift for your dependencies

09:03

Merge

You review it over coffee.

That's your whole job. Your CI runs your tests on the pull request, like any PR. You read a few lines, and you merge it or you don't.

8
pull requests merged by outside maintainers

Counted on 2026-11-19. One of them, in full: finite-sample/rmcp #114, merged 2026-10-19, 2 days after it was opened.

Three possible mornings.

  • A pull request, when patch-it is sure of the fix.
  • An issue, when it isn't sure. It says what changed and where it probably lands.
  • Nothing, when the change doesn't touch your code. Silence beats a wrong PR.

Install the Action.

For teams who want everything inside their own CI. One workflow file and a short list of what you depend on. It runs on your schedule, with your model key as a GitHub secret.

uses: patch-it-dev/patch-it@v1

Read the docs

.github/workflows/patch-it.yml
name: patch-it
on:
  schedule:
    - cron: "17 6 * * *"
jobs:
  patch-it:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: patch-it-dev/patch-it@v1
        with:
          anthropic-api-key: ${{ secrets.ANTHROPIC_API_KEY }}
patch-it.yml
apis:
  - name: stripe
    version: "16.0.0"
  - name: openai-python
    version_range: ">=1,<2"