Skip to content

Delete the `json_wrapper_legacy_mode` feature flag

This feature flag was introduced in 13.0, which is more than 12 milestones ago.

As part of our process we want to ensure feature flags don't stay too long in the codebase.

Rollout issue: #369436

The feature flag is enabled by default. Unless it's disabled on GitLab.com, you should keep the feature-flag code branch, otherwise, keep the other branch.

Remaining mentions of the feature flag (click to expand)

It is possible that this MR will still need some changes to remove references to the feature flag in the code. At the moment the gitlab-housekeeper is not always capable of removing all references so you must check the diff and pipeline failures to confirm if there are any issues. It is the responsibility of groupsource code to push those changes to this branch. If they are already removing this feature flag in another merge request then they can just close this merge request.

You can also see the status of the rollout by checking #369436 and https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/-/issues/?search=json_wrapper_legacy_mode&sort=created_date&state=all&label_name%5B%5D=host%3A%3Agitlab.com.

This change was generated by gitlab-housekeeper using the Keeps::DeleteOldFeatureFlags keep.

To provide feedback on your experience with gitlab-housekeeper please create an issue with the label GitLab Housekeeper and consider pinging the author of this keep.

Merge request reports