sshkeeper/docs
mirivlad 878f7b4472 fix: normalize file modes when packaging a release
release.sh normalized entry order, ownership and mtimes, but not permissions,
so the archives inherited the builder's umask. A host with umask 002 packaged
664/775 while ubuntu-latest packaged 644/755, and the two archives hashed
differently even though every file inside was byte-identical:

  CI     -rw-r--r--  README.md   local  -rw-rw-r--  README.md
  CI     -rwxr-xr-x  sshkeeper   local  -rwxrwxr-x  sshkeeper

Force 755 on directories and the program, 644 on everything else. Building the
same commit under umask 002 and umask 022 now yields identical checksums.

Also correct the reproducibility claim in the release docs. What is reproducible
is the binary, given the same commit and Go version; the archive hash still
depends on the host tar and gzip, so the documented verification step now
compares the extracted binary instead.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 19:06:12 +08:00
..
roadmap docs: align guide and screenshots 2026-06-06 03:35:24 +08:00
screenshots docs: refresh unified tui screenshots 2026-08-18 18:33:14 +08:00
superpowers docs: plan unified tui shell 2026-08-14 07:44:35 +08:00
guide.md docs: refresh unified tui screenshots 2026-08-18 18:33:14 +08:00
release.md fix: normalize file modes when packaging a release 2026-08-18 19:06:12 +08:00