Now in trial — OpenAI SDK

Your dependencies broke.
The pull request is already open.

Drift watches the SDKs you depend on. When one ships a breaking change, it finds every affected line in your code and opens a migration pull request — the mechanical fixes done, the judgment calls flagged.

Today: OpenAI SDK. Stripe, Twilio & more in development.
index.js · migrate openai to 6.0.0
opened by Drift
1-const { Configuration, OpenAIApi } = require("openai");
1+const OpenAI = require("openai");
2
3-const configuration = new Configuration({ apiKey });
4-const openai = new OpenAIApi(configuration);
3+const openai = new OpenAI({ apiKey });
5
6-const res = await openai.createChatCompletion({ … });
6+const res = await openai.chat.completions.create({ … });
How it works

From a release note to a reviewable diff.

Install Drift on a repo and it works on its own. No dashboard to check, no config to write — the pull request shows up where you already review code.

01 — WATCH

A release ships

Drift tracks the SDKs your repo depends on and notices the moment a new major version lands on npm.

02 — READ

Read the breaking changes

It reads the release notes and pulls out exactly what broke — renamed methods, removed classes, moved imports.

03 — SCAN

Find every affected line

It scans your codebase for the calls that changed, so it only touches files that actually use them.

04 — OPEN

Open the pull request

It rewrites each affected file and opens a PR you review and merge. Your CI is the source of truth.

What it fixes

It fixes what's mechanical. It flags what needs you.

Most of what breaks in a version upgrade is a find-and-replace a machine can do safely. The rest needs a human. Drift knows the difference — and never guesses on the calls that matter.

Fixed automatically

Mechanical changes

Deterministic rewrites with one right answer. Drift applies these and opens the PR.

  • Renamed methods
  • Removed classes
  • Moved imports
  • Restructured namespaces
Flagged for review

Semantic changes

Behavior shifts that need a decision. Drift points them out instead of guessing.

  • Changed defaults
  • Caching behavior
  • Timing & retries
  • Anything that needs judgment
Install

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.

1

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.

2

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.

3

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.

Stop migrating SDKs by hand.

Trial release · OpenAI SDK supported today