Loading
Enable mr_pipelines_graphql by default as a beta flag
What does this MR do and why?
Switches mr_pipelines_graphql to a beta flag and enables it by default, so GitLab Self-Managed and Dedicated instances get the GraphQL-backed MR Pipelines tab on upgrade. The flag has been at 100% of actors on GitLab.com since 2026-10-07 with no regressions.
Rollout issue: [Feature flag] Rollout `mr_pipelines_graphql` (#419726)
How to set up and validate locally
- Make sure the flag has no gate in your GDK:
Feature.remove(:mr_pipelines_graphql)in a Rails console. - Open any MR's Pipelines tab. The GraphQL table renders without enabling anything.
Changelog: changed
Edited by Sahil Sharma