Mark the BLSA flow as beta

Problem

BLSA (the bl_security foundational flow) is a closed, paid beta, but its definition still says feature_maturity: "experimental". Model selection labels it an experiment too.

Change

  • feature_maturity: "beta" in the BLSA flow definition. Its REFERENCE (bl_security/experimental) is a version key and stays.
  • Model selection shows BLSA as Beta (release_state: BETA).
  • Docs: model selection and scan profiles say BLSA is in beta. The BLSA page keeps "closed beta" and lists the group's experiment and beta features setting as a prerequisite.

Impact

Beta flows need one setting experimental flows don't: on GitLab.com, the top-level group must turn on experiment and beta GitLab Duo features. The flow availability check, the item consumers finder and the item consumer policy all enforce it.

Group Before After
Group with BLSA and experiment features on BLSA available BLSA available
Group with BLSA, experiment features off BLSA available BLSA hidden, and scans refused
Group without BLSA hidden hidden

Both groups that have BLSA today have experiment features on, so nobody loses it. Billing doesn't change. Self-Managed and Dedicated don't change: BLSA is saas_only, so it is unavailable there either way. Only the model selection badge changes on every deployment.

How to set up and validate

Tested on 2026-10-22 at a7514cf242b2, on master a7e7f1f36a13.

Check Result
25 spec files covering BLSA (definition, foundational flows, item consumers, Duo Workflow APIs and services, triggers, feature settings) all pass
definition_spec.rb with the maturity set back to experimental fails
sync_foundational_flows_service_spec.rb:840 failed under beta without the group setting; passes with it (fixture updated)
RuboCop; markdownlint, Vale and docs link check on the changed docs no offenses, 0 errors

Context

🤖 Generated with Claude Code

Edited by Meir Benayoun

Merge request reports

Loading
Loading