What problem does it solve? Cutting a core ComfyUI frontend release is a stateful, non-idempotent pipeline where a published PyPI version cannot be replaced, and merged backports do not guarantee the fixes actually shipped. This Skill prevents the classic failure mode where a release is advertised as fixed while the QA commits sit unreleased past the tag. ## Core Features & Use Cases - Biweekly release orchestration: Fires the biweekly workflow with an explicit target_branch so the resolver cannot pick the wrong minor, and skips dead minors by targeting the branch directly. - Tag-before-publish ordering and recovery: Enforces the correct merge-bump-PR → tag → publish sequence, and recovers failed runs with gh run rerun --failed instead of a risky fresh re-resolve. - Release-done verification: Asserts all four shipped conditions — patch-id content presence on the branch, zero commits past the tag, PyPI latest version, and the ComfyUI requirements.txt pin. - Use Case: When publishing core v1.47.10, fire the biweekly workflow targeting core/1.47, merge the Release-labeled bump PR promptly, rerun failed jobs if the tag-wait times out, then verify PyPI and the ComfyUI pin before claiming the release shipped. ## Quick Start Cut the core 1.47 patch release targeting branch core/1.47 and verify it actually reached PyPI and the ComfyUI requirements.txt pin.
