Request manual review: CRT-Nodes didn't merge for unknown reasons

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