-
released this
2026-08-18 09:42:58 +00:00 | 21 commits to master since this releaseFixes a macOS packaging fault: v1.0.0 would not open at all, reporting
"WarpEngine Store is damaged and can't be opened."Open it on macOS
The app is ad-hoc signed but not notarised, so macOS asks before running it.
The reliable way through, once it is in your Applications folder:xattr -dr com.apple.quarantine "/Applications/WarpEngine Store.app"If macOS offers Open Anyway under System Settings ▸ Privacy & Security after
a blocked attempt, that works too. Nothing the store itself downloads is affected:
Python fetches those files, and Python does not set the quarantine flag.Notarisation is the only way to remove this step, and it needs a paid Apple
Developer ID.What was wrong
v1.0.0's bundle carried only the linker's ad-hoc signature on the main
executable, with no resource seal —codesign --verifysaid "code has no
resources but signature indicates they must be present". That is an integrity
failure, and macOS reports it as damaged rather than merely unverified, with no
way to approve it.The build now signs the bundle itself (
scripts/after-pack.js), and the result
verifies:valid on disk,satisfies its Designated Requirement, with our own
bundle identifier rather thanElectron.Measured before and after, on the artifact from this release:
v1.0.0 v1.0.1 codesign --verify --deep --strictno resource seal valid on disk launches without quarantine yes yes, self-test passes launches with quarantine reported as damaged still needs the approval above What is attached
macOS arm64 only — the machine this was built and verified on. Windows and
Linux packages need a build on those platforms (npm run dist:win/dist:linux)
and are not attached.Downloads