Migration status / change

Idempotency keys are required on POST requests

Breaking change · announced Jun 10, 2026

Live since Jun 10
Affected521installed repos using the old API
Migrated93%483 repos
Via Driftfix89%of those who migrated
DeadlinePassedSep 15, 2026

Share of affected installed repos migrated

0%25%50%75%100%Jun 10Jul 1Jul 22Aug 12Sep 2Sep 30DeadlineMigrated · Jun 10: 0%Migrated · Jun 17: 12%Migrated · Jun 24: 23%Migrated · Jul 1: 33%Migrated · Jul 8: 42%Migrated · Jul 15: 51%Migrated · Jul 22: 58%Migrated · Jul 29: 65%Migrated · Aug 5: 71%Migrated · Aug 12: 77%Migrated · Aug 19: 81%Migrated · Aug 26: 85%Migrated · Sep 2: 88%Migrated · Sep 9: 90%Migrated · Sep 16: 92%Migrated · Sep 23: 93%Migrated · Sep 30: 93%
MigratedProjected at this pace

From affected to migrated

Repos using the old API521
Got a Driftfix pull request498
Merged it431
Migrated on their own52
Closed our PR after moving off the old API themselves

How they migrated

Merged a Driftfix PR: 431 (83%)Migrated on their own: 52 (10%)Not yet: 38 (7%) 93%migrated
  • Merged a Driftfix PR431
  • Migrated on their own52
  • Not yet38

Why the rest haven’t migrated yet

Tests failed on the patch12
They got a draft PR showing which tests failed
Your guide doesn’t cover their code9
Adding an example for this pattern to the guide would unblock them
Closed the PR, still on the old API11
Turned Driftfix off6
In progress0

Customers who chose to share their name

RepoStatus
orbit-labs/webMigrated
orbit-labs/apiMigrated
orbit-labs/checkoutMigrated
fernway/checkoutMigrated

Delivery

Live since Jun 10, 2026. Repos that install Driftfix later get this pull request too. Pausing stops new pull requests; the ones already open stay open.

These counts cover repos where your customers installed the Driftfix app, not your whole customer base. You never see customer code, diffs, file paths or test output, and counts under 5 are hidden so no single customer can be picked out. Repos are named only when their owners turned that on.