Checksums now verify with sha256sum as well as Get-FileHash
The SHA256SUMS.txt published with each release was written with Windows line endings, which the standard sha256sum tool cannot read: it treats the invisible carriage return as part of the filename, looks for a file that does not exist, and reports that no file was verified. If you verify downloads from WSL, Git Bash, or a Mac, that is what you would have seen.
The file is now written with plain newlines and no byte-order mark, so both the PowerShell Get-FileHash route in the release notes and a direct sha256sum -c run work. The release pipeline checks for a stray carriage return or byte-order mark before publishing, so this cannot return unnoticed. The Windows instructions in the release notes were never affected, and the checksums themselves were always correct.
Highlights
- SHA256SUMS.txt now verifies with sha256sum -c, not just PowerShell.