Add 3.2 support

.github/ISSUE_TEMPLATE/add_tool_request.md

@@ -6,7 +6,7 @@ labels: ""
 assignees: ""
 ---
 
-> **Please use this template for tools that cannot be tagged on GitHub. If your tool is on GitHub use the `openapi3` and `openapi31` tags to allow your data to be collected automatically.**
+> **Please use this template for tools that cannot be tagged on GitHub. If your tool is on GitHub use the `openapi3`, `openapi31`, and `openapi32` tags to allow your data to be collected automatically.**
 
 ## Tool Properties
 
@@ -21,6 +21,7 @@ assignees: ""
 
 > **Please indicate the versions of OpenAPI supported by your tool by marking them true or false below.**
 
+- 3.2: false
 - 3.1: false
 - 3.0: false
 - 2.0: false

README.md

@@ -27,6 +27,7 @@ If you want your project included in the tooling list tag your project with one-
 - `swagger` or `openapi2` (For Swagger/OpenAPI 2.0 support).
 - `openapi3` (For OpenAPI 3.0 support).
 - `openapi31` (For OpenAPI 3.1 support).
+- `openapi32` (For OpenAPI 3.2 support).
 
 If you aren't familiar with topics in GitHub please follow [this guide](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics) to add them to your repository.
 

gulpfile.js/metadata.json

@@ -24,6 +24,12 @@
       "topic": "openapi31",
       "version": "v3_1"
     },
+    {
+      "title": "openapi32 tags",
+      "processor": "../processors/tagged-repository-processor.js",
+      "topic": "openapi32",
+      "version": "v3_2"
+    },
     {
       "title": "Tooling repository issues",
       "processor": "../processors/open-tooling-repository-issues.js",
@@ -35,4 +41,4 @@
       "processor": "../processors/master-processor.js"
     }
   ]
-}
+}