[PR #230] [MERGED] chore: sync vendored Comfy Router spec (cloud@d9624758) #230

New issue

Closed

opened 2026-10-31 22:02:30 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 22:02:30 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfy-python-sdk/pull/230
Author: @cloud-code-bot[bot]
Created: 10/31/2026
Status: ✅ Merged
Merged: 10/31/2026
Merged by: @vqt123

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

📝 Commits (1)

0bf2367 chore: sync vendored Comfy Router spec from cloud@d9624758

📊 Changes

1 file changed (+5 additions, -5 deletions)

View changed files

📝 spec/router-openapi.yaml (+5 -5)

📄 Description

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

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 is the single rolling sync pull request for spec/router-openapi.yaml. It lives
on chore/sync-router-spec, and every later change to the upstream contract
force-updates this same branch and refreshes this description with the
new source commit — so there is only ever one open sync PR for this
spec, and its diff is always the current one.

The error-type class commit described above is the one commit that
belongs here. Once a commit of yours is on this branch, the next sync
refuses to force-update it and fails, naming this pull request, so
land this pull request promptly. Push any other follow-up work to a
branch of your own.

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

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 — its 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.

Commit that class to this branch and land this pull request once it
is green. The class cannot land separately: the drift check also
fails on a class the vendored spec does not declare yet. Your commit
is safe here — the next sync will not overwrite it; it fails instead,
naming this pull request — but every later sync for this spec stays
paused until this pull request is merged (which deletes the branch,
so the following sync starts fresh), or closed and its branch
deleted.

_{🔄 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-python-sdk/pull/230 **Author:** [@cloud-code-bot[bot]](https://github.com/apps/cloud-code-bot) **Created:** 10/31/2026 **Status:** ✅ Merged **Merged:** 10/31/2026 **Merged by:** [@vqt123](https://github.com/vqt123) **Base:** `main` ← **Head:** `chore/sync-router-spec` --- ### 📝 Commits (1) - [`0bf2367`](https://github.com/Comfy-Org/comfy-python-sdk/commit/0bf236798138df091b0189d18bb2dca10a6e36a8) chore: sync vendored Comfy Router spec from cloud@d9624758 ### 📊 Changes **1 file changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `spec/router-openapi.yaml` (+5 -5) </details> ### 📄 Description Automated sync of the public Comfy Router spec, projected from the canonical contract (internal notes stripped). Source: `cloud@d9624758`. 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 is the single rolling sync pull request for `spec/router-openapi.yaml`. It lives on `chore/sync-router-spec`, and every later change to the upstream contract force-updates this same branch and refreshes this description with the new source commit — so there is only ever one open sync PR for this spec, and its diff is always the current one. The error-type class commit described above is the one commit that belongs here. Once a commit of yours is on this branch, the next sync refuses to force-update it and fails, naming this pull request, so land this pull request promptly. Push any other follow-up work to a branch of your own.   No Router operations are currently unserved (as of `cloud@d9624758`). 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 — its 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. Commit that class to this branch and land this pull request once it is green. The class cannot land separately: the drift check also fails on a class the vendored spec does not declare yet. Your commit is safe here — the next sync will not overwrite it; it fails instead, naming this pull request — but every later sync for this spec stays paused until this pull request is merged (which deletes the branch, so the following sync starts fresh), or closed and its branch deleted. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 22:02:30 +00:00