[PR #160] [CLOSED] chore: sync vendored Comfy API v2 spec (cloud@8759533) #162

New issue

Closed

opened 2026-10-31 22:01:54 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 22:01:54 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfy-python-sdk/pull/160
Author: @comfy-pr-bot
Created: 9/17/2026
Status: ❌ Closed

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

📝 Commits (1)

12312da chore: sync vendored Comfy API v2 spec from cloud@2bdc0c1

📊 Changes

2 files changed (+210 additions, -6 deletions)

View changed files

📝 spec/openapi.yaml (+171 -4)
📝 src/comfy_low/models/_generated.py (+39 -2)

📄 Description

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

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.

No regen commit needed. This sync ran bash scripts/gen_models.sh against the
vendored spec and committed what it produced, so the generated low
layer in this pull request is already in step with
spec/openapi.yaml and this repository's spec-drift check should be green as
opened.

Green is not a substitute for reading the diff. The drift check
confirms only that the vendored spec and the generated low layer
agree with each other — it says nothing about whether either is what
the contract change meant, and the generated bytes were produced
upstream, by a generator this repository does not run. Review the
generated diff as you would any other.

_{🔄 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/160 **Author:** [@comfy-pr-bot](https://github.com/comfy-pr-bot) **Created:** 9/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `chore/sync-v2-spec` --- ### 📝 Commits (1) - [`12312da`](https://github.com/Comfy-Org/comfy-python-sdk/commit/12312da63798a95192335157737a22362cf55aad) chore: sync vendored Comfy API v2 spec from cloud@2bdc0c1 ### 📊 Changes **2 files changed** (+210 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `spec/openapi.yaml` (+171 -4) 📝 `src/comfy_low/models/_generated.py` (+39 -2) </details> ### 📄 Description Automated sync of the public Comfy API v2 spec, projected from the canonical contract (internal notes stripped). Source: `cloud@8759533`. 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. **No regen commit needed.** This sync ran `bash scripts/gen_models.sh` against the vendored spec and committed what it produced, so the generated low layer in this pull request is already in step with `spec/openapi.yaml` and this repository's spec-drift check should be green as opened. Green is not a substitute for reading the diff. The drift check confirms only that the vendored spec and the generated low layer agree with each other — it says nothing about whether either is what the contract change meant, and the generated bytes were produced upstream, by a generator this repository does not run. Review the generated diff as you would any other. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 22:01:54 +00:00