Rolling back an OpenAPI schema change without breaking already-generated clients
Assume a REST API documented with OpenAPI 3.0.x, where consumers generate their own clients from the published document. A recent schema change added a new enum value to a response field and made one previously optional request field required. The deployment now needs to be rolled back, but some consumers may have already regenerated clients against the newe
swagger