Release pipelines are in beta, and are available only to certain customers with an Enterprise or Guardian plan. Aspects of this feature may change without notice or become deprecated in favor of other release management features.
This topic explains how to add, remove, and move flags between existing release pipelines.
After you have created a release pipeline, you are redirected to the releases view to add your first flags to the pipeline. You can add only boolean flags to release pipelines.
To add a flag to a release pipeline:

The release appears in the right sidebar.
You can also use the REST API: Create a new release for flag
After you have set up the automation for each of your phases, you can begin a phase for an individual flag. This activates the automation within that phase for that flag.
To begin a phase for a flag:
Release pipelines run the following automated steps when you start the phase for a flag:
When the phase is complete, the next phase in the release pipeline is marked as “Ready to start.”

When you’re ready for the flag to move through the next phase, click the start arrow for that phase.
Each time a flag begins or completes a phase, anyone following the flag receives an email notification and, if you have the Slack integration configured, a Slack notification.
You can also use the REST API: Update phase status for release
If a flag is already assigned to a release pipeline, you can move it to another pipeline.
To move a flag:
To remove a flag from a release pipeline, navigate to the flag’s right sidebar, click the three-dot overflow menu for the release, and then click Cancel release.
You can also use the REST API: Delete a release for flag