Releasing Updates
Once your app is configured and distributed to users, and you've made JavaScript or asset changes, it's time to release them as OTA updates.
Prerequisites
Before releasing updates:
- ✅ Your app must be published to the App Store/Play Store with the DOTA SDK integrated
- ✅ Deployment keys must be configured in your app code
- ✅ You must have generated the JavaScript bundle and assets
See Bundle Generation for creating bundles.
Release Methods
Choose one of the following:
- Web Panel (UI)
- CLI (Terminal)
Best when:
- You prefer a guided UI and visual confirmations
- Non‑technical teammates need to publish
- You want built‑in charts/monitoring as you release
Full walkthrough: Web Panel Deployment Guide
Best when:
- You automate releases in CI/CD
- You need repeatable, scripted workflows
- You want granular options (rollout, semver ranges, patch, Brotli)
Quick start commands:
- yarn
- npm
Install CLI (project):
yarn add --dev @d11/delivr-cli
Check current session:
yarn code-push-standalone whoami
If not logged in, see the login steps in the Installation guide.
Release to Production (100% rollout):
yarn code-push-standalone release <AppName> ./codepush 1.0.0 -d Production -des "Release"
Install CLI (project):
npm install --save-dev @d11/delivr-cli
Check current session:
npm run code-push-standalone -- whoami
If not logged in, see the login steps in the Installation guide.
Release to Production (100% rollout):
npm run code-push-standalone -- release <AppName> ./codepush 1.0.0 -d Production -des "Release"
For complete options, examples, and best practices (rollout, semver ranges, patch bundles, Brotli, promotions), see the detailed guide: CLI Release Management.
More resources
- CLI: Release Management
- Web: Web Panel guide
- SDK: Debugging, API Reference