chore: sync vendored Comfy Router spec (cloud@5a3b668) - #148
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe OpenAPI descriptions for router model IDs now use ChangesOpenAPI description update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This updates the OpenAPI documentation to match the supported two-segment model ID format without changing runtime behavior. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Automated sync of the public Comfy Router spec,
projected from the canonical contract (internal notes stripped).
Source:
cloud@5a3b668.It lands at
spec/router-openapi.yamland is a contract of itsown — it is never merged into another vendored spec in this repo.
This PR is on its own per-source-commit branch (
chore/sync-router-spec-5a3b668); a laterspec change opens a separate PR and will not touch this branch, so a
regen commit pushed here is safe.
No Router operations are currently unserved (as of
cloud@5a3b668).This note auto-refreshes while this PR is open: a change to comfy-api's
exclude list rewrites this section in place, and a change to the
PUBLISHED Router surface opens its own sync PR carrying the set as of
ITS commit. Once this PR is merged the note is a permanent snapshot —
for the current state, check
services/comfy-api/drip/codegen.yamlinComfy-Org/cloud directly.
No code generation for this spec yet. Nothing in this repo
generates code from
spec/router-openapi.yaml, so this sync has no low layer toregenerate and the workflow that opened this pull request could not
prepare one for you.
That is not the same as nothing to do. This repo keeps a hand-written
surface coupled to this contract — its error-type class table — with
a drift check of its own, so a sync that adds an error bucket still
needs a commit here before this pull request goes green. When code
generation does land for this spec, its command is configured
upstream, in the same sync workflow that opened this PR, and this
section becomes the automatic one.
Summary by CodeRabbit
{provider}/{model}.