releasing
Installation
SKILL.md
Releasing mergify-cli
Everything is driven by .github/workflows/release.yml. There is no version
to bump in any file — pyproject.toml and Cargo.toml keep their placeholder
versions and the workflow stamps the tag in at build time. Never open a "release
prep" PR.
Versions are calver: YYYY.M.N (no zero padding, N counts releases within the
UTC month from 1, e.g. 2026.10.1). Three components so the version is valid
SemVer for npm, since the CLI shares its version with the test-framework
clients. Releases before October 2026 used YYYY.M.D.N.
RELEASING.md at the repo root is the human-facing runbook and explains why
the flow is shaped this way (GitHub's immutable-releases policy). Read it when
something goes wrong or the workflow itself needs changing.