Skip to content

fix: regenerate client from updated forge-dashboard spec #121

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
alrayyes merged 1 commit into from
Oct 5, 2026
Merged

fix: regenerate client from updated forge-dashboard spec #121

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion openapi/SPEC_COMMIT
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
e3ee3e3875c65499e5b9daad5f56c329d18ff36e
05b8317c466daafb9fa4e7be2a6aad0909dda7a4
5 changes: 5 additions & 0 deletions openapi/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ info:
CI status), open issues, and per-forge reachability. The backend holds
both forges' credentials; the frontend only ever calls the endpoints
below.

A request body is capped at 1 MiB, except the forges' own webhook
deliveries (5 MiB). A body whose declared length is over the cap is
answered `413` with an `Error` before it is read; one with no declared
length is cut off at the cap and answered as an invalid body.
version: 1.0.0
contact:
name: forge-dashboard
Expand Down
Loading