[PR #109] [CLOSED] chore: sync vendored Comfy Router spec (cloud@b7481bb) #112

New issue

Closed

opened 2026-10-31 22:04:40 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 22:04:40 +00:00

Owner

📋 Pull Request Information

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

Base: main ← Head: chore/sync-router-spec-b7481bb

📝 Commits (1)

6f449ba chore: sync vendored Comfy Router spec from cloud@b7481bb

📊 Changes

1 file changed (+74 additions, -23 deletions)

View changed files

📝 spec/router-openapi.yaml (+74 -23)

📄 Description

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

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-b7481bb); a later
spec change opens a separate PR and will not touch this branch, so a
regen commit pushed here is safe.

No Router operations are currently unserved (as of cloud@b7481bb).

This note auto-refreshes while this PR is open: a change to comfy-api's
exclude list rewrites this section in place, and a change to the
PUBLISHED Router surface opens its own sync PR carrying the set as of
ITS commit. Once this PR is merged the note is a permanent snapshot —
for the current state, check services/comfy-api/drip/codegen.yaml in
Comfy-Org/cloud directly.

No code generation for this spec yet. Nothing in this repo
generates code from spec/router-openapi.yaml, so this sync has no low layer to
regenerate and the workflow that opened this pull request could not
prepare one for you.

That is not the same as nothing to do. This repo keeps a hand-written
surface coupled to this contract — the error_type class table — with
a drift check of its own, so a sync that adds an error bucket still
needs a commit here before this pull request goes green. When code
generation does land for this spec, its command is configured
upstream, in the same sync workflow that opened this PR, and this
section becomes the automatic one.

_{🔄 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/109 **Author:** [@comfy-pr-bot](https://github.com/comfy-pr-bot) **Created:** 8/31/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `chore/sync-router-spec-b7481bb` --- ### 📝 Commits (1) - [`6f449ba`](https://github.com/Comfy-Org/comfy-typescript-sdk/commit/6f449ba940ac27be6b39852973241f728fb5b71b) chore: sync vendored Comfy Router spec from cloud@b7481bb ### 📊 Changes **1 file changed** (+74 additions, -23 deletions) <details> <summary>View changed files</summary> 📝 `spec/router-openapi.yaml` (+74 -23) </details> ### 📄 Description Automated sync of the public Comfy Router spec, projected from the canonical contract (internal notes stripped). Source: `cloud@b7481bb`. 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-b7481bb`); a later spec change opens a separate PR and will not touch this branch, so a regen commit pushed here is safe.   No Router operations are currently unserved (as of `cloud@b7481bb`). This note auto-refreshes while this PR is open: a change to comfy-api's exclude list rewrites this section in place, and a change to the PUBLISHED Router surface opens its own sync PR carrying the set as of ITS commit. Once this PR is merged the note is a permanent snapshot — for the current state, check `services/comfy-api/drip/codegen.yaml` in Comfy-Org/cloud directly.  **No code generation for this spec yet.** Nothing in this repo *generates* code from `spec/router-openapi.yaml`, so this sync has no low layer to regenerate and the workflow that opened this pull request could not prepare one for you. That is not the same as nothing to do. This repo keeps a hand-written surface coupled to this contract — the `error_type` class table — with a drift check of its own, so a sync that adds an error bucket still needs a commit here before this pull request goes green. When code generation does land for this spec, its command is configured upstream, in the same sync workflow that opened this PR, and this section becomes the automatic one. --- <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:40 +00:00