Updates & release notes
The platform ships improvements continuously, and tells you about them the way a mobile OS does. When a new version is live, a small prompt appears with the version number and the highlights of what changed; one click refreshes you onto it (installed app users tap Update now). The full history lives under Support > What’s new.
- Update prompt: the app checks quietly every few minutes (and whenever you return to the tab) whether a newer build is live. Nothing interrupts your work: the prompt waits until you choose to refresh. Once you’ve updated or dismissed a version it won’t ask again, only a genuinely newer build brings it back.
- What’s in the update: each release lists its highlights in plain language, so you know what you’re getting before you refresh. The full feed with longer notes is on the What’s new page.
- Safe releases: every release is shipped through automated checks (types, tests, security scans) and progressive rollout: new modules go live dark and expand cohort by cohort. Each release records its rollback plan, and database changes are expand-only. An update never destroys your data.
- Instant rollback: if anything ever misbehaves, the previous version can be restored in seconds (deployments are immutable), and point-in-time database recovery protects your data independently of app releases.
- Versioned & signed: every release carries a semantic version (v1.2.3) minted automatically by CI, with a tamper-evident provenance record: which commit, which pull request, which automated checks passed. You can see the exact version you are on at the top of What’s new.
- Security updates: releases marked as security fixes show a non-dismissible update prompt so no one keeps running a vulnerable build. The prompt clears caches on update, guaranteeing the fixed version loads.
- Unseen badge: a count on What’s new in the sidebar shows updates you haven’t read yet, synced across your devices.
Rollouts vs releases (for platform operators): two different dials. Rollout stage (off/internal/beta/percent/GA, in Platform ▸ Feature Rollout) controls WHICH ORGS a capability actually behaves as on for; a release note’s audience (all/internal) only controls WHO CAN READ the announcement about it. Platform ▸ Releases edits both inline per release: an Audience select, a Status select (choosing Published goes through the same governed publish path as the Publish button, including the two-person rule when it’s on), and, when the release is tied to a plan feature, a Rollout-stage select on the same row.
Security: release notes are read-only for everyone; only platform operators can author them. Drafts and internal notes are never visible to workspaces.