Skip to content

fix: Go SDK validation uses the fresh FOAS instead of the stale committed spec #1474

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
oarbusi merged 1 commit into from
Sep 4, 2026
Merged

fix: Go SDK validation uses the fresh FOAS instead of the stale committed spec #1474

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions .github/workflows/required-spec-validations.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,10 @@ jobs:
id: go-sdk-validation
run: |
cp -rf "openapi-foas.yaml" "atlas-sdk-go/openapi/atlas-sdk.yaml"
# Point the SDK generation pipeline at the freshly built FOAS.
# Without this, generate.sh falls back to its default and
# validates the stale atlas-api.yaml committed in the SDK repo.
export OPENAPI_FILE_NAME="atlas-sdk.yaml"
pushd atlas-sdk-go
make -e openapi-pipeline
popd