announcement_milestone:"15.3"# (required) The milestone when this feature was first announced as deprecated.
removal_milestone:"16.0"# (required) The milestone when this feature is planned to be removed
breaking_change:true# (required) If this deprecation is a breaking change, set this value to true
reporter:matt_wilson # (required) GitLab username of the person reporting the deprecation
stage:Secure # (required) String value of the stage that the feature was created in. e.g., Growth
issue_url:https://gitlab.com/gitlab-org/gitlab/-/issues/367166 # (required) Link to the deprecation issue in GitLab
body:| # (required) Do not modify this line, instead modify the lines below.
You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status of a vulnerability finding to `Dismissed`. Previously, this mutation used the `id` field to identify findings uniquely. However, this did not work for dismissing findings from the pipeline security tab. Therefore, using the `id` field as an identifier has been dropped in favor of the `uuid` field. Using the 'uuid' field as an identifier allows you to dismiss the finding from the pipeline security tab.
#
# OPTIONAL FIELDS
#
end_of_support_milestone:# (optional) Use "XX.YY" format. The milestone when support for this feature will end.
tiers:# (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
