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
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.
# 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
image_url:# (optional) This is a link to a thumbnail image depicting the feature
video_url:# (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
