Skip to content

chore: regenerate openapi spec - #56937

Merged
rekram1-node merged 1 commit into
devfrom
regenerate-openapi
Oct 19, 2026
Merged

rekram1-node merged 1 commit into
devfrom
regenerate-openapi

Conversation

@rekram1-node

@rekram1-node rekram1-node commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Problem

The OpenAPI files checked in on dev were behind the server HttpApi. The permission.saved.update route was missing from the spec.

Change

This only reruns the existing generators (bun run generate in packages/protocol, packages/client, and services/www). The client generator produced no changes.

 paths:
   /api/permission/saved/{id}:
+    patch: permission.saved.update
     delete: permission.saved.remove
 components.schemas:
+  PermissionSavedNotFoundErrorEncoded

Applied identically to packages/protocol/openapi.json, services/www/openapi.json, and services/www/public/openapi.json.

Out of scope

No source or HttpApi changes.

Verification

  • bun run check:generated in services/www and packages/protocol: pass
  • bun typecheck in packages/client and packages/protocol: pass

Added 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)

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

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