Victor KuznetsovandClaude Opus 5 9bb4e9cd54 Tell a pending ComfyUI upload apart from one that never happened ...

The check read `latest_version` on the node object, which reports only the
ACTIVE version. The registry reviews an upload before activating it, so for the
length of that review a correctly published version looks exactly like a release
that was never synced -- and 0.37.0 hit precisely that: the node repo bumped to
0.1.37 requiring >=0.37.0, the registry accepted it as
NodeVersionStatusPending, and the check called it missing.

Read the versions list instead and branch on the status: active passes, pending
passes while saying so in the summary rather than claiming the node is live, and
anything else fails. A missing version still fails hard, which is the case this
check exists for. Sort the matches by createdAt rather than trusting the
endpoint's current newest-first ordering.

Verified against the live registry in all three states: 0.37.0 pending, 0.36.0
active, 0.99.0 absent and erroring.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-01 18:00:53 -07:00

..

distribute.yml

Reject the uncalibrated text-manifest tiling and verify Content Seal transforms

2026-08-27 16:53:34 -07:00

publish-photo-classify-hf.yml

Point the classify weights at wiltodelta/raiw-photo-classify

2026-09-01 15:33:01 -07:00

publish.yml

chore(deps): bump actions/checkout from 6 to 7 in the actions group (#52)

2026-06-24 09:51:00 -07:00

test.yml

Make the release verification actually verify the Space and the node

2026-09-01 15:33:11 -07:00

verify-release.yml

Tell a pending ComfyUI upload apart from one that never happened

2026-09-01 18:00:53 -07:00