Request: Add version tag to all release filenames

[Ehs6n]

Android builds already include the version in their filenames (e.g., mhrv-rs-android-arm64-v8a-v1.7.6.apk), but other platforms don't (e.g., mhrv-rs-linux-amd64.tar.gz).
Please add the same version tag -v{version} before the file extension to Linux, macOS, Windows, and other release files for consistency.
It would be helpful for identification if all release filenames followed the same pattern and include the version. This makes it clear which version each asset belongs to without any double check.

Example:

• mhrv-rs-linux-amd64-v1.7.6.tar.gz
• mhrv-rs-macos-arm64-app-v1.7.6.zip
• mhrv-rs-windows-amd64-v1.7.6.zip

Thanks!

[therealaleph]

@Ehs6n — fair request, easy fix. Each platform's archive currently has the version baked into the contents (Cargo.toml inside the binary, etc.) but the filename is version-stable. Adding -v{version} suffix to all release artifacts is a 5-line change in the workflow's Make archive step.

What it changes:

• mhrv-rs-linux-amd64.tar.gz → mhrv-rs-linux-amd64-v1.7.7.tar.gz
• mhrv-rs-windows-amd64.zip → mhrv-rs-windows-amd64-v1.7.7.zip
• mhrv-rs-macos-arm64.tar.gz → mhrv-rs-macos-arm64-v1.7.7.tar.gz
• (etc.)
• Android APKs already have the version, no change

Implementation: in .github/workflows/release.yml, the Make archive step uses ${{ matrix.name }}.tar.gz etc. Just need to inject ${VER} in the filename pattern.

Will ship in next release. Tracking this issue as the umbrella.

If you want to take it as a PR (small, similar shape to amiralishoja's #288), the change is in .github/workflows/release.yml around the Make archive step. Otherwise I'll batch it into the next round.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}