The API change that looked harmless in reviewNobody on the team thought the change was risky. One field removed from a response. One header now required. The diff was four lines, the tests passed, two people approved it. What nobody could see inOct 21 · 4 min readimpactgate.hashnode.dev
I built 13 labelled OpenAPI breaking-change cases, and oasdiff missed 2 of themI'm working on Impact Gate, a warn-only PR check that tells you which consumers an API change can affect. Before claiming anything about it, I wanted a public set of cases anyone can run. So I wrote oOct 18 · 2 min readimpactgate.hashnode.dev
The two API changes oasdiff let through, and why consumers still breakLast week I ran oasdiff on 13 labelled API change cases I wrote. It caught 8 of the 10 breaking ones (oasdiff v1.33.0, default ERR-level gate) and missed 2. This post is about those 2, because they poOct 16 · 3 min readimpactgate.hashnode.dev
