The v0.1.1 release surfaced two latent gaps:
1. The v0.1.0 tag was on an orphaned merge commit (PR #26 was
re-merged), so `git describe --tags` failed and ComfyUI-Manager
showed the installed version as "unknown".
2. `[tool.comfy] PublisherId` was the placeholder "CristianP", which
does not exist on the Comfy Registry. Every `Publish to Comfy
registry` workflow run since at least Feb 2026 failed with the
misleading `400 "Failed to validate token"`.
Both were the consequence of cutting releases ad-hoc. RELEASING.md
codifies the procedure so future releases follow the same path:
- pre-release validation
- release branch + PR with version bump and CHANGELOG entry
- registry publish validated via workflow_dispatch BEFORE merge
(catches PublisherId / token / version-conflict errors in PR review)
- squash-merge (single commit per release prevents the orphan-tag class)
- annotated tag at the squash-merge SHA
- GitHub Release from the matching CHANGELOG section
- post-release verification (Manager UI + registry status)
Also updates the per-release issue template to mirror RELEASING.md,
and adds links from README and CLAUDE.md so both humans and agents
land on the canonical doc.
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>