All pages
Versioning
Manifest versions
Draft and rejected versions can be edited and submitted from Versions on your app page. Once a version is submitted, approved, live or retired, its manifest is immutable. To ship changes after going live, tap New version (pre-filled from your latest version with the patch number bumped), save and submit.
When a new version is approved:
- It becomes the app’s live version and the previous live version moves to retired.
- Every active, paused or pending installation upgrades automatically if the new version adds no scopes or Resident events beyond what the installer already approved.
- If the new version requests additional
scopesorevents, existing installations stay on their current version until the installer approves the update in Your apps (where they see “A newer version asks for more permissions.”). When they tap Review and update, you receiveinstallation.updatedwith the newgranted_scopes.
Removing a capability, scope or event never requires re-consent.
API versions
The REST API is versioned by date in the X-Craving-API-Version header. The current version is 2026-09-01 (passing an unknown version returns 400 unsupported_version). When a breaking change ships under a new date, the previous version remains supported for at least 12 months.
Deprecations
Fields are never removed within an API version. Deprecated fields remain active until the next version date.