You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automated sync of the public Comfy API v2 spec,
projected from the canonical contract (internal notes stripped).
Source: cloud@5a3b668.
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.
No actionable comments were generated in the recent review. 🎉
ℹ️ Recent review info⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Advanced
Run ID: 7d984091-1f40-403b-a3ab-d37366caae83
📥 Commits
Reviewing files that changed from the base of the PR and between 3702e6f and 5d35330.
📒 Files selected for processing (2)
spec/openapi.yaml
src/comfy_low/models/_generated.py
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.
📝 Walkthrough
Walkthrough
The OpenAPI contract now defines captured job-log retrieval, the JobLogs model, optional log links, session-token metadata, SSE reconciliation semantics, and clarified output node identifiers. Generated Python models reflect the new log entities and metadata.
Changes
Job logs contract
Layer / File(s)
Summary
Job logs API contract spec/openapi.yaml
Adds GET /api/v2/jobs/{id}/logs, the JobLogs schema, and the optional JobUrls.logs link.
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check
✅ Passed
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
✅ Passed
Check skipped because no linked issues were found for this pull request.
Description Check
✅ Passed
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
✅ Passed
The title clearly identifies the main change as synchronizing the vendored Comfy API v2 specification. The referenced upstream commit differs from the PR objective, but this does not make the title un…
✨ Finishing Touches📝 Generate docstrings
Create stacked PR
Commit on current branch
🧪 Generate unit tests (beta)
Create PR with unit tests
Commit unit tests in branch chore/sync-v2-spec
Comment @coderabbitai help to get the list of available commands.
comfy-pr-bot
changed the title
chore: sync vendored Comfy API v2 spec (cloud@f2cb906)
chore: sync vendored Comfy API v2 spec (cloud@941d631)
Aug 28, 2026
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
2 participants
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@5a3b668.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.