After moving a spec from OpenAPI 3.0.3 to 3.1.0, nullable fields break older code generators
Compatibility boundary between nullable: true and JSON Schema type arrays I maintain an OpenAPI document that describes a REST API consumed by several downstream teams, each running their own validation and code-generation pipelines. The spec currently declares openapi: 3.0.3 and uses nullable: true on a number of schema properties. I want to adopt 3.1.0, wh