Keep the native digest list and manifest LF on every checkout
Soul found that on a Windows clone (core.autocrlf=true) SHA256SUMS and MANIFEST.txt were written with CRLF, so the documented `sha256sum -c SHA256SUMS` failed on every line: each filename ended in \r. CI stayed green only because it checks out on Linux. After this rule and a fresh checkout, the check passes on Starfire for all four binaries. Provenance, recorded here because verify-committed only checks the committed files against the committed sums: run 35912901846 rebuilt all four binaries from scratch after they were committed, and every artifact is byte-identical to the committed file (libmsquic.so.2 c09a72f9..., libgamecult_mesh_quic_native.so 0ee3d283..., msquic.dll c17c6581..., gamecult_mesh_quic_native.dll 9dae391a...). Two independent CI builds produce the same bytes, which shows both where they came from and that the build is reproducible. Self edited this one-line config directly instead of dispatching Hands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
2785f28f5b
commit
cdb8f3ca6d
1 changed files with 7 additions and 0 deletions
7
.gitattributes
vendored
7
.gitattributes
vendored
|
|
@ -22,3 +22,10 @@
|
|||
packages/cultmesh-ts/native/**/*.dll binary
|
||||
packages/cultmesh-ts/native/**/*.so binary
|
||||
packages/cultmesh-ts/native/**/*.so.* binary
|
||||
|
||||
# The digest list and manifest beside them keep LF on every checkout. Left to
|
||||
# `text=auto`, a Windows clone writes them with carriage returns, and the
|
||||
# documented `sha256sum -c SHA256SUMS` then fails on every line (each filename
|
||||
# ends in `\r`) while CI, checking out on Linux, stays green.
|
||||
packages/cultmesh-ts/native/SHA256SUMS text eol=lf
|
||||
packages/cultmesh-ts/native/MANIFEST.txt text eol=lf
|
||||
|
|
|
|||
Loading…
Reference in a new issue