After you create a release, it must be promoted to a channel to be active.
Releases are not editable after being promoted to a channel. However, release notes, version numbers, and the required status can be edited by visiting the channel’s history.
To promote a release:
From the Replicated vendor portal, click Releases.
From the Releases list, find the release you want to promote and click Promote.
The Promote Release dialog opens.
Edit the fields:
Channel: Select the channel where you want to promote the release. The defaults are Stable, Beta, and Unstable. If you created custom channels using the CLI, they are listed here also.
Version label: Enter a version label. If semantic versioning is enabled for the channel, you must use a valid semantic version. For more information, see Enabling Semantic Versioning.
Requirements: Select Prevent this release from being skipped during upgrades to mark the release as required. When a release is required, the admin console requires users to upgrade to that version before they can upgrade to a later version. For example, if you select Prevent this release from being skipped during upgrades for release v2.0.0, users with v1.0.0 deployed must upgrade to v2.0.0 before they can upgrade to a version later than v2.0.0, such as v2.1.0.
After users deploy a required version, they can no longer redeploy, or roll back to, versions earlier than the required version, even if
truein the Application custom resource manifest. For more information about rollbacks, see allowRollback in the Application custom resource topic.
Release notes: Add detailed release notes. The release notes support markdown and are shown to your customer.