Skip to content

ci: let the Swagger validator's browser launch #162

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
sk-portkey merged 2 commits into from
Sep 30, 2026
Merged

ci: let the Swagger validator's browser launch #162

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e44b541
ci: let the Swagger validator's browser launch
vrv-panw Sep 29, 2026
a3ed747
ci: pin the Swagger Editor service to v4
vrv-panw Sep 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .github/workflows/validate-openapi.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,19 @@ jobs:
services:
# Label used to access the service container
swagger-editor:
# Docker Hub image
image: swaggerapi/swagger-editor
# Docker Hub image. Pinned to v4: `latest` is now SwaggerEditor 5, which
# serves on port 80 and lacks the v4 error panel the validator reads.
image: swaggerapi/swagger-editor:v4.14.8
ports:
# Maps port 8080 on service container to the host 80
- 80:8080

steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v4
# Ubuntu 24.04 runners block the unprivileged user namespaces Chromium's
# sandbox needs, so the validator's headless browser fails to launch.
- name: Allow Chromium sandbox
run: sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
- name: Validate OpenAPI definition
uses: char0n/swagger-editor-validate@v1
with:
Expand Down
Loading