Many companies with more than a handful of services end up with a channel like #api-changes . Producer teams post there before a breaking change. It's the responsible thing to do, and it's what most of us were taught: announce early, announce widely.
Widely is the problem. An announcement is written for everyone, so it gets read as if it were for no one in particular. What you actually need is to reach the few teams whose code breaks, and a post written for everyone is a poor way to find them.
We build Graphwake , which tells the teams that consume an API when a change in its OpenAPI spec is about to break them. Here's what we learned about why the shared channel stops working, and what to do instead.
Why the announcement channel feels right
It's cheap: one post, no list to keep, and you don't need to know who your consumers are. It's visible, since anyone can scroll back and see what changed. And it covers you.β¦