diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-08 09:12:23 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-08 09:12:23 +0300 |
| commit | 6eed20a9c4ecc6ad0ce1615c9922eb615db7a45f (patch) | |
| tree | 1892908ad91458313725603b7b86023a0e34b3dc /data | |
| parent | 746488c848df9868601d0db51a5d3da65e29e3b6 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data')
| -rw-r--r-- | data/deprecations/15-1-project-pipeline-securityReportFindings.yml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/data/deprecations/15-1-project-pipeline-securityReportFindings.yml b/data/deprecations/15-1-project-pipeline-securityReportFindings.yml index 1bb60adb812..40fe3bf5bff 100644 --- a/data/deprecations/15-1-project-pipeline-securityReportFindings.yml +++ b/data/deprecations/15-1-project-pipeline-securityReportFindings.yml @@ -1,12 +1,12 @@ - title: "project.pipeline.securityReportFindings GraphQL query" # (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 + 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 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/343475 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - Previous work helped [align the vulnerabilities calls for pipeline security tabs](https://gitlab.com/gitlab-org/gitlab/-/issues/343469) to match the vulnerabilities calls for project-level and group-level vulnerability reports. This helped the frontend have a more consistent interface. The old `project.pipeline.securityReportFindings` query was formatted differently than other vulnerability data calls. Now that it has been replaced with the new `project.pipeline.vulnerabilities` field, the old `project.pipeline.securityReportFindings` is being deprecated and will be removed in GitLab 16.0. + Previous work helped [align the vulnerabilities calls for pipeline security tabs](https://gitlab.com/gitlab-org/gitlab/-/issues/343469) to match the vulnerabilities calls for project-level and group-level vulnerability reports. This helped the frontend have a more consistent interface. The old `project.pipeline.securityReportFindings` query was formatted differently than other vulnerability data calls. Now that it has been replaced with the new `project.pipeline.vulnerabilities` field, the old `project.pipeline.securityReportFindings` is being deprecated and will be removed in GitLab 17.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 |