Deprecation Issue for VulnerabilityFindingDismiss

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Deprecation Summary

The VulnerabilityFindingDismiss GraphQL mutation is being deprecated and will be removed. This mutation was never used much, as the Vulnerability Finding ID was not available to users. Users should be using VulnerabilityDismiss to dismiss Vulnerabilities in the Vulnerability Report or SecurityFindingDismiss for Security Findings in the CI Pipeline Security tab.

Breaking Change

  • Does this MR contain a breaking change?

If yes:

  • Add the breaking change label to this issue.
  • Add instructions for how users can update their workflow.

Affected Topology

Who is affected by this deprecation, Self-managed users, SaaS users, or both?

  • Both

Affected Tier

  • Premium
  • 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):
  • 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:

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
  • 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.

Deprecation Milestone

Planned Removal Milestone

Links

Edited by Jonathan Schafer