Murasaki v0.47.3
Murasaki v0.47.3 fixes macOS app-bundle signing order so packaged apps pass strict code-signature verification after all resources and Info.plist entries are written.
Run the packaged default scaffold
Use Murasaki 0.47.4 or newer. The developer-preview CLI detects Apple silicon or Intel, verifies the published SHA256 and strict ad-hoc code signature, explicitly removes quarantine, and launches the app:
pnpm dlx murasaki@latest demo
These are developer previews, not notarized consumer downloads. Production apps should be Developer ID signed and notarized by their publisher.
Build artifacts
| Platform | Installer | Portable app |
|---|---|---|
| macOS Apple silicon | MurasakiDemo-0.47.3-darwin-arm64.dmg | MurasakiDemo-darwin-arm64.app.zip |
| macOS Intel | MurasakiDemo-0.47.3-darwin-x64.dmg | MurasakiDemo-darwin-x64.app.zip |
| Windows x64 | MurasakiDemo-0.47.3-setup.exe | MurasakiDemo-win32-x64.zip |
The macOS demo is validly ad-hoc signed and passes codesign --verify --deep --strict, but is not Developer ID notarized. Browser-downloaded copies may be blocked by Gatekeeper. Windows may show SmartScreen.
Verify downloads against SHA256SUMS.txt.
What changed
- Sign macOS .app bundles only after every resource and Info.plist entry is in place.
- Fail packaging if ad-hoc signing or strict verification fails.
- Prevent the former “a sealed resource is missing or invalid” launch failure.
Create your own
pnpm create murasaki@latest my-app
cd my-app
pnpm dev