Repository navigation
chore: regenerate openapi spec - #56937
Conversation
There was a problem hiding this comment.
Looks good. On the base, check:generated in packages/protocol fails because the spec is out of date. With this PR it passes in both packages/protocol and services/www. The three spec files got identical changes, and they match the existing permission.saved.update HttpApi endpoint. Regenerating the client produces no changes, since the generated client already has this operation. packages/protocol typecheck passes.
Public API: the OpenAPI spec now documents an endpoint the server already serves. It adds PATCH /api/permission/saved/{id} (permission.saved.update) and the PermissionSavedNotFoundErrorEncoded schema. This is backwards compatible: nothing is removed or changed, and server behaviour is unchanged.
Related: #53105
Problem
The OpenAPI files checked in on
devwere behind the server HttpApi. Thepermission.saved.updateroute was missing from the spec.Change
This only reruns the existing generators (
bun run generateinpackages/protocol,packages/client, andservices/www). The client generator produced no changes.paths: /api/permission/saved/{id}: + patch: permission.saved.update delete: permission.saved.remove components.schemas: + PermissionSavedNotFoundErrorEncodedApplied identically to
packages/protocol/openapi.json,services/www/openapi.json, andservices/www/public/openapi.json.Out of scope
No source or HttpApi changes.
Verification
bun run check:generatedinservices/wwwandpackages/protocol: passbun typecheckinpackages/clientandpackages/protocol: passAdded by the opencode bot (AI-generated).
Related: #53105
Public API: documents the existing PATCH /api/permission/saved/{id} (permission.saved.update) and PermissionSavedNotFoundErrorEncoded in the OpenAPI spec (backwards compatible)