Announce removal of `version` field in feature flag API
For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features
Release notes
In GitLab 17.0, we are removing the already optional and ignored version
parameter on Feature Flag APIs. Support for the version
parameter was deprecated and is ignored since GitLab 14.0. This change might break tools that still send in the version
parameter when they call some Feature Flag APIs.
https://docs.gitlab.com/ee/api/feature_flags.html
Deprecation Summary
From Remove `version` parameter/column from Feature ... (#333460):
In #254324 (closed), we removed access to Legacy Feature Flags for customers. To complete the removal, after becoming confident letting the Feature Flag block access to the Legacy Feature Flag, we will clean up the old feature flag code in our code base.
Specifically, the removal of the optional (and ignored) version
field of the Feature Flag API will affect users that still send it. Those API calls are accepted today even though the field is deprecated and ignored. Once we remove it, those API calls will fail.
Breaking Change
The version
field is for the legacy feature flags and can just be omitted from the user's calls.
Affected Topology
Affected Tier
Checklists
Labels
-
This issue is labeled deprecation, and with the relevant ~devops::
,~group::
, and~Category:
labels. -
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.
Timeline
Please add links to the relevant merge requests.
- As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule:
14.8, 14.9, 14.10, 15.0
–14.8
is the third milestone preceding the major release):-
A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page. -
Documentation has been updated to mark the feature as deprecated.
-
-
On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post. - On the major milestone:
-
The deprecated item has been removed. -
If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.
-
Mentions
-
Your stage's stable counterparts have been @mentioned
on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.- To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams
- If there is no stable counterpart listed for Support please mention
@gitlab-com/support/managers
- If there is no stable counterpart listed for Marketing please mention
@cfoster3
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
Your GPM has been @mentioned
so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.