The skills follow the latest CLI release. When mergify rejects a command or
flag a skill names (unrecognized subcommand, unexpected argument), the
installed CLI is probably older than the skill.
1. Compare versions
mergify --version prints the installed version. The
release notes give the
latest one and the release that added the command. A CLI recent enough to have
mergify self-update --check prints both versions.
2. Ask the user
Upgrading replaces a binary on the user's machine: ask before you do it.
3. Upgrade through the channel that installed it
- Homebrew (
command -v mergifyis under/opt/homebrew/or aCellar/):brew upgrade mergify-cli - uv (
uv tool listnames it):uv tool upgrade mergify-cli - pipx (
pipx listnames it):pipx upgrade mergify-cli - pip (
pip show mergify-clifinds it):pip install --upgrade mergify-cli - Install script or manual download:
mergify self-update
4. Run the command again
If the upgraded CLI still rejects it, the skill names a command no release has yet: tell the user rather than guessing another one.