Skip to content

chore(api): regenerate the OpenAPI schema under FastAPI 0.156 - #132

Merged
TranBaDat2607 merged 1 commit into
mainfrom
chore/regen-openapi-fastapi-0.156
Oct 21, 2026
Merged

TranBaDat2607 merged 1 commit into
mainfrom
chore/regen-openapi-fastapi-0.156

Conversation

@TranBaDat2607

Copy link
Copy Markdown
Owner

Why

The Windows CI job's OpenAPI diff-check started failing with no code change (seen on #131). requirements.txt allows fastapi>=0.115.0,<1.0.0, CI now installs 0.156.8, and that version emits the ProviderId alias's description on the four /providers/{provider_id} path parameters. main's last green run predates that release, so main would fail the same check on its next run.

What

Regenerated desktop/src/lib/openapi.json and api-types.d.ts with FastAPI 0.156.8 / Pydantic 2.14.1 (the versions in the failing CI log). 4 added lines each: the provider_id description; in the .d.ts they're doc comments only.

Note

Anyone regenerating locally with an older FastAPI will drop these lines again — upgrade FastAPI before running export_openapi. Pinning FastAPI in requirements.txt would be the alternative if that becomes a nuisance.

🤖 Generated with Claude Code

FastAPI 0.156 emits the ProviderId alias's description on the four
/providers/{provider_id} path parameters. CI installs the latest
FastAPI allowed by requirements.txt, so the committed schema went stale
without any code change and the OpenAPI diff-check fails on every PR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@TranBaDat2607
TranBaDat2607 merged commit b2d5c6d into main Oct 21, 2026
6 checks passed
@TranBaDat2607
TranBaDat2607 deleted the chore/regen-openapi-fastapi-0.156 branch October 21, 2026 10:29
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