Breaking API changes, turned into tested pull requests

Versyka — Thu, 22 Oct 2026 14:13:10 +0000

Every app lean on other companies' APIs: payments, email, auth, cloud, AI models. Those vendors ship breaking changes on their own schedule. A method disappears, a parameter is renamed, a model ID stops answering. Your build breaks, and someone spends a day in a migration guide.

Dependabot and Renovate bump the version number. When the new version has breaking changes, that upgrade PR fails, and a person still has to rewrite the code. That rewrite is the part we automated.

Versyka also works alongside them: on every Dependabot or Renovate pull request it comments with what the release changes and whether your code uses it, with file and line. "Check before merging", or nothing your code uses changed.

What Versyka does

When an SDK your code uses ships a breaking change, Versyka:

Reads the vendor's changelog or migration guide and turns it into a migration rule.
Finds every affected call site with ast-grep. This step is deterministic: structural search, not the model, decides which files are touched.
Rewrites only those call sites with Claude, inside a disposable sandbox.
Runs your own checks: typecheck, build and tests. If they fail, the errors go back for another attempt, up to three times.
Opens a pull request only if the checks pass. It never pushes to your default branch. If the checks never pass, you get a note about what blocked it instead of a broken PR.

What it watches

A daily scan of your repositories flags:

Every package your app runs on, including SDKs from 100+ API vendors (Stripe, OpenAI, AWS, Twilio, Slack, Supabase and more), when a stable new major version is out or yours is deprecated
Python and Node.js versions that reach end of life
Vulnerable packages, from OSV.dev, grouped into the upgrades that fix them
AI models about to be retired, with shutdown dates from OpenAI, Anthropic, Google, Mistral and Cohere, plus AWS Bedrock, Azure, Groq and Together AI

Every Monday it also sends one pull request per repository with the minor and patch upgrades of the packages you use, each explained and tested. Retiring AI models with a direct replacement are swapped for free, before you ask.

An example

The demo is a recorded run: an SDK in the style of the OpenAI Python v0 to v1 change removes its module-level calls. The tests fail. Versyka finds four call sites in three files, rewrites them, the tests go green, and the diff lands as a pull request. Watch it at versyka.com/demo.

Free tools, no signup

Upgrade check: paste a package.json or requirements.txt and see which API SDKs are major versions behind, with release notes.
AI model retirement calendar: every announced shutdown date, and a check that finds the model IDs your repository still calls.
SDK tracker: latest versions for 100+ API vendors' SDKs.
GitHub Action and MCP server: the same checks in your CI or your coding agent.

Where it stands

Versyka works with TypeScript, JavaScript, Python, Go, Java and Kotlin repositories, on GitHub or GitLab. The free plan covers 5 repositories, 2 migration pull requests a month, and unlimited version upgrades. We're running free pilots with a few teams. If you have an SDK upgrade you keep putting off, we'd like to run it on your repo.

We'd also like to hear where this breaks for you: monorepos, generated code, repositories with few tests. Comments are open.