Skip to content

ci: regenerate frontend api.ts and gate on OpenAPI spec drift - #438

Open
temiport25 wants to merge 1 commit into
ChainForgee:mainfrom
temiport25:ci/openapi-spec-drift-gate
Open

ci: regenerate frontend api.ts and gate on OpenAPI spec drift#438
temiport25 wants to merge 1 commit into
ChainForgee:mainfrom
temiport25:ci/openapi-spec-drift-gate

Conversation

@temiport25

Copy link
Copy Markdown

Summary

The backend-ci already exports the spec and gates on openapi.json drift, but the generated frontend types (api.ts) could silently diverge. This adds a "Regenerate frontend client types" step and updates the drift check to cover both openapi.json and api.ts.

Closes #434

Testing

  • Verified the workflow regenerates api.ts and checks both files for drift
  • Verified the failure message tells the contributor the exact commands to run

Checklist

  • Tests added or updated for new/changed behavior
  • Existing tests pass
  • No secrets, keys, or seed phrases committed
  • Follows the coding conventions in the relevant service README
  • PR is focused on a single concern

The backend-ci already exports the spec and gates on openapi.json
drift, but the generated frontend types (api.ts) could silently
diverge. This adds a 'Regenerate frontend client types' step and
updates the drift check to cover both openapi.json and api.ts.

Closes ChainForgee#434
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.

committed openapi.json drifts from the backend with no CI regen gate: generated client types silently lie

1 participant