Skip to content

Render OpenAPI 3.1 specs by upgrading Swagger UI to 5.x - #45

Merged
rferreira merged 1 commit into
mainfrom
raf/bump-spec
May 4, 2026
Merged

rferreira merged 1 commit into
mainfrom
raf/bump-spec

Conversation

@rferreira

Copy link
Copy Markdown
Contributor

Summary

  • The deployed docs site was failing to render v22.yaml with "The provided definition does not specify a valid version field" after the spec was bumped to openapi: 3.1.0 in c379d0f.
  • Root cause: Legion2/swagger-ui-action@v1 defaults to bundling Swagger UI ^3.0.0, which predates OpenAPI 3.1 support.
  • Pinned the action to @v1.3.0 and passed version: ^5.0.0 so the deployed assets are Swagger UI 5.x — handles 3.1 (and renders 3.0.x identically).
  • Applied the same version: ^5.0.0 to the v2.1 render step for consistency, even though 3.0.3 worked under the old default.

Test plan

  • Merge to main, watch the Release workflow deploy to GitHub Pages
  • Open https://scanii.github.io/openapi/v22/ and confirm the spec renders (no version-field error)
  • Open https://scanii.github.io/openapi/v21/ and confirm v2.1 still renders

🤖 Generated with Claude Code

Default Swagger UI ^3.0.0 doesn't understand openapi: 3.1.0,
which broke rendering on the deployed docs site after v22.yaml
was bumped to 3.1.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rferreira
rferreira merged commit e77071c into main May 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant