Patching Update Metadata
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>
[--label <releaseLabel>]
[--mandatory <isMandatory>]
[--description <description>]
[--rollout <rolloutPercentage>]
[--disabled <isDisabled>]
[--targetBinaryVersion <targetBinaryVersion>]
tip
To fix broken code, use rollback instead, then release a new update.
Examples
# Mark latest production release as mandatory
npx turbopush patch myapp-ios Production -m
# Increase rollout for v23 to 50%
npx 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) |