Add latest changes from gitlab-org/gitlab@master

3 files changed, 32 insertions, 0 deletions

diff --git a/data/removals/16-0/16-0-vulnerabilityFindingDismiss-mutation.yml b/data/removals/16-0/16-0-vulnerabilityFindingDismiss-mutation.yml
new file mode 100644
index 00000000000..dd9de9e118b
--- /dev/null
+++ b/data/removals/16-0/16-0-vulnerabilityFindingDismiss-mutation.yml
@@ -0,0 +1,11 @@
+- title: "Use of `id` field in vulnerabilityFindingDismiss mutation"
+  announcement_milestone: "15.3"
+  removal_milestone: "16.0"
+  breaking_change: true
+  reporter: abellucci
+  stage: Govern
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/367166
+  body: |
+    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.
+  tiers: Ultimate
+  documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#mutationvulnerabilityfindingdismiss
diff --git a/data/removals/16_0/16-0-PipelineSecurityReportFinding-name-GraphQL-field.yml b/data/removals/16_0/16-0-PipelineSecurityReportFinding-name-GraphQL-field.yml
new file mode 100644
index 00000000000..8d535040686
--- /dev/null
+++ b/data/removals/16_0/16-0-PipelineSecurityReportFinding-name-GraphQL-field.yml
@@ -0,0 +1,10 @@
+- title: "PipelineSecurityReportFinding name GraphQL field"
+  announcement_milestone: "15.1"
+  removal_milestone: "16.0"
+  breaking_change: true
+  reporter: abellucci
+  stage: Govern
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/346335
+  body: |
+    Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https://gitlab.com/gitlab-org/gitlab/-/issues/335372) to include a new `title` field. This field is an alias for the current `name` field, making the less specific `name` field redundant. The `name` field is removed from the PipelineSecurityReportFinding type in GitLab 16.0.
+  tiers: [Ultimate]
diff --git a/data/removals/16_0/16-0-vulnerabilityFindingDismiss-GraphQL-mutation.yml b/data/removals/16_0/16-0-vulnerabilityFindingDismiss-GraphQL-mutation.yml
new file mode 100644
index 00000000000..cb5bb21ea74
--- /dev/null
+++ b/data/removals/16_0/16-0-vulnerabilityFindingDismiss-GraphQL-mutation.yml
@@ -0,0 +1,11 @@
+- title: "vulnerabilityFindingDismiss GraphQL mutation"
+  announcement_milestone: "15.5"
+  removal_milestone: "16.0"
+  breaking_change: true
+  reporter: abellucci
+  stage: Govern
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/375645
+  body: |
+    The `VulnerabilityFindingDismiss` GraphQL mutation has been removed. This mutation was not used often as the Vulnerability Finding ID was not available to users (this field was [deprecated in 15.3](https://docs.gitlab.com/ee/update/deprecations.html#use-of-id-field-in-vulnerabilityfindingdismiss-mutation)). Instead of `VulnerabilityFindingDismiss`, you should use `VulnerabilityDismiss` to dismiss vulnerabilities in the Vulnerability Report or `SecurityFindingDismiss` for security findings in the CI Pipeline Security tab.
+  tiers: [Ultimate]
+  documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#mutationvulnerabilityfindingdismiss