Deprecate use of id for vulnerabilityFindingDismiss mutation
For guidance on the overall deprecations, removals and breaking changes workflow, please visit https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features
Deprecation Summary
The use of id
as an argument for the vulnerabilityFindingDismiss mutation is being deprecated in favor of uuid
Breaking Change
Does this MR contain a breaking change? yes
Users can use the uuid
argument as a replacement
Affected Topology
This will affect all users
Affected Tier
- Ultimate
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 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.