websocat.aarch64-unknown-linux-musl binary missing from v1.14.0 assets

[Th0masL]

Hi,

I'm trying to update from v1.13.0 to v1.14.0, and it looks like the binary websocat.aarch64-unknown-linux-musl hasn't been built on v1.14.0.

Any chance you can trigger the CI/CD pipeline again to get that binary built for v1.14.0 ?

Thanks

Thomas

[vi]

CI only builds Docker images (including for aach64).

Most release artifacts are built manually, on my laptop, including websocat_max.aarch64-unknown-linux-musl.

It is visible if you press "Show all 16 assets" button in Github UI.

It's unlikely to be worth touching v1.14 files, as v1.15 (with some minor changes and updates) may be nearing.

[Th0masL]

The file you shared is the _max one, but in the previous releases there was also a non-max one.

# Set file name
file=websocat.aarch64-unknown-linux-musl

# With v1.13.0 - Redirects then download the file
$ curl --silent -I -L https://github.com/vi/websocat/releases/download/v1.13.0/$file | grep "^HTTP/"
HTTP/2 302 
HTTP/2 200 

# With v1.14.0 - File not found
$ curl --silent -I -L https://github.com/vi/websocat/releases/download/v1.14.0/$file | grep "^HTTP/"
HTTP/2 404 

[vi]

Is file size a problem for using the _max version of just the fact that URL is different?

Attached current aarch64 musl build of the current master branch (without _max things) just in case.

websocat_x86_64-unknown-linux-musl.zip

[Th0masL]

I'm using a CI/CD pipeline to download the binaries, so I was hoping to only have to bump the tag in the vars file and the URL would remain the same.

That's fine, I'll continue using v1.13.0 for the moment, and will keep an eye on the repo for the release of v1.15