What problem does it solve? Releasing the mergify CLI involves a strict two-stage GitHub Actions workflow with immutable releases, a seven-asset requirement, and downstream PyPI and Homebrew propagation — doing any step by hand (or in the wrong order) can permanently block a version. This Skill encodes the exact guarded procedure so releases ship correctly and failed runs can be recovered safely. ## Core Features & Use Cases - Two-stage release orchestration: Stage 1 triggers release.yml to build the five-target binary matrix, archives, SHA256SUMS, and a draft release; Stage 2 publishes the draft, which pushes to PyPI via Trusted Publishing. - Guardrails and verification: Enforces pre-flight checks (green CI on main, no leftover drafts), asserts the draft carries exactly seven assets, and verifies PyPI version and the Homebrew tap PR after publishing. - Failure recovery runbook: Provides a symptom-to-fix table covering failed builds, missing assets, immutable-release traps, and PyPI publish outages. - Use Case: You are asked to cut a new version of mergify CLI. The Skill runs pre-flight checks, triggers the workflow, watches the build, hands you the draft URL for approval, then publishes and confirms PyPI and the Homebrew tap picked it up. ## Quick Start Ask the assistant to cut a new release of mergify CLI and it will run the pre-flight checks, trigger the release workflow, and report the draft release URL for your approval before publishing.
