Closed mturadek-ledger closed 3 months ago
Hi! Sorry for the inconvenience, this issue was resolved in the latest release. The issue was that we didn't bump the release number in one of our scripts.
Is it ok to you to use the latest release with correct binaries names, or you want us to fix them from v20.1-2
?
Hi!
Thank you very much for getting back to me so quickly.
There are no other steps needed.
Many thanks!
No problem 😄 , closing the issue then.
Clarification and motivation
I use automation for building new Docker images:
Unfortunately, version 20.1-2 is still downloaded as version 20.1-1, so the pattern needs to be fixed.
Acceptance criteria
Can you fix the binaries' naming and adequately expose them to the directory (v20.1-2) reflecting the tag (v20.1-2)?