[PR #98] [MERGED] chore: sync vendored Comfy Router spec (cloud@2a369ae) #97

New issue

Closed

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

bsakaguchi commented

2026-10-31 22:01:21 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfy-python-sdk/pull/98
Author: @comfy-pr-bot
Created: 8/27/2026
Status: ✅ Merged
Merged: 8/27/2026
Merged by: @wei-hai

Base: main ← Head: chore/sync-router-spec-2a369ae

📝 Commits (1)

e5c32a9 chore: sync vendored Comfy Router spec from cloud@2a369ae

📊 Changes

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

View changed files

📝 spec/router-openapi.yaml (+6 -6)

📄 Description

Automated sync of the public Comfy Router spec,
projected from the canonical contract (internal notes stripped).
Source: cloud@2a369ae.

It lands at spec/router-openapi.yaml and is a contract of its
own — 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-2a369ae);
a later spec 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@2a369ae).

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.yaml in
Comfy-Org/cloud directly.

No regeneration step for this spec yet. Nothing in this repo reads
spec/router-openapi.yaml, so there is no low layer to regenerate before merge and
no spec-drift check to satisfy — merging vendors the contract and
nothing else. When Router code generation does land here, this
section should carry its command; it is configured upstream, in the
same sync workflow that opened this PR.

_{🔄 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/98 **Author:** [@comfy-pr-bot](https://github.com/comfy-pr-bot) **Created:** 8/27/2026 **Status:** ✅ Merged **Merged:** 8/27/2026 **Merged by:** [@wei-hai](https://github.com/wei-hai) **Base:** `main` ← **Head:** `chore/sync-router-spec-2a369ae` --- ### 📝 Commits (1) - [`e5c32a9`](https://github.com/Comfy-Org/comfy-python-sdk/commit/e5c32a981026104b67b434af728dea73f3b429f6) chore: sync vendored Comfy Router spec from cloud@2a369ae ### 📊 Changes **1 file changed** (+6 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `spec/router-openapi.yaml` (+6 -6) </details> ### 📄 Description Automated sync of the public Comfy Router spec, projected from the canonical contract (internal notes stripped). Source: `cloud@2a369ae`. It lands at `spec/router-openapi.yaml` and is a contract of its own — 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-2a369ae`); a later spec 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@2a369ae`). 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.yaml` in Comfy-Org/cloud directly.  **No regeneration step for this spec yet.** Nothing in this repo reads `spec/router-openapi.yaml`, so there is no low layer to regenerate before merge and no spec-drift check to satisfy — merging vendors the contract and nothing else. When Router code generation does land here, this section should carry its command; it is configured upstream, in the same sync workflow that opened this PR. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-31 22:01:21 +00:00

bsakaguchi referenced this issue

2026-10-31 22:01:21 +00:00

[PR #97] [MERGED] feat: carry the Idempotency-Key and request id on every exception models.run raises #98

bsakaguchi closed this issue

2026-10-31 22:01:21 +00:00

bsakaguchi referenced this issue

2026-10-31 22:01:39 +00:00

[PR #130] [MERGED] fix(models): raise the original failure when a same-key retry is refused 422 #131