NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Modern OpenAPI types
Last release 2 days ago
12 Oct 2026
Release timing varies
gaps range from 2 weeks to 3 months
Nearly every release is documented
notes for 42 of 42 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
42 releases · first in 2024
One column per month.
### Patch Changes - #10529: Align import and export ordering with the Biome checks. - #10520: Sort imports and exports to satisfy the Biome checks. -
### Patch Changes - #10273: Accept valid OpenAPI 3.1 and 3.2 schemas with JSON Schema core keywords, references with sibling keywords, custom formats,
### Patch Changes - #9886: Fix empty $dynamicRef array items in the Models section. A model that binds a generic template's item type through a $ref s
$dynamicRef array items in the Models section. A model that binds a
generic template's item type through a $ref sibling $defs (a named
Paginated<User>) lost that binding while resolving the schema for display, so
the item rendered empty. The model now keeps the binding and shows the bound type.### Patch Changes - #9941: Republish every package through npm trusted publishing. No functional changes.
### Patch Changes - #9733: fix: add explicit .js file extensions to relative imports in the published 2.0, 3.0, 3.1 and 3.2 type declarations, so they
.js file extensions to relative imports in the published 2.0, 3.0, 3.1 and 3.2 type declarations, so they resolve with moduleResolution: nodenext and node16### Patch Changes - #9719: docs: update the Scalar platform overview block in the README
### Patch Changes - #9710: Republish so the updated README (with the Scalar platform overview) reaches npm. Also renames the README generator metadata
readme to scalarReadme: npm treats a readme field as the readme text itself, so affected packages were published with a literal [object Object] readme on the registry instead of README.md.OpenAPI 3.1 schemas are JSON Schema, where true and false are valid schemas (true allows any instance, false allows none). The SchemaObject type now a
#9378: fix: allow boolean schemas in OpenAPI 3.1 types
OpenAPI 3.1 schemas are JSON Schema, where true and false are valid schemas (true allows any instance, false allows none). The SchemaObject type now accepts booleans anywhere a schema is expected, matching the existing 3.2 behavior.
Also tightens MultiTypeObject in the strict 3.1 and 3.2 schema types so that type is a required PrimitiveSchemaType[] (the single-type case is already
#9261: Add schema discriminator helpers (isObjectSchema, isArraySchema, isStringSchema, isNumberSchema, isIntegerSchema, isNumericSchema, isBooleanSchema, isNullSchema, isMultiTypeSchema, isUntypedSchema, isBooleanJsonSchema) for narrowing SchemaObject unions across OpenAPI 2.0, 3.0, 3.1, and 3.2.
Also tightens MultiTypeObject in the strict 3.1 and 3.2 schema types so that type is a required PrimitiveSchemaType[] (the single-type case is already covered by the dedicated variants), and removes MultiTypeObject from the strict 3.0 schema since OpenAPI 3.0 does not support multi-type schemas.
### Minor Changes - #8942: feat: export new stricter openapi types ### Patch Changes - #8949: fix 3.0 parameter object typing for in and style to use
### Minor Changes - #8641: remove experimental zod schema entrypoints from openapi-types ### Patch Changes - #8664: refactor: replace wildcard export
### Patch Changes - #8466: chore: new build pipeline
### Minor Changes - #8322: chore: bump required node version to >=22 (LTS)
### Patch Changes - #8275: fix(openapi-types): make the $ref property in the ReferenceObject type required
$ref property in the ReferenceObject type required### Patch Changes - #7506 `72cd82f` Thanks @marcalexiei! - fix: use caret version for zod
72cd82f Thanks @marcalexiei! - fix: use caret version for zod### Patch Changes - #7453 `a164d76` Thanks @hanspagel! - fix: exclusiveMinimum and exclusiveMaximum allow booleans
a164d76 Thanks @hanspagel! - fix: exclusiveMinimum and exclusiveMaximum allow booleans### Patch Changes - #7116 `2239843` Thanks @baywet! - docs adds a mention that OpenAPI 3.2.0 is now supported
f69e7cc: adds support for OpenAPI 3.2.0 definitions
15c4240: feat: adds vesion 3.1.2 to the type definitions
008a0f3: feat: migrate to Zod 4
ccf875a: feat: support x-scalar-credentials-location extension
591562f: feat: add support for x-scalar-security-body extension
2d7f995: refactor: use more common straight apostrophe ' instead of the real apostrophe ’
533469b: refactor: decouple request code block from the state (not in use yet)
### Patch Changes - 221e35f: feat: added webhooks
05c22c7: chore: removed enum from http methods
4440949: chore: bumping packages
cb9428c: Support additional query parameters for the OAuth authorization request (prompt, audience, anything), and handle OAuth authorization denials
8c7bad8: chore: move build tooling to esbuild
fa8ed84: feat: custom OpenAPI extension to add SDK setup instructions
e62e677: feat: OpenAPI-compliant Zod Schemas
### Patch Changes - c10bbf5: chore: code style
### Patch Changes - e350f23: chore: code style
f9bf5f1: feat(api-reference): implement rendering of patternProperties
patternProperties13333e6: feat: add http methods
a607115: feat: add openapi 3.0.4 and openapi 3.1.1
2b540b9: Include 3.0.3 in allowed OpenApiV3 versions
3.0.3 in allowed OpenApiV3 versions8759e7f: chore: use build tooling scripts
### Patch Changes - e911047: Add default exports
dc9aff2: feat: expose HeadersObject
b4f9f97: feat: new @scalar/openapi-types package
a8db3b0: feat(openapi-types): add openapi-types package with temporary old parser types
Your coding agent can read these notes before it upgrades. Set up the MCP server →