Projects now have release channels: named streams of releases, like staging and production, and every deployment follows one. Until now every release went to every deployment; channels let parts of your install base move at different speeds, like an internal staging deployment, a cautious enterprise customer, or a region you roll last:

# CI publishes every build to staging
alien release --channel staging

# When it's proven, promote the exact same artifacts to production
alien releases promote rel_8f3ka92 --channel production

Promotion doesn't rebuild anything, so production runs the exact bytes staging tested. It's also how you roll back: promote an earlier release and the channel's deployments follow. Every project gets a production channel automatically, and alien release with no flags advances it, so if you never think about channels, nothing changes.

Every release also has a detail page now: each deployment classified as updated, updating, failed, pending, or pinned, with rollout durations, failures sorted first, and a live view while the rollout is in flight.

• Channels are groupings, not environments: staging, regions, one nervous enterprise account
• Rollback is a promotion: point the channel at an earlier release
• Nothing hides: pinned and failed deployments stay visible instead of becoming version drift

Read the docs →