SPB Git

Repository Public

RELEASE.md 5.4 KB

# SP Term — Release procedure

# Prerequisites (checked, never created, by the scripts)

  • Xcode 27, XcodeGen.
  • A Developer ID Application certificate with its private key in the login keychain (security find-identity -v -p codesigning).
  • For notarization: a notarytool keychain profile created once by the account owner with xcrun notarytool store-credentials <name>; the scripts only refer to it by name (NOTARY_PROFILE, default MacLustr-Notarize) and never print or modify credentials.

# Versioning

MARKETING_VERSION (semantic version shown to users) and CURRENT_PROJECT_VERSION (build number, increased for every build that leaves the machine) live in project.yml. Bump them, add a section to docs/RELEASE_NOTES.md and to the changelog below, then regenerate the project (Scripts/build.sh generate).

Bundle identifier: ai.spboucher.spterm (configurable in project.yml). Team: 3YM54G49SN.

# Steps

sh
Scripts/build.sh kits          # 1. unit tests of the three packages
Scripts/build.sh test          # 2. integration tests hosted in the app
Scripts/release.sh             # 3. universal Release build, Developer ID signature, hardened runtime, verification
Scripts/smoke.sh "dist/SP Term.app"   # 4. end-to-end check of the signed build
Scripts/notarize.sh            # 5. notarize + staple the app, build/sign/notarize/staple the DMG, SHA-256

Scripts/release.sh prints the identity used, the architectures, the signature flags (runtime) and the entitlements, and fails if codesign --verify --deep --strict fails.

Scripts/notarize.sh uploads the app to Apple's notary service — the only step that sends anything off the machine — and says "notarized" only when the service answers Accepted. Results and Apple's logs are kept in build/notary/ (they contain no credentials). If no valid profile or certificate exists, stop after step 3: the build is signed locally but not notarized, and that is what must be reported.

Nothing is published by these scripts: the DMG stays in dist/.

# Verification of a finished release

sh
codesign --verify --deep --strict --verbose=2 "dist/SP Term.app"
codesign -d --entitlements - --xml "dist/SP Term.app" | plutil -p -
xcrun stapler validate "dist/SP Term.app"
xcrun stapler validate dist/SPTerm-<version>.dmg
spctl --assess --type execute --verbose=2 "dist/SP Term.app"
spctl --assess --type open --context context:primary-signature --verbose=2 dist/SPTerm-<version>.dmg
shasum -a 256 -c dist/SPTerm-<version>.dmg.sha256

# Entitlements

Entitlement Why
com.apple.security.automation.apple-events Lets programs run from a session send Apple Events (still subject to the per-app consent prompt).

No sandbox (see docs/SECURITY.md), no JIT, no library-validation exception, no debugging entitlement.

# Updates

No automatic update mechanism is enabled: there is no distribution URL. When one exists, add Sparkle with an EdDSA-signed appcast served over HTTPS and keep the private key off the build machine's repository.

# Changelog

# 2.0.0 (2) — 2026-11-19

  • "SP Term Next": design language, motion system, window architecture. See docs/RELEASE_NOTES.md.

# 1.0.0 (1) — 2026-11-17

  • First release. See docs/RELEASE_NOTES.md.

# State of this release

2.0.0 (2), built 2026-11-19 on macOS 27.0 / Xcode 27.2:

Item Result
dist/SP Term.app universal (x86_64 arm64), Developer ID Application: Simon-Pierre Boucher (3YM54G49SN), hardened runtime, one entitlement
Notarization (app) Accepted — submission c34b14bf-7989-4d76-a2dc-b5d1697a1dbc
Notarization (DMG) Accepted — submission d9bdb3ea-8f62-4133-b4c3-4f987e281d48
Stapling app and DMG validated with stapler validate
Gatekeeper spctl: accepted, source=Notarized Developer ID (app and DMG)
dist/SPTerm-2.0.0.dmg 8720915 bytes, SHA-256 5a55747280833aed1996aaf298d559bce6fcfc247af15107095b051aa572073d
Step 4 (Scripts/smoke.sh) Not run: it quits every running SP Term by name and an instance was in use. The signed build was checked with the hosted tests, isolated captures and a real click on the close button.
Published Yes, 2026-11-19: https://git.spboucher.ai/sp-term/releases (/releases/sp-term/v2.0.0/SPTerm.dmg); the downloaded file has the same SHA-256 and passes stapler validate and spctl.

Not verified: download-and-open on another Mac, execution of the Intel slice, macOS 14/15, the app inside the mounted DMG.

# State of the previous release

1.0.0 (1), built 2026-11-17 on macOS 27.0 / Xcode 27.2:

Item Result
dist/SP Term.app universal (x86_64 arm64), Developer ID Application: Simon-Pierre Boucher (3YM54G49SN), hardened runtime, one entitlement
Notarization (app) Accepted — submission 7a507c0c-ce4b-47d6-8111-da25c045e712
Notarization (DMG) Accepted — submission 4b91a4c0-efb5-4d42-90d2-fa5f3135d09b
Stapling app and DMG validated with stapler validate
Gatekeeper spctl: accepted, source=Notarized Developer ID (app, DMG, app inside the mounted DMG)
dist/SPTerm-1.0.0.dmg 8 287 990 bytes, SHA-256 9f07160dd2f174d19a4830e90d89656a1accc28f779650a8febeda2e24eb5a00
Published No. Nothing was uploaded except to Apple's notary service.

Apple's JSON answers and logs are in build/notary/ (not versioned; they contain no credentials). Not verified: download-and-open on another Mac, execution of the Intel slice, macOS 14/15.

Files main
Menu

Theme