Skip to content

Blog

Notes on shipping API changes safely

Engineering essays, checklists and lessons from building change verification for the API economy.

Engineering5 min read

Inside a behavioral diff: what to compare and what to ignore when replaying API traffic

A behavioral diff is only useful if it ignores noise and catches real changes. How to normalize IDs, timestamps, ordering, headers, latency and secrets.

Read post →

Engineering5 min read

Deterministic verification vs LLM-as-judge for code changes

A model grading its own patch is not evidence. Why code changes need deterministic, reproducible verification, and where LLMs still earn their place.

Read post →

Guides5 min read

How API providers can cut their customers' migration time

Every breaking change costs your customers engineering time. Machine-readable changelogs, OpenAPI diffs, codemods and automated PRs shrink that cost.

Read post →

AI6 min read

Why AI agents make API changes more dangerous

AI agents call tools backed by real APIs. When those APIs drift, agents fail quietly or act confidently wrong. Here is how to version, check and replay.

Read post →

Guides5 min read

How to ship a breaking API change without burning your consumers

A provider checklist for breaking API changes: announcing, Deprecation and Sunset headers, precise changelogs, migration tooling, dual running and removal.

Read post →

Engineering5 min read

Your tests passed. Your migration still broke production.

Mocks encode the old API, so migration tests pass while production breaks. A worked billing example shows behavioral vs contract breaks and how to catch both.

Read post →

Engineering5 min read

The hidden cost of an API breaking change, for the people who consume it

An API breaking change looks like a one-line fix. For consumers the hours go to discovery, finding call sites, patching, verifying, rollout and incidents.

Read post →

Company4 min read

Why API change verification needs to be its own category

Detecting API breaking changes is largely solved and patches are getting easier to write. Proving a migration did not change behavior is the missing step.

Read post →

Coming soon

Ship API changes without breaking your customers.

Releo is in private beta. Join the waitlist for early access.