Skip to content

docs(downgrader): note that a 3.1 document using 3.2 itemSchema needs downgradeSpecV32ToV31 first #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dinwwwh merged 1 commit into from
Oct 30, 2026
Merged

docs(downgrader): note that a 3.1 document using 3.2 itemSchema needs downgradeSpecV32ToV31 first #211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions packages/downgrader/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,7 @@ Schema Objects inside the document convert as in [Schema](#schema-downgradeschem
- Links and discriminator `mapping` values that point into a removed part, and Links that name a webhook operation by `operationId`, are left as written.
- Encoding Objects pass through, although 3.0 serializes `multipart` parts by other defaults: it ignores `style`, `explode`, and `allowReserved` there, and gives an untyped part no `application/octet-stream` default.
- A `security` list whose alternatives all use only mutual TLS is removed. On an operation it then falls back to the document's `security`, and on the document it leaves none, so no security is required.
- A 3.1 document that already uses 3.2 fields, as FastAPI writes `itemSchema` for streaming responses, keeps them as written, and the schemas inside them are not converted. Run `downgradeSpecV32ToV31` on it first.

### Schema (`downgradeSchemaV31ToV30`)

Expand Down
Loading