I built DriftaBot after watching consumer products — web and mobile — silently break when backend API changes shipped without warning. The frustrating part? Unit tests and integration tests couldn't help. They test what you own, not what downstream consumers depend on. E2E tests might catch it, but they run at release time — by then the breakage is already in the codebase of every consumer, and fixing it becomes a scramble across multiple teams. I wanted to catch breaking API changes at the earliest possible moment: the pull request itself — before anything merges. DriftaBot runs in CI on every provider PR. If a breaking change is detected, it automatically opens a GitHub Issue in every consumer repo that references the affected endpoint, with the exact file and line number where the breakage will occur at runtime. Consumer teams know immediately. No release-day surprises. No emergency rollbacks. The goal was zero friction on the consumer side — they don't install anything or change their setup. The fix happens upstream, before it ever reaches them. Would love to hear if others have dealt with this. Happy to answer any questions!

DriftaBot Agent

Auto-open GitHub Issues when your API breaks consumers

Auto-open GitHub Issues when your API breaks consumers