[PR #87] [CLOSED] chore: sync vendored Comfy Router spec (cloud@2b9c2cf) #89

Closed
opened 2026-10-31 22:04:26 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfy-typescript-sdk/pull/87
Author: @comfy-pr-bot
Created: 8/26/2026
Status: ❌ Closed

Base: main ← Head: chore/sync-router-spec-2b9c2cf


📝 Commits (1)

  • 398c8b8 chore: sync vendored Comfy Router spec from cloud@2b9c2cf

📊 Changes

1 file changed (+441 additions, -0 deletions)

View changed files

➕ spec/router-openapi.yaml (+441 -0)

📄 Description

Automated sync of the public Comfy Router spec,
projected from the canonical contract (internal notes stripped).
Source: cloud@2b9c2cf.

It lands at spec/router-openapi.yaml and is a contract of its
own — it is never merged into another vendored spec in this repo.

This PR is on its own per-source-commit branch
(chore/sync-router-spec-2b9c2cf);
a later spec change opens a separate PR and will not touch this
branch, so a regen commit pushed here is safe.

Heads-up: not yet served. These operations are part of this spec's
contract but are NOT served as of cloud@2b9c2cf — a call to one
fails today (404, or 405 if a sibling operation on the same path has
already been wired):
getRouterModel, getRouterModelInputSchema, listRouterModels, runRouterModel.
Merging vendors the contract only; nothing in this repo generates code
from spec/router-openapi.yaml yet.

That is a snapshot at the source commit above, not a live status. A
later change to the PUBLISHED Router surface opens its own sync PR
that carries the set as of ITS commit. A change that only removes an
id from comfy-api's exclude list does not touch the published surface
and does not retrigger this pipeline, so this note can go stale
without a new sync PR appearing to replace it — if you need the
current answer, check services/comfy-api/drip/codegen.yaml in
Comfy-Org/cloud directly.

No regeneration step for this spec yet. Nothing in this repo reads
spec/router-openapi.yaml, so there is no low layer to regenerate before merge and
no spec-drift check to satisfy — merging vendors the contract and
nothing else. When Router code generation does land here, this
section should carry its command; it is configured upstream, in the
same sync workflow that opened this PR.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/comfy-typescript-sdk/pull/87 **Author:** [@comfy-pr-bot](https://github.com/comfy-pr-bot) **Created:** 8/26/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `chore/sync-router-spec-2b9c2cf` --- ### 📝 Commits (1) - [`398c8b8`](https://github.com/Comfy-Org/comfy-typescript-sdk/commit/398c8b896f03bc4d59daacad39ac8b90e4339676) chore: sync vendored Comfy Router spec from cloud@2b9c2cf ### 📊 Changes **1 file changed** (+441 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `spec/router-openapi.yaml` (+441 -0) </details> ### 📄 Description Automated sync of the public Comfy Router spec, projected from the canonical contract (internal notes stripped). Source: `cloud@2b9c2cf`. It lands at `spec/router-openapi.yaml` and is a contract of its own — it is never merged into another vendored spec in this repo. This PR is on its own per-source-commit branch (`chore/sync-router-spec-2b9c2cf`); a later spec change opens a separate PR and will not touch this branch, so a regen commit pushed here is safe. **Heads-up: not yet served.** These operations are part of this spec's contract but are NOT served as of `cloud@2b9c2cf` — a call to one fails today (404, or 405 if a sibling operation on the same path has already been wired): `getRouterModel`, `getRouterModelInputSchema`, `listRouterModels`, `runRouterModel`. Merging vendors the contract only; nothing in this repo generates code from `spec/router-openapi.yaml` yet. That is a snapshot at the source commit above, not a live status. A later change to the PUBLISHED Router surface opens its own sync PR that carries the set as of ITS commit. A change that only removes an id from comfy-api's exclude list does not touch the published surface and does not retrigger this pipeline, so this note can go stale without a new sync PR appearing to replace it — if you need the current answer, check `services/comfy-api/drip/codegen.yaml` in Comfy-Org/cloud directly. **No regeneration step for this spec yet.** Nothing in this repo reads `spec/router-openapi.yaml`, so there is no low layer to regenerate before merge and no spec-drift check to satisfy — merging vendors the contract and nothing else. When Router code generation does land here, this section should carry its command; it is configured upstream, in the same sync workflow that opened this PR. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 22:04:26 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/comfy-typescript-sdk#89
No description provided.