Update to mflux 0.13.1 #1
Draft
Conversation
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
…test; pin mflux==0.10.0
…tadata content test; pin mflux==0.10.0
…eep backward compatibility
added 20 commits
December 8, 2025 20:36
- Update `Mflux_Pro.py`: Fix TypeError in Fill, Depth, and Redux nodes by aligning `save_images_with_metadata` calls with the new Core signature. - Update `__init__.py`: Register `MfluxFill`, `MfluxDepth`, and `MfluxRedux` in mappings so they appear in the ComfyUI menu.
…ot interfere with json fibos json prompts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi there!
I wanted to update the Mflux-ComfyUI nodes to work with version mflux 0.13.1 to be able to generate with Z-Image Turbo. There is still things missing but I tried to bring over some of the functionality of the new mflux version. I also updated the tests, the readme files and release notes, changelog etc.
More testing and someone looking over this maybe needed.
Why was version 2.0.0 never put into the registry? I seems, the registry still only has the very old original version?
Greetings