From 603259aba9014e80940b7203b8061989e7d27886 Mon Sep 17 00:00:00 2001 From: Vinh Trinh Date: Wed, 11 Nov 2026 09:09:53 -0800 Subject: [PATCH] docs(changelog): roll for v1.26.0 Splits Unreleased into 1.25.0 (never rolled) and 1.26.0, drops a 1.24.0 entry listed twice, adds entries for #1098, #1115, #1119 and #1007, and marks the watch_auth_lost exit code and the push --dry-run sign-in change Breaking. --- CHANGELOG.md | 257 ++++++++++++++++++++++++++++++++------------------- 1 file changed, 160 insertions(+), 97 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 51788a9f8..2c5f883c0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -15,54 +15,9 @@ history. ## [Unreleased] -### Changed +## [1.26.0] - 2026-11-11 -- `comfy workflow save --where cloud` prints a link that opens only the saved - workflow (`?workflowId=`) when Cloud's `/api/features` has - `private_saved_file_links_enabled` on. The workflow id is the one record - Cloud made from the saved file. With the setting off, or when that record - is missing, not unique, or the search for it fails, the link opens the - folder as before. The receipt adds `url_opens` (`workflow` or `folder`) and - `folder_link_reason`. -- Release watches poll through `stopping` and report `build_stopped` (exit 1) when a release stops. Log following reads the final lines after `stopped` and exits successfully. - -- `comfy deploy status` explains beside its sampled counts that they may lag after workers scale down. The deploy-failure guidance also clarifies that sampled counts cannot establish whether a worker or job is running now. -- Both `comfy assets library upload` and `comfy model upload` request resumable - model uploads up to 25 GB. Dropped connections retry from storage's held - bytes. Running the command again continues a saved upload for the same file, - account, workspace and folder while its session remains valid. Sessions expire - no later than seven days after creation; the server can expire them earlier. - A paused upload reports whether its session was saved for a later run. Older - servers keep the single-PUT upload. A server with resumable uploads turned off - refuses the resumable start (403 `FEATURE_DISABLED`); the upload then starts - once more as a single PUT, as the editor does, and a refusal of that start - (such as `FILE_TOO_LARGE` over 2 GiB) is shown as before. - File approval, block checks and the final stored-hash - check still apply. The final storage check no longer stops after fifteen - minutes. The retired `asset_upload_timeout` error code stays discoverable - for compatibility with older versions. The task id is reported before the - storage wait. Refused resumable sessions are discarded and restarted once; - certificate verification and invalid CA-bundle failures stop immediately - without transport exception text. - HTTP timeouts and transient TLS interruptions query the held bytes and retry. - A closed progress pipe or stream does not stop task polling or the final - stored-hash check, including when Rich converts the pipe failure to an exit. - Legacy single-PUT storage addresses - retain HTTP compatibility. Certificate verification and invalid CA-bundle - errors on that path also stop immediately with fixed TLS guidance. - Both paths recognize certificate failures wrapped by an HTTPS proxy while - retaining retries for temporary proxy failures. -- `comfy assets library upload` and `comfy model upload` tell Comfy Cloud - which client sent an upload and whether its transfer resumed from bytes - storage already held. When a transfer stops for good (it gives up, pauses or - is canceled), the command sends Comfy Cloud one report with a fixed reason, - the size and the folder, if the server asks for such reports. Any stopped - upload (one that gives up, pauses, restarts as a fresh upload or gets Ctrl+C) - can take up to 3 seconds longer to exit while that report goes out to a slow - Comfy Cloud. A second Ctrl+C ends that wait within a tenth of a second. - `DO_NOT_TRACK` or `COMFY_NO_TELEMETRY` turns all of it off. -- `comfy build push` shares the upload progress reporter. A broken pipe or - closed progress stream now mutes its progress instead of ending the push. +[Full notes](https://github.com/Comfy-Org/comfy-cli/releases/tag/v1.26.0) · 30 commits since v1.25.0. Breaking changes are marked **Breaking** under Changed. ### Added @@ -77,6 +32,7 @@ history. deploy commands read them; when `--builder-url` or `COMFY_BUILDER_URL` points the builder elsewhere, or `COMFY_BUILDER_TOKEN` signs the builder reads with another credential, `note` says so. + - A release cut refused at the release limit (`build_release_limit`) lists, under `--json`, each visible Build in `details.builds`: its release count, its newest release, and how many deployments use it (`deployments` and `inUse`). @@ -93,6 +49,7 @@ history. `details.activeDeployments`, whenever the refusal names that limit, and says `comfy deploy stop` frees one; a refusal over the per-deployment worker limit lists none. When the extra reads fail, both envelopes are as before. + - The `comfy-run-on-cloud` agent skill, installed with the other bundled skills and read with `comfy skills show comfy-run-on-cloud`. It takes one workflow from a running local ComfyUI (read through the server's @@ -115,6 +72,7 @@ history. `comfy-deploy` and `comfy-deploy-failures` read a deployment with `deploy show` outside a Build folder, since `deploy status` needs one. Builds on #1008. + - `comfy deploy run --allow-upload ` (repeatable) uploads a local file the deployment lacks only if its hash is listed; any other file fails with `deploy_asset_missing` and is not sent. A file Cloud already holds is reused @@ -129,6 +87,7 @@ history. `local_path`, `bytes`, `hash`) rather than stopping at the first, so a person can approve the exact files the scanner picked. When two asset folders hold files of the same name, this shows which one it picked. + - `comfy workflow check --where cloud` says whether Comfy Cloud runs a workflow with no custom build. Signed in, it reads Cloud's node list and your uploaded models, and answers `covered`, `covered_with_remaps` (a model sits in @@ -137,6 +96,7 @@ history. folder and any local copy. `--models-dir` hashes local copies against Cloud's; `--apply-remaps --out ` writes a remapped copy and leaves the original alone. + - `comfy workflow save` on Comfy Cloud, when the workspace's `cli_cloud_save_enabled` flag is on, writes an editor-format workflow into a new folder in the Cloud Workflows sidebar (``, then ` (2)` and so @@ -151,28 +111,13 @@ history. version, so a same-named file of another workflow is never named. With the flag off, or when Cloud's features cannot be read, save and delete are unchanged. + - `comfy knowledge pick` includes authored discovery-only routes in a separate `discovery` list, marks every route `ranking: "unranked"`, and carries the capability's `failure_policy` without promoting or reordering ranked picks. `--check-local` reports `discovery_not_checked` when ranked-pick checks pass but discovery routes are present. -- `comfy assets library upload --type ` puts a `.safetensors` - model file of up to 2 GB into your Comfy Cloud workspace's model library, - e.g. `comfy assets library upload my_style.safetensors --type loras`. The - file name, size, that the file can be read, and `--type` are checked before - anything is sent (`--type` against the folders the workspace takes); a file - that cannot be read mid-transfer ends as `asset_upload_failed` with - `details.reason` `file_unreadable`, and a TLS setting that stops the transfer - (e.g. `REQUESTS_CA_BUNDLE` naming a missing file) with `details.reason` - `tls_setup` and its message; neither is retried. The bytes stream straight to - storage with the same progress line and events as `comfy build push`, and - the command waits for Comfy Cloud to store the file, then prints the asset - id, name, folder and hash (`--json`: the `assets_library` schema). A - refusal from Comfy Cloud, such as uploads being off for the workspace or the - model storage cap being reached, is shown with the server's message as - `asset_upload_refused`; new codes `asset_upload_invalid`, - `asset_upload_failed` and `asset_upload_timeout` cover the other ways it - can end. + - `comfy model upload --type --where cloud` uploads one local model file into your Comfy Cloud model library, so a workflow run on Comfy Cloud can load it, e.g. `comfy model upload my_style.safetensors --type loras @@ -188,6 +133,7 @@ history. workflow's loader node takes to load the file on Comfy Cloud. It is Comfy Cloud's own value from its record of the model, and null when Comfy Cloud gives none or when a dry run would upload. Builds on #1008. + - `comfy model upload` and `comfy assets library upload` upload only the file named, and succeed only once Comfy Cloud's hash of the stored file equals the local file's. Before anything is sent they look the name up in that folder of @@ -208,29 +154,81 @@ history. `asset_upload_unverified`. `comfy assets library upload` gains `--dry-run`, and its `--json` output gains `loader_path`, `sha256`, `workspace_id`, `uploaded`, `already_present` and `dry_run`. -- `comfy knowledge resolve` suggests canonical model ids for an incomplete - family/version name such as `Qwen 2.1`. The command still fails with - `knowledge_unknown_model` and exit 1, but `error.details.candidate_ids` lists - up to five sorted, distinct ids whose id or alias has the same family word - and the same numeric components in order, and the hint names them and asks - which model is intended before retrying `comfy knowledge resolve `. - A single candidate is still only a suggestion: nothing is auto-resolved, - downloaded or run. Substituted family words, different versions and names - with non-ASCII letters or digits get no candidates. Exact id and alias - resolution, `close_matches` and the hint for a name with no candidates are - unchanged. + +- `comfy workflow print --format json` adds `nodes`, one record per printed + node: its id, name, type, title, mode (`normal`, `muted` or `bypassed`), + `collapsed` and `pinned` flags, output names, widget values, and `links` keyed + by the input names the edit commands take (`null` for an unlinked socket). A + subgraph's interior nodes appear once per instance address (`57/3`), and an + interior widget fed by a subgraph input is listed under `promoted`. A class + missing from the catalog sets `class_unknown`. `--format py` is unchanged. ### Changed -- A `connect` into a widget input of an agent-built node is now type-checked. - `comfy workflow add-node` gives every widget input a socket entry (see Fixed - below), so a link into one is an ordinary connect to an existing slot rather - than a `grow` that minted a new slot and took the source's type unchecked. A - mismatched scalar — `INT` into a `FLOAT` widget such as `force_rate`, or - `IMAGE` into a `COMBO` — now fails the existing type check instead of being - accepted silently. A `COMBO` widget socket still accepts `COMBO`, `STRING`, - `INT` and `FLOAT`, because that is how a computed file name or a numeric - option reaches a combo; every other source type is refused. +- **Breaking:** a watch whose sign-in is still refused after the shared refresh, + while a refreshable sign-in remains stored, now ends with the new code + `watch_auth_lost` and exit code 75, as `deploy_watch_lost` does, instead of + `build_not_signed_in` or `deploy_not_signed_in` and exit 1. This covers + `comfy build release create --watch`, `comfy deploy up`, `promote`, + `rollback` and `comfy deploy status --watch`. The release or deployment may + still be going on the server, and the stored sign-in is kept. The hint names + the command that reads the release or deployment again. A 401 before + anything was accepted, on a workspace API key, or when no refreshable sign-in + remains still reports `build_not_signed_in` or `deploy_not_signed_in`. + +- **Breaking:** `comfy build push --dry-run` now runs the push's registry-pin check, so a pin the builder cannot place fails the dry run with the push's own `build_registry_pin_missing` error instead of passing it. A version the registry has Flagged was the common case: the dry run passed, and the push was refused only after the plan had been disclosed. The check asks the builder's snapshot importer to place each public pack, a read that writes nothing, and the dry run still uploads and saves nothing. The `--json` payload of a push and a dry run carries `public_pins_checked`, the number of public pins the builder placed (0 when the spec has none and the builder was not asked), so a script can tell a checked pin set from a spec with nothing to check. A spec that pins a public pack now needs sign-in for its dry run (`build_not_signed_in` otherwise); a spec whose packs are all local still sends no request. Push and dry run also refuse when the registry did not answer for a pack (the importer's `unverifiedPins`), instead of treating the unchecked pin as resolved; refuse with `build_spec_invalid`, before sending anything, a `repository` that is not a public GitHub address (`https://github.com//`, `git@github.com:/.git` or `ssh://git@github.com//`), so one that carries a user name or token, does not parse, or names another host never leaves the machine; and report a builder response that times out or drops mid-body as `build_builder_error` instead of an internal error. + +- `comfy workflow save --where cloud` prints a link that opens only the saved + workflow (`?workflowId=`) when Cloud's `/api/features` has + `private_saved_file_links_enabled` on. The workflow id is the one record + Cloud made from the saved file. With the setting off, or when that record + is missing, not unique, or the search for it fails, the link opens the + folder as before. The receipt adds `url_opens` (`workflow` or `folder`) and + `folder_link_reason`. + +- Release watches poll through `stopping` and report `build_stopped` (exit 1) when a release stops. Log following reads the final lines after `stopped` and exits successfully. + +- `comfy deploy status` explains beside its sampled counts that they may lag after workers scale down. The deploy-failure guidance also clarifies that sampled counts cannot establish whether a worker or job is running now. + +- Both `comfy assets library upload` and `comfy model upload` request resumable + model uploads up to 25 GB. Dropped connections retry from storage's held + bytes. Running the command again continues a saved upload for the same file, + account, workspace and folder while its session remains valid. Sessions expire + no later than seven days after creation; the server can expire them earlier. + A paused upload reports whether its session was saved for a later run. Older + servers keep the single-PUT upload. A server with resumable uploads turned off + refuses the resumable start (403 `FEATURE_DISABLED`); the upload then starts + once more as a single PUT, as the editor does, and a refusal of that start + (such as `FILE_TOO_LARGE` over 2 GiB) is shown as before. + File approval, block checks and the final stored-hash + check still apply. The final storage check no longer stops after fifteen + minutes. The retired `asset_upload_timeout` error code stays discoverable + for compatibility with older versions. The task id is reported before the + storage wait. Refused resumable sessions are discarded and restarted once; + certificate verification and invalid CA-bundle failures stop immediately + without transport exception text. + HTTP timeouts and transient TLS interruptions query the held bytes and retry. + A closed progress pipe or stream does not stop task polling or the final + stored-hash check, including when Rich converts the pipe failure to an exit. + Legacy single-PUT storage addresses + retain HTTP compatibility. Certificate verification and invalid CA-bundle + errors on that path also stop immediately with fixed TLS guidance. + Both paths recognize certificate failures wrapped by an HTTPS proxy while + retaining retries for temporary proxy failures. + +- `comfy assets library upload` and `comfy model upload` tell Comfy Cloud + which client sent an upload and whether its transfer resumed from bytes + storage already held. When a transfer stops for good (it gives up, pauses or + is canceled), the command sends Comfy Cloud one report with a fixed reason, + the size and the folder, if the server asks for such reports. Any stopped + upload (one that gives up, pauses, restarts as a fresh upload or gets Ctrl+C) + can take up to 3 seconds longer to exit while that report goes out to a slow + Comfy Cloud. A second Ctrl+C ends that wait within a tenth of a second. + `DO_NOT_TRACK` or `COMFY_NO_TELEMETRY` turns all of it off. + +- `comfy build push` shares the upload progress reporter. A broken pipe or + closed progress stream now mutes its progress instead of ending the push. + - Commands that load a node catalog but read only a few classes (`workflow print`, `workflow validate`, `workflow slots`, `nodes show`) no longer parse every class in it: a class is parsed when first looked up, and the type @@ -241,9 +239,16 @@ history. - Search matches names however their separators are written. `comfy models search --text` on Cloud now finds `minimax_h3_ref2va_….safetensors` for `MiniMax H3` and `wan2.2_t2v_….safetensors` for `wan 2.2`: every word must appear, with `- _ . space` ignored, the rule local search already used. Before, Cloud sent the whole query as one substring and a multi-word name found nothing. `comfy templates ls` (and `templates get --where`) match `--model`, `--name` and `--provider` the same way, so `--model "Wan 2.2"` finds the gallery's `Wan2.2`, and `comfy nodes search` finds `LTX 2.5` nodes for `LTX-2.5`. On Cloud a word the filename splits (`sdxl` for `sd_xl_base_1.0.safetensors`) is found too: when the server's narrowed answer has no match, search scans without the server filter. A scan stops after 10,000 assets, and `total_is_lower_bound` is then true. -- `comfy build push --dry-run` now runs the push's registry-pin check, so a pin the builder cannot place fails the dry run with the push's own `build_registry_pin_missing` error instead of passing it. A version the registry has Flagged was the common case: the dry run passed, and the push was refused only after the plan had been disclosed. The check asks the builder's snapshot importer to place each public pack, a read that writes nothing, and the dry run still uploads and saves nothing. The `--json` payload of a push and a dry run carries `public_pins_checked`, the number of public pins the builder placed (0 when the spec has none and the builder was not asked), so a script can tell a checked pin set from a spec with nothing to check. A spec that pins a public pack now needs sign-in for its dry run (`build_not_signed_in` otherwise); a spec whose packs are all local still sends no request. Push and dry run also refuse when the registry did not answer for a pack (the importer's `unverifiedPins`), instead of treating the unchecked pin as resolved; refuse with `build_spec_invalid`, before sending anything, a `repository` that is not a public GitHub address (`https://github.com//`, `git@github.com:/.git` or `ssh://git@github.com//`), so one that carries a user name or token, does not parse, or names another host never leaves the machine; and report a builder response that times out or drops mid-body as `build_builder_error` instead of an internal error. +- Parallel build and deploy requests rejected on an old access token now adopt a peer's refreshed token under the shared refresh lock instead of rotating it again. Each rejected request retries at most once. -- Parallel build and deploy requests rejected on an old access token now adopt a peer's refreshed token under the shared refresh lock instead of rotating it again. Each rejected request retries at most once. If session recovery still fails while a refreshable sign-in remains stored, the watch reports that the remote work may continue instead of telling you to sign in again. `comfy build release create --watch`, `comfy deploy up`, `promote`, `rollback` and `comfy deploy status --watch` now end with the new code `watch_auth_lost` and exit code 75, as `deploy_watch_lost` does. Its hint names the command that reads the release or deployment again. A 401 before anything was accepted, on a workspace API key, or when no refreshable sign-in remains still reports `build_not_signed_in` or `deploy_not_signed_in`. +- `comfy jobs status`, `jobs watch` and `jobs wait` add a note when a completed + run's record reports outputs this tool cannot turn into a file or text, such + as a `tags` list or a `null` image entry. The note says how many entries the + record reported and names their keys, so `outputs: 1` in `comfy jobs ls` + beside `outputs: []` in `jobs status` is explained. A record whose node + entries are empty (`{"images": []}`) now gets the existing empty-completion + note. Both notes say this is not a service outage. The run is still + `completed`. - `comfy update` no longer dies with a `FileNotFoundError` traceback when the configured workspace directory does not exist (never installed, or deleted). @@ -263,6 +268,7 @@ history. stay on stderr in JSON/NDJSON modes, which end with one success or error envelope. - Desktop discovery reads both modern and legacy registries and keeps each registry's shared model roots with its own installs. The selected Desktop install is a registry-derived candidate (the only usable install, or the most recently launched); it is not matched to a running server. + - `comfy which` and `comfy env` report Desktop's split code, data and model roots without changing launch/install selection. On Linux, shared model roots are read from `settings.json` under `XDG_CONFIG_HOME`, where Desktop keeps it. A nonexistent selected workspace still exits 0 but reports `exists: false` and a `workspace_not_found` warning; discovery reports malformed or unreadable Desktop configuration, and Desktop paths that cannot be checked (permission denied, a symlink loop, no home directory), as `desktop_config_unreadable` warnings and marks inferred data roots as unverified. Both codes appear only in `data.warnings[]`; they are not error codes and `comfy discover` does not list them under `data.error_codes`. - `comfy node deps` reports malformed installed package versions as `unknown` @@ -271,16 +277,6 @@ history. compares raw strings case-insensitively, including in mixed constraints; ordinary clauses still require valid versions and use semantic comparison. -- UI→API conversion expands a `COMFY_DYNAMICCOMBO_V3` selector's sub-inputs in - the order the workflow was SAVED with, when the saved graph records one, - instead of the option's current order. An option that has since gained a - sub-input shifted every later slot by one, and once the alignment was off the - `control_after_generate` marker was consumed as a real value too — a - Seedance 2.0 graph converted with `model.auto_upscale` holding the seed and - `seed` holding `"randomize"`. `validate` catches the seed type but not the - boolean, so fixing only the seed still submitted the wrong graph. A sub-input - the save never carried now takes no slot, and a save that names one the - option no longer declares falls back to the current expansion untouched. - UI→API conversion no longer synthesizes an input for an optional widget the saved node never carried. `graphToPrompt()` serializes the widgets a node actually has, so padding one from its schema default attached inputs the @@ -295,9 +291,74 @@ history. frontend wrote when it marked only the widgets converted to a socket. A dict widget declared as one input but marked per leaf (`regions.face_oval`) counts as marked, so its default survives too. + +- UI→API conversion gives a subgraph's promoted input value to every plain + socket inside the subgraph that the input feeds, not only to widgets, as the + frontend's Run button does. In the Qwen Image 2.1 templates the `prompt` + input also feeds a `ComfySwitchNode`'s `on_false` socket. That socket was + dropped, the switch returned `None`, and the image came out blank. When the + instance has no saved value, the value comes from the interior source widget. + +- Two writes to the same value in one `comfy workflow apply` batch now resolve in + the order the specs were given, so the later write wins. Before, random op ids + decided the winner: a later write could be silently ignored, and an earlier + dynamic-combo selector or group-count write could win and break the specs + after it. Op ids keep their 32-hex-character shape. + +## [1.25.0] - 2026-11-03 + +[Full notes](https://github.com/Comfy-Org/comfy-cli/releases/tag/v1.25.0) · 17 commits since v1.24.0. + +### Added + +- `comfy assets library upload --type ` puts a `.safetensors` + model file of up to 2 GB into your Comfy Cloud workspace's model library, + e.g. `comfy assets library upload my_style.safetensors --type loras`. The + file name, size, that the file can be read, and `--type` are checked before + anything is sent (`--type` against the folders the workspace takes); a file + that cannot be read mid-transfer ends as `asset_upload_failed` with + `details.reason` `file_unreadable`, and a TLS setting that stops the transfer + (e.g. `REQUESTS_CA_BUNDLE` naming a missing file) with `details.reason` + `tls_setup` and its message; neither is retried. The bytes stream straight to + storage with the same progress line and events as `comfy build push`, and + the command waits for Comfy Cloud to store the file, then prints the asset + id, name, folder and hash (`--json`: the `assets_library` schema). A + refusal from Comfy Cloud, such as uploads being off for the workspace or the + model storage cap being reached, is shown with the server's message as + `asset_upload_refused`; new codes `asset_upload_invalid`, + `asset_upload_failed` and `asset_upload_timeout` cover the other ways it + can end. + +- `comfy knowledge resolve` suggests canonical model ids for an incomplete + family/version name such as `Qwen 2.1`. The command still fails with + `knowledge_unknown_model` and exit 1, but `error.details.candidate_ids` lists + up to five sorted, distinct ids whose id or alias has the same family word + and the same numeric components in order, and the hint names them and asks + which model is intended before retrying `comfy knowledge resolve `. + A single candidate is still only a suggestion: nothing is auto-resolved, + downloaded or run. Substituted family words, different versions and names + with non-ASCII letters or digits get no candidates. Exact id and alias + resolution, `close_matches` and the hint for a name with no candidates are + unchanged. + +### Changed + +- A `connect` into a widget input of an agent-built node is now type-checked. + `comfy workflow add-node` gives every widget input a socket entry (see Fixed + below), so a link into one is an ordinary connect to an existing slot rather + than a `grow` that minted a new slot and took the source's type unchecked. A + mismatched scalar — `INT` into a `FLOAT` widget such as `force_rate`, or + `IMAGE` into a `COMBO` — now fails the existing type check instead of being + accepted silently. A `COMBO` widget socket still accepts `COMBO`, `STRING`, + `INT` and `FLOAT`, because that is how a computed file name or a numeric + option reaches a combo; every other source type is refused. + +### Fixed + - `comfy assets library ls` reports a 401 or 403 as `cloud_unauthorized` even when the server drops the connection partway through its error body, instead of crashing with `IncompleteRead`. + - A typed `comfy model download` with no `--relative-path` now saves into the folder the running local ComfyUI scans for that model type, and says where. On Comfy Desktop that is the shared library, not the install's `models/`. @@ -1487,7 +1548,9 @@ from the terminal. Additive and backward-compatible for interactive use. [releases page](https://github.com/Comfy-Org/comfy-cli/releases) with auto-generated pull-request lists. -[Unreleased]: https://github.com/Comfy-Org/comfy-cli/compare/v1.24.0...HEAD +[Unreleased]: https://github.com/Comfy-Org/comfy-cli/compare/v1.26.0...HEAD +[1.26.0]: https://github.com/Comfy-Org/comfy-cli/compare/v1.25.0...v1.26.0 +[1.25.0]: https://github.com/Comfy-Org/comfy-cli/compare/v1.24.0...v1.25.0 [1.24.0]: https://github.com/Comfy-Org/comfy-cli/compare/v1.23.0...v1.24.0 [1.23.0]: https://github.com/Comfy-Org/comfy-cli/compare/v1.22.0...v1.23.0 [1.22.0]: https://github.com/Comfy-Org/comfy-cli/compare/v1.21.0...v1.22.0