diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-13 09:08:59 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-13 09:08:59 +0300 |
| commit | c053e70de25ad332aa99e4eefadccd7b9b46748e (patch) | |
| tree | 4d904e6248902e3ab8e9058a335b2ad7575780a9 /doc/update | |
| parent | 9d7001c66ec5cd4e3d360f91486f32a2ede294df (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/update')
| -rw-r--r-- | doc/update/deprecations.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 3e31c1ab46c..73c4812fe37 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -1117,7 +1117,7 @@ The GitLab [**License Compliance**](https://docs.gitlab.com/ee/user/compliance/l To continue using GitLab for license compliance, remove the **License Compliance** template from your CI/CD pipeline and add the **Dependency Scanning** template. The **Dependency Scanning** template is now capable of gathering the required license information, so it is no longer necessary to run a separate license compliance job. -Before you remove the **License Compliance** CI/CD template, verify that the `license_scanning_sbom_scanner` and `package_metadata_synchronization` flags are enabled for the instance and that the instance has been upgraded to a version that supports the new method of license scanning. +Before you remove the **License Compliance** CI/CD template, verify that the instance has been upgraded to a version that supports the new method of license scanning. To begin using the Dependency Scanner quickly at scale, you may set up a scan execution policy at the group level to enforce the SBOM-based license scan for all projects in the group. Then, you may remove the inclusion of the `Jobs/License-Scanning.gitlab-ci.yml` template from your CI/CD configuration. |