chore: re-gen openapi spec to update the version

RELEASE.md

@@ -34,6 +34,7 @@ For `1.0.0` and beyond, this should work differently. Maybe even before. However
 In a nutshell, the steps are:
 
 * Ensure the cargo versions are aligned with the release tag that we create next
+* Re-generate the OpenAPI spec, as it contains the version
 * Tag the release
 * Push the tag
 
@@ -71,6 +72,12 @@ If the result looks good, execute the changes using:
 cargo release version alpha -x
 ```
 
+Update the OpenAPI spec by regenerating it:
+
+```bash
+cargo xtask generate-schemas
+```
+
 Commit the changes to git:
 
 ```bash

openapi.yaml

@@ -4,7 +4,7 @@ info:
   description: Software Supply-Chain Security API
   license:
     name: ''
-  version: 0.1.0-alpha.12
+  version: 0.1.0-alpha.13
 paths:
   /api/v1/advisory:
     get: