Builds are signed with the self-signed "Shift Local Signing" identity and are not notarized, so Gatekeeper calls Shift an unidentified developer. Dragging the app out of the DMG hands that verdict to the app: a fresh machine refuses the first launch until the user approves it in 系统设置 → 隐私与安全性. `scripts/macos-pkg.sh` wraps the built bundle with pkgbuild and the channel now publishes `Shift-macOS-universal.pkg` alongside the DMG. Verified rather than assumed: installing a quarantined copy of the package leaves the installed app with only `com.apple.provenance` — no `com.apple.quarantine` — and `codesign --verify --deep --strict` still passes, because pkgbuild neither re-signs nor strips the payload (CDHash identical across built bundle, DMG copy and pkg copy: 3b7fac6c…). The package is unsigned because `productsign` needs an Installer Signing certificate and this build has only a code-signing identity, so the approval does not vanish — it moves to the download, once, before anything is installed. `installer -pkg … -target /` needs no approval at all. The `macos` manifest key stays a DMG on purpose: `update_install`'s handoff mounts the image with hdiutil, so pointing the key at a .pkg would break in-app updates. |
||
|---|---|---|
| .. | ||
| linux | ||
| build-macos-drag-bridge.sh | ||
| build-windows-release.sh | ||
| macos-pkg.sh | ||
| prepare-ocr-assets.sh | ||
| publish-release.sh | ||
| release-key.py | ||
| windows-installer.nsi | ||