PatchFlow turns the breaking SDK release your team keeps postponing into a test-gated draft pull request, with a Migration Proof Report showing the evidence, the exact commit, and every Check.
Humans decide what merges. PatchFlow stops at a draft PR.
Migration Proof Report
merged by a humantypescript
5.9.3
typescript
6.0.2
Ready only on the refreshed head
No second paid agent run · draft PR · patchflow:ready
Built for the upgrades that sit in backlogs · any public npm package
The middle mile, automated
Dependency bots find the update. PatchFlow does the engineering between “new version available” and “safe to review”, and shows its work at every step.
01
A breaking version lands on npm. PatchFlow pins the exact transition.
02
Playbook, vendor migration guide, or release notes, recorded with its evidence class.
03
A bounded coding agent changes the package and its call sites on one scoped branch.
04
Your required GitHub Checks run on the exact head commit. Missing or red means not ready.
05
A draft pull request with a Migration Proof Report. A human reviews and merges.
Built to stop safely
required checks · head 9f3c2e1
typecheckpass on exact commit
testpass on exact commit
smokepass on exact commit
labelled patchflow:ready
Ready means your Checks passed on that exact commit.
Not the agent’s word. PatchFlow reads your required GitHub Checks on the pull request’s head SHA and fails closed on anything missing, pending, cancelled, or red.
playbookStructured before → after
release notesVendor guide or changelog
inferredFlagged for closer review
Every change says what informed it.
Require more review for inferred migrations, or restrict majors until a playbook exists.
Draftchore: migrate stripe to 17
It never merges.
Output is a draft pull request under your branch protection. A human decides.
src/**allowed
package.jsonallowed
.github/workflows/**blocked
retriesbounded
A small, known blast radius.
Diff-scope policy, no edits to CI definitions by default, capped retries and concurrency.
acme/billing-api selected
acme/web selected
acme/infra no access
Only the repositories you pick.
A GitHub App grant per repository. Tokens stay out of clone URLs, logs, and branches.
Repository and branch names above are illustrative.
Not another update alert
A version bump is easy. Understanding the break, changing the right code, and proving it still works is where engineering time goes. That is the part PatchFlow owns.
See how evidence works| Capability | Update bots | General coding agents | PatchFlow |
|---|---|---|---|
| Notices the new version | on request | ||
| Changes the broken call sites | — | ||
| Records what informed the change | — | — | |
| Ready only when your Checks pass on that exact commit | — | self-reported | |
| Stops at a draft PR, by design | configurable | depends on setup | |
| Per-run cost and outcome ledger | — | — |
Measured · owned repository
The first run cost 83.43 cents and changed 16 files. PatchFlow did not call it ready until the repository’s real smoke Check was fixed, rerun, and proven on the refreshed pull-request head.
Evidence from a repository owned by the PatchFlow team; not yet an external customer claim.
Security review, answered
Pricing
Start with the migration your team keeps postponing. Cancel after the pilot month.
One measured, test-gated migration per repository per month, delivered as a draft pull request with a Migration Proof Report.
They can write a change. PatchFlow's job is the proof around it: which breaking changes apply, a bounded scope, your own Checks recorded on the exact commit, and a report a reviewer can trust. If your team already does that reliably with an agent, you may not need us.
They bump the version and tell you it moved. The engineering work, finding and fixing the call sites the release broke, is still yours. PatchFlow does that part, and works alongside them.
A GitHub App installed on the repositories you select. Every output is a draft pull request. The trust centre lists every subprocessor, including the coding-agent provider.
It can't merge. Your required Checks decide whether a run is ready, and a failed or stopped run is shown as failed, never as ready. You review under your own branch protection.
Public npm packages in GitHub repositories today. We would rather do one ecosystem properly than many badly.
The PatchFlow control plane runs in AWS Sydney. Coding-agent execution and GitHub are overseas subprocessors, disclosed on the subprocessors page.
Field notes
What a real private-pilot migration cost, where it failed, and why a red check was the most useful result.
Field report · TypeScript
Version detection is useful. Breaking upgrades still leave teams with evidence gathering, call-site changes, and CI interpretation.
Dependency management · Engineering productivity
Why migration verdicts must be bound to immutable pull-request heads—and what to do when the base branch advances.
CI · Security model
Your backlog has one of these
A 20-minute assessment tells you whether it’s a fit. If it isn’t, we’ll tell you why.