Rollback
Rollback restores your installation to the exact state it was in before the last deployment. This includes the previous version, configuration, environment variables, and secrets that were active at that time.Only successful deployments can be rolled back to. Failed deployments won’t appear as rollback options.
Force Deploy
Force Deploy lets you deploy any available version to your installation, regardless of release channels or promotion rules.Force deploy uses the latest configuration and current secrets, combined with the build assets from the selected version.
Automatic Change Protection
After performing a rollback or force deploy, Ryvn automatically blocks all automatic changes to your installation. This prevents promotions, config sync, and other automated updates from overwriting your manual deployment. You’ll see a “Changes Blocked” indicator in the installation header:
- Click on the Changes Blocked status
- Find the active exclusion in the popup
- Click the trash icon to remove it
- Confirm the removal
Additional Notes
- After removing protection: If a newer version is available on your release channel or configuration changes were made while protection was active, those will apply immediately. However, if your installation is on a higher version than the release channel, it will not auto-downgrade.
- Registry deployments: If the image from a previous deployment is no longer available in your registry, the rollback will fail.