Skip to content

Release controls ​

Select your app, deployment and release in the dashboard. Release actions apply to that selected version.

Available actions ​

ControlWhat it does
EditChange required/optional status, notes and rollout percentage.
Pause / ResumeStop or resume offering that release to eligible clients.
PromoteCopy the selected signed artifact to another deployment.
RollbackPublish selected previous content as the new release, after confirmation.

While an action runs, its button shows progress and prevents duplicate submissions. Your dashboard and scroll position stay in place; the release status, history and activity update when it finishes. Navigation between apps or deployments still shows the page loading indicator.

If you see Change saved, but the view could not refresh, the change succeeded. Choose Refresh to reload the latest state; do not publish or roll back again. If the action itself fails, its dialog stays open with the error so you can correct the problem.

Required updates ​

A required update uses the same signature checks and healthy fallback as an optional update. It does not lock out a healthy app if downloading fails. The supplied helper silently installs downloaded updates immediately.

Operator rollback ​

Rollback creates a new release label for known healthy content. Devices receive it on their next update check. It does not remove releases from history or restore an old server database.

Monitoring and audit ​

The summary cards describe the selected deployment over the last 30 days:

CardWhat it counts
DownloadsRetained download reports from clients.
Healthy startsRetained successful-start reports from clients.
Rollback releasesSuccessful rollback publications recorded by the server, including dashboard and terminal actions.
Device rollbacksRetained reports from devices that recovered after an update failed.

Publishing a rollback creates a Rollback release immediately. It does not increment Device rollbacks: that count changes when a device reports an automatic recovery. A published rollback also does not prove that every device has received it. The release-history table's Device rollbacks column shows reports for that release.

Client reports are bounded, deduplicated observations, not lifetime users or independent proof of fleet health. See delivery observations. Combine the dashboard with application crash monitoring and a tested rollout process.

Activity history ​

Activity shows the latest three actions across the selected app, including all its deployments. The deployment label on an event identifies its scope; App-wide actions apply to the app itself.

Choose View activity to open the history when more events are available. Filter by Deployment and Event type, then choose Load older events to continue through matching records. Deployment filters use the names recorded when the actions happened, including renamed or removed deployments. History is no longer limited to the latest 100 events. These controls filter existing records; they do not delete or change activity.

Events use readable labels and identify the actor; your own actions are labelled You. Times use your browser's local timezone. Closing the dialog returns you to the dashboard. Access to history follows the same organisation and app permissions as other project information.

Signed React Native updates. Self-hosted on your infrastructure.