Updates
Desk can check for new builds and download them in the background when your organization publishes releases.
Automatic check
On launch, Desk may query the configured update channel (release base URL). Downloads are hash-verified before apply.
When a newer build is found, Desk shows a What's New card with release highlights (eyebrow, title, and feature rows from whats-new.json on the release CDN). You can download from the card or dismiss it; a bottom banner still tracks download progress and offers Restart when the update is ready.
Check for Updates
Help → Check for Updates… runs a manual check and reports status in the UI. If an update is available, the same What's New card opens even if you dismissed it earlier for that version.
When an update is ready, a Restart banner appears. If you have unsaved changes, Desk prompts you to save before applying the update.
After you install
The first launch of a new version can show a one-shot What's New summary for that build (bundled notes, so it works offline). Dismissing it marks the version as seen so it does not appear again.
Release notes packaging
Editors update src/shared/whats-new.json per release. make stage-updates stages it for the public releases repo (and optional private staff mirror). The app also bundles a copy for offline post-install. Do not put release copy inside Electrobun's *-update.json schema.
Ops: tag v{version} → CI Publish public releases. Private build-repo assets cannot drive Check for Updates.
Installer downloads
Stable releases ship four installers named from package.json version:
| File | Platform |
|---|---|
AnthrenaDesk-{ver}-macos-arm64.dmg | Apple Silicon |
AnthrenaDesk-{ver}-macos-x64.dmg | Intel Mac |
AnthrenaDesk-{ver}-windows-x64-Setup.exe | Windows Inno GUI wizard (ARM PCs use x64 via emulation) |
AnthrenaDesk-{ver}-linux-x64-Setup.tar.gz | Linux |
Bump version in package.json, commit, then tag v{version} to publish.
Channels
| Channel | Typical use |
|---|---|
| Stable | Production releases (make release packaging) |
| Canary / beta | Pre-release builds (for example beta DMGs) |
Your installer and menu version string indicate which channel you are on (for example a canary menu label on beta builds).
Corporate installs
IT may pin a specific version or host updates from an internal mirror. If Check for Updates does nothing, ask whether outbound access to the update host is allowed, or install the next package manually.
Microsoft Store
Store builds ship as MSIX (separate from the Inno .exe). Those installs update through the Store only — Check for Updates explains that when ANTHRENA_WINDOWS_STORE=1 (or future package detection). See docs/windows-packaging/context.md.
Related
- Getting started
- Security — update network surface