From a8b6092d5597f1ad76a83eca4dffd78fc8f1c03c Mon Sep 17 00:00:00 2001 From: Marcel Amirault <mamirault@gitlab.com> Date: Tue, 18 Jun 2024 16:00:44 +0000 Subject: [PATCH] Shorten header that is too long --- ...zzing-ci-configuration-create-mutation.yml | 2 +- .../14-8-graphql-project-network-policies.yml | 2 +- ...5-1-pipelinesecurityreportfinding-name.yml | 4 +- ...curityreportfinding-projectfingerprint.yml | 4 +- ...3-vulnerabilityFindingDismiss-mutation.yml | 4 +- ...5-vulnerabilityFindingDismiss-mutation.yml | 2 +- ...led-with-override-runner-setting-value.yml | 5 +- data/deprecations/15-9-Vault-integration.yml | 2 +- ...-3-runner-terminationgracepriodseconds.yml | 2 +- ...name-require_password_to_approve-field.yml | 2 +- doc/update/deprecations.md | 133 +++++++++--------- 11 files changed, 82 insertions(+), 80 deletions(-) diff --git a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml index 9ee015c9883c..282ec79c5397 100644 --- a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml +++ b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml @@ -1,4 +1,4 @@ -- title: "apiFuzzingCiConfigurationCreate GraphQL mutation" +- title: "`apiFuzzingCiConfigurationCreate` GraphQL mutation" announcement_milestone: "14.6" removal_milestone: "15.0" breaking_change: true diff --git a/data/deprecations/14-8-graphql-project-network-policies.yml b/data/deprecations/14-8-graphql-project-network-policies.yml index e9d68987ebef..34654e603a3a 100644 --- a/data/deprecations/14-8-graphql-project-network-policies.yml +++ b/data/deprecations/14-8-graphql-project-network-policies.yml @@ -1,4 +1,4 @@ -- title: "GraphQL networkPolicies resource deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." +- title: "GraphQL `networkPolicies` resource deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed announcement_milestone: "14.8" # (required) The milestone when this feature was first announced as deprecated. breaking_change: true # (required) Change to false if this is not a breaking change. diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml index a77b39c3c7ec..0a47b35c1c4f 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml @@ -1,4 +1,4 @@ -- title: "PipelineSecurityReportFinding name GraphQL field" # (required) The name of the feature to be deprecated +- title: "`name` field for `PipelineSecurityReportFinding` GraphQL type" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (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 @@ -6,7 +6,7 @@ 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/346335 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - 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 will be removed from the PipelineSecurityReportFinding type in GitLab 16.0. + 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 will be removed from the `PipelineSecurityReportFinding` type in GitLab 16.0. # The following items are not published on the docs page, but may be used in the future. tiers: Ultimate # (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] documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml index 6d6d2ec137ad..62c60efc2b08 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml @@ -1,4 +1,4 @@ -- title: "PipelineSecurityReportFinding projectFingerprint GraphQL field" # (required) The name of the feature to be deprecated +- title: "`projectFingerprint` GraphQL field" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. removal_milestone: "17.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 @@ -6,7 +6,7 @@ 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/343475 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 17.0. Starting in 16.1, the output of `project_fingerprint` returns the same value as the `uuid` field. + The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 17.0. Starting in 16.1, the output of `project_fingerprint` returns the same value as the `uuid` field. # The following items are not published on the docs page, but may be used in the future. tiers: Ultimate # (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] documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml b/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml index 1050b0e83274..176ff74fe0b9 100644 --- a/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml +++ b/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- title: "Use of `id` field in vulnerabilityFindingDismiss mutation" # (required) The name of the feature to be deprecated +- title: "Use of `id` field in `vulnerabilityFindingDismiss` mutation" # (required) The name of the feature to be deprecated 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 @@ -9,7 +9,7 @@ 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. + 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 # diff --git a/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml b/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml index cd9fa8796df2..2a289b4070d6 100644 --- a/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml +++ b/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml @@ -1,4 +1,4 @@ -- title: "vulnerabilityFindingDismiss GraphQL mutation" +- title: "`vulnerabilityFindingDismiss` GraphQL mutation" announcement_milestone: "15.5" removal_milestone: "16.0" breaking_change: true diff --git a/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml b/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml index c7712a628ae9..1f61b8ca05d6 100644 --- a/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml +++ b/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml @@ -1,7 +1,7 @@ # # REQUIRED FIELDS # -- title: "GraphQL: The `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` enum is deprecated. Use `DISABLED_AND_OVERRIDABLE` instead" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. +- title: "GraphQL: The `DISABLED_WITH_OVERRIDE` value for the `SharedRunnersSetting` enum is deprecated" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. announcement_date: "2023-01-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: "17.0" # (required) The milestone when this feature is planned to be removed @@ -11,7 +11,8 @@ stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/385636 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be replaced with the value, `DISABLED_AND_OVERRIDABLE`. + In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be removed. + Use `DISABLED_AND_OVERRIDABLE` instead. # # OTHER OPTIONAL FIELDS # diff --git a/data/deprecations/15-9-Vault-integration.yml b/data/deprecations/15-9-Vault-integration.yml index 2f484e15f773..701dde6eb755 100644 --- a/data/deprecations/15-9-Vault-integration.yml +++ b/data/deprecations/15-9-Vault-integration.yml @@ -17,7 +17,7 @@ # # REQUIRED FIELDS # -- title: "HashiCorp Vault integration will no longer use CI_JOB_JWT by default" +- title: "HashiCorp Vault integration will no longer use the `CI_JOB_JWT` CI/CD job token by default" announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed breaking_change: true # (required) Change to false if this is not a breaking change. diff --git a/data/deprecations/16-3-runner-terminationgracepriodseconds.yml b/data/deprecations/16-3-runner-terminationgracepriodseconds.yml index bdb54ab3981c..50898c62e69b 100644 --- a/data/deprecations/16-3-runner-terminationgracepriodseconds.yml +++ b/data/deprecations/16-3-runner-terminationgracepriodseconds.yml @@ -6,7 +6,7 @@ stage: stage # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: "https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28165" # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings). + The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings). # # OPTIONAL END OF SUPPORT FIELDS diff --git a/data/deprecations/16-9-rename-require_password_to_approve-field.yml b/data/deprecations/16-9-rename-require_password_to_approve-field.yml index f22600aa585f..ff7805d41142 100644 --- a/data/deprecations/16-9-rename-require_password_to_approve-field.yml +++ b/data/deprecations/16-9-rename-require_password_to_approve-field.yml @@ -1,4 +1,4 @@ -- title: "Rename the 'require_password_to_approve' field" +- title: "Rename the `require_password_to_approve` field" removal_milestone: "17.0" announcement_milestone: "16.9" breaking_change: true diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 01bc4a0ad703..2b0f5c9ddfa3 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -1137,7 +1137,7 @@ The message field was removed from security reports schema in GitLab 16.0 and is - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28165). </div> -The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings). +The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings). </div> @@ -1381,6 +1381,20 @@ For customers already using documented and supported token types, there are no b <div class="deprecation breaking-change" data-milestone="17.0"> +### GraphQL `networkPolicies` resource deprecated + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/421440). +</div> + +The `networkPolicies` [GraphQL resource](https://docs.gitlab.com/ee/api/graphql/reference/#projectnetworkpolicies) has been deprecated and will be removed in GitLab 17.0. Since GitLab 15.0 this field has returned no data. + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### GraphQL deprecation of `dependencyProxyTotalSizeInBytes` field <div class="deprecation-notes"> @@ -1443,20 +1457,6 @@ Use `totalIssueWeight` instead, introduced in GitLab 16.2. <div class="deprecation breaking-change" data-milestone="17.0"> -### GraphQL networkPolicies resource deprecated - -<div class="deprecation-notes"> -- Announced in GitLab <span class="milestone">14.8</span> -- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/421440). -</div> - -The `networkPolicies` [GraphQL resource](https://docs.gitlab.com/ee/api/graphql/reference/#projectnetworkpolicies) has been deprecated and will be removed in GitLab 17.0. Since GitLab 15.0 this field has returned no data. - -</div> - -<div class="deprecation breaking-change" data-milestone="17.0"> - ### GraphQL type, `RunnerMembershipFilter` renamed to `CiRunnerMembershipFilter` <div class="deprecation-notes"> @@ -1472,7 +1472,7 @@ the aliasing for the `RunnerMembershipFilter` type will be removed. <div class="deprecation breaking-change" data-milestone="17.0"> -### GraphQL: The `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` enum is deprecated. Use `DISABLED_AND_OVERRIDABLE` instead +### GraphQL: The `DISABLED_WITH_OVERRIDE` value for the `SharedRunnersSetting` enum is deprecated <div class="deprecation-notes"> - Announced in GitLab <span class="milestone">15.8</span> @@ -1480,7 +1480,8 @@ the aliasing for the `RunnerMembershipFilter` type will be removed. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385636). </div> -In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be replaced with the value, `DISABLED_AND_OVERRIDABLE`. +In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be removed. +Use `DISABLED_AND_OVERRIDABLE` instead. </div> @@ -1504,7 +1505,7 @@ This is a breaking change that will be completed in 17.0. <div class="deprecation breaking-change" data-milestone="17.0"> -### HashiCorp Vault integration will no longer use CI_JOB_JWT by default +### HashiCorp Vault integration will no longer use the `CI_JOB_JWT` CI/CD job token by default <div class="deprecation-notes"> - Announced in GitLab <span class="milestone">15.9</span> @@ -1839,20 +1840,6 @@ In milestone 17.0, we will remove the `pipelines` attribute from the API respons <div class="deprecation breaking-change" data-milestone="17.0"> -### PipelineSecurityReportFinding projectFingerprint GraphQL field - -<div class="deprecation-notes"> -- Announced in GitLab <span class="milestone">15.1</span> -- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343475). -</div> - -The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 17.0. Starting in 16.1, the output of `project_fingerprint` returns the same value as the `uuid` field. - -</div> - -<div class="deprecation breaking-change" data-milestone="17.0"> - ### PostgreSQL 13 no longer supported <div class="deprecation-notes"> @@ -1926,7 +1913,7 @@ For more information, see [Removing tags from our small SaaS runner on Linux](ht <div class="deprecation breaking-change" data-milestone="17.0"> -### Rename the 'require_password_to_approve' field +### Rename the `require_password_to_approve` field <div class="deprecation-notes"> - Announced in GitLab <span class="milestone">16.9</span> @@ -2421,6 +2408,20 @@ enable `postgres_exporter['flags']['collector.stat_user_tables']` instead. <div class="deprecation breaking-change" data-milestone="17.0"> +### `projectFingerprint` GraphQL field + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343475). +</div> + +The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 17.0. Starting in 16.1, the output of `project_fingerprint` returns the same value as the `uuid` field. + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### npm package uploads now occur asynchronously <div class="deprecation-notes"> @@ -3535,20 +3536,6 @@ The option to delete groups and projects immediately by default was deprecated t <div class="deprecation breaking-change" data-milestone="16.0"> -### PipelineSecurityReportFinding name GraphQL field - -<div class="deprecation-notes"> -- Announced in GitLab <span class="milestone">15.1</span> -- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346335). -</div> - -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 will be removed from the PipelineSecurityReportFinding type in GitLab 16.0. - -</div> - -<div class="deprecation breaking-change" data-milestone="16.0"> - ### PostgreSQL 12 deprecated <div class="deprecation-notes"> @@ -3934,7 +3921,7 @@ In order to make the behavior of toggling the draft status of a merge request mo <div class="deprecation breaking-change" data-milestone="16.0"> -### Use of `id` field in vulnerabilityFindingDismiss mutation +### Use of `id` field in `vulnerabilityFindingDismiss` mutation <div class="deprecation-notes"> - Announced in GitLab <span class="milestone">15.3</span> @@ -3942,7 +3929,7 @@ In order to make the behavior of toggling the draft status of a merge request mo - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/367166). </div> -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. +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. </div> @@ -4048,6 +4035,20 @@ To avoid confusion and duplication, the `environment_tier` parameter is deprecat <div class="deprecation breaking-change" data-milestone="16.0"> +### `name` field for `PipelineSecurityReportFinding` GraphQL type + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346335). +</div> + +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 will be removed from the `PipelineSecurityReportFinding` type in GitLab 16.0. + +</div> + +<div class="deprecation breaking-change" data-milestone="16.0"> + ### `started` iteration state <div class="deprecation-notes"> @@ -4068,7 +4069,7 @@ We plan to continue to support the `started` state in REST API version until the <div class="deprecation breaking-change" data-milestone="16.0"> -### vulnerabilityFindingDismiss GraphQL mutation +### `vulnerabilityFindingDismiss` GraphQL mutation <div class="deprecation-notes"> - Announced in GitLab <span class="milestone">15.5</span> @@ -5544,6 +5545,22 @@ In milestone 15.0, we will completely remove `Version` from `PackageType`. <div class="deprecation breaking-change" data-milestone="15.0"> +### `apiFuzzingCiConfigurationCreate` GraphQL mutation + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">14.6</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/333233). +</div> + +The API Fuzzing configuration snippet is now being generated client-side and does not require an +API request anymore. We are therefore deprecating the `apiFuzzingCiConfigurationCreate` mutation +which isn't being used in GitLab anymore. + +</div> + +<div class="deprecation breaking-change" data-milestone="15.0"> + ### `artifacts:reports:cobertura` keyword <div class="deprecation-notes"> @@ -5667,22 +5684,6 @@ The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines <div class="deprecation breaking-change" data-milestone="15.0"> -### apiFuzzingCiConfigurationCreate GraphQL mutation - -<div class="deprecation-notes"> -- Announced in GitLab <span class="milestone">14.6</span> -- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/333233). -</div> - -The API Fuzzing configuration snippet is now being generated client-side and does not require an -API request anymore. We are therefore deprecating the `apiFuzzingCiConfigurationCreate` mutation -which isn't being used in GitLab anymore. - -</div> - -<div class="deprecation breaking-change" data-milestone="15.0"> - ### bundler-audit Dependency Scanning tool <div class="deprecation-notes"> -- GitLab