Pragma Updates
Pragma releases are built as desktop installers for macOS, Windows, and Linux. Users download the installer for their operating system, and the app can also support update flows after installation.
Users should only need to choose the right operating system, install the app, and keep it updated through the approved release channel.
Release Channels
Release channels let the team separate stable builds from test builds.
| Channel | Purpose |
|---|---|
| Stable | Recommended release for normal users |
| Preview | Early release for testers |
| Development | Internal builds for engineering |
Installer Types
Each release should publish:
- macOS
.dmg. - Windows
.exe. - Linux
.deb. - Linux
.rpm. - Linux
.AppImage.
Version Numbers
Every release should have a clear version number. Users and support teams should be able to tell exactly which version is installed.
Checksums
Checksums let users verify downloaded files.
Example:
sha256sum Pragma-*.AppImage
The value should match the checksum published with the release.
Autoupdate
Autoupdate should help users receive fixes without manually downloading every release. Enterprise users may need admin controls for when updates are allowed.
Production Notes
For production trust:
- macOS builds should be signed and notarized.
- Windows builds should be code-signed.
- Linux packages should use stable package metadata.
- Release files should be stored somewhere durable and public.
- The download page should always point to the current approved release.