Publish releases using standard host triple

[coolaj86]

There are two standards that I'm aware of.

The first is how Rust and Zig do it, which I think is the C-style language quasi-posix standard:

<thing>-<version>-<cpu>-<vendor>-<os>[-toolchain]<.ext>
bls-1.0.0-x86_64-pc-windows-msvc.zip
bls-1.0.0-aarch64-unknown-linux-gnu.tar.gz
bls-1.0.0-x86_64-unknown-linux-musl.tar.gz

The second is how GoReleaser does it, which is basically just omitting "vendor" and "toolchain" and using "mac" rather than "darwin" and "amd64" and "arm64" rather than "x8664" and "aarch64", and using "" more than "-". Perhaps more human friendly, but perhaps not as posix-y:

bls_1.0.0_mac_arm64.tar.gz
bls_1.0.0_windows_arm64.zip
bls_1.0.0_linux_amd64.tar.gz

Since this is a C-family CLI tool, the Rust / Zig style is probably the better choice.

[coolaj86]

See these examples:

• https://clang.llvm.org/docs/CrossCompilation.html
• https://ziglang.org/download/
• https://github.com/BurntSushi/ripgrep/releases/tag/13.0.0

[wmerfalen]

@coolaj86 did you see this? https://github.com/dashhive/bls/releases/tag/v1.0.0 The assets were renamed. That's why I closed this issue.

[wmerfalen]

@coolaj86

Evidence of the github actions completing:

https://github.com/dashhive/bls/actions/runs/3288011090

... and subsequently creating the release (based on tag v2.0.0):

https://github.com/dashhive/bls/releases/tag/v2.0.0

With instructions on how to accomplish it in the README:

https://github.com/dashhive/bls#automating-releases-via-github-actions