[PR #18] [CLOSED] chore: sync vendored Comfy API v2 spec (cloud@e344fc7) #26

New issue

Closed

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

bsakaguchi commented

2026-10-31 22:00:52 +00:00

Owner

📋 Pull Request Information

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

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

📝 Commits (1)

5084a98 chore: sync vendored Comfy API v2 spec from cloud@e344fc7

📊 Changes

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

View changed files

📝 spec/openapi.yaml (+1 -1)

📄 Description

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

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

Action required before merge: regenerate the low layer and commit
the result so the spec-drift check passes —

scripts/gen_models.sh (datamodel-code-generator)

_{🔄 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/18 **Author:** [@comfy-pr-bot](https://github.com/comfy-pr-bot) **Created:** 7/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `chore/sync-v2-spec-e344fc7` --- ### 📝 Commits (1) - [`5084a98`](https://github.com/Comfy-Org/comfy-python-sdk/commit/5084a98cafc4b888a38f08557bdfd3b6b6e53d2e) chore: sync vendored Comfy API v2 spec from cloud@e344fc7 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `spec/openapi.yaml` (+1 -1) </details> ### 📄 Description Automated sync of the public Comfy API v2 spec, projected from the canonical contract (internal notes stripped, all component schemas kept). Source: `cloud@e344fc7`. This PR is on its own per-source-commit branch (`chore/sync-v2-spec-e344fc7`); a later spec change opens a separate PR and will not touch this branch, so a regen commit pushed here is safe. **Action required before merge:** regenerate the low layer and commit the result so the spec-drift check passes — ``` scripts/gen_models.sh (datamodel-code-generator) ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 22:00:52 +00:00