pypi / openapi-schema-validator
openapi-schema-validator
What changed in openapi-schema-validator 0.7 to 0.9, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-24.
8 breaking4 new APIs and options2 performance3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initopenapi-schema-validator 0.92 changes
Breaking changes 2
In OpenAPI 3.1 and 3.2, discriminator is only a hint or annotation and no longer drives schema selection or changes validation outcomes.
Properties marked as required are now enforced during validation.
openapi-schema-validator 0.83 changes
Breaking changes 1
By default, validate uses a local-only empty registry and does not retrieve remote $ref targets. Pass an explicit registry to resolve external references, or set allow_remote_references=True to accept jsonschema's default remote retrieval behavior.
Performance 2
An optional schema-check fast path speeds up validate().
validate() is sped up with validator caching.
openapi-schema-validator 0.712 changes
Breaking changes 5
OAS 3.0 byte format validation now enforces strict base64.
The official OAS 3.2 dialect is supported and set as the default.
With schema type string, OAS30Validator now accepts only str; previously it accepted both str and bytes.
Drops support for Python 3.8 and 3.9.
False values for readOnly and writeOnly are ignored.
New APIs and options 4
An optional ecma-regex backend enables strict OpenAPI pattern validation.
Adds OAS 3.1 dialect registration and validator discovery.
Adds the OAS32Validator API for validating OpenAPI 3.2.0 documents.
Adds a strict validator for OAS 3.0 schemas.
Fixes and other changes 3
Fixes discriminator handling for non-object instances.
Adds support for Python 3.12, 3.13, and 3.14.
Narrows handling around unresolved references.