fix: CRLF the new scripts, as .gitattributes pins them

zmerge.ps1, zpull.ps1 and zpull.cmd went in with LF endings. .gitattributes
pins *.ps1 and *.cmd to eol=crlf precisely so CHECKSUMS.txt can hold one hash
per file rather than one per platform - so git handed CI a CRLF checkout while
the manifest carried hashes taken from my LF copies, and the three new files
were the only ones that failed.

Local verification passed and CI did not, which is the tell: the manifest was
generated against bytes that only existed on this machine.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
KellyMichels 2026-09-12 15:05:46 -05:00
parent e3ca10f2e3
commit bfddc64743

View File

@ -20,9 +20,9 @@ e904b06017619f0ea13a79c34f56c70e642a5f0aae7dfab55159885aac2ac384 ZHelpers.ps1
1eb4c23bdc0ed1a82dc495c623b49e5dcd4e342f026b4d896e32c79d592667db zkill.ps1
1c908b69fb9200610e080ac6bb8f4c15d3d7edf402d2e119c2405158e1986a52 ZKiller.ps1
558dfdfc7b4d12231e476c14a00c678e2e536140c4b7abbc05364bf214562291 ZKillOnly.ps1
ac391726eead5008ab343e096fa6395d0dd2e3bdc6d556518e7233af7bb60382 zmerge.ps1
5434f004042635622e66f17e096ee7e322e7350a5f6c93c4e51e5b5afeb01df2 zpull.cmd
66029cfecb1af3600061a9b4c4201b1b103bc93b8af7aee3de2c5691ea68b3ca zpull.ps1
b42899ffd20c0b287af0072199d52a945b82123c86b9969cbf68b78b9f81f3d5 zmerge.ps1
b8f89795ccb1f31e9a4feb8abdaa04e764f361b2d2db5e3e13d9ca839afdbf75 zpull.cmd
628d26a64a4765667627db199fee7a0ca80aadebd3299350fa742e66bcd83580 zpull.ps1
36b01f2cd1d5967dc3ec1313fc4f82ada2ea669d0529a0d313300e21a5b38d04 zrelease.cmd
e48b994605b1ad9f793f95d653f50df41db628a6b2c6976415b7d03e3900a373 zrelease.ps1
02635351847f84d0f644ffa9c0073804e480d360fcabcd6a8b793cffd6f0026f zrepair.cmd