Releases: selfup/hmrcmd
v0.5.0
Update Code Deps
Unzip the releases zip and you will find:
$ ls releases
darwin-hmrcmd-0.5.0 hmrcmd-0.4.5.exe.sha256 rpi-hmrcmd-0.5.0
darwin-hmrcmd-0.5.0.sha256 linux-hmrcmd-0.5.0 rpi-hmrcmd-0.5.0.sha256
hmrcmd-0.5.0.exe linux-hmrcmd-0.5.0.sha256
Pick your platform of choice.
None of the execs are signed.
All I can do is provide shasums in hopes that they will not be modified.
The known sha256sums are in the repo itself. Here are the known shas for v0.5.0
As a code block:
a40300e786db4089f90864655543c27c548e63ec6b5d6b357e1431a93e2f631b releases/darwin-hmrcmd-0.5.0
92d9c782c81b93648622ab681caf713194c1dcae88abed04260fe5ff7d28e870 releases/linux-hmrcmd-0.5.0
ac8148b8b44db22eba2187f080ba0b3044de868faf17296811ffdae9718bb717 releases/rpi-hmrcmd-0.5.0
181dfd103aee257c43cb0a5ee84d27db20f8c46c4c07e91977910eb4335c7b57 releases/hmrcmd-0.5.0.exe
v0.4.0
Unzip the releases zip and you will find:
$ ls releases
darwin-hmrcmd-0.4.0 hmrcmd-0.4.0.exe.sha256 rpi-hmrcmd-0.4.0
darwin-hmrcmd-0.4.0.sha256 linux-hmrcmd-0.4.0 rpi-hmrcmd-0.4.0.sha256
hmrcmd-0.4.0.exe linux-hmrcmd-0.4.0.sha256
Pick your platform of choice.
None of the execs are signed.
All I can do is provide shasums in hopes that they will not be modified.
The known sha256sums are in the repo itself. Here are the known shas for v0.4.0
As a code block:
439cd49e33900a2eebed5ab95380932cf090c948ed5e268778183ca63a655e75 releases/darwin-hmrcmd-0.4.0
71549d7661d5cd16e40737077763423ff4777ad9d25b4d78bc263c1fcc0a0dfd releases/linux-hmrcmd-0.4.0
24026925265a83352d9dcfd603bf10cca10151d13c0b837a09545ebc5c82f74e releases/rpi-hmrcmd-0.4.0
111853357020248366a7d8021036e98eb8f4d29a5f9e8e617181ef6637d46373 releases/hmrcmd-0.4.0.exe
In the commit this release was created on: the commit for this release
You can use: shasum -a 256 file_name
and see if the checksums match!
Example:
$ shasum -a 256 releases/linux-hmrcmd-0.4.0
71549d7661d5cd16e40737077763423ff4777ad9d25b4d78bc263c1fcc0a0dfd releases/linux-hmrcmd-0.4.0
$ cat releases/linux-hmrcmd-*.sha256
71549d7661d5cd16e40737077763423ff4777ad9d25b4d78bc263c1fcc0a0dfd releases/linux-hmrcmd-0.4.0
v0.3.2
Unzip the releases zip and you will find:
$ ls releases
darwin-hmrcmd-0.3.1 linux-hmrcmd-0.3.1
darwin-hmrcmd-0.3.1.sha256 linux-hmrcmd-0.3.1.sha256
hmrcmd-0.3.1.exe rpi-hmrcmd-0.3.1
hmrcmd-0.3.1.exe.sha256 rpi-hmrcmd-0.3.1.sha256
Pick your platform of choice.
None of the execs are signed.
All I can do is provide shasums in hopes that they will not be modified.
You can use: shasum -a 256 file_name
and see if the checksums match!
Example:
$ shasum -a 256 releases/linux-hmrcmd-0.3.2
71549d7661d5cd16e40737077763423ff4777ad9d25b4d78bc263c1fcc0a0dfd releases/linux-hmrcmd-0.3.2
$ cat releases/linux-hmrcmd-*.sha256
71549d7661d5cd16e40737077763423ff4777ad9d25b4d78bc263c1fcc0a0dfd releases/linux-hmrcmd-0.3.2
v0.3.1
Unzip the releases zip and you will find:
$ ls releases
darwin-hmrcmd-0.3.1 linux-hmrcmd-0.3.1
darwin-hmrcmd-0.3.1.sha256 linux-hmrcmd-0.3.1.sha256
hmrcmd-0.3.1.exe rpi-hmrcmd-0.3.1
hmrcmd-0.3.1.exe.sha256 rpi-hmrcmd-0.3.1.sha256
Pick your platform of choice.
None of the execs are signed.
All I can do is provide shasums in hopes that they will not be modified.
You can use: shasum -a 256 file_name
and see if the checksums match!
Example:
$ shasum releases/linux-hmrcmd-0.3.1
fb4d074090a22d4850929a176bb973eb6eb204e5 releases/linux-hmrcmd-0.3.1
$ cat releases/linux-hmrcmd-0.3.1.sha256
71549d7661d5cd16e40737077763423ff4777ad9d25b4d78bc263c1fcc0a0dfd releases/linux-hmrcmd-0.3.1
Windows vs OSX/Linux paths
Write dotfile to HOME dir
Fix "No File but LocalStorage" Bug
Bug where if the new release was fired up, current JSON config would get wiped 😭
Sync File To Host Filesystem
The Config will now persist on the host machine. Import/Export of config is still doable as well.
There is a manual sync button but it isn't really needed. Just peace of mind 🙏