Release assets incomplete since v0.3.22 — v0.3.26 has none, v0.3.27 is Windows-only, so mise/ubi installs fail on macOS and Linux

[artile]

Summary

GitHub release assets have been degrading since v0.3.22 and are now unusable for anything but Windows. v0.3.26 ships no assets at all; v0.3.27 ships only the Windows zip. Every installer that pulls binaries from GitHub releases — mise, ubi, eget, Homebrew-from-release taps — is therefore stuck on v0.3.25 or older on macOS and Linux.

This is separate from #42 (which is about crates.io lagging master). Even a fresh 0.3.28 publish would not help GitHub-release installers unless the release workflow's build matrix is fixed too.

Asset matrix

Target names are shown with the linear-cli- prefix and archive suffix stripped; checksum files excluded.

tag	assets
v0.3.20	aarch64-apple-darwin x86_64-apple-darwin aarch64-unknown-linux-gnu x86_64-unknown-linux-gnu x86_64-pc-windows-msvc
v0.3.21	aarch64-apple-darwin x86_64-apple-darwin aarch64-unknown-linux-gnu x86_64-unknown-linux-gnu x86_64-pc-windows-msvc
v0.3.22	aarch64-unknown-linux-gnu x86_64-unknown-linux-gnu x86_64-pc-windows-msvc — no macOS
v0.3.23	aarch64-apple-darwin — only
v0.3.24	aarch64-apple-darwin x86_64-apple-darwin x86_64-unknown-linux-gnu — no Windows
v0.3.25	aarch64-apple-darwin x86_64-apple-darwin x86_64-unknown-linux-gnu x86_64-pc-windows-msvc + SHA256SUMS
v0.3.26	none
v0.3.27	x86_64-pc-windows-msvc — only

v0.3.20 and v0.3.21 are the last releases with the full five-target matrix. aarch64-unknown-linux-gnu (ARM Linux — CI runners, Graviton, Raspberry Pi) has been absent since v0.3.22.

Reproduction

$ mise use github:Finesssee/linear-cli@0.3.27
mise ERROR Failed to install github:Finesssee/linear-cli@0.3.27: No matching asset found for platform macos-arm64
Available assets:
linear-cli-x86_64-pc-windows-msvc.zip

v0.3.26 fails the same way with an empty asset list. v0.3.25 installs cleanly:

$ mise use github:Finesssee/linear-cli@0.3.25
mise github:Finesssee/linear-cli@0.3.25 [2/3] verify SLSA provenance
mise github:Finesssee/linear-cli@0.3.25 [3/3] extract linear-cli-aarch64-apple-darwin.tar.gz
mise github:Finesssee/linear-cli@0.3.25 ✓ installed

So 0.3.25 is the newest version a macOS user can pin, and 0.3.21 the newest an ARM-Linux user can pin.

Secondary observation: --version does not match the tag it came from

The binary mise installed for tag v0.3.22 reports a different version:

$ ~/.local/share/mise/installs/github-finesssee-linear-cli/0.3.22/bin/linear-cli --version
linear-cli 0.3.25

I can't fully rule out a re-tag on the release (the v0.3.22 release currently carries no macOS asset at all, yet this install directory holds a working aarch64-apple-darwin binary), so treat this as an observation rather than a confirmed build bug. Either way, it means --version can't be relied on to tell which release a binary came from. Deriving the crate version from the git tag in the release workflow, and publishing SHA256SUMS for every release the way v0.3.25 does, would make this verifiable.

Ask

1. Make the release workflow fail the release when the build matrix is incomplete, rather than publishing a partial or empty set of assets.
2. Restore the full five-target matrix, including aarch64-unknown-linux-gnu.
3. Re-cut assets for v0.3.26/v0.3.27, or publish a 0.3.28 with the complete matrix.

[Finesssee]

Thanks for the issue, I will fix this ASAP.