Skip to content

ci(release-matrix): install cargo-zigbuild from its pinned release binary - #55

Open
zeekay wants to merge 1 commit into
mainfrom
ci/zigbuild-install-once
Open

zeekay wants to merge 1 commit into
mainfrom
ci/zigbuild-install-once

Conversation

@zeekay

@zeekay zeekay commented Nov 12, 2026

Copy link
Copy Markdown
Member

release-matrix.yml compiles cargo-zigbuild with cargo install in every one of the five matrix legs (serial, max-parallel: 1), recent release runs being 35-48 min. This downloads the upstream x86_64-unknown-linux-gnu tarball for the same pinned version, checks its sha256 (c636e4f7…a373, identical to upstream's published .sha256), and falls back to the old cargo install on any failure, so a bad download costs time and never a release.

Not run on a runner from here (it needs a tag push); the tarball layout and cargo-zigbuild --version were checked against the asset.

🤖 Generated with Claude Code

…elease binary

Each of the five legs ran cargo install cargo-zigbuild from nothing (the comment on max-parallel records it). Last five release runs took 35-48 min per leg group. Download the upstream x86_64 linux tarball (sha256 pinned, verified against upstream's .sha256), keep the compile as the fallback.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant