mirror of
https://github.com/Comfy-Org/comfy-python-sdk.git
synced 2026-11-04 23:37:47 +00:00
[PR #8] [MERGED] chore: sync vendored Comfy API v2 spec (cloud@2d78853) #14
Labels
No labels
audit:ai-readiness
audit:community
audit:github
audit:health-scoring
audit:policy
audit:release
audit:supply-chain
effort:medium
effort:small
effort:small
effort:trivial
priority:nice-to-have
priority:nice-to-have
priority:recommended
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/comfy-python-sdk#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Comfy-Org/comfy-python-sdk/pull/8
Author: @comfy-pr-bot
Created: 7/20/2026
Status: ✅ Merged
Merged: 7/21/2026
Merged by: @wei-hai
Base:
main← Head:chore/sync-v2-spec-2d78853📝 Commits (2)
c34e23cchore: sync vendored Comfy API v2 spec from cloud@2d788531415dc8chore: regenerate low layer for the synced v2 spec📊 Changes
2 files changed (+343 additions, -311 deletions)
View changed files
📝
spec/openapi.yaml(+342 -310)📝
src/comfy_low/models/_generated.py(+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@2d78853.This PR is on its own per-source-commit branch
(
chore/sync-v2-spec-2d78853); a laterspec 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 —
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.