SAM v3.2.3 — Proof Before Publish

Nothing changes in the app. This is 3.2.2 with its Windows download named correctly.

Fixed

• Windows: the installer was published under the wrong name. electron-builder writes that
  file with spaces in it, and GitHub turns spaces into dots when a file is attached to a
  release — so the download arrived as SAM.Setup.3.2.2.exe while the update feed, and the
  one-paste installer, both looked for SAM-Setup-3.2.2.exe. Nothing errored: the release
  looked complete, and then every Windows update quietly failed and the install script reported
  no installer found. 3.2.2 has been withdrawn. The file is now named without spaces, so there
  is nothing left to rewrite.

Changed

• A build is published only after it has been proven to start (this is what 3.2.2 was for).
  Packaging used to upload the installers as part of building them, with the check that boots
  the app running afterwards — a report rather than a gate. 3.2.0 is what that cost. The order
  is now build → boot it → check the signature stuck → upload.
• The upload step now also refuses to publish if the update feed points at a file that is not
  actually attached, which is exactly the fault above. Both of these failures were invisible
  from the outside: the download works, and only the next thing quietly stops working.

---

🔒 Verify your download (SHA-256)

The one-paste installers verify this automatically. To check by hand, compute the hash and match:

• macOS/Linux: shasum -a 256 <file>
• Windows (PowerShell): Get-FileHash <file> -Algorithm SHA256

e5c65d22c5c4e86636955f8af499d781e66ff4365bc0bf9ebdfd79c93c7fadfd  SAM-3.2.3-arm64.dmg
bad0751cf2992ad8bfad41155574544233a6c12b3ca09028e6b7c2e42dcf4d59  SAM-3.2.3.AppImage
d4f5a52d585d4d1a0795bc07e061bc39624a3857a56b70ed7a2d9db6d50c8a08  SAM-3.2.3.dmg
ac3191cb5ca83499d556f9382d4c7cc176b48a98f63fb10d363e02b0b9932d69  SAM-Setup-3.2.3.exe
0bd308c352498382fa134ea393f0eda577b19c93e75a474de0bbc688c6e5521e  sam_3.2.3_amd64.deb