Skip to content

Bump ComfyUI to 0.34.0; fix Docker Hub description sync for org tokens - #238

Open
lukepiette wants to merge 3 commits into
mainfrom
bump-comfyui-0.34
Open

Bump ComfyUI to 0.34.0; fix Docker Hub description sync for org tokens#238
lukepiette wants to merge 3 commits into
mainfrom
bump-comfyui-0.34

Conversation

@lukepiette

Copy link
Copy Markdown
Contributor

Why

ComfyUI pin (0.29.0 → 0.34.0). Workflows exported from current ComfyUI use core nodes that don't exist in older runtimes and fail at execution with "missing node" errors. This is breaking comfyui-wizard (comfy.getrunpod.io), which builds every generated image FROM runpod/worker-comfyui:*-base. ComfyUI's dependency floors are unchanged between 0.29.0 and 0.34.0 (same transformers>=4.50.3, bare torch), so the existing torch==2.11.0+cu128 and transformers<5/huggingface-hub<1 pins still apply, and the build-time ComfyUI startup smoke test gates the release.

Release workflow fix. peter-evans/dockerhub-description authenticates via Docker Hub's legacy user-login API (/v2/users/login + legacy /v2/repositories/...), which rejects organization access tokens unconditionally — per Docker's docs, legacy paths refuse every OAT regardless of scopes. Since the credential rotation to an org token, this step 401s on every release and aborts post-release before the GitHub release is created (5.9.0's release/tag had to be backfilled manually). Replaced with a direct PATCH https://hub.docker.com/v2/namespaces/{ns}/repositories/{repo} using the same DOCKERHUB_TOKEN as a Bearer token (a supported OAT endpoint), and moved gh release create above it so a description failure can never block a release again.

Changes

  • Dockerfile, docker-bake.hcl: COMFYUI_VERSION 0.29.0 → 0.34.0
  • .github/workflows/release.yml: reorder GitHub-release step ahead of description sync; swap the description action for a curl to the namespaces endpoint
  • Changeset: minor (next release 5.10.0)

Validation

  • Release workflow YAML parses.
  • ComfyUI requirements.txt diffed across v0.29.0/v0.30.0/v0.34.0 — no floor changes affecting the image's pinned deps.
  • Runtime behavior is gated by the existing build-time smoke test (fails the release build if ComfyUI can't start).

Follow-ups (separate, comfyui-wizard repo)

Bump the wizard's BASE_IMAGE (lib/parser/dockerfile.ts) to the release this produces and regenerate builtin-nodes.json from the new image's /object_info — the wizard misclassifies post-0.16.4 core nodes until that list is refreshed.

🤖 Generated with Claude Code

lukepiette and others added 3 commits August 31, 2026 13:40
Pin ComfyUI 0.34.0 in Dockerfile and docker-bake.hcl (was 0.29.0).
Replace peter-evans/dockerhub-description (legacy Hub API, rejects
organization access tokens) with a direct PATCH to the namespaces
endpoint, and move GitHub release creation ahead of it so a
description failure can't abort the release.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The image bundles its own CUDA 12.8 runtime; hosts advertising newer
CUDA versions satisfy the driver floor and run it unchanged. Without
these entries, endpoints were locked out of hosts reporting 13.1/13.2
(most RTX 5090 and RTX PRO 6000 capacity).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant