chore: sync vendored Comfy API v2 spec (cloud@941d631) - #107
Open
comfy-pr-bot wants to merge 1 commit into
Open
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: Comment |
comfy-pr-bot
force-pushed
the
chore/sync-v2-spec
branch
from
August 28, 2026 13:54
4e7f0f0 to
cbe9325
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated sync of the public Comfy API v2 spec,
projected from the canonical contract (internal notes stripped).
Source:
cloud@941d631.It lands at
spec/openapi.yamland is a contract of itsown — it is never merged into another vendored spec in this repo.
This is the single rolling sync pull request for
spec/openapi.yaml. It liveson
chore/sync-v2-spec, and every later change to the upstream contractforce-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.shagainst thevendored spec and committed what it produced, so the generated low
layer in this pull request is already in step with
spec/openapi.yamland this repository's spec-drift check should be green asopened.
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.