3.91.1
(fix): Fix coerce-optional-schemas-to-nullable incorrectly making header parameters
nullable. HTTP headers don’t have a “null” concept — they’re either present with
a value or absent. The coerceOptionalSchemasToNullable option now only affects
request/response body properties, not header parameters. Explicitly nullable header
schemas (via nullable: true in the OpenAPI spec) are still respected.