Releases
A release is an ordered bundle of completed update sets with a version — the thing you promote between environments.
Creating a release
- Releases → New release. Name it, give it a version (e.g.
1.4.0) and pick the app it belongs to. - Link the update sets that make up the release, in the order they should apply.
- Move the release through its states:
draft → ready → published.
Promoting between environments
From the console (or the environment's release view) choose Promote, pick the source release and the target environment. The platform then:
- Exports each linked update set from the source environment.
- Imports them into the target as drafts, running the core version check (a target on an older core version blocks the promotion unless forced).
- Creates a draft release in the target linking the imported sets.
Nothing applies automatically: you review the imported sets in the target and apply them there. Promotion moves changes, never data.
Version discipline
- The release version is yours (semver recommended); the core version is recorded automatically per update set.
- A release that spans multiple apps should be split — releases are app-scoped so the marketplace and promotion stay predictable.