How are existing users impacted? What migration steps/scripts do we need?
We have removed all the .tgz.sha256 and the uncompressed binaries from the release, so workflows depending on the tgz.sha256 (which is very unlikely), and users downloading the uncompressed binary will have to first download the compressed binary and then uncompress it and if necessary cross check and compare the SHA of the binary with respective one in the Github release.
Checklist:
I have:
[ ] updated the documentation and/or roadmap (if required)
alexellis
commented
3 years ago
Fixes #85
Signed-off-by: Utsav Anand utsavanand2@gmail.com
Description
Reduces the number of files uploaded to Github release by only uploading the .tgz and .sha256 files to the release.
How Has This Been Tested?
Tested with this release: https://github.com/utsavanand2/inletsctl/releases/tag/0.6.5
How are existing users impacted? What migration steps/scripts do we need?
We have removed all the .tgz.sha256 and the uncompressed binaries from the release, so workflows depending on the tgz.sha256 (which is very unlikely), and users downloading the uncompressed binary will have to first download the compressed binary and then uncompress it and if necessary cross check and compare the SHA of the binary with respective one in the Github release.
Checklist:
I have:
git commit -s