Continuously Scanning Dependencies after GLAD Update - making Generally Available (GA)
### Problem to solve The first MVC of Continuous Vulnerability Scans has been launched with [Experiment support level](https://docs.gitlab.com/ee/policy/experiment-beta-support.html#experiment). Increasing support to reach Beta is being tracked in https://gitlab.com/groups/gitlab-org/-/epics/11473+ This epics contains the work required to reach the Generally Available level https://docs.gitlab.com/ee/policy/experiment-beta-support.html#generally-available-ga ### Proposal These are high level tasks to give an overview of the work to be done. SSOT will be attached issues and epics. - [x] Complete the production readiness review for Generally Available (GA) level - [x] related Infrastucture epic: https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1113 - [x] related production readiness issue: https://gitlab.com/gitlab-com/gl-infra/readiness/-/issues/66 - [x] Ensure the feature is stable and ready for production use at any scale - [x] Update the UI to reflect the GA level - [x] Remove Beta/Experiment mention - [x] Remove Setting or enable it by default (TBD) - [x] Update the Documentation to reflect the GA level - [ ] Announce in a release post that reflects GA status? (TBC)
epic