Releases and approvals
Plan a change ahead of time, roll it out in stages, and require review where it matters.
What a release is#
A release is one planned change to one flag in one environment. It covers a scheduled change, a progressive rollout in stages, or a change waiting for approval. Each step sets an explicit on/off state and a rollout percentage, so running a step twice does no harm. A release has at most 20 steps.
Manage them on the Releases page or from a flag's Releases tab.
Approvals#
Turn on Require approval for an environment, usually production. Direct toggles and rollout, targeting and variant changes there are then refused with APPROVAL_REQUIRED; propose a release instead. A reviewer approves or rejects with a note, and the steps run as planned.
- Release managers and administrators can review. Developers and product managers can propose. Whatever the environment setting, a release proposed by someone who cannot review releases always waits for a reviewer. The proposer still chooses when it happens: start as soon as it is approved, or at a date and time they set (a start time already passed when approval comes runs at once).
- When proposing, you can ask a specific reviewer. They get their own email and the request shows who was asked, but every release manager and administrator is still told and can approve or reject it.
- Only the person who proposed a release can cancel it. Reviewers approve or reject instead.
- You cannot approve your own release unless the operator sets
ALLOW_SELF_APPROVAL=true. - The reviewer must hold the permissions the steps need. A request nobody reviews within 72 hours is cancelled and the proposer is told.
- Reviewers, the proposer and, for failed steps, the people involved are emailed when an email provider is set up. See Observability.
- The emergency stop and rollback are never held up by approval.
How steps run#
A scheduler inside the server checks every 15 seconds. Each due release is claimed with an atomic update, so several instances never run the same step twice. A claim stuck for five minutes is taken over, and temporary faults retry three times. A refused step fails the release and skips the rest.
Limits today