[GH-ISSUE #3290] Request manual review: CRT-Nodes didn't merge for unknown reasons #1135

New issue

Open

opened 2026-10-27 21:26:07 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-27 21:26:07 +00:00

Owner

Originally created by @PGCRT on GitHub (Sep 16, 2026).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3290

I'm the publisher of "CRT-Nodes"

I noticed that versions after 2.17.0 (2026-08-25) weren’t being merged into the registry, despite being properly published and appearing in the history without any errors.

There was no blocking notification, automated message, or other indication explaining why the versions weren’t being merged.
From the publisher’s perspective, everything appeared to have succeeded, while the registry silently failed to incorporate the new versions.

What is the expected workflow in this situation?
Are we supposed to figure out ourselves that something went wrong and open a New Issue, or is there supposed to be some notification when a published version cannot be merged into the registry?

Repo: https://github.com/PGCRT/CRT-Nodes
Package: crt-nodes
PublisherId: crt
Last merged version: 2.17.0
Published but unmerged: 2.18.0, 2.19.0, 2.20.0

Originally created by @PGCRT on GitHub (Sep 16, 2026). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3290 I'm the publisher of "CRT-Nodes" I noticed that versions after 2.17.0 (2026-08-25) weren’t being merged into the registry, despite being properly published and appearing in the history without any errors. There was no blocking notification, automated message, or other indication explaining why the versions weren’t being merged. From the publisher’s perspective, everything appeared to have succeeded, while the registry silently failed to incorporate the new versions. What is the expected workflow in this situation? Are we supposed to figure out ourselves that something went wrong and open a New Issue, or is there supposed to be some notification when a published version cannot be merged into the registry? - Repo: https://github.com/PGCRT/CRT-Nodes - Package: `crt-nodes` - PublisherId: `crt` - Last merged version: `2.17.0` - Published but unmerged: `2.18.0`, `2.19.0`, `2.20.0`

bsakaguchi referenced this issue

2026-10-28 21:03:40 +00:00

[PR #1135] [MERGED] Update custom-node-list.json to add playbook-3d nodes #1724