My OpenAPI differ flagged a breaking change that broke nobody — the enum shrank on the response side
A DEV Community post describes an OpenAPI differ that flagged a breaking change which, according to the author, broke nobody. The specific change the tool flagged was an enum that shrank on the response side. The title frames the piece as an account of that discrepancy: the differ classified the schema change as breaking, while the author reports no breakage resulted. The provided source text is dominated by page-level CSS for the article's theme, including rules for light and dark modes and a retro styling treatment, rather than by the article's technical body. Because of that, the only substantive technical facts available are those stated in the title: the tool is an OpenAPI differ, the flagged change was a response-side enum that shrank, and the author characterizes it as having broken nobody. No tool name, version, enum values, schema details, or consumer impact specifics are present in the supplied excerpt, so none are reported here.
It illustrates that an OpenAPI differ can label a response-side enum reduction as breaking even when, per the author, no consumer broke.