Skip to content

Promoting releases

Promotion copies a release from one deployment to another, typically Staging to Production, without re-bundling anything:

Terminal window
aether promote MyApp Staging Production

By default this takes the latest release in the source deployment. Pick an older one with -l v3.

The destination deployment gets a brand-new release with its own label, releaseMethod: Promote, and two provenance fields: originalLabel (the source release’s label) and originalDeployment (where it came from). The bundle bytes and packageHash stay identical.

Metadata is copied from the source release unless you override it:

Terminal window
aether promote MyApp Staging Production -r 25 -m true --des "Production rollout"
  • --rollout / -r starts the promoted release as a staged rollout in the destination.
  • --mandatory / -m and --disabled / -x set those flags on the new release.
  • --targetBinaryVersion / -t retargets it; without this flag the promoted release keeps the source’s target range.
  • --noDuplicateReleaseError downgrades the identical-package error to a warning, useful when re-promoting.