Stripe names its breaking releases the way meteorologists name storms — alphabetically, on a schedule. Twilio, OpenAI, Shopify, and Slack all break in their own quieter ways. Breakwater tracks all five against your actual code and warns you before it makes landfall in production.
Named system tracking
Every dot below is a real, dated Stripe API release. The gap in between is real too — Stripe doesn't publish a master list, so most teams only ever hear about the one that just hit them.
Built for teams who ship on top of vendors
How a watch is set
Sign in with GitHub and pick which repository — and which vendor it depends on — Breakwater should watch.
Every day, Breakwater checks the vendor's real API version history against your actual code, quietly, in the background.
One email when something concrete changes — the file, the line, why it matters, and the fix. Nothing when there's nothing to say.
What actually changes
The actual gap
Stripe already tells the world when something changes — a changelog entry, an email, a named release. What it doesn't do is open your repository and check whether it's affected.
That translation — from a general announcement to "this line, in this file, needs to change" — is work every team quietly skips until it costs them. Breakwater does that translation automatically, every day, for exactly the code you actually shipped.
src/lib/stripe/client.ts
const stripe = new Stripe(key, {
apiVersion: null,
});
// scanning against 2026-08-26.dahlia…