From df80022e52b19dbca3cc1895069bbf8ec4305cfc Mon Sep 17 00:00:00 2001
From: Phil Sturgeon <67381+philsturgeon@users.noreply.github.com>
Date: Thu, 24 Sep 2026 12:19:28 +0100
Subject: [PATCH] guide: fastify supports OpenAPI v3.2 now

---
 openapi/frameworks/fastify.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/openapi/frameworks/fastify.mdx b/openapi/frameworks/fastify.mdx
index c674cb45..1620726b 100644
--- a/openapi/frameworks/fastify.mdx
+++ b/openapi/frameworks/fastify.mdx
@@ -20,7 +20,7 @@ Once the Fastify OpenAPI plugin has generated the OpenAPI document from those ex
 
 Here is what we will cover:
 
-1. Install and configure `@fastify/swagger`, and don't worry it supports OpenAPI v3.x.
+1. Install and configure `@fastify/swagger`, and don't worry it supports OpenAPI v3.2.
 2. Generate an OpenAPI document from route schemas.
 3. Add reusable component schemas with `fastify.addSchema()`.
 4. Define stable `operationId` and tags for SDK ergonomics.
@@ -54,7 +54,7 @@ The specific versions of packages will change over time, but these are the versi
   "dependencies": {
     "@fastify/autoload": "^6.3.0",
     "@fastify/sensible": "^6.0.0",
-    "@fastify/swagger": "^9.7.0",
+    "@fastify/swagger": "^9.9.0",
     "@scalar/fastify-api-reference": "^1.25.11",
     "fastify": "^5.8.0",
     "fastify-cli": "^8.0",
@@ -86,7 +86,7 @@ import scalar from "@scalar/fastify-api-reference";
 export default fp(async (fastify) => {
   await fastify.register(swagger, {
     openapi: {
-      openapi: "3.1.2",
+      openapi: "3.2.0",
       info: {
         title: "Train Travel API",
         description: "API for finding and booking train trips across Europe.",
@@ -130,7 +130,7 @@ What happens next will depend very much on how the routes are defined and how mu
 
 ```json
 {
-  "openapi": "3.1.2",
+  "openapi": "3.2.0",
   "info": {
     "title": "Train Travel API",
     "description": "API for finding and booking train trips across Europe.",