Skip to content
Snippets Groups Projects

Deprecate use of id for vulnerabilityFindingDismiss mutation

Merged Matt Wilson requested to merge matt_wilson-vulnerabilityFindingDismiss-deprecation into master
All threads resolved!
Files
2
@@ -5,13 +5,13 @@
announcement_milestone: "15.2" # (required) The milestone when this feature was first announced as deprecated.
announcement_date: "2022-07-22" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
removal_milestone: "16.0" # (required) The milestone when this feature is planned to be removed
removal_date: 2023-05-22 # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
removal_date: 2023-05-22 # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
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.
The vulnerabilityFindingDismiss GraphQL mutation can be used to set the status of a vulnerability finding to `Dismissed`. Previously, this mutation used the `id` field to uniquely identify findings. However, this did not work for dismissing findings from the pipeline security tab. Use of this identifier has subsequently been dropped in favor of the `uuid` field which will allow proper dismissal from the pipeline security tab.
The vulnerabilityFindingDismiss GraphQL mutation can be used to set the status of a vulnerability finding to `Dismissed`. Previously, this mutation used the `id` field to uniquely identify findings. However, this did not work for dismissing findings from the pipeline security tab. Use of this identifier has subsequently been dropped in favor of the `uuid` field which will allow proper dismissal from the pipeline security tab.
#
# OPTIONAL FIELDS
#
Loading