Updates and releases

One version

The app, the CLI and the server share one product version (MAJOR.MINOR.PATCH). A version is published once: a new build needs a new version, and every release is kept. The brain on AMP has its own version and release.

What a release contains

• the app's signed disk image (.dmg, Apple silicon);
• the CLI's wheel;
• the app's update archive, with its update signature;
• a manifest and a SHA256SUMS file.

The installer installs the latest release and refuses a file whose checksum, or an app whose signing team, doesn't match it.

How clients update

• The app checks at launch and shows a banner with the release notes: install and restart, or later. It installs only an update signed with the release key it ships with. When a release has no update archive, the banner links the disk image instead.
• The CLI checks when the chat window opens and shows the exact install line for the new version; crewdesk version checks on demand.

Neither waits on the check, and a failed check shows nothing.

Publishing

The server operator builds and signs the app on a Mac, then publishes with crewdesk-hub release, which also builds the CLI wheel, signs the update archive, checks the signature against the app's public key and writes the manifest.

Notarization

Builds are signed with an Apple Developer ID. Notarization is not in place yet; see Roadmap and known limits.