Releases: javaLux/hashguard
Releases · javaLux/hashguard
Release v5.0.0
What's Changed
- Update dependencies
- improved CLI-Handling
- Refactoring
- improved validation of the hash argument
- improved colored output
Breaking Changes
- the CLI Flag
[-s, --save]for controlling the saving of the calculated hash, must now be set before specifying a command- e.g.
- Old:
hashguard download -s "http://example.com" - New:
hashguard -s download "http://example.com"
- Old:
- e.g.
Added
- Now you can disable the colored output, useful if the output is to be redirected to a file
Release v4.1.0
- Update dependencies
- improve CLI-Handling
- Refactoring
- improve error messages
Added
- You can now use a prefix when passing a hash to specify the algorithm to be used.
Release v4.0.3
- Update dependencies
- Migration to the new Rust Edition 2024
- fix
cargoclippy hints - Reformatting code style
- improve error messages
Release v4.0.2
- Update dependencies
- fix
cargoclippy hints - improve the Hash-Spinner progress bar
Release v4.0.1
- Update dependencies
- Refactoring
- Improved error handling
Added
- Local-Command
- Adding the processed bytes to the ProgressBar spinner during the hash sum calculation
Release v4.0.0
- Update dependencies
- The calculation of the hash sum when downloading a file has been made more efficient. Now the hash sum is calculated directly during the download, which reduces CPU and memory usage. As only small blocks of data are used for the calculation. The same applies to local files and directories.
Changed
- Insecure hash algorithms have been removed (MD5, SHA1)
Added
SHA3hash algorithm is now supported-s, --saveflag, to be able to store the calculated hash sum in a file, stored in the app data directory- Local-Command
- It is now possible to include file and directory names in the calculation of the hash sum by using the
-i, --include-namesflag
- It is now possible to include file and directory names in the calculation of the hash sum by using the
Release v3.1.1
- Update dependencies
Release v3.1.0
- Update dependencies
- Improved panic handling to enhance stability
- Enhanced error messages for better debugging
- Improved CLI command descriptions for clarity
- Refactoring
Added
- pre compiled binaries for Linux, MacOs and Windows
- provided builds for
x86_64andaarch_64(ARM64)
- provided builds for
Changed
- The data directory for log and crash report files has been moved to the user data directory, which varies based on the operating system.
- It is no longer created as a hidden directory.
- Updated logging mechanism:
- Instead of creating a new log file on every app start, logs are now written to a single file until it reaches 1MB.
- Once the file reaches this limit, it is renamed with the
.oldsuffix, and a new log file is created. - This prevents excessive log file creation and improves log management.
- Switched from
color-eyretoanyhowfor error handling. - Removed stack trace display when
logging=debug.
Release v3.0.5
- Update dependencies
Fixed
- with the
downloadcommand, the reading of the file name from the server response was not implemented correctly - this bug has been fixed in this version
Release v3.0.4
- Refactoring
- Update dependencies
- improve user error messages
Fixed
- report handler crashed(panicked) on windows if
RUST_BACKTRACEset to full downloadcommand- parsing
Content-Rangeheader was incorrect - if the header specifies an unknown content size (e.g. Content-Range: bytes 0-1023/*), this was not taken into account
- now a streamed download is initiated in this case
- parsing
Added
infolog level to write only necessary information to the log filedownloadcommand- set connection time out to 25 sec
- display user info during the connection establishment
- improve logging behavior by using the debug log level
- in case of an successfully request, the response headers will be logged
- in case of an failed request, the response headers and the response body will be logged