Adjust removal milestone for project.pipeline.securityReportFindings
What does this MR do and why?
Describe in detail what your merge request does and why.
Bumping the removal of project.pipeline.securityReportFindings to %17.0.
Why?:
- The replacement for this field hasn't been implemented yet
- The frontend is still using the existing field
- The field hasn't been marked as deprecated in the graphql schema, which per the GraphQL deprecation process needs to be done at least 6 months in advance
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Thiago Figueiró