Release Policies now support additional configuration options that make it easier to standardize how teams run guarded and progressive releases.

What’s new:

• Default traffic progression: Set the number, percentage, and duration of rollout stages
• Default Target-by context: Choose the context kind used for randomization
• Default metric selection: Preselect metrics teams should monitor during releases
• Tag scoping: Apply a policy only to flags with specific tags within an environment

Why it matters
Setting up a guarded or progressive release can be difficult if teams aren’t sure which metrics, contexts, or rollout stages to choose. Release Policies allow admins and engineering leads to define smart defaults so that individual contributors can ship safely without having to configure every detail. This helps teams adopt best practices and ensures consistent, reliable release workflows.

Learn more
Docs