[GH-ISSUE #1865] Version history is not added for most custom node packages #797

New issue

Closed

opened 2026-10-27 21:22:19 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-27 21:22:19 +00:00

Owner

Originally created by @LevelPixel on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1865

Problem:
I noticed that versions for my node packages are not added to the general version history. And for most custom node packages the same situation.
I did not find information whether this is a bug or a behavior specified by the developers.

Current behavior:
My node package (https://github.com/LevelPixel/ComfyUI-LevelPixel) has been listed in the custom-node-list.json of ComfyUI-Manager for more than half a year, during this time I have updated my package and its versions several times. However, the versions still have not appeared in ComfyUI-Manager.
As I understand it, the version update is performed on the side of your ComfyUI organization server and is stored at the path: https://api.comfy.org/nodes/[node-name]/versions

However, for my package, versions are not created, only an empty list is available at this link:
https://api.comfy.org/nodes/comfyui-level-pixel/versions

Questions:

Is this behavior done intentionally for little-known node packages?
Is it possible to somehow perform a request to add the current version of the package to the version history?
Why is the version history dependent on the Internet and only on the api.comfy.org website, and does not include the ability to locally version (in the node package repository)? For example, why not add local manual versioning with a link to github for the corresponding version of the node package? Are there any problems or risks with this?
Where can I find more detailed documentation about how version history works and how the node package is organized in general?

Originally created by @LevelPixel on GitHub (May 23, 2025). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1865 Problem: I noticed that versions for my node packages are not added to the general version history. And for most custom node packages the same situation. I did not find information whether this is a bug or a behavior specified by the developers. Current behavior: My node package (https://github.com/LevelPixel/ComfyUI-LevelPixel) has been listed in the custom-node-list.json of ComfyUI-Manager for more than half a year, during this time I have updated my package and its versions several times. However, the versions still have not appeared in ComfyUI-Manager. As I understand it, the version update is performed on the side of your ComfyUI organization server and is stored at the path: https://api.comfy.org/nodes/[node-name]/versions However, for my package, versions are not created, only an empty list is available at this link: https://api.comfy.org/nodes/comfyui-level-pixel/versions Questions: 1) Is this behavior done intentionally for little-known node packages? 2) Is it possible to somehow perform a request to add the current version of the package to the version history? 3) Why is the version history dependent on the Internet and only on the api.comfy.org website, and does not include the ability to locally version (in the node package repository)? For example, why not add local manual versioning with a link to github for the corresponding version of the node package? Are there any problems or risks with this? 4) Where can I find more detailed documentation about how version history works and how the node package is organized in general?

bsakaguchi closed this issue

2026-10-27 21:22:19 +00:00

bsakaguchi commented

2026-10-27 21:22:20 +00:00

Author

Owner

@ltdrdata commented on GitHub (May 25, 2025):

There was an ongoing implementation of a feature that automatically registers nodes as unclaimed in the system if they were not published to CNR by the author. This likely caused the registration to CNR to fail.

I removed the entry marked as unclaimed. Try running the publish GitHub Action again in the ComfyUI-LevelPixel repo. The publish should succeed this time.

@ltdrdata commented on GitHub (May 25, 2025): There was an ongoing implementation of a feature that automatically registers nodes as unclaimed in the system if they were not published to CNR by the author. This likely caused the registration to CNR to fail. I removed the entry marked as unclaimed. Try running the publish GitHub Action again in the ComfyUI-LevelPixel repo. The publish should succeed this time.

bsakaguchi commented

2026-10-27 21:22:20 +00:00

Author

Owner

@snomiao commented on GitHub (Aug 2, 2025):

Claim My Node Docs

For future visitors to this issue, you can check this tutorial to Claim Your Nodes:

https://docs.comfy.org/registry/claim-my-node

@snomiao commented on GitHub (Aug 2, 2025): ## Claim My Node Docs For future visitors to this issue, you can check this tutorial to Claim Your Nodes: https://docs.comfy.org/registry/claim-my-node

bsakaguchi referenced this issue

2026-10-27 21:32:21 +00:00

[PR #797] [MERGED] support download via aria2 #1528

bsakaguchi referenced this issue

2026-10-27 21:32:32 +00:00

[PR #829] [MERGED] fix parse aria2 host #1547