feat: install mergify-cli from prebuilt release binary#2
Open
sileht wants to merge 1 commit into
Conversation
sileht
commented
Jun 17, 2026
sileht
changed the title
sileht
force-pushed
the
devs/sileht/mrgfy-7660-setup-cli-prebuilt-binaries/install-mergify-cli-prebuilt-release-binaries--f70ad03d
branch
from
f4d8ea7 to
0b2f151
Compare
Member
Author
Revision history
|
sileht
commented
Jun 17, 2026
| if [ -z "${MERGIFY_CLI_VERSION}" ] || [ "${MERGIFY_CLI_VERSION}" = "latest" ]; then | ||
| effective=$(curl -fsSL -o /dev/null -w '%{url_effective}' "https://github.com/${REPO}/releases/latest") \ | ||
| || die "could not reach github.com to resolve the latest mergify-cli release" | ||
| version=${effective##*/tag/} |
Member
Author
There was a problem hiding this comment.
Just pick main for latest
Member
Author
There was a problem hiding this comment.
Done. Dropped the redirect resolution: for latest/empty the action now fetches install.sh from main and lets it resolve+install the latest release; for a pinned version it still fetches install.sh from that release tag. MERGIFY_VERSION just forwards the input.
Replace the Python + uv install path (`uv tool install mergify-cli`) with the mergify-cli prebuilt binary, installed via the CLI's own `install.sh` installer. Why delegate to install.sh rather than re-implement the download/verify: - install.sh owns platform detection, asset naming, and SHA256SUMS verification, so the action doesn't duplicate that logic or have to track it when the asset naming changes (it already changed once between releases). - For a pinned version we fetch install.sh from that release tag (its asset naming matches the binary it installs); for `latest`/empty we fetch it from `main` and let the installer resolve the latest release. Details: - Fetch install.sh (tag or main), run it with MERGIFY_VERSION + MERGIFY_INSTALL_DIR, add the dir to $GITHUB_PATH. - The `mergify_cli_version` output is read back from `mergify --version` (the binary reports its real version), accurate for both pinned and `latest`. - Default bumped to 2026.6.16.1, the first release with prebuilt binaries + install.sh under the canonical versioned asset naming. - Renovate datasource moved pypi -> github-releases (Mergifyio/mergify-cli, pep440). - CI test-install is a matrix over the target triples install.sh supports (linux/macos, x86_64 + aarch64). install.sh currently supports Linux and macOS only; Windows is picked up automatically once install.sh ships a Windows path. BREAKING CHANGE: the `python_version` input is removed (no Python is used) and the action no longer provisions Python/uv on PATH as a side effect. Fixes MRGFY-7660 Change-Id: If70ad03ddf01ec196f051fef6489b68904d02b20
sileht
force-pushed
the
devs/sileht/mrgfy-7660-setup-cli-prebuilt-binaries/install-mergify-cli-prebuilt-release-binaries--f70ad03d
branch
from
0b2f151 to
4a66dc7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the Python + uv install path (
uv tool install mergify-cli) with themergify-cli prebuilt binary, installed via the CLI's own
install.shinstaller.Why delegate to install.sh rather than re-implement the download/verify:
verification, so the action doesn't duplicate that logic or have to track it
when the asset naming changes (it already changed once between releases).
naming matches the binary it installs); for
latest/empty we fetch it frommainand let the installer resolve the latest release.Details:
MERGIFY_INSTALL_DIR, add the dir to $GITHUB_PATH.
mergify_cli_versionoutput is read back frommergify --version(thebinary reports its real version), accurate for both pinned and
latest.install.sh under the canonical versioned asset naming.
pep440).
(linux/macos, x86_64 + aarch64).
install.sh currently supports Linux and macOS only; Windows is picked up
automatically once install.sh ships a Windows path.
BREAKING CHANGE: the
python_versioninput is removed (no Python is used) andthe action no longer provisions Python/uv on PATH as a side effect.
Fixes MRGFY-7660