CLI
Patching Update Metadata
Modify metadata of an existing release — change mandatory status, rollout percentage, or description — without touching the code.
Modify metadata of an existing release without changing the code, for example, if you forgot to mark a critical bug fix as mandatory or you want to increase the rollout percentage of an update:
npx turbopush patch <appSlug> <deploymentName>yarn turbopush patch <appSlug> <deploymentName>pnpm turbopush patch <appSlug> <deploymentName>Tip
To fix broken code, use rollback instead, then release a new update.
Examples
Mark Latest Release as Mandatory
npx turbopush patch myapp-ios Production -myarn turbopush patch myapp-ios Production -mpnpm turbopush patch myapp-ios Production -mIncrease Rollout Percentage
npx turbopush patch myapp-ios Production -l v23 --rollout 50%yarn turbopush patch myapp-ios Production -l v23 --rollout 50%pnpm turbopush patch myapp-ios Production -l v23 --rollout 50%Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
appSlug | Yes | - | The app slug |
deploymentName | Yes | - | The deployment name (e.g., Staging, Production) |
--label, -l | No | latest | Target a specific release. Find labels via deployment history |
--mandatory, -m | No | - | Set as mandatory. Use --mandatory false to make optional |
--description, --des | No | - | Update release description |
--disabled, -x | No | - | Disable/enable downloads. Use --disabled false to re-enable |
--rollout, -r | No | - | Increase rollout % |
--targetBinaryVersion, -t | No | - | Change compatible binary versions (semver range) |
How is this guide?