NEXTERM — Release & distribution
Distribution is Developer ID + notarization (the app is not sandboxed, so the Mac App Store is not an option). Everything needed is already on this Mac:
| Item | Value |
|---|---|
| Signing identity | Developer ID Application: Simon-Pierre Boucher (3YM54G49SN) (security find-identity -v -p codesigning) |
| Notarization credentials | notarytool keychain profile MacLustr-Notarize (used for MacLustr 5.0.0, accepted 2026-09-29); App Store Connect API keys also present in ~/.appstoreconnect/private_keys/ |
| Hardened runtime | enabled in project.yml (ENABLE_HARDENED_RUNTIME), entitlements in Resources/NEXTERM.entitlements |
| Bundle id / version | ai.spboucher.nexterm, MARKETING_VERSION in project.yml |
Pipeline
bash
Scripts/release.sh # build Release, sign, DMG, notarize (--wait), staple
Scripts/release.sh --skip-notarize # local signed build onlyOutputs: dist/NEXTERM.app (signed, stapled) and dist/NEXTERM-<version>.dmg (signed, notarized, stapled),
dist/notarize.log.
Verification after the pipeline:
bash
codesign --verify --deep --strict --verbose=2 dist/NEXTERM.app
spctl -a -vv -t exec dist/NEXTERM.app # "accepted … source=Notarized Developer ID"
xcrun stapler validate dist/NEXTERM-*.dmgBumping a version
- Edit
MARKETING_VERSION/CURRENT_PROJECT_VERSIONinproject.yml. Scripts/build.sh generate(xcodegen), thenScripts/release.sh.
First-run notes for users
- macOS will ask for Accessibility only if you use the System Events smoke test; the app itself needs no special permissions.
- Privacy prompts (Desktop/Documents/Downloads) appear when a shell in NEXTERM touches those folders — same as Terminal.app.
- Notifications permission is requested the first time a Claude hook event needs attention (only if hooks are enabled).