From c94c1fede0f60fc9d9d2c02fbdc39092ea73e674 Mon Sep 17 00:00:00 2001 From: Hunter Senft-Grupp Date: Wed, 11 Nov 2026 17:26:16 +0000 Subject: [PATCH] docs(changelog): roll Unreleased into 1.25.0 and 1.26.0 v1.25.0 was tagged without a roll, so Unreleased held its nine entries plus everything merged since. Entries present in v1.25.0's CHANGELOG go under 1.25.0; the rest go under 1.26.0. No entry text changed. Co-Authored-By: Claude Sonnet 5.5 --- CHANGELOG.md | 203 ++++++++++++++++++++++++++++++--------------------- 1 file changed, 118 insertions(+), 85 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 51788a9f8..4a8b7ac53 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) · 29 commits since v1.25.0. ### 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,60 @@ 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. ### 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. +- `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 @@ -263,6 +240,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` @@ -281,6 +259,7 @@ history. 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 +274,61 @@ 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. + +## [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 +1518,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