Release channels and promotion pipelines

Most teams don't ship a release straight to every environment at once. A build goes to staging first, then production, then out to customer environments over time. But without a structured way to model this, promotion logic ends up scattered across brittle CI workflows, runbooks, and Slack threads.

Release channels and promotion pipelines give this process a formal shape. Channels group environments by rollout stage — staging, production, canary, stable — and promotion pipelines define how a release moves between them. Each step can require a manual approval, wait for a timed duration, or evaluate canary health conditions before promoting.

Pipelines are defined declaratively in your Ryvn YAML configuration: