v1.2.0

Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for cargo install in most cases. Install it today with cargo install cargo-binstall, from the binaries below, or if you already have it, upgrade with cargo binstall cargo-binstall.

[Reddit] [Bluesky] [Twitter] [Masto]

In this release:

• We now verify checksum integrity of the crate metadata downloaded from registries (#1183, #1260)

• Pre-built binaries below now support HTTP/3. When building from source, you can use the http3 feature and the --cfg reqwest_unstable rustflag to opt-in to HTTP/3 support as well. (#1261)

• We've added out-of-the-box support for more variants of monorepos (#1244, #1245)

• We now support passing a workspace to --manifest-path (#1246)

  Previously we would load the root Cargo.toml and treat it as the manifest for the crate, which did not work as expected for workspaces.

• We now provide x86_64h-apple-darwin (Intel Haswell architecture tuning) pre-built binaries, for higher performance on macOS! Universal builds are also improved. (#1228, #1234, #1238)

• And of course we support installing binaries for the x86_64h-apple-darwin target. (#1233)

• Finally, we have a new, minimal GitHub Action: - uses: cargo-bins/cargo-binstall@main will install the latest cargo-binstall and do nothing else. (#1269, contributed by @smallstepman)

Bugfixes:

• We've fixed issues that resulted in your terminals getting flooded with too many 429 responses. (#1229, #1231, with thanks to @CAD97, @halostatue, and @0atman)
• We are now case-insensitive when reading the CARGO_REGISTRIES_{registry_name}_INDEX environment variables (#1258)
• The installation scripts had a few bugs:
  • On macOS, it would fail if you had the stock bash (#1254, #1263)
  • It would show a spurious warning if $CARGO_HOME/bin was already in $PATH (#1239, contributed by @tyilo)
  • It would fail if CARGO_HOME didn't exist (#1241, contributed by @gifnksm)

Thank you!

If you've made it this far, thank you! If you care about package signing, or have opinions on it, especially but not exclusively in the Rust context, please visit #1 and tell us all about it!