...will work. Until we publish a new release, as v0.5.5 won't have a file subo-v0.5.4-linux-amd64.tar.gz in it.
Could we remove the version number from the published release artifact names and just use the target?
Note: there is a two-step way to do this using the GitHub API but that would be considerably more complex to accomplish, and by-version artifact references would remain possible through the release path
I got tired of manually updating
suboon Linux and wanted to write a script that pulls & installs the latest release.Conveniently, GitHub provides a "
latest" virtual folder for asset downloads so...will work. Until we publish a new release, as v0.5.5 won't have a file
subo-v0.5.4-linux-amd64.tar.gzin it.Could we remove the version number from the published release artifact names and just use the target?
Note: there is a two-step way to do this using the GitHub API but that would be considerably more complex to accomplish, and by-version artifact references would remain possible through the release path