Drift.
When the SDKs you depend on ship breaking changes, Drift opens the pull request that fixes them — the mechanical breakage handled, the judgment calls flagged.
Every SDK upgrade is an interruption you didn't schedule.
You depend on other people's code. Stripe, OpenAI, Twilio — the SDKs your product is built on. And every so often, one of them ships a new major version that breaks the way you called it. A method gets renamed. A class disappears. An import moves.
So you stop what you're doing, open the migration guide, and spend an afternoon hunting through your codebase for every place that broke — reading changelogs, fixing call sites, hoping you caught them all. It's tedious, it's error-prone, and it's work that almost always has one correct answer.
Drift is built on a simple observation: most of what breaks in an upgrade is mechanical. A rename is a find-and-replace. A removed class has a known successor. A moved import has a new path. These don't need a human — they need to be done carefully and consistently. Drift does exactly that part, automatically, and leaves the genuine judgment calls to you.
From a release note to a reviewable diff.
Install Drift on a repo and it runs on its own. No dashboard to check, no config to write, nothing to run — the pull request shows up where you already review code.
A release ships
Drift tracks the SDKs your repo depends on and notices the moment a new major version lands on npm.
Read the breaking changes
It reads the release notes and pulls out exactly what broke — renamed methods, removed classes, moved imports.
Find every affected line
It scans your codebase for the calls that changed, touching only the files that actually use them.
Open the pull request
It rewrites each affected file and opens a PR you review and merge. Your CI stays the source of truth.
It fixes what's mechanical. It flags what needs you.
This line is the whole product. Drift is confident exactly where a machine should be, and hands back control exactly where a human should have it — so the diffs it opens are ones you can trust.
Mechanical changes
Deterministic rewrites with one right answer. Drift applies these and opens the PR.
- Renamed methods
- Removed classes
- Moved imports
- Restructured namespaces
Semantic changes
Behavior shifts that need a decision. Drift points them out instead of guessing.
- Changed defaults
- Caching behavior
- Timing & retries
- Anything needing judgment
Three steps, then it runs itself.
Drift is a GitHub App. Installing takes under a minute, and the first scan runs the moment you add a repo.
Install the GitHub App →
Add Drift to your account and pick the repos it should watch. It asks only for the access it needs to open pull requests.
Drift scans on install
The moment a repo is added, Drift checks whether it's behind on any SDK it supports and starts a migration if it is.
Review the pull request
A migration PR appears in your repo like any other. Read the diff, let your CI run, and merge when you're happy — or close it and tell Drift it was wrong.