Release channels let you organize your installation releases into groups with similar characteristics, like development builds or production-ready versions. Each environment in your system subscribes to a specific channel, and Ryvn checks maintenance windows to determine when to update environments with the latest compatible installation release.Documentation Index
Fetch the complete documentation index at: https://ryvn.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Default Release Channels
Ryvn includes two built-in release channels:| Channel | Purpose |
|---|---|
staging | Pre-production verification and testing |
production | Live production deployments |
You can configure additional channels to match your specific workflow needs.
Release channel promotion
You can add a release to a channel in one of three ways:1. Default channel assignment
When you publish a new release, it can be automatically added to a default release channel based on your configuration.2. Manual promotion
You can manually promote releases between channels. This is useful when:- You’re responding to support or stability incidents requiring quick version changes
- You want to override the configured promotion pipeline
- You need to run manual testing or validation before promotion
3. Automated promotion
Configure releases to automatically promote between channels based on promotion criteria. A release will move to the next channel when all criteria are met during a maintenance window. To configure automated promotion paths:Add promotion path
- Click Add Promotion Path
- Select the source channel (e.g.,
staging) - Select the target channel (e.g.,
production) - Add promotion criteria:
- Enable security scan checks
- Configure health check requirements
- Set required duration for health checks
- Enable manual approval if needed
- Click Save to create the promotion path
development → staging → production, each with their own promotion criteria.
Promotion criteria
You can use these criteria to control promotion between channels:| Type | Description |
|---|---|
health_check | Release must maintain healthy status in a specified environment for a specified duration |
security_scan | No critical security vulnerabilities found in scan |
manual_approval | Requires manual approval |