Please fix the filenames of the 8.22 release binaries to include the version number

[saltedlolly]

As discussed in detail in #138, please fix the filenames of the v8.22 final release, so they use the standard naming convention that was used for the previous releases. This is also the same convention that is used by Bitcoin and Litecoin.

I want to update DigiNode Tools to support v8.22 final but can't until this has been fixed, since there is no way for my download scripts to correctly identify the file names. They should only take a minute or two to rename.

The filenames should be digibyte-8.22.0-aarch64-linux-gnu.tar.gz etc. (i.e. include the version number in the filename.)

Many thanks.

[saltedlolly]

@ycagel @gto90 @JaredTate @SmartArray Can you please fix this? DigiNode Tools is designed to make it is easy to manage installing, updating, and monitoring a DigiByte full node on a linux box. It has a single prerequisite to work - the filenames of the binaries need to be named consistently across releases. It follows the standard naming convention used by Bitcoin, Litecoin and prior releases of DigiByte. The latest release does not follow the standard naming structure so Diginode Tools cannot currently install v8.22 final. Please can this be fixed urgently. I can then add support for the new release.

[JaredTate]

Hang tight @saltedlolly as we will need to release a v8.22.1 wallet in the next couple of days to fix several memory bug fixes and a few other things. We will get the file formatting standardized and also do some updates to DigiByte dot org website to handle same file naming as well.

We were waiting to finish this PR as we have been working on it for a couple of weeks and knew we needed to release another version.: #282

[JaredTate]

The latest release should work for you: https://github.com/DigiByte-Core/digibyte/releases/tag/v8.22.1

Going to close this now. Feel free to reopen if you have any other issues.

[saltedlolly]

@JaredTate Thanks. I spotted a small issue with the arm binary filename that includes some random characters - I guess it was a typo. It's probably a good idea to remove them. I don't have permission to reopen an issue.