@scalar/openapi-upgrader

0.2.13

Patch Changes

#9827: Convert nullable $ref patterns to the 3.1 null-union form when upgrading from OpenAPI 3.0 to 3.1

0.2.12

Patch Changes

#9758: fix: stop the 3.0 to 3.1 upgrade from mangling non-schema nodes

The upgrade applied its schema transforms to every object node, regardless of where it sat in the document. Three cases are now handled correctly:
- Members named example inside a map of named subschemas (properties, patternProperties, $defs, definitions, and components/schemas) are names, not the example keyword, so they are no longer rewritten into an examples array.
- Data held by the example, default, const, and enum keywords, and by an Example Object's value, is left untouched instead of being walked as if it were a schema (which turned nullable: true into a type array, collapsed exclusiveMinimum, renamed a nested x-webhooks, and so on).
- x-webhooks is only renamed to webhooks at the document root, not wherever a key happens to share that name.

0.2.11

Patch Changes

#9719: docs: update the Scalar platform overview block in the README

0.2.10

Patch Changes

#9710: Republish so the updated README (with the Scalar platform overview) reaches npm. Also renames the README generator metadata in package.json from 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.

0.2.9

0.2.8

0.2.7

Patch Changes

#9043: chore: move test documents to cdn

0.2.6

0.2.5

Patch Changes

#8825: chore: moving files around in preparation for the big deletion of client v1

0.2.4

0.2.3

Patch Changes

#8622: fix: swagger 2.0 mixed media types for produces & examples

0.2.2

Patch Changes

#8502: feat: transforms x-examples keyed by example name

0.2.1

Patch Changes

#8466: chore: new build pipeline

0.2.0

Minor Changes

#8322: chore: bump required node version to >=22 (LTS)

Patch Changes

Updated Dependencies

@scalar/openapi-types@0.6.0
- #8322: chore: bump required node version to >=22 (LTS)

0.1.11

Patch Changes

#8326: feat: keep named request examples when upgrading from Swagger 2.0

Updated Dependencies

@scalar/openapi-types@0.5.4
- #8275: fix(openapi-types): make the $ref property in the ReferenceObject type required

0.1.10

Patch Changes

#8272: feat: migrate swagger 2.0 response examples

0.1.9

Patch Changes

#8251: feat: migrate swagger 2.0 defaults for parameter

0.1.8

Patch Changes

#7842: feat: migrate swagger 2.0 responses

0.1.7

Patch Changes

#7739: fix: upgrade form to multipart/form
#7694: feat: migrate x-example and x-examples

0.1.6

Patch Changes

Updated dependencies [72cd82f]:
- @scalar/openapi-types@0.5.3

0.1.5

Patch Changes

Updated dependencies [a164d76]:
- @scalar/openapi-types@0.5.2

0.1.4

Patch Changes

#7215 11a6e64 Thanks @luke-hagar-sp! - fix: don't upgrade "example" if it's just a key
#7092 134ff5f Thanks @baywet! - feat - upgrader - adds support for migrating XML nodes to 3.2.0
Updated dependencies [2239843]:
- @scalar/openapi-types@0.5.1

0.1.3

Patch Changes

Updated dependencies [f69e7cc]
- @scalar/openapi-types@0.5.0

0.1.2

Patch Changes

Updated dependencies [15c4240]
- @scalar/openapi-types@0.4.1

0.1.1

Patch Changes

Updated dependencies [008a0f3]
- @scalar/openapi-types@0.4.0

0.1.0

Minor Changes

6221e4a: hello world :)
02085ef: feat: add OpenAPI 3.1 > 3.2 upgrader (not enabled by default)

Patch Changes

2d612e4: fix: consumed media types are not deleted for non-existing body parameter and referenced parameter is added empty schema object

Getting Started