chore: version packages - #239
Merged
Merged
Conversation
lukepiette
self-requested a review
September 1, 2026 16:56
lukepiette
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
worker-comfyui@5.10.0
Minor Changes
dcab982: Bump the pinned ComfyUI version from 0.29.0 to 0.34.0 (current upstream latest). Workflows exported from recent ComfyUI versions use core nodes that don't exist in 0.29-era images and fail at runtime with "missing node" errors — notably every image consumed as a base by comfyui-wizard. ComfyUI's dependency floors are unchanged between 0.29 and 0.34, so the existing torch 2.11.0+cu128 and transformers<5 pins still apply, and the build-time smoke test gates startup.
Also widens
allowedCudaVersionsto include 13.1 and 13.2. The image bundles its own CUDA 12.8 runtime, so any host with a driver at or beyond the 12.8 floor (driver >= 570) runs it identically — newer host CUDA versions are backward compatible. Without this, endpoints were locked out of the growing share of hosts advertising 13.1/13.2 (including most RTX 5090 and RTX PRO 6000 capacity).Also fixes the release workflow's Docker Hub description sync: the previous action authenticated via Docker Hub's legacy user-login API, which rejects organization access tokens unconditionally — it 401'd on every release since the org token rotation and aborted the job before the GitHub release was created (5.9.0's images shipped to Docker Hub, but its GitHub release was never created, so the Hub never indexed it). The step is now a direct PATCH to the modern namespaces endpoint using the same token, and runs after the GitHub release step so a description failure can never block a release again.