diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-13 18:10:07 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-13 18:10:07 +0300 |
| commit | b38e4ad7e808458e1ad51e55dc5593d1e4044051 (patch) | |
| tree | 23dc57f656f0bfe3584917b3b307f7573f02caea | |
| parent | 2d027c892abf04bbe74d15f205376a27f7107d55 (diff) | |
Add latest changes from gitlab-org/gitlab@master
| -rw-r--r-- | doc/user/compliance/license_compliance/index.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/user/compliance/license_compliance/index.md b/doc/user/compliance/license_compliance/index.md index 9d6f8216a07..f757a548aee 100644 --- a/doc/user/compliance/license_compliance/index.md +++ b/doc/user/compliance/license_compliance/index.md @@ -560,6 +560,9 @@ You can supply a custom root certificate to complete TLS verification by using t ### Migration from `license_management` to `license_scanning` +WARNING: +The `license_management` job was deprecated in GitLab 12.8. The `License-Management.gitlab-ci.yml` template was removed from GitLab 14.0. + In GitLab 12.8 a new name for `license_management` job was introduced. This change was made to improve clarity around the purpose of the scan, which is to scan and collect the types of licenses present in a projects dependencies. GitLab 13.0 drops support for `license_management`. If you're using a custom setup for License Compliance, you're required |