Skip to content

fix(ci): fix generation of swagger-ui page #2141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Conversation

Alenar
Copy link
Collaborator

@Alenar Alenar commented Nov 25, 2024

Content

This PR fixes our swagger ui page, https://mithril.network/openapi-ui/, that has been broken since merging #2062:

image

The faulty PR modified the version of our openapi file to 3.1.1, but the action that we use (Legion2/swagger-ui-action@v1) is configured by default to use swagger ui version 3 or up, said swagger ui is only compatible with openapi 3.1 since version 5.

Pre-submit checklist

  • Branch
    • Commit sequence broadly makes sense
    • Key commits have useful messages
  • PR
    • Self-reviewed the diff
    • Useful pull request description
    • Reviewer requested

Since #2062 the version of our openapi file is `3.1.1` but the action
that we use (`Legion2/swagger-ui-action@v1`) is configured by default to
use swaggerui version 3 or up and swagger ui is only compatible with
openapi 3.1 since version 5.
@Alenar Alenar self-assigned this Nov 25, 2024
Copy link

Test Results

    4 files  ±0     51 suites  ±0   11m 55s ⏱️ +15s
1 455 tests ±0  1 455 ✅ ±0  0 💤 ±0  0 ❌ ±0 
1 666 runs  ±0  1 666 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0db650b. ± Comparison against base commit ad40680.

@Alenar Alenar temporarily deployed to testing-preview November 25, 2024 14:40 — with GitHub Actions Inactive
@Alenar Alenar temporarily deployed to testing-sanchonet November 25, 2024 14:40 — with GitHub Actions Inactive
@Alenar Alenar merged commit 67d7501 into main Nov 25, 2024
47 of 48 checks passed
@Alenar Alenar deleted the djo/fix-swagger-ui-build branch November 25, 2024 14:41
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.

4 participants