[PR #158] chore: sync vendored Comfy API v2 spec (cloud@d9624758) #159

New issue

Open

opened 2026-10-31 22:05:09 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 22:05:09 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfy-typescript-sdk/pull/158
Author: @comfy-pr-bot
Created: 9/19/2026
Status: 🔄 Open

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

📝 Commits (1)

90978d1 chore: sync vendored Comfy API v2 spec from cloud@baf9281b

📊 Changes

1 file changed (+844 additions, -371 deletions)

View changed files

📝 spec/openapi.yaml (+844 -371)

📄 Description

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

It lands at spec/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/openapi.yaml. It lives
on chore/sync-v2-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.

Please do not push commits to this branch: the next sync would
overwrite them. (It will not do so silently — the workflow checks the
branch first and fails, naming this pull request, if it finds a commit
it did not make.) Push follow-up work to a branch of your own instead.

Action required before merge: this sync could not regenerate the
low layer itself, so this repository's spec-drift check will be red
until it is regenerated —

pnpm run generate

Please do NOT commit that to this branch. This is the rolling sync
branch (see below): the next sync force-updates it, and a commit of
yours on it fails every later sync for this spec until this pull
request is landed or dropped. Re-run the upstream sync workflow
instead — it runs the generator itself and refreshes this pull request
in place.

_{🔄 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/158 **Author:** [@comfy-pr-bot](https://github.com/comfy-pr-bot) **Created:** 9/19/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `chore/sync-v2-spec` --- ### 📝 Commits (1) - [`90978d1`](https://github.com/Comfy-Org/comfy-typescript-sdk/commit/90978d1959f6e8408eb67fe293e128eca3e2f0f6) chore: sync vendored Comfy API v2 spec from cloud@baf9281b ### 📊 Changes **1 file changed** (+844 additions, -371 deletions) <details> <summary>View changed files</summary> 📝 `spec/openapi.yaml` (+844 -371) </details> ### 📄 Description Automated sync of the public Comfy API v2 spec, projected from the canonical contract (internal notes stripped). Source: `cloud@d9624758`. It lands at `spec/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/openapi.yaml`. It lives on `chore/sync-v2-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. Please do not push commits to this branch: the next sync would overwrite them. (It will not do so silently — the workflow checks the branch first and fails, naming this pull request, if it finds a commit it did not make.) Push follow-up work to a branch of your own instead. **Action required before merge:** this sync could not regenerate the low layer itself, so this repository's spec-drift check will be red until it is regenerated — ``` pnpm run generate ``` Please do NOT commit that to this branch. This is the rolling sync branch (see below): the next sync force-updates it, and a commit of yours on it fails every later sync for this spec until this pull request is landed or dropped. Re-run the upstream sync workflow instead — it runs the generator itself and refreshes this pull request in place. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-31 22:05:09 +00:00

bsakaguchi referenced this issue

2026-10-31 22:05:09 +00:00

[PR #159] [MERGED] docs(assets): asset handles bind only to a filename input, never an IMAGE/VIDEO/AUDIO/MASK socket #160