OLmatter 0891d18fb6 fix(packaging): force LF for .sh/.command to fix macOS/Linux /bin/bash^M ...

Root cause (per Dixon): repo had no .gitattributes, so on Windows git checkout
converted shell scripts to CRLF; release zips built on Windows then carried
CRLF -> macOS/Linux users hit /bin/bash^M: bad interpreter.

Fix (two layers):
- Add .gitattributes: *.sh/*.command = eol=lf (force LF on checkout/commit),
  *.ps1/*.cmd = eol=crlf (PS/cmd friendly), JS/py/md = lf, binaries = binary.
- build_release_zips.ps1 / build_portable.ps1: when writing .sh/.command into
  the zip, replace CRLF with LF (defense-in-depth even if autocrlf slipped).
Also normalize scripts/setup_backend_macos.sh (was CRLF in working tree).
Verified: new zips have ALL .sh/.command as LF.

2026-06-24 21:09:07 +08:00

..

build_portable.ps1

fix(packaging): force LF for .sh/.command to fix macOS/Linux /bin/bash^M

2026-06-24 21:09:07 +08:00

build_release_zips.ps1

fix(packaging): force LF for .sh/.command to fix macOS/Linux /bin/bash^M

2026-06-24 21:09:07 +08:00

build-release-zips.cmd

Simplify release packaging and direct captcha flow

2026-05-27 20:52:57 +08:00

make-portable.cmd

Simplify release packaging and direct captcha flow

2026-05-27 20:52:57 +08:00

upload_release_assets.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

upload-release-assets.cmd

Simplify release packaging and direct captcha flow

2026-05-27 20:52:57 +08:00