2025-09-25: CI/CD variable environment scope is not editable

CI/CD variable environment scope is not editable (Severity 3 (Medium))

Problem: Users were unable to set the environment scope when creating new CI/CD variables at the group level—the option was greyed out and not selectable.

Impact: All GitLab.com users could not set the environment scope for new CI/CD variables at the group level, preventing them from limiting variables to specific environments.

Causes: A code change on September 23rd, 2025 removed backward compatibility for licensed features in the feature flags plugin. This broke the CI/CD variable environment scope functionality because the component was still relying on the old behavior to access the 'groupScopedCiVariables' licensed feature.

Response strategy: We updated the CI group variables component to use the correct mixin for licensed features and deployed the fix. The environment scope field is now editable again.

---

This ticket was created to track INC-4204, by incident.io 🔥