This content is associated with a legacy version of the Replicated product. For the current Replicated product documentation, see docs.replicated.com.
The Replicated vendor portal provides you with a location to create and release versions of your application to various release channels. The vendor portal hosts a built-in YAML editor and linter to help you write and validate YAML for the Replicated Native Scheduler.
Once a release is ready to be installed, the release can be promoted to one or more release channels. More details can be found in our Promote Releases documentation.
By default, there are 3 release channels: Stable, Beta and Unstable. When you first log in to Replicated and select the Channels tab, you’ll see these default release channels created. You can delete, edit or create new channels at any time. The channels Replicated creates by default are commonly used for:
The Unstable channel is designed for you to constantly push releases to, much in the same way that you continuously deploy new versions to your cloud product. This is the channel that your development environment should have a license assigned to. This channel is designed to be internal and for testing, not for your customers to be licensed against.
The Beta channel is created for release candidates and early adopting customers. We recommend you promote a release to the Beta channel once it’s passed automated testing in the Unstable channel. You can also choose to license some early-adopting customers against this channel.
For most of your customers, you will create a license that assigns them to the Stable channel. By doing so, they’ll only receive updates when you push a new version to this channel.