Invalid binary names in Release

[t-webber]

Tools like cargo-binstall want a valid name for the release binaries in the format <binary-name>-<arch>-<os> like

• taplo-cli-x86_64-unknown-linux-gnu
• taplo-cli-armv7-linux-androideabi
• taplo-cli-aarch64-apple-darwnin
• taplo-cli-x86_64-apple-darwnin

As the names used in the releases aren't valid, cargo binstall falls back to compiling from source, which is long, especially in CIs.

Could you use the official name of the platforms for your binaries in the releases?

[LittleBoxOfSunshine]

I was looking to resolve this by adding:

[package.metadata.binstall]
pkg-url = "{ repo }/releases/download/{ version }/{ name }-{ target-family }-{ target-arch }{ archive-suffix }"

Which makes the naming pattern cargo-binstall friendly, but I learned the "gz" format isn't supported: cargo-bins/cargo-binstall#2119

While I am unblocked on Windows we do have use case on Linux as well, so I'll be looking to see what the progress on the linked issue has been.