Fix OpenAPI 3.1 spec validation errors#31250
Closed
andig wants to merge 1 commit into
Closed
Conversation
Quote 200 response keys, replace nullable with type arrays, and use examples instead of example for enum schemas. Regenerate mcp/openapi.json.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes 14 spec validation errors flagged by
vacuumlint (quality score 10→69; remaining items are warnings/infos only).Changes in
server/openapi.yaml:200response keys (status codes must be string keys)nullable: true+type: Xwithtype: ["X", "null"](×4) —nullableis removed in OpenAPI 3.1examplesarray instead of singularexampleonLogLevelandPhases— 3.1 schemas follow JSON Schema 2020-12; the singularexamplecaused enum mis-validationserver/mcp/openapi.jsonregenerated viago generate ./server/.🤖 Generated with Claude Code