CLI
Promoting Updates
Promote a tested release from Staging to Production without rebuilding — deploy the exact same bundle your QA approved.
Copy a release from one deployment to another (e.g., Staging → Production):
npx turbopush promote <appSlug> <sourceDeploymentName> <destDeploymentName>yarn turbopush promote <appSlug> <sourceDeploymentName> <destDeploymentName>pnpm turbopush promote <appSlug> <sourceDeploymentName> <destDeploymentName>Why Promote?
- Faster — No need to reassemble release assets
- Safer — Exact same code you tested gets deployed
Recommended workflow: Release to Staging → Test → Promote to Production
Example
npx turbopush promote myapp-ios Staging Production -t "*"yarn turbopush promote myapp-ios Staging Production -t "*"pnpm turbopush promote myapp-ios Staging Production -t "*"Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
appSlug | Yes | - | The app slug |
sourceDeploymentName | Yes | - | Source deployment (e.g., Staging) |
destDeploymentName | Yes | - | Destination deployment (e.g., Production) |
--label, -l | No | latest | Specific release to promote |
--description, --des | No | inherited | Change log |
--disabled, -x | No | inherited | Prevent downloads |
--mandatory, -m | No | inherited | Force update |
--rollout, -r | No | 100 | % of users (not inherited, must be explicit) |
--targetBinaryVersion, -t | No | inherited | Compatible binary versions |
--noDuplicateReleaseError | No | false | Warn instead of error on duplicate |
Optional parameters override values from the source release. If omitted, values are inherited.
How is this guide?