diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 09:45:46 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 09:45:46 +0000 |
| commit | a7b3560714b4d9cc4ab32dffcd1f74a284b93580 (patch) | |
| tree | 7452bd5c3545c2fa67a28aa013835fb4fa071baf /data | |
| parent | ee9173579ae56a3dbfe5afe9f9410c65bb327ca7 (diff) | |
| download | gitlab-ce-a7b3560714b4d9cc4ab32dffcd1f74a284b93580.tar.gz | |
Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42
Diffstat (limited to 'data')
119 files changed, 990 insertions, 103 deletions
diff --git a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml index 7e2d8338dfd..fd5db7f8835 100644 --- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml +++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml @@ -1,4 +1,4 @@ -- name: "NFS for Git repository storage deprecated" # The name of the feature to be deprecated +- name: "NFS for Git repository storage" # The name of the feature to be deprecated announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml index 72281be5e97..97a7a01b593 100644 --- a/data/deprecations/14-3-repository-push-audit-events.yml +++ b/data/deprecations/14-3-repository-push-audit-events.yml @@ -5,7 +5,7 @@ removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. - Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#repository-push) are now deprecated and will be removed in GitLab 15.0. + Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#repository-push-deprecated) are now deprecated and will be removed in GitLab 15.0. These events have always been disabled by default and had to be manually enabled with a feature flag. Enabling them can cause too many events to be generated which can @@ -13,4 +13,4 @@ stage: Manage tiers: Premium issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/337993 - documentation_url: https://docs.gitlab.com/ee/administration/audit_events.html#repository-push + documentation_url: https://docs.gitlab.com/ee/administration/audit_events.html#repository-push-deprecated diff --git a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml index 60664f785b2..698d8b0dc69 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml @@ -1,19 +1,23 @@ - name: "Certificate-based integration with Kubernetes" announcement_milestone: "14.5" announcement_date: "2021-11-15" - removal_milestone: "15.0" - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed + removal_milestone: "15.6" + removal_date: "2022-11-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | [We are deprecating the certificate-based integration with Kubernetes](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). - The timeline of removal of the integration from the product is not yet planned and we will communicate - more details as they emerge. The certificate-based integration will continue to receive security and + The timeline of removal of the integration from the product is planned to happen in two steps, starting with milestone 15.0 and finishing in GitLab version 15.6. + + In 15.0, we plan to introduce a feature flag that will allow GitLab Self-Managed customers to keep the certificate-based integration enabled, it will be disabled by default. We plan to remove this feature flag together with the underlying code in GitLab version 15.6. + The certificate-based integration will continue to receive security and critical fixes, and features built on the integration will continue to work with supported Kubernetes - versions. We will provide migration plans in a future iteration. See [the list of features affected by this deprecation](https://docs.gitlab.com/ee/user/infrastructure/clusters/#deprecated-features). - For updates and details, follow this [epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). + versions until the final removal in 15.6. For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend the use of the - [Kubernetes Agent](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. + [Kubernetes Agent](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. + We provide [migration plans](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html) in the documentation. + + For updates and details around this deprecation, follow this [epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). stage: Configure tiers: [Free, Silver, Gold, Core, Premium, Ultimate] issue_url: 'https://gitlab.com/groups/gitlab-org/configure/-/epics/8' diff --git a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml index b33f2cc88f1..9cf806da021 100644 --- a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml +++ b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml @@ -1,4 +1,4 @@ -- name: "Converting an instance (shared) runner to a project (specific) runner is deprecated" +- name: "Converting an instance (shared) runner to a project (specific) runner" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml index 6fb97cbc7f4..af172f47ed1 100644 --- a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml +++ b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml @@ -1,4 +1,4 @@ -- name: "Removal of `defaultMergeCommitMessageWithDescription` GraphQL API field" # The name of the feature to be deprecated +- name: "`defaultMergeCommitMessageWithDescription` GraphQL API field" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-deprecate-sles-12sp2.yml b/data/deprecations/14-5-deprecate-sles-12sp2.yml index 61e989defd3..9c6d1f6da52 100644 --- a/data/deprecations/14-5-deprecate-sles-12sp2.yml +++ b/data/deprecations/14-5-deprecate-sles-12sp2.yml @@ -1,4 +1,4 @@ -- name: "Deprecate support for SLES 12 SP2" # The name of the feature to be deprecated +- name: "Support for SLES 12 SP2" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-deprecation-versions-packagetype.yml b/data/deprecations/14-5-deprecation-versions-packagetype.yml index 78db5c0d414..92188b1b21d 100644 --- a/data/deprecations/14-5-deprecation-versions-packagetype.yml +++ b/data/deprecations/14-5-deprecation-versions-packagetype.yml @@ -1,4 +1,4 @@ -- name: "Deprecate `Versions` on base `PackageType`" +- name: "`Versions` on base `PackageType`" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-geo-deprecate-promote-db.yml b/data/deprecations/14-5-geo-deprecate-promote-db.yml index 113ddc53165..81a2d10e35b 100644 --- a/data/deprecations/14-5-geo-deprecate-promote-db.yml +++ b/data/deprecations/14-5-geo-deprecate-promote-db.yml @@ -1,4 +1,4 @@ -- name: "Removal of `promote-db` command from `gitlab-ctl`" # The name of the feature to be deprecated +- name: "`promote-db` command from `gitlab-ctl`" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml index 591ca6f6a87..bbecfcd65ec 100644 --- a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml +++ b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml @@ -1,4 +1,4 @@ -- name: "Removal of `promote-to-primary-node` command from `gitlab-ctl`" # The name of the feature to be deprecated +- name: "`promote-to-primary-node` command from `gitlab-ctl`" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml index 1e6a4e7d378..098be766942 100644 --- a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml +++ b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml @@ -1,4 +1,4 @@ -- name: "Remove the `:dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated +- name: "`dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-remove-pipelines-from-version-field.yml b/data/deprecations/14-5-remove-pipelines-from-version-field.yml index 917442219e5..fc8ec519fa7 100644 --- a/data/deprecations/14-5-remove-pipelines-from-version-field.yml +++ b/data/deprecations/14-5-remove-pipelines-from-version-field.yml @@ -1,4 +1,4 @@ -- name: "Remove the `pipelines` field from the `version` field" # The name of the feature to be deprecated +- name: "`pipelines` field from the `version` field" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml index dd2e6e7a6fb..c3fbe553706 100644 --- a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml +++ b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml @@ -1,4 +1,4 @@ -- name: "REST API Runner will not contain `paused`" +- name: "REST and GraphQL API Runner status will not return `paused`" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed @@ -11,7 +11,7 @@ `online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear. When checking if a runner is `paused`, API users are advised to check the boolean attribute - `active` to be `false` instead. When checking if a runner is `active`, check if `active` is `true`. + `paused` to be `true` instead. When checking if a runner is `active`, check if `paused` is `false`. stage: Verify tiers: [Core, Premium, Ultimate] issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648 diff --git a/data/deprecations/14-6-deprecate-types.yml b/data/deprecations/14-6-deprecate-types.yml index 3e04ad1d6fe..f8886eeef37 100644 --- a/data/deprecations/14-6-deprecate-types.yml +++ b/data/deprecations/14-6-deprecate-types.yml @@ -1,4 +1,4 @@ -- name: "Remove `type` and `types` keyword in CI/CD configuration" # The name of the feature to be deprecated +- name: "`type` and `types` keyword in CI/CD configuration" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml index 55c74ddfabd..e09205f2d9b 100644 --- a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml +++ b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml @@ -1,4 +1,4 @@ -- name: "Deprecate legacy approval status names from License Compliance API" # The name of the feature to be deprecated +- name: "Legacy approval status names from License Compliance API" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml index 8cf0ddc49f4..4f4a2ad8a7d 100644 --- a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml +++ b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml @@ -1,4 +1,4 @@ -- name: "Deprecation of bundler-audit Dependency Scanning tool" # The name of the feature to be deprecated +- name: "bundler-audit Dependency Scanning tool" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml index b9140a84cdd..897886d2d0b 100644 --- a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml +++ b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml @@ -1,4 +1,4 @@ -- name: "Deprecate `pipelines` fields in the Package GraphQL types" +- name: "`pipelines` fields in the Package GraphQL types" announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-6-runner-api-status-renames-not_connected.yml b/data/deprecations/14-6-runner-api-status-renames-not_connected.yml index 5654d3227eb..a535cfbf7a7 100644 --- a/data/deprecations/14-6-runner-api-status-renames-not_connected.yml +++ b/data/deprecations/14-6-runner-api-status-renames-not_connected.yml @@ -1,4 +1,4 @@ -- name: "Deprecation of Runner status `not_connected` API value" +- name: "Runner status `not_connected` API value" announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. removal_milestone: "15.0" # the milestone when this feature is planned to be removed removal_date: "2022-05-22" diff --git a/data/deprecations/14-7-deprecate-artifacts-keyword.yml b/data/deprecations/14-7-deprecate-artifacts-keyword.yml index cbd1a6d41e5..20be00ef6d0 100644 --- a/data/deprecations/14-7-deprecate-artifacts-keyword.yml +++ b/data/deprecations/14-7-deprecate-artifacts-keyword.yml @@ -1,4 +1,4 @@ -- name: "Removal of `artifacts:report:cobertura` keyword" +- name: "`artifacts:report:cobertura` keyword" announcement_milestone: "14.7" announcement_date: "2022-01-22" removal_milestone: "15.0" diff --git a/data/deprecations/14-7-deprecate-merged_by-api-field.yml b/data/deprecations/14-7-deprecate-merged_by-api-field.yml index 31b2d9c9244..e2ecef1aa6a 100644 --- a/data/deprecations/14-7-deprecate-merged_by-api-field.yml +++ b/data/deprecations/14-7-deprecate-merged_by-api-field.yml @@ -15,7 +15,7 @@ announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed - breaking_change: false # If this deprecation is a breaking change, set this value to true + breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-requests) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `merge_user` field (already present in GraphQL) which more correctly identifies who merged a merge request when performing actions (merge when pipeline succeeds, add to merge train) other than a simple merge. # The following items are not published on the docs page, but may be used in the future. diff --git a/data/deprecations/14-7-deprecate-static-site-editor.yml b/data/deprecations/14-7-deprecate-static-site-editor.yml index d8acfbf8ab3..e522699e823 100644 --- a/data/deprecations/14-7-deprecate-static-site-editor.yml +++ b/data/deprecations/14-7-deprecate-static-site-editor.yml @@ -1,4 +1,4 @@ -- name: "Removal of Static Site Editor" # The name of the feature to be deprecated +- name: "Static Site Editor" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. removal_milestone: "15.0" # The milestone when this feature is planned to be removed diff --git a/data/deprecations/14-8-Elasticsearch-6-8.yml b/data/deprecations/14-8-Elasticsearch-6-8.yml new file mode 100644 index 00000000000..20f32966f24 --- /dev/null +++ b/data/deprecations/14-8-Elasticsearch-6-8.yml @@ -0,0 +1,18 @@ +- name: "Elasticsearch 6.8" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + body: | + Elasticsearch 6.8 is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. + Customers using Elasticsearch 6.8 need to upgrade their Elasticsearch version to 7.x prior to upgrading to GitLab 15.0. + We recommend using the latest version of Elasticsearch 7 to benefit from all Elasticsearch improvements. + + Elasticsearch 6.8 is also incompatible with Amazon OpenSearch, which we [plan to support in GitLab 15.0](https://gitlab.com/gitlab-org/gitlab/-/issues/327560). + + stage: Enablement + tiers: [Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350275 + documentation_url: https://docs.gitlab.com/ee/integration/elasticsearch.html#version-requirements + diff --git a/data/deprecations/14-8-ci-build-variables.yml b/data/deprecations/14-8-ci-build-variables.yml new file mode 100644 index 00000000000..52c7ecf6c52 --- /dev/null +++ b/data/deprecations/14-8-ci-build-variables.yml @@ -0,0 +1,16 @@ +- name: "`CI_BUILD_*` predefined variables" + announcement_milestone: "14.8" + announcement_date: "2021-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: dhershkovitch + body: | + The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in GitLab 9.0, and will be removed in GitLab 15.0. If you still use these variables, be sure to change to the current [`CI_JOB_*` predefined variables](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) which are identical (except for the updated name). +# The following items are not published on the docs page, but may be used in the future. + stage: Verify + tiers: [Free, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352957 + documentation_url: https://docs.gitlab.com/ee/ci/variables/predefined_variables.html + 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 diff --git a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml new file mode 100644 index 00000000000..73ba7d8011a --- /dev/null +++ b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml @@ -0,0 +1,16 @@ +- name: "Required pipeline configurations in Premium tier" + announcement_milestone: "14.8" + announcement_date: "2021-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: sam.white + body: | # Do not modify this line, instead modify the lines below. + The [required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers. + + This change to move the feature to GitLab's Ultimate tier is intended to help our features better align with our [pricing philosophy](https://about.gitlab.com/company/pricing/#three-tiers) as we see demand for this feature originating primarily from executives. + + This change will also help GitLab remain consistent in its tiering strategy with the other related Ultimate-tier features of: + [Security policies](https://docs.gitlab.com/ee/user/application_security/policies/) and [compliance framework pipelines](https://docs.gitlab.com/ee/user/project/settings/index.html#compliance-pipeline-configuration). +# The following items are not published on the docs page, but may be used in the future. + stage: "Manage" diff --git a/data/deprecations/14-8-compliance-status-check-api-field.yml b/data/deprecations/14-8-compliance-status-check-api-field.yml new file mode 100644 index 00000000000..f32a8379481 --- /dev/null +++ b/data/deprecations/14-8-compliance-status-check-api-field.yml @@ -0,0 +1,25 @@ +- name: "External status check API breaking changes" + announcement_milestone: "14.8" + announcement_date: "2021-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: sam.white + body: | # Do not modify this line, instead modify the lines below. + The [external status check API](https://docs.gitlab.com/ee/api/status_checks.html) was originally implemented to + support pass-by-default requests to mark a status check as passing. Pass-by-default requests are now deprecated. + Specifically, the following are deprecated: + + - Requests that do not contain the `status` field. + - Requests that have the `status` field set to `approved`. + + Beginning in GitLab 15.0, status checks will only be updated to a passing state if the `status` field is both present + and set to `pass`. Requests that: + + - Do not contain the `status` field will be rejected with a `422` error. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/338827). + - Contain any value other than `pass` will cause the status check to fail. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/339039). + + To align with this change, API calls to list external status checks will also return the value of `pass` rather than + `approved` for status checks that have passed. +# The following items are not published on the docs page, but may be used in the future. + stage: "Manage" diff --git a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml new file mode 100644 index 00000000000..ea75e70afe3 --- /dev/null +++ b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml @@ -0,0 +1,19 @@ +- name: "`projectFingerprint` in `PipelineSecurityReportFinding` GraphQL" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: matt_wilson # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + The `projectFingerprint` field in the [PipelineSecurityReportFinding](https://docs.gitlab.com/ee/api/graphql/reference/index.html#pipelinesecurityreportfinding) + GraphQL object is being deprecated. This field contains a "fingerprint" of security findings used to determine uniqueness. + The method for calculating fingerprints has changed, resulting in different values. Going forward, the new values will be + exposed in the UUID field. Data previously available in the projectFingerprint field will eventually be removed entirely. +# The following items are not published on the docs page, but may be used in the future. + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml new file mode 100644 index 00000000000..a5e5ce6e9ea --- /dev/null +++ b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml @@ -0,0 +1,17 @@ +- name: "Retire-JS Dependency Scanning tool" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + breaking_change: true + body: | # Do not modify this line, instead modify the lines below. + As of 14.8 the retire.js job is being deprecated from Dependency Scanning. It will continue to be included in our CI/CD template while deprecated. We are removing retire.js from Dependency Scanning on May 22, 2022 in GitLab 15.0. JavaScript scanning functionality will not be affected as it is still being covered by Gemnasium. + + If you have explicitly excluded retire.js using DS_EXCLUDED_ANALYZERS you will need to clean up (remove the reference) in 15.0. If you have customized your pipeline's Dependency Scanning configuration related to the `retire-js-dependency_scanning` job you will want to switch to gemnasium-dependency_scanning before the removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference retire.js, or customized your template specifically for retire.js, you will not need to take action. +# The following items are not published on the docs page, but may be used in the future. + stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + 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] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350510 # (optional) This is a link to the deprecation issue in GitLab + documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.html # (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 + removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed diff --git a/data/deprecations/14-8-enforce-pat-expiration.yml b/data/deprecations/14-8-enforce-pat-expiration.yml new file mode 100644 index 00000000000..6c6fdf31fe6 --- /dev/null +++ b/data/deprecations/14-8-enforce-pat-expiration.yml @@ -0,0 +1,13 @@ +- name: "Optional enforcement of PAT expiration" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: djensen # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + The feature to disable enforcement of PAT expiration is unusual from a security perspective. + We have become concerned that this unusual feature could create unexpected behavior for users. + Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature. + issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351962" # (optional) This is a link to the deprecation issue in GitLab + documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-personal-access-tokens-to-be-used-deprecated" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-enforce-ssh-expiration.yml b/data/deprecations/14-8-enforce-ssh-expiration.yml new file mode 100644 index 00000000000..815d592a2a9 --- /dev/null +++ b/data/deprecations/14-8-enforce-ssh-expiration.yml @@ -0,0 +1,13 @@ +- name: "Optional enforcement of SSH expiration" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: djensen # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + The feature to disable enforcement of SSH expiration is unusual from a security perspective. + We have become concerned that this unusual feature could create unexpected behavior for users. + Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature. + issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351963" # (optional) This is a link to the deprecation issue in GitLab + documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-ssh-keys-to-be-used-deprecated" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml new file mode 100644 index 00000000000..137ae01f63b --- /dev/null +++ b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml @@ -0,0 +1,34 @@ +- name: "Deprecate custom Geo:db:* Rake tasks" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: false + reporter: nhxnguyen + body: | + In GitLab 14.8, we are [replacing the `geo:db:*` Rake tasks with built-in tasks](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77269/diffs) that are now possible after [switching the Geo tracking database to use Rails' 6 support of multiple databases](https://gitlab.com/groups/gitlab-org/-/epics/6458). + The following `geo:db:*` tasks will be replaced with their corresponding `db:*:geo` tasks: + + - `geo:db:drop` -> `db:drop:geo` + - `geo:db:create` -> `db:create:geo` + - `geo:db:setup` -> `db:setup:geo` + - `geo:db:migrate` -> `db:migrate:geo` + - `geo:db:rollback` -> `db:rollback:geo` + - `geo:db:version` -> `db:version:geo` + - `geo:db:reset` -> `db:reset:geo` + - `geo:db:seed` -> `db:seed:geo` + - `geo:schema:load:geo` -> `db:schema:load:geo` + - `geo:db:schema:dump` -> `db:schema:dump:geo` + - `geo:db:migrate:up` -> `db:migrate:up:geo` + - `geo:db:migrate:down` -> `db:migrate:down:geo` + - `geo:db:migrate:redo` -> `db:migrate:redo:geo` + - `geo:db:migrate:status` -> `db:migrate:status:geo` + - `geo:db:test:prepare` -> `db:test:prepare:geo` + - `geo:db:test:load` -> `db:test:load:geo` + - `geo:db:test:purge` -> `db:test:purge:geo` + stage: "Enablement" + tiers: ["Premium", "Ultimate"] + issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351945" + 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 diff --git a/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml new file mode 100644 index 00000000000..94a026edd81 --- /dev/null +++ b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml @@ -0,0 +1,15 @@ +- name: "Deprecate Geo Admin UI Routes" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: false + reporter: nhxnguyen + body: | + In GitLab 13.0, we introduced new project and design replication details routes in the Geo Admin UI. These routes are `/admin/geo/replication/projects` and `/admin/geo/replication/designs`. We kept the legacy routes and redirected them to the new routes. In GitLab 15.0, we will remove support for the legacy routes `/admin/geo/projects` and `/admin/geo/designs`. Please update any bookmarks or scripts that may use the legacy routes. + stage: "Enablement" + tiers: ["Premium", "Ultimate"] + issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351345" + 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 diff --git a/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml b/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml new file mode 100644 index 00000000000..861bed1e976 --- /dev/null +++ b/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml @@ -0,0 +1,20 @@ +- name: "Deprecate legacy Gitaly configuration methods" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: mjwood # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + Using environment variables `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configure Gitaly is [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/352609). + These variables are being replaced with standard [`config.toml` Gitaly configuration](https://docs.gitlab.com/ee/administration/gitaly/reference.html). + + GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configure Gitaly should switch to configuring using + `config.toml`. +# The following items are not published on the docs page, but may be used in the future. + stage: "Create" # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/352609" # (optional) This is a link to the deprecation issue in GitLab + documentation_url: "https://docs.gitlab.com/ee/administration/gitaly/reference.html" # (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 diff --git a/data/deprecations/14-8-gitaly-remove-per-repository-election.yml b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml new file mode 100644 index 00000000000..334da51c4a0 --- /dev/null +++ b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml @@ -0,0 +1,19 @@ +- name: "Configurable Gitaly `per_repository` election strategy" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "14.9" # The milestone when this feature is planned to be removed + removal_date: "2022-03-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: false # If this deprecation is a breaking change, set this value to true + reporter: mjwood # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + Configuring the `per_repository` Gitaly election strategy is [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/352612). + `per_repository` has been the only option since GitLab 14.0. + + This change is part of regular maintenance to keep our codebase clean. +# The following items are not published on the docs page, but may be used in the future. + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/352612" # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/14-8-graphql-ids.yml b/data/deprecations/14-8-graphql-ids.yml new file mode 100644 index 00000000000..dd73f310335 --- /dev/null +++ b/data/deprecations/14-8-graphql-ids.yml @@ -0,0 +1,66 @@ +- name: "GraphQL ID and GlobalID compatibility" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-04-22" + breaking_change: true + reporter: alexkalderimis + body: | # Do not modify this line, instead modify the lines below. + We are removing a non-standard extension to our GraphQL processor, which we added for backwards compatibility. This extension modifies the validation of GraphQL queries, allowing the use of the `ID` type for arguments where it would normally be rejected. + Some arguments originally had the type `ID`. These were changed to specific + kinds of `ID`. This change may be a breaking change if you: + + - Use GraphQL. + - Use the `ID` type for any argument in your query signatures. + + Some field arguments still have the `ID` type. These are typically for + IID values, or namespace paths. An example is `Query.project(fullPath: ID!)`. + + For a list of affected and unaffected field arguments, + see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352832). + + You can test if this change affects you by validating + your queries locally, using schema data fetched from a GitLab server. + You can do this by using the GraphQL explorer tool for the relevant GitLab + instance. For example: `https://gitlab.com/-/graphql-explorer`. + + For example, the following query illustrates the breaking change: + + ```graphql + # a query using the deprecated type of Query.issue(id:) + # WARNING: This will not work after GitLab 15.0 + query($id: ID!) { + deprecated: issue(id: $id) { + title, description + } + } + ``` + + The query above will not work after GitLab 15.0 is released, because the type + of `Query.issue(id:)` is actually `IssueID!`. + + Instead, you should use one of the following two forms: + + ```graphql + # This will continue to work + query($id: IssueID!) { + a: issue(id: $id) { + title, description + } + b: issue(id: "gid://gitlab/Issue/12345") { + title, description + } + } + ``` + + This query works now, and will continue to work after GitLab 15.0. + You should convert any queries in the first form (using `ID` as a named type in the signature) + to one of the other two forms (using the correct appropriate type in the signature, or using + an inline argument expression). +# The following items are not published on the docs page, but may be used in the future. + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/257883' + 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 diff --git a/data/deprecations/14-8-grpc-proxy.yml b/data/deprecations/14-8-grpc-proxy.yml new file mode 100644 index 00000000000..353c0abc901 --- /dev/null +++ b/data/deprecations/14-8-grpc-proxy.yml @@ -0,0 +1,26 @@ +- name: "Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab" + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: 2022-05-22 # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: jacobvosmaer-gitlab # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + Although not recommended or documented, it was possible to deploy a gRPC-aware proxy between Gitaly and + the rest of GitLab. For example, NGINX and Envoy. The ability to deploy a gRPC-aware proxy is + [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/352517). If you currently use a gRPC-aware proxy for + Gitaly connections, you should change your proxy configuration to use TCP or TLS proxying (OSI layer 4) instead. + + Gitaly Cluster became incompatible with gRPC-aware proxies in GitLab 13.12. Now all GitLab installations will be incompatible with + gRPC-aware proxies, even without Gitaly Cluster. + + By sending some of our internal RPC traffic through a custom protocol (instead of gRPC) we + increase throughput and reduce Go garbage collection latency. For more information, see + the [relevant epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463). +# The following items are not published on the docs page, but may be used in the future. + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/14-8-iteration-started-field.yml b/data/deprecations/14-8-iteration-started-field.yml new file mode 100644 index 00000000000..590c9800db6 --- /dev/null +++ b/data/deprecations/14-8-iteration-started-field.yml @@ -0,0 +1,15 @@ +- name: "`started` iterations API field" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + body: | # Do not modify this line, instead modify the lines below. + The `started` field in the [iterations API](https://docs.gitlab.com/ee/api/iterations.html#list-project-iterations) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `current` field (already available) which aligns with the naming for other time-based entities, such as milestones. +# The following items are not published on the docs page, but may be used in the future. + stage: plan + tiers: # (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] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/334018 + 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 diff --git a/data/deprecations/14-8-nfs_support.yml b/data/deprecations/14-8-nfs_support.yml new file mode 100644 index 00000000000..832b309e979 --- /dev/null +++ b/data/deprecations/14-8-nfs_support.yml @@ -0,0 +1,28 @@ +- name: "Reminder: support for NFS repository storage" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: mjwood # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + As [announced](https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/#nfs-for-git-repository-storage-deprecated) at the + release of GitLab 14.0, technical support for NFS storage for Git repositories is being removed. Please see our official + [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for additional information. + + We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on + [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/#migrating-to-gitaly-cluster). + + Gitaly Cluster offers tremendous benefits for our customers such as: + + - [Variable replication factors](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#configure-replication-factor) + - [Strong consistency](https://docs.gitlab.com/ee/administration/gitaly/#strong-consistency) + - [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/#distributed-reads) + +# The following items are not published on the docs page, but may be used in the future. + stage: Gitaly # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/14-8-protect-cns-chs.yml b/data/deprecations/14-8-protect-cns-chs.yml new file mode 100644 index 00000000000..b3a4cc8c1e8 --- /dev/null +++ b/data/deprecations/14-8-protect-cns-chs.yml @@ -0,0 +1,20 @@ +- name: "Container Network and Host Security" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: sam.white + body: | # Do not modify this line, instead modify the lines below. + All functionality related to GitLab's Container Network Security and Container Host Security categories is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies into GitLab, add the desired Helm charts into your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through the GitLab [Secure CI/CD Tunnel](https://docs.gitlab.com/ee/user/clusters/agent/repository.html#run-kubectl-commands-using-the-cicd-tunnel). + + As part of this change, the following specific capabilities within GitLab are now deprecated, and are scheduled for removal in GitLab 15.0: + + - The **Security & Compliance > Threat Monitoring** page. + - The `Network Policy` security policy type, as found on the **Security & Compliance > Policies** page. + - The ability to manage integrations with the following technologies through GitLab: AppArmor, Cilium, Falco, FluentD, and Pod Security Policies. + - All APIs related to the above functionality. + + For additional context, or to provide feedback regarding this change, please reference our open [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/7476). +# The following items are not published on the docs page, but may be used in the future. + stage: "Protect" diff --git a/data/deprecations/14-8-protect-vulnerability-check.yml b/data/deprecations/14-8-protect-vulnerability-check.yml new file mode 100644 index 00000000000..0f8fb44081a --- /dev/null +++ b/data/deprecations/14-8-protect-vulnerability-check.yml @@ -0,0 +1,18 @@ +- name: "Vulnerability Check" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: sam.white + body: | # Do not modify this line, instead modify the lines below. + The vulnerability check feature is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. We encourage you to migrate to the new security approvals feature instead. You can do so by navigating to **Security & Compliance > Policies** and creating a new Scan Result Policy. + + The new security approvals feature is similar to vulnerability check. For example, both can require approvals for MRs that contain security vulnerabilities. However, security approvals improve the previous experience in several ways: + + - Users can choose who is allowed to edit security approval rules. An independent security or compliance team can therefore manage rules in a way that prevents development project maintainers from modifying the rules. + - Multiple rules can be created and chained together to allow for filtering on different severity thresholds for each scanner type. + - A two-step approval process can be enforced for any desired changes to security approval rules. + - A single set of security policies can be applied to multiple development projects to allow for ease in maintaining a single, centralized ruleset. +# The following items are not published on the docs page, but may be used in the future. + stage: "Protect" diff --git a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml new file mode 100644 index 00000000000..b93b25c00d0 --- /dev/null +++ b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml @@ -0,0 +1,16 @@ +- name: "Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: sarahwaldner # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 15.0. Upon its removal, push rules will supersede CODEOWNERS. The CODEOWNERS feature will no longer be available for access control. +# The following items are not published on the docs page, but may be used in the future. + stage: create # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/262019 # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/14-8-request-profiling.yml b/data/deprecations/14-8-request-profiling.yml new file mode 100644 index 00000000000..8b549a6002f --- /dev/null +++ b/data/deprecations/14-8-request-profiling.yml @@ -0,0 +1,19 @@ +- name: "Request profiling" + announcement_milestone: "14.8" + announcement_date: "2021-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: iroussos + body: | # Do not modify this line, instead modify the lines below. + [Request profiling](https://docs.gitlab.com/ee/administration/monitoring/performance/request_profiling.html) is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. + + We're working on [consolidating our profiling tools](https://gitlab.com/groups/gitlab-org/-/epics/7327) and making them more easily accessible. + We [evaluated](https://gitlab.com/gitlab-org/gitlab/-/issues/350152) the use of this feature and we found that it is not widely used. + It also depends on a few third-party gems that are not actively maintained anymore, have not been updated for the latest version of Ruby, or crash frequently when profiling heavy page loads. + + For more information, check the [summary section of the deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352488#deprecation-summary). + stage: Monitor + tiers: [Free, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352488 + documentation_url: https://docs.gitlab.com/ee/administration/monitoring/performance/request_profiling.html diff --git a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml new file mode 100644 index 00000000000..63178061aae --- /dev/null +++ b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml @@ -0,0 +1,33 @@ +- name: "REST and GraphQL API Runner usage of `active` replaced by `paused`" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "16.0" + removal_date: "2023-04-22" + breaking_change: true + reporter: pedropombeiro + body: | + Occurrences of the `active` identifier in the GitLab Runner REST and GraphQL API endpoints will be + renamed to `paused` in GitLab 16.0, namely: + + - GraphQL API: + - the `CiRunner` property; + - the `RunnerUpdateInput` input type for the `runnerUpdate` mutation; + - the `runners` and `Group.runners` queries. + - REST API: + - endpoints taking or returning `active` properties, such as: + - `GET /runners` + - `GET /runners/all` + - `GET /runners/:id` / `PUT /runners/:id` + - `PUT --form "active=false" /runners/:runner_id` + - `GET /projects/:id/runners` / `POST /projects/:id/runners` + - `GET /groups/:id/runners` + + The 16.0 release of the GitLab Runner will start using the `paused` property when registering runners, and therefore + will only be compatible with GitLab 16.0 and later. Until 16.0, GitLab will accept the deprecated `active` flag from + existing runners. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347211 + documentation_url: https://docs.gitlab.com/ee/api/runners.html + 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 diff --git a/data/deprecations/14-8-runner-api-project_type-breaking-change.yml b/data/deprecations/14-8-runner-api-project_type-breaking-change.yml new file mode 100644 index 00000000000..67cd854aa89 --- /dev/null +++ b/data/deprecations/14-8-runner-api-project_type-breaking-change.yml @@ -0,0 +1,15 @@ +- name: "REST API endpoint to list group runners no longer accepts `project_type` value for `type` argument" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "16.0" + removal_date: "2023-04-22" + breaking_change: true + reporter: pedropombeiro + body: | + The `GET /groups/:id/runners?type=project_type` endpoint will be removed in GitLab 16.0. The endpoint always returned an empty collection. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351466 + documentation_url: https://docs.gitlab.com/ee/api/runners.html + 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 diff --git a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml new file mode 100644 index 00000000000..51472b3cd28 --- /dev/null +++ b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml @@ -0,0 +1,18 @@ +- name: "REST API Runner will not accept `status` filter values of `active` or `paused`" + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" + removal_milestone: "16.0" + removal_date: "2023-04-22" + breaking_change: true + body: | # Do not modify this line, instead modify the lines below. + The GitLab Runner REST endpoints will stop accepting `paused` or `active` as a status value in GitLab 16.0. + + A runner's status will only relate to runner contact status, such as: `online`, `offline`. + Status values `paused` or `active` will no longer be accepted and will be replaced by the `paused` query parameter. + + When checking for paused runners, API users are advised to specify `paused=true` as the query parameter. + When checking for active runners, specify `paused=false`. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351109 + documentation_url: https://docs.gitlab.com/ee/api/runners.html diff --git a/data/deprecations/14-8-sast-analyzer-removals.yml b/data/deprecations/14-8-sast-analyzer-removals.yml new file mode 100644 index 00000000000..6bbeee0cd6b --- /dev/null +++ b/data/deprecations/14-8-sast-analyzer-removals.yml @@ -0,0 +1,32 @@ +- name: "SAST analyzer consolidation and CI/CD template changes" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: connorgilbert + body: | # Do not modify this line, instead modify the lines below. + GitLab SAST uses various [analyzers](https://docs.gitlab.com/ee/user/application_security/sast/analyzers/) to scan code for vulnerabilities. + + We are reducing the number of analyzers used in GitLab SAST as part of our long-term strategy to deliver a better and more consistent user experience. + Streamlining the set of analyzers will also enable faster [iteration](https://about.gitlab.com/handbook/values/#iteration), better [results](https://about.gitlab.com/handbook/values/#results), and greater [efficiency](https://about.gitlab.com/handbook/values/#results) (including a reduction in CI runner usage in most cases). + + In GitLab 15.0, GitLab SAST will no longer use the following analyzers: + + - [ESLint](https://gitlab.com/gitlab-org/security-products/analyzers/eslint) (JavaScript, TypeScript, React) + - [Gosec](https://gitlab.com/gitlab-org/security-products/analyzers/gosec) (Go) + - [Bandit](https://gitlab.com/gitlab-org/security-products/analyzers/bandit) (Python) + + These analyzers will be removed from the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml) and replaced with the [Semgrep-based analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/semgrep). + They will no longer receive routine updates, except for security issues. + We will not delete container images previously published for these analyzers; any such change would be announced as a [deprecation, removal, or breaking change announcement](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes). + + We will also remove Java from the scope of the [SpotBugs](https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs) analyzer and replace it with the [Semgrep-based analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/semgrep). + This change will make it simpler to scan Java code; compilation will no longer be required. + This change will be reflected in the automatic language detection portion of the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml). + + If you applied customizations to any of the affected analyzers, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352554#breaking-change). +# The following items are not published on the docs page, but may be used in the future. + stage: Secure + tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352554 diff --git a/data/deprecations/14-8-sast-dotnet-21.yml b/data/deprecations/14-8-sast-dotnet-21.yml new file mode 100644 index 00000000000..ab1b3c16b23 --- /dev/null +++ b/data/deprecations/14-8-sast-dotnet-21.yml @@ -0,0 +1,31 @@ +- name: "SAST support for .NET 2.1" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: connorgilbert + body: | # Do not modify this line, instead modify the lines below. + The GitLab SAST Security Code Scan analyzer scans .NET code for security vulnerabilities. + For technical reasons, the analyzer must first build the code to scan it. + + In GitLab versions prior to 15.0, the default analyzer image (version 2) includes support for: + + - .NET 2.1 + - .NET 3.0 and .NET Core 3.0 + - .NET Core 3.1 + - .NET 5.0 + + In GitLab 15.0, we will change the default major version for this analyzer from version 2 to version 3. This change: + + - Adds [severity values for vulnerabilities](https://gitlab.com/gitlab-org/gitlab/-/issues/350408) along with [other new features and improvements](https://gitlab.com/gitlab-org/security-products/analyzers/security-code-scan/-/blob/master/CHANGELOG.md). + - Removes .NET 2.1 support. + - Adds support for .NET 6.0, Visual Studio 2019, and Visual Studio 2022. + + Version 3 was [announced in GitLab 14.6](https://about.gitlab.com/releases/2021/12/22/gitlab-14-6-released/#sast-support-for-net-6) and made available as an optional upgrade. + + If you rely on .NET 2.1 support being present in the analyzer image by default, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352553#breaking-change). +# The following items are not published on the docs page, but may be used in the future. + stage: Secure + tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352553 diff --git a/data/deprecations/14-8-sast-secret-analyzer-image.yml b/data/deprecations/14-8-sast-secret-analyzer-image.yml new file mode 100644 index 00000000000..b1cb5c82764 --- /dev/null +++ b/data/deprecations/14-8-sast-secret-analyzer-image.yml @@ -0,0 +1,27 @@ +- name: "Secure and Protect analyzer images published in new location" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: connorgilbert + body: | # Do not modify this line, instead modify the lines below. + GitLab uses various [analyzers](https://docs.gitlab.com/ee/user/application_security/terminology/#analyzer) to [scan for security vulnerabilities](https://docs.gitlab.com/ee/user/application_security/). + Each analyzer is distributed as a container image. + + Starting in GitLab 14.8, new versions of GitLab Secure and Protect analyzers are published to a new registry location under `registry.gitlab.com/security-products`. + + We will update the default value of [GitLab-managed CI/CD templates](https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/gitlab/ci/templates/Security) to reflect this change: + + - For all analyzers except Container Scanning, we will update the variable `SECURE_ANALYZERS_PREFIX` to the new image registry location. + - For Container Scanning, the default image address is already updated. There is no `SECURE_ANALYZERS_PREFIX` variable for Container Scanning. + + In a future release, we will stop publishing images to `registry.gitlab.com/gitlab-org/security-products/analyzers`. + Once this happens, you must take action if you manually pull images and push them into a separate registry. This is commonly the case for [offline deployments](https://docs.gitlab.com/ee/user/application_security/offline_deployments/index.html). + Otherwise, you won't receive further updates. + + See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564) for more details. +# The following items are not published on the docs page, but may be used in the future. + stage: Secure + tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352564 diff --git a/data/deprecations/14-8-sast-spotbugs-java-8.yml b/data/deprecations/14-8-sast-spotbugs-java-8.yml new file mode 100644 index 00000000000..3e3672eeb63 --- /dev/null +++ b/data/deprecations/14-8-sast-spotbugs-java-8.yml @@ -0,0 +1,24 @@ +- name: "Out-of-the-box SAST support for Java 8" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + reporter: connorgilbert + body: | # Do not modify this line, instead modify the lines below. + The [GitLab SAST SpotBugs analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs) scans [Java, Scala, Groovy, and Kotlin code](https://docs.gitlab.com/ee/user/application_security/sast/#supported-languages-and-frameworks) for security vulnerabilities. + For technical reasons, the analyzer must first compile the code before scanning. + Unless you use the [pre-compilation strategy](https://docs.gitlab.com/ee/user/application_security/sast/#pre-compilation), the analyzer attempts to automatically compile your project's code. + + In GitLab versions prior to 15.0, the analyzer image includes Java 8 and Java 11 runtimes to facilitate compilation. + + In GitLab 15.0, we will: + + - Remove Java 8 from the analyzer image to reduce the size of the image. + - Add Java 17 to the analyzer image to make it easier to compile with Java 17. + + If you rely on Java 8 being present in the analyzer environment, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352549#breaking-change). +# The following items are not published on the docs page, but may be used in the future. + stage: Secure + tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352549 diff --git a/data/deprecations/14-8-secret-detection-configurations.yml b/data/deprecations/14-8-secret-detection-configurations.yml new file mode 100644 index 00000000000..f9103c1cea3 --- /dev/null +++ b/data/deprecations/14-8-secret-detection-configurations.yml @@ -0,0 +1,28 @@ +- name: "Secret Detection configuration variables deprecated" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: false + reporter: connorgilbert + body: | # Do not modify this line, instead modify the lines below. + To make it simpler and more reliable to [customize GitLab Secret Detection](https://docs.gitlab.com/ee/user/application_security/secret_detection/#customizing-settings), we're deprecating some of the variables that you could previously set in your CI/CD configuration. + + The following variables currently allow you to customize the options for historical scanning, but interact poorly with the [GitLab-managed CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Secret-Detection.gitlab-ci.yml) and are now deprecated: + + - `SECRET_DETECTION_COMMIT_FROM` + - `SECRET_DETECTION_COMMIT_TO` + - `SECRET_DETECTION_COMMITS` + - `SECRET_DETECTION_COMMITS_FILE` + + The `SECRET_DETECTION_ENTROPY_LEVEL` previously allowed you to configure rules that only considered the entropy level of strings in your codebase, and is now deprecated. + This type of entropy-only rule created an unacceptable number of incorrect results (false positives) and is no longer supported. + + In GitLab 15.0, we'll update the Secret Detection [analyzer](https://docs.gitlab.com/ee/user/application_security/terminology/#analyzer) to ignore these deprecated options. + You'll still be able to configure historical scanning of your commit history by setting the [`SECRET_DETECTION_HISTORIC_SCAN` CI/CD variable](https://docs.gitlab.com/ee/user/application_security/secret_detection/#available-cicd-variables). + + For further details, see [the deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352565). +# The following items are not published on the docs page, but may be used in the future. + stage: Secure + tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352565 diff --git a/data/deprecations/14-8-secure-ca-python-deprecation.yml b/data/deprecations/14-8-secure-ca-python-deprecation.yml new file mode 100644 index 00000000000..c4b5c2e36b7 --- /dev/null +++ b/data/deprecations/14-8-secure-ca-python-deprecation.yml @@ -0,0 +1,33 @@ +- name: "Dependency Scanning Python 3.9 and 3.6 image deprecation" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2021-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: 2021-05-22 # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + body: | # Do not modify this line, instead modify the lines below. + For those using Dependency Scanning for Python projects, we are deprecating the default `gemnasium-python:2` image which uses Python 3.6 as well as the custom `gemnasium-python:2-python-3.9` image which uses Python 3.9. The new default image as of GitLab 15.0 will be for Python 3.9 as it is a [supported version](https://endoflife.date/python) and 3.6 [is no longer supported](https://endoflife.date/python). + + For users using Python 3.9 or 3.9-compatible projects, you should not need to take action and dependency scanning should begin to work in GitLab 15.0. If you wish to test the new container now please run a test pipeline in your project with this container (which will be removed in 15.0). Use the Python 3.9 image: + + ```yaml + gemnasium-python-dependency_scanning: + image: + name: registry.gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python:2-python-3.9 + ``` + + For users using Python 3.6, as of GitLab 15.0 you will no longer be able to use the default template for dependency scanning. You will need to switch to use the deprecated `gemnasium-python:2` analyzer image. If you are impacted by this please comment in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351503) so we can extend the removal if needed. + + For users using the 3.9 special exception image, you must instead use the default value and no longer override your container. To verify if you are using the 3.9 special exception image, check your `.gitlab-ci.yml` file for the following reference: + + ```yaml + gemnasium-python-dependency_scanning: + image: + name: registry.gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python:2-python-3.9 + ``` +# The following items are not published on the docs page, but may be used in the future. + stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + 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] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/334060 # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/14-9-deprecate-testcoveragesetting.yml b/data/deprecations/14-9-deprecate-testcoveragesetting.yml new file mode 100644 index 00000000000..19bc6004b02 --- /dev/null +++ b/data/deprecations/14-9-deprecate-testcoveragesetting.yml @@ -0,0 +1,14 @@ +- name: "Test coverage project CI/CD setting" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: jreporter # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + To simplify setting a test coverage pattern, in GitLab 15.0 the + [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-deprecated) + is being removed. + + Instead, using the project’s `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set + testing coverage results in merge requests. diff --git a/data/deprecations/15-0-deprecate-monitor-tracing.yml b/data/deprecations/15-0-deprecate-monitor-tracing.yml index 126ada081f4..448404a5c70 100644 --- a/data/deprecations/15-0-deprecate-monitor-tracing.yml +++ b/data/deprecations/15-0-deprecate-monitor-tracing.yml @@ -13,4 +13,3 @@ documentation_url: https://docs.gitlab.com/ee/operations/tracing.html#tracing # (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 - diff --git a/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml new file mode 100644 index 00000000000..c617a6cc478 --- /dev/null +++ b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml @@ -0,0 +1,13 @@ +- name: "Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.0" + removal_date: "2022-05-22" + breaking_change: true + body: | # Do not modify this line, instead modify the lines below. + The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTrendsMeasurements` in 13.10 and the old field name has been marked as deprecated. To fix the existing GraphQL queries, replace `instanceStatisticsMeasurements` with `usageTrendsMeasurements`. +# The following items are not published on the docs page, but may be used in the future. + stage: Manage + tiers: [FREE] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/332323 + documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#queryusagetrendsmeasurements diff --git a/data/deprecations/15-0-oauth-noexpiry.yml b/data/deprecations/15-0-oauth-noexpiry.yml new file mode 100644 index 00000000000..2e1e4a35f7b --- /dev/null +++ b/data/deprecations/15-0-oauth-noexpiry.yml @@ -0,0 +1,24 @@ +- name: "OAuth tokens without expiration" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: 2022-05-22 # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + body: | # Do not modify this line, instead modify the lines below. + By default, all new applications expire access tokens after 2 hours. In GitLab 14.2 and earlier, OAuth access tokens + had no expiration. In GitLab 15.0, an expiry will be automatically generated for any existing token that does not + already have one. + + You should [opt in](https://docs.gitlab.com/ee/integration/oauth_provider.html#expiring-access-tokens) to expiring + tokens before GitLab 15.0 is released: + + 1. Edit the application. + 1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don’t expire. + +# The following items are not published on the docs page, but may be used in the future. + stage: # Manage + tiers: # (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] + issue_url: # https://gitlab.com/gitlab-org/gitlab/-/issues/21745 + 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 diff --git a/data/deprecations/15-0-oauth.yml b/data/deprecations/15-0-oauth.yml new file mode 100644 index 00000000000..5ca30d9f330 --- /dev/null +++ b/data/deprecations/15-0-oauth.yml @@ -0,0 +1,15 @@ +- name: "OAuth implicit grant" # The name of the feature to be deprecated + announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. + announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: 2022-05-22 # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: yes # If this deprecation is a breaking change, set this value to true + body: | # Do not modify this line, instead modify the lines below. + The OAuth implicit grant authorization flow will be removed in our next major release, GitLab 15.0. Any applications that use OAuth implicit grant should switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html). +# The following items are not published on the docs page, but may be used in the future. + stage: # Manage + tiers: # (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] + issue_url: # https://gitlab.com/gitlab-org/gitlab/-/issues/344609 + 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 diff --git a/data/deprecations/JTW_v2_update.yml b/data/deprecations/JTW_v2_update.yml new file mode 100644 index 00000000000..53aa9ca2c19 --- /dev/null +++ b/data/deprecations/JTW_v2_update.yml @@ -0,0 +1,28 @@ +# This is a template for a feature deprecation +# A deprecation typically occurs when a feature or capability is planned to be removed in a future release. +# Deprecations should be announced at least two releases prior to removal. Any breaking changes should only be done in major releases. +# +# Below is an example of what a single entry should look like, it's required attributes, +# and what types we expect those attribute values to be. +# +# For more information please refer to the handbook documentation here: +# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations +# +# Please delete this line and above before submitting your merge request. + +- name: "Changes to the `CI_JOB_JWT`" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.0" # The milestone when this feature is planned to be removed + removal_date: # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: dhershkovitch # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + The `CI_JOB_JWT` will be updated to support a wider variety of cloud providers. It will be changed to match [`CI_JOB_JWT_V2`](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html), but this change may not be backwards compatible for all users, including Hashicorp Vault users. To maintain the current behavior, users can switch to using `CI_JOB_JWT_V1`, or update their configuration in GitLab 15.0 to use the improved `CI_JOB_JWT`. +# The following items are not published on the docs page, but may be used in the future. + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/deprecations/data/deprecations/14-9-secure-and-protect-analyzer-bump.yml.yml b/data/deprecations/data/deprecations/14-9-secure-and-protect-analyzer-bump.yml.yml new file mode 100644 index 00000000000..8f1d030f47c --- /dev/null +++ b/data/deprecations/data/deprecations/14-9-secure-and-protect-analyzer-bump.yml.yml @@ -0,0 +1,44 @@ +- name: "Secure and Protect analyzer major version update" # The name of the feature to be deprecated + announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. + announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "15.00" # The milestone when this feature is planned to be removed + removal_date: # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # If this deprecation is a breaking change, set this value to true + reporter: NicoleSchwartz # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. + The Secure and Protect stages will be bumping the major versions of their analyzers in tandem with the GitLab 15.0 release. This major bump will enable a clear delineation for analyzers, between: + + - Those released prior to May 22, 2022, which generate reports that _are not_ subject to stringent schema validation. + - Those released after May 22, 2022, which generate reports that _are_ subject to stringent schema validation. + + If you are not using the default inclusion templates, or have pinned your analyzer version(s) you will need to update your CI/CD job definition to either remove the pinned version or to update the latest major version. + Users of GitLab 12.0-14.10 will continue to experience analyzer updates as normal until the release of GitLab 15.0, following which all newly fixed bugs and newly released features in the new major versions of the analyzers will not be available in the deprecated versions because we do not backport bugs and new features as per our [maintenance policy](https://docs.gitlab.com/ee/policy/maintenance.html). As required security patches will be backported within the latest 3 minor releases. + Specifically, the following are being deprecated and will no longer be updated after 15.0 GitLab release: + + - API Security: version 1 + - Container Scanning: version 4 + - Coverage-guided fuzz testing: version 2 + - Dependency Scanning: version 2 + - Dynamic Application Security Testing (DAST): version 2 + - License Scanning: version 3 + - Secret Detection: version 3 + - Static Application Security Testing (SAST): version 2, except security-code-scan which is version 3 + - `bandit`: version 2 + - `brakeman`: version 2 + - `eslint`: version 2 + - `flawfinder`: version 2 + - `gosec`: version 3 + - `kubesec`: version 2 + - `mobsf`: version 2 + - `nodejs-scan`: version 2 + - `phpcs-security-audit`: version 2 + - `pmd-apex`: version 2 + - `security-code-scan`: version 3 + - `semgrep`: version 2 + - `sobelow`: version 2 + - `spotbugs`: version 2 +# The following items are not published on the docs page, but may be used in the future. + stage: secure, protect # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: Free, Silver, Gold, Core, Premium, 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] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350936 # (optional) This is a link to the deprecation issue in GitLab + documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index 70169ef5c5c..1ef2af67a98 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -49,8 +49,10 @@ Before updating GitLab, review the details carefully to determine if you need to changes to your code, settings, or workflow. <%= deprecation["body"] -%><% else %> -<%= deprecation["body"] -%><% end %> +<%= deprecation["body"] -%><% end %><%- if deprecation["removal_milestone"] -%> + **Planned removal milestone: <%= deprecation["removal_milestone"]%> (<%= deprecation["removal_date"]%>)** + <%- end -%> <%- end -%> <%- end -%> <%- else -%> diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml index 3097db557b8..06e53084ed2 100644 --- a/data/deprecations/templates/example.yml +++ b/data/deprecations/templates/example.yml @@ -10,13 +10,14 @@ # # Please delete this line and above before submitting your merge request. -- name: "Feature name" # The name of the feature to be deprecated - announcement_milestone: "XX.YY" # The milestone when this feature was first announced as deprecated. - announcement_date: "YYYY-MM-DD" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. - removal_milestone: "XX.YY" # The milestone when this feature is planned to be removed - removal_date: # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. - breaking_change: false # If this deprecation is a breaking change, set this value to true - body: | # Do not modify this line, instead modify the lines below. +- name: "Feature name" # The name of the feature to be deprecated + announcement_milestone: "XX.YY" # The milestone when this feature was first announced as deprecated. + announcement_date: "YYYY-MM-DD" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "XX.YY" # The milestone when this feature is planned to be removed + removal_date: # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: false # If this deprecation is a breaking change, set this value to true + reporter: exampleuser # GitLab username of the person reporting the deprecation + body: | # Do not modify this line, instead modify the lines below. <!-- START OF BODY COMMENT This area supports markdown. Delete this entire comment and replace it with your markdown content. @@ -25,9 +26,9 @@ END OF BODY COMMENT --> # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth - tiers: # (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] - issue_url: # (optional) This is a link to the deprecation issue in GitLab - 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 + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/removals/14_0/14_0-ds-deprecations.yml b/data/removals/14_0/14_0-ds-deprecations.yml index c9eefe65c91..91da10097ed 100644 --- a/data/removals/14_0/14_0-ds-deprecations.yml +++ b/data/removals/14_0/14_0-ds-deprecations.yml @@ -1,7 +1,8 @@ -- name: "Deprecations for Dependency Scanning" +- name: "Dependency Scanning" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: nicoleschwartz + breaking_change: true body: | As mentioned in [13.9](https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#deprecations-for-dependency-scanning) and [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/) several removals for Dependency Scanning take effect. diff --git a/data/removals/14_0/14_0-lc-deprecations.yml b/data/removals/14_0/14_0-lc-deprecations.yml index 8f59fdbb557..6322b102ec5 100644 --- a/data/removals/14_0/14_0-lc-deprecations.yml +++ b/data/removals/14_0/14_0-lc-deprecations.yml @@ -1,6 +1,7 @@ -- name: "Removals for License Compliance" +- name: "License Compliance" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: nicoleschwartz + breaking_change: true body: | In 13.0, we deprecated the License-Management CI template and renamed it License-Scanning. We have been providing backward compatibility by warning users of the old template to switch. Now in 14.0, we are completely removing the License-Management CI template. Read about it in [issue #216261](https://gitlab.com/gitlab-org/gitlab/-/issues/216261) or [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/). diff --git a/data/removals/14_0/change_default_branch_name_to_main.yml b/data/removals/14_0/change_default_branch_name_to_main.yml index d2c0128daa5..1c47f99870b 100644 --- a/data/removals/14_0/change_default_branch_name_to_main.yml +++ b/data/removals/14_0/change_default_branch_name_to_main.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: sarahwaldner + breaking_change: true body: | Every Git repository has an initial branch, which is named `master` by default. It's the first branch to be created automatically when you create a new repository. Future [Git versions](https://lore.kernel.org/git/pull.656.v4.git.1593009996.gitgitgadget@gmail.com/) will change the default branch name in Git from `master` to `main`. In coordination with the Git project and the broader community, [GitLab has changed the default branch name](https://gitlab.com/gitlab-org/gitlab/-/issues/223789) for new projects on both our SaaS (GitLab.com) and self-managed offerings starting with GitLab 14.0. This will not affect existing projects. diff --git a/data/removals/14_0/create-code-review-draft-wip.yml b/data/removals/14_0/create-code-review-draft-wip.yml index addd6c400a6..20eaaf3cd02 100644 --- a/data/removals/14_0/create-code-review-draft-wip.yml +++ b/data/removals/14_0/create-code-review-draft-wip.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: phikai + breaking_change: true body: | The WIP (work in progress) status for merge requests signaled to reviewers that the merge request in question wasn't ready to merge. We've renamed the WIP feature to **Draft**, a more inclusive and self-explanatory term. **Draft** clearly communicates the merge request in question isn't ready for review, and makes no assumptions about the progress being made toward it. **Draft** also reduces the cognitive load for new users, non-English speakers, and anyone unfamiliar with the WIP acronym. diff --git a/data/removals/14_0/create-code-review-w-parameter-removal.yml b/data/removals/14_0/create-code-review-w-parameter-removal.yml index 471df85b540..3adec30a1e7 100644 --- a/data/removals/14_0/create-code-review-w-parameter-removal.yml +++ b/data/removals/14_0/create-code-review-w-parameter-removal.yml @@ -1,6 +1,7 @@ -- name: "Remove `?w=1` URL parameter to ignore whitespace changes" +- name: "`?w=1` URL parameter to ignore whitespace changes" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: phikai + breaking_change: true body: | To create a consistent experience for users based on their preferences, support for toggling whitespace changes via URL parameter has been removed in GitLab 14.0. diff --git a/data/removals/14_0/deprecate_ci_project_config_path_variable.yml b/data/removals/14_0/deprecate_ci_project_config_path_variable.yml deleted file mode 100644 index c262a641bd1..00000000000 --- a/data/removals/14_0/deprecate_ci_project_config_path_variable.yml +++ /dev/null @@ -1,6 +0,0 @@ -- name: "`CI_PROJECT_CONFIG_PATH` removed in GitLab 14.0" - removal_date: "2021-06-22" - removal_milestone: "14.0" - reporter: stkerr - body: | - GitLab 14.0 removes the `CI_PROJECT_CONFIG_PATH` pre-defined project variable in favor of `CI_CONFIG_PATH`, which is functionally the same. If you are using `CI_PROJECT_CONFIG_PATH` in your pipeline configurations, update them to use `CI_CONFIG_PATH` instead. diff --git a/data/removals/14_0/deprecation_bump_terraform_template_version.yml b/data/removals/14_0/deprecation_bump_terraform_template_version.yml index a2e4bad9913..253dd81e9ea 100644 --- a/data/removals/14_0/deprecation_bump_terraform_template_version.yml +++ b/data/removals/14_0/deprecation_bump_terraform_template_version.yml @@ -1,8 +1,9 @@ -- name: "New Terraform template version" +- name: "Terraform template version" removal_date: "2021-06-22" removal_milestone: "14.0" # example issue_url: "" reporter: nagyv-gitlab + breaking_change: true body: | As we continuously [develop GitLab's Terraform integrations](https://gitlab.com/gitlab-org/gitlab/-/issues/325312), to minimize customer disruption, we maintain two GitLab CI/CD templates for Terraform: diff --git a/data/removals/14_0/deprecation_manage_access_14_0.yml b/data/removals/14_0/deprecation_manage_access_14_0.yml index bc82067821f..30167d23d60 100644 --- a/data/removals/14_0/deprecation_manage_access_14_0.yml +++ b/data/removals/14_0/deprecation_manage_access_14_0.yml @@ -3,15 +3,17 @@ removal_milestone: "14.0" reporter: ogolowisnki issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/257829 + breaking_change: true body: | To improve performance, we are limiting the number of projects returned from the `GET /groups/:id/` API call to 100. A complete list of projects can still be retrieved with the `GET /groups/:id/projects` API call. -- name: "GitLab OAuth implicit grant deprecation" +- name: "GitLab OAuth implicit grant" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: ogolowinski issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/288516' + breaking_change: true body: | GitLab is deprecating the [OAuth 2 implicit grant flow](https://docs.gitlab.com/ee/api/oauth2.html#implicit-grant-flow) as it has been removed for [OAuth 2.1](https://oauth.net/2.1/). - Beginning in 14.0, new applications can't be created with the OAuth 2 implicit grant flow. Existing OAuth implicit grant flows are no longer supported in 14.4. Migrate your existing applications to other supported [OAuth2 flows](https://docs.gitlab.com/ee/api/oauth2.html#supported-oauth2-flows) before release 14.4. + Migrate your existing applications to other supported [OAuth2 flows](https://docs.gitlab.com/ee/api/oauth2.html#supported-oauth2-flows). diff --git a/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml b/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml index 97adc4bb050..4df59321bc5 100644 --- a/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml +++ b/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml @@ -1,6 +1,7 @@ -- name: "Update CI/CD templates to stop using hardcoded `master`" +- name: "Hardcoded `master` in CI/CD templates" reporter: dhershkovitch removal_date: "2021-06-22" removal_milestone: "14.0" + breaking_change: true body: | Our CI/CD templates have been updated to no longer use hard-coded references to a `master` branch. In 14.0, they all use a variable that points to your project's configured default branch instead. If your CI/CD pipeline relies on our built-in templates, verify that this change works with your current configuration. For example, if you have a `master` branch and a different default branch, the updates to the templates may cause changes to your pipeline behavior. For more information, [read the issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324131). diff --git a/data/removals/14_0/deuley_servicetemplates_removal.yml b/data/removals/14_0/deuley_servicetemplates_removal.yml index 94816bbee4a..bbc70d98562 100644 --- a/data/removals/14_0/deuley_servicetemplates_removal.yml +++ b/data/removals/14_0/deuley_servicetemplates_removal.yml @@ -1,7 +1,8 @@ -- name: "Service Templates removed" +- name: "Service Templates" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deuley + breaking_change: true body: | Service Templates are [removed in GitLab 14.0](https://gitlab.com/groups/gitlab-org/-/epics/5672). They were used to apply identical settings to a large number of projects, but they only did so at the time of project creation. diff --git a/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml b/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml index 066022dae87..d7e12a89f14 100644 --- a/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml +++ b/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml @@ -1,7 +1,8 @@ -- name: "Removal of release description in the Tags API" +- name: "Release description in the Tags API" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/300887' + breaking_change: true body: | GitLab 14.0 removes support for the release description in the Tags API. You can no longer add a release description when [creating a new tag](https://docs.gitlab.com/ee/api/tags.html#create-a-new-tag). You also can no longer [create](https://docs.gitlab.com/ee/api/tags.html#create-a-new-release) or [update](https://docs.gitlab.com/ee/api/tags.html#update-a-release) a release through the Tags API. Please migrate to use the [Releases API](https://docs.gitlab.com/ee/api/releases/#create-a-release) instead. diff --git a/data/removals/14_0/release_deprecation_auto-deploy-image.yml b/data/removals/14_0/release_deprecation_auto-deploy-image.yml index 7a8f0e598c4..d6cd9ac23ca 100644 --- a/data/removals/14_0/release_deprecation_auto-deploy-image.yml +++ b/data/removals/14_0/release_deprecation_auto-deploy-image.yml @@ -1,9 +1,10 @@ -- name: "Update Auto Deploy template version" +- name: "Auto Deploy CI template v1" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/300862' + breaking_change: true body: | - In GitLab 14.0, we will update the [Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-deploy) CI template to the latest version. This includes new features, bug fixes, and performance improvements with a dependency on the v2 [auto-deploy-image](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image). Auto Deploy CI tempalte v1 will is deprecated going forward. + In GitLab 14.0, we will update the [Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-deploy) CI template to the latest version. This includes new features, bug fixes, and performance improvements with a dependency on the v2 [auto-deploy-image](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image). Auto Deploy CI template v1 is deprecated going forward. Since the v1 and v2 versions are not backward-compatible, your project might encounter an unexpected failure if you already have a deployed application. Follow the [upgrade guide](https://docs.gitlab.com/ee/topics/autodevops/upgrading_auto_deploy_dependencies.html#upgrade-guide) to upgrade your environments. You can also start using the latest template today by following the [early adoption guide](https://docs.gitlab.com/ee/topics/autodevops/upgrading_auto_deploy_dependencies.html#early-adopters). diff --git a/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml b/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml index 694c168fb93..bb10ab8a2ab 100644 --- a/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml +++ b/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml @@ -1,7 +1,8 @@ -- name: "Remove disk source configuration for GitLab Pages" +- name: "Disk source configuration for GitLab Pages" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5993' + breaking_change: true body: | GitLab Pages [API-based configuration](https://docs.gitlab.com/ee/administration/pages/#gitlab-api-based-configuration) has been available since GitLab 13.0. It replaces the unsupported `disk` source configuration removed in GitLab 14.0, which can no longer be chosen. You should stop using `disk` source configuration, and move to `gitlab` for an API-based configuration. To migrate away from the 'disk' source configuration, set `gitlab_pages['domain_config_source'] = "gitlab"` in your `/etc/gitlab/gitlab.rb` file. We recommend you migrate before updating to GitLab 14.0, to identify and troubleshoot any potential problems before upgrading. diff --git a/data/removals/14_0/release_legacy_feature_flags_deprecation.yml b/data/removals/14_0/release_legacy_feature_flags_deprecation.yml index aa62be7eb1d..bf0075faa1e 100644 --- a/data/removals/14_0/release_legacy_feature_flags_deprecation.yml +++ b/data/removals/14_0/release_legacy_feature_flags_deprecation.yml @@ -1,7 +1,8 @@ -- name: "Legacy feature flags removed" +- name: "Legacy feature flags" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/254324' + breaking_change: true body: | Legacy feature flags became read-only in GitLab 13.4. GitLab 14.0 removes support for legacy feature flags, so you must migrate them to the [new version](https://docs.gitlab.com/ee/operations/feature_flags.html). You can do this by first taking a note (screenshot) of the legacy flag, then deleting the flag through the API or UI (you don't need to alter the code), and finally create a new Feature Flag with the same name as the legacy flag you deleted. Also, make sure the strategies and environments match the deleted flag. We created a [video tutorial](https://www.youtube.com/watch?v=CAJY2IGep7Y) to help with this migration. diff --git a/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml b/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml index 48e79230297..47c58bcb143 100644 --- a/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml +++ b/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml @@ -1,7 +1,8 @@ -- name: "Remove redundant timestamp field from DORA metrics API payload" +- name: "Redundant timestamp field from DORA metrics API payload" reporter: kbychu removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/325931' + breaking_change: true body: | The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora4_project_analytics.html#list-project-deployment-frequencies) endpoint has been deprecated in favor of the [DORA 4 API](https://docs.gitlab.com/ee/api/dora/metrics.html), which consolidates all the metrics under one API with the specific metric as a required field. As a result, the timestamp field, which doesn't allow adding future extensions and causes performance issues, will be removed. With the old API, an example response would be `{ "2021-03-01": 3, "date": "2021-03-01", "value": 3 }`. The first key/value (`"2021-03-01": 3`) will be removed and replaced by the last two (`"date": "2021-03-01", "value": 3`). diff --git a/data/removals/14_0/removal-geo-fdw-settings.yml b/data/removals/14_0/removal-geo-fdw-settings.yml index c2066269cb8..5997705bf30 100644 --- a/data/removals/14_0/removal-geo-fdw-settings.yml +++ b/data/removals/14_0/removal-geo-fdw-settings.yml @@ -1,7 +1,8 @@ -- name: "Geo Foreign Data Wrapper settings removed" +- name: "Geo Foreign Data Wrapper settings" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: fzimmer + breaking_change: true body: | As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/#geo-foreign-data-wrapper-settings-deprecated), the following configuration settings in `/etc/gitlab/gitlab.rb` have been removed in 14.0: diff --git a/data/removals/14_0/removal-graphql-fields.yml b/data/removals/14_0/removal-graphql-fields.yml index 24d2bb4a4eb..71d277bd6fc 100644 --- a/data/removals/14_0/removal-graphql-fields.yml +++ b/data/removals/14_0/removal-graphql-fields.yml @@ -1,7 +1,8 @@ -- name: "Deprecated GraphQL fields have been removed" +- name: "Deprecated GraphQL fields" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: gweaver + breaking_change: true body: | In accordance with our [GraphQL deprecation and removal process](https://docs.gitlab.com/ee/api/graphql/#deprecation-process), the following fields that were deprecated prior to 13.7 are [fully removed in 14.0](https://gitlab.com/gitlab-org/gitlab/-/issues/267966): diff --git a/data/removals/14_0/removal-legacy-storage.yml b/data/removals/14_0/removal-legacy-storage.yml index 677ec7b8512..28b6ffeb0d1 100644 --- a/data/removals/14_0/removal-legacy-storage.yml +++ b/data/removals/14_0/removal-legacy-storage.yml @@ -1,6 +1,7 @@ -- name: "Legacy storage removed" +- name: "Legacy storage" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: fzimmer + breaking_change: true body: | As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/#planned-removal-of-legacy-storage-in-14.0), [legacy storage](https://docs.gitlab.com/ee/administration/repository_storage_types.html#legacy-storage) has been removed in GitLab 14.0. diff --git a/data/removals/14_0/removal-protect-features.yml b/data/removals/14_0/removal-protect-features.yml index 8e50925f6db..e8e71f7bbcd 100644 --- a/data/removals/14_0/removal-protect-features.yml +++ b/data/removals/14_0/removal-protect-features.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: sam.white + breaking_change: true body: | Clair, the default container scanning engine, was deprecated in GitLab 13.9 and is removed from GitLab 14.0 and replaced by Trivy. We advise customers who are customizing variables for their container scanning job to [follow these instructions](https://docs.gitlab.com/ee/user/application_security/container_scanning/#change-scanners) to ensure that their container scanning jobs continue to work. @@ -9,5 +10,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: sam.white + breaking_change: true body: | The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed from GitLab 14.0. The WAF had limitations inherent in the architectural design that made it difficult to meet the requirements traditionally expected of a WAF. By removing the WAF, GitLab is able to focus on improving other areas in the product where more value can be provided to users. Users who currently rely on the WAF can continue to use the free and open source [ModSecurity](https://github.com/SpiderLabs/ModSecurity) project, which is independent from GitLab. Additional details are available in the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271276). diff --git a/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml b/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml index 442c0e97cde..9995e5a2b55 100644 --- a/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml +++ b/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml @@ -1,7 +1,8 @@ -- name: Sidekiq queue selector options no longer accept the 'experimental' prefix +- name: Experimental prefix in Sidekiq queue selector options removal_date: "2021-06-22" removal_milestone: "14.0" reporter: smcgivern + breaking_change: true body: | GitLab supports a [queue selector](https://docs.gitlab.com/ee/administration/operations/extra_sidekiq_processes.html#queue-selector) to run only a subset of background jobs for a given process. When it was introduced, this option had an 'experimental' prefix (`experimental_queue_selector` in Omnibus, `experimentalQueueSelector` in Helm charts). diff --git a/data/removals/14_0/removal-unicorn.yml b/data/removals/14_0/removal-unicorn.yml index af0bed0f3ec..d5062aa0eea 100644 --- a/data/removals/14_0/removal-unicorn.yml +++ b/data/removals/14_0/removal-unicorn.yml @@ -1,6 +1,7 @@ -- name: "Unicorn removed in favor of Puma for GitLab self-managed" +- name: "Unicorn in GitLab self-managed" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: fzimmer + breaking_change: true body: | [Support for Unicorn](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6078) has been removed in GitLab 14.0 in favor of Puma. [Puma has a multi-threaded architecture](https://docs.gitlab.com/ee/administration/operations/puma.html) which uses less memory than a multi-process application server like Unicorn. On GitLab.com, we saw a 40% reduction in memory consumption by using Puma. diff --git a/data/removals/14_0/removal_ci_project_config_path.yml b/data/removals/14_0/removal_ci_project_config_path.yml index 8e90c83c7c4..64fe187c505 100644 --- a/data/removals/14_0/removal_ci_project_config_path.yml +++ b/data/removals/14_0/removal_ci_project_config_path.yml @@ -1,7 +1,8 @@ -- name: "`CI_PROJECT_CONFIG_PATH` variable has been removed" +- name: "`CI_PROJECT_CONFIG_PATH` variable" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: stkerr + breaking_change: true body: | The `CI_PROJECT_CONFIG_PATH` [predefined project variable](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) has been removed in favor of `CI_CONFIG_PATH`, which is functionally the same. diff --git a/data/removals/14_0/removal_enablement_helm2.yml b/data/removals/14_0/removal_enablement_helm2.yml index 323b22fd3b4..09136bead3e 100644 --- a/data/removals/14_0/removal_enablement_helm2.yml +++ b/data/removals/14_0/removal_enablement_helm2.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: joshlambert + breaking_change: true body: | Helm v2 was [officially deprecated](https://helm.sh/blog/helm-v2-deprecation-timeline/) in November of 2020, with the `stable` repository being [de-listed from the Helm Hub](https://about.gitlab.com/blog/2020/11/09/ensure-auto-devops-work-after-helm-stable-repo/) shortly thereafter. With the release of GitLab 14.0, which will include the 5.0 release of the [GitLab Helm chart](https://docs.gitlab.com/charts/), Helm v2 will no longer be supported. diff --git a/data/removals/14_0/removal_enablement_opensuse_15_1.yml b/data/removals/14_0/removal_enablement_opensuse_15_1.yml index cff442d7b92..2e0333c3b88 100644 --- a/data/removals/14_0/removal_enablement_opensuse_15_1.yml +++ b/data/removals/14_0/removal_enablement_opensuse_15_1.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: dorrino + breaking_change: true body: | Support for [OpenSUSE Leap 15.1 is being deprecated](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/5135). Support for 15.1 will be dropped in 14.0. We are now providing support for openSUSE Leap 15.2 packages. diff --git a/data/removals/14_0/removal_enablement_pg11.yml b/data/removals/14_0/removal_enablement_pg11.yml index c7b9f8b528b..7c5738b7ff9 100644 --- a/data/removals/14_0/removal_enablement_pg11.yml +++ b/data/removals/14_0/removal_enablement_pg11.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: joshlambert + breaking_change: true body: | PostgreSQL 12 will be the minimum required version in GitLab 14.0. It offers [significant improvements](https://www.postgresql.org/about/news/postgresql-12-released-1976/) to indexing, partitioning, and general performance benefits. diff --git a/data/removals/14_0/removal_enablement_ubuntu_16.yml b/data/removals/14_0/removal_enablement_ubuntu_16.yml index 65457db8c68..593bac720c1 100644 --- a/data/removals/14_0/removal_enablement_ubuntu_16.yml +++ b/data/removals/14_0/removal_enablement_ubuntu_16.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: joshlambert + breaking_change: true body: | Ubuntu 16.04 [reached end-of-life in April 2021](https://ubuntu.com/about/release-cycle), and no longer receives maintenance updates. We strongly recommend users to upgrade to a newer release, such as 20.04. diff --git a/data/removals/14_0/removal_repost_static_analysis_notices.yml b/data/removals/14_0/removal_repost_static_analysis_notices.yml index 1105f21e3fd..1a2ae93a902 100644 --- a/data/removals/14_0/removal_repost_static_analysis_notices.yml +++ b/data/removals/14_0/removal_repost_static_analysis_notices.yml @@ -3,34 +3,37 @@ removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/229974' + breaking_change: true body: | Until GitLab 13.9, if you wanted to avoid running one particular GitLab SAST analyzer, you needed to remove it from the [long string of analyzers in the `SAST.gitlab-ci.yml` file](https://gitlab.com/gitlab-org/gitlab/-/blob/390afc431e7ce1ac253b35beb39f19e49c746bff/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L12) and use that to set the [`SAST_DEFAULT_ANALYZERS`](https://docs.gitlab.com/ee/user/application_security/sast/#docker-images) variable in your project's CI file. If you did this, it would exclude you from future new analyzers because this string hard codes the list of analyzers to execute. We avoid this problem by inverting this variable's logic to exclude, rather than choose default analyzers. Beginning with 13.9, [we migrated](https://gitlab.com/gitlab-org/gitlab/-/blob/14fed7a33bfdbd4663d8928e46002a5ef3e3282c/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L13) to `SAST_EXCLUDED_ANALYZERS` in our `SAST.gitlab-ci.yml` file. We encourage anyone who uses a [customized SAST configuration](https://docs.gitlab.com/ee/user/application_security/sast/#customizing-the-sast-settings) in their project CI file to migrate to this new variable. If you have not overridden `SAST_DEFAULT_ANALYZERS`, no action is needed. The CI/CD variable `SAST_DEFAULT_ANALYZERS` has been removed in GitLab 14.0, which released on June 22, 2021. -- name: "Remove `secret_detection_default_branch` job" +- name: "`secret_detection_default_branch` job" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/297269' + breaking_change: true body: | To ensure Secret Detection was scanning both default branches and feature branches, we introduced two separate secret detection CI jobs (`secret_detection_default_branch` and `secret_detection`) in our managed [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Secret-Detection.gitlab-ci.yml) template. These two CI jobs created confusion and complexity in the CI rules logic. This deprecation moves the `rule` logic into the `script` section, which then determines how the `secret_detection` job is run (historic, on a branch, commits, etc). If you override or maintain custom versions of `SAST.gitlab-ci.yml` or `Secret-Detection.gitlab-ci.yml`, you must update your CI templates. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/secret_detection/#custom-settings-example) to future-proof your CI templates. GitLab 14.0 no longer supports the old `secret_detection_default_branch` job. -- name: "Remove SAST analyzer `SAST_GOSEC_CONFIG` variable in favor of - custom rulesets" +- name: "SAST analyzer `SAST_GOSEC_CONFIG` variable" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/301215' + breaking_change: true body: | With the release of [SAST Custom Rulesets](https://docs.gitlab.com/ee/user/application_security/sast/#customize-rulesets) in GitLab 13.5 we allow greater flexibility in configuration options for our Go analyzer (GoSec). As a result we no longer plan to support our less flexible [`SAST_GOSEC_CONFIG`](https://docs.gitlab.com/ee/user/application_security/sast/#analyzer-settings) analyzer setting. This variable was deprecated in GitLab 13.10. GitLab 14.0 removes the old `SAST_GOSEC_CONFIG variable`. If you use or override `SAST_GOSEC_CONFIG` in your CI file, update your SAST CI configuration or pin to an older version of the GoSec analyzer. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/sast/#overriding-sast-jobs) to future-proof your CI templates. -- name: "Removed Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template" +- name: "Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template" reporter: tmccaslin removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/301216' + breaking_change: true body: | With the maturity of GitLab Secure scanning tools, we've needed to add more granularity to our release process. Previously, GitLab shared a major version number for [all analyzers and tools](https://docs.gitlab.com/ee/user/application_security/sast/#supported-languages-and-frameworks). This requires all tools to share a major version, and prevents the use of [semantic version numbering](https://semver.org/). In GitLab 14.0, SAST removes the `SAST_ANALYZER_IMAGE_TAG` global variable in our [managed `SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST.gitlab-ci.yml) CI template, in favor of the analyzer job variable setting the `major.minor` tag in the SAST vendored template. diff --git a/data/removals/14_0/removal_runner_25555.yml b/data/removals/14_0/removal_runner_25555.yml index f317eaab846..706614618ce 100644 --- a/data/removals/14_0/removal_runner_25555.yml +++ b/data/removals/14_0/removal_runner_25555.yml @@ -1,7 +1,8 @@ -- name: "Remove off peak time mode configuration for Docker Machine autoscaling" +- name: "Off peak time mode configuration for Docker Machine autoscaling" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/5069), we introduced new timing options for the GitLab Docker Machine executor. In GitLab Runner 14.0, we have removed the old configuration option, [off peak time mode](https://docs.gitlab.com/runner/configuration/autoscale.html#off-peak-time-mode-configuration-deprecated). diff --git a/data/removals/14_0/removal_runner_26036.yml b/data/removals/14_0/removal_runner_26036.yml index 564143fda82..5f391909a2d 100644 --- a/data/removals/14_0/removal_runner_26036.yml +++ b/data/removals/14_0/removal_runner_26036.yml @@ -1,6 +1,7 @@ -- name: "Remove Ubuntu 19.10 (Eoan Ermine) package" +- name: "Ubuntu 19.10 (Eoan Ermine) package" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitLab Runner 14.0, Ubuntu 19.10 (Eoan Ermine) is no longer available from our package distribution. Refer to [issue #26036](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26036) for details. diff --git a/data/removals/14_0/removal_runner_26419.yml b/data/removals/14_0/removal_runner_26419.yml index 8b0f3846c7a..85d57de763e 100644 --- a/data/removals/14_0/removal_runner_26419.yml +++ b/data/removals/14_0/removal_runner_26419.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor. In 14.0, PowerShell Core, `pwsh` is now the default shell for newly-registered Windows runners. Windows `CMD` will still be available as a shell option for Windows runners. Refer to [issue #26419](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26419) for details. diff --git a/data/removals/14_0/removal_runner_4845.yml b/data/removals/14_0/removal_runner_4845.yml index 92e4e0172f2..db25c0741cb 100644 --- a/data/removals/14_0/removal_runner_4845.yml +++ b/data/removals/14_0/removal_runner_4845.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In GitLab Runner 14.0, the installation process will ignore the `skel` directory by default when creating the user home directory. Refer to [issue #4845](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4845) for details. diff --git a/data/removals/14_0/removal_runner_6413.yml b/data/removals/14_0/removal_runner_6413.yml index f08b1091cca..514cb254d8d 100644 --- a/data/removals/14_0/removal_runner_6413.yml +++ b/data/removals/14_0/removal_runner_6413.yml @@ -1,6 +1,7 @@ -- name: "Remove `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag" +- name: "`FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitlab-131-and-later), [issue #3376](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3376), we introduced `sigterm` and then `sigkill` to a process in the Shell executor. We also introduced a new feature flag, `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL`, so you can use the previous process termination sequence. In GitLab Runner 14.0, [issue #6413](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6413), the feature flag has been removed. diff --git a/data/removals/14_0/removals-14-testing-team.yml b/data/removals/14_0/removals-14-testing-team.yml index d76de564cdd..2012f8738b8 100644 --- a/data/removals/14_0/removals-14-testing-team.yml +++ b/data/removals/14_0/removals-14-testing-team.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jheimbuck_gl + breaking_change: true body: | Browser Performance Testing has run in a job named `performance` by default. With the introduction of [Load Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/load_performance_testing.html) in GitLab 13.2, this naming could be confusing. To make it clear which job is running [Browser Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html), the default job name is changed from `performance` to `browser_performance` in the template in GitLab 14.0. @@ -10,6 +11,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jheimbuck_gl + breaking_change: true body: | By default, the Code Quality feature has not provided support for Ruby 2.6+ if you're using the Code Quality template. To better support the latest versions of Ruby, the default RuboCop version is updated to add support for Ruby 2.4 through 3.0. As a result, support for Ruby 2.1, 2.2, and 2.3 is removed. You can re-enable support for older versions by [customizing your configuration](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#rubocop-errors). @@ -18,6 +20,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jheimbuck_gl + breaking_change: true body: | By default, the `Ruby.gitlab-ci.yml` file has included Ruby 2.5. diff --git a/data/removals/14_0/removals_runner_26651.yml b/data/removals/14_0/removals_runner_26651.yml index a22f8dfc9ac..8a35996c81a 100644 --- a/data/removals/14_0/removals_runner_26651.yml +++ b/data/removals/14_0/removals_runner_26651.yml @@ -1,6 +1,7 @@ -- name: "Remove `/usr/lib/gitlab-runner` symlink from package" +- name: "`/usr/lib/gitlab-runner` symlink from package" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab-runner` to `/usr/bin/gitlab-runner`. In 14.0, the symlink has been removed and the runner is now installed in `/usr/bin/gitlab-runner`. Refer to [issue #26651](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26651) for details. diff --git a/data/removals/14_0/removals_runner_26679.yml b/data/removals/14_0/removals_runner_26679.yml index 816bd8f37d5..e99a551a293 100644 --- a/data/removals/14_0/removals_runner_26679.yml +++ b/data/removals/14_0/removals_runner_26679.yml @@ -1,6 +1,7 @@ -- name: "Remove `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag" +- name: "`FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag. Refer to issue [#26679](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26679) for details. diff --git a/data/removals/14_0/removals_runner_26900.yml b/data/removals/14_0/removals_runner_26900.yml index bdba368eee8..addf11c86ad 100644 --- a/data/removals/14_0/removals_runner_26900.yml +++ b/data/removals/14_0/removals_runner_26900.yml @@ -1,6 +1,7 @@ -- name: "Remove success and failure for finished build metric conversion" +- name: "Success and failure for finished build metric conversion" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In GitLab Runner 13.5, we introduced `failed` and `success` states for a job. To support Prometheus rules, we chose to convert `success/failure` to `finished` for the metric. In 14.0, the conversion has now been removed. Refer to [issue #26900](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26900) for details. diff --git a/data/removals/14_0/removals_runner_27175.yml b/data/removals/14_0/removals_runner_27175.yml index 33629084073..a31c4e757e7 100644 --- a/data/removals/14_0/removals_runner_27175.yml +++ b/data/removals/14_0/removals_runner_27175.yml @@ -1,6 +1,7 @@ -- name: "Remove `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag" +- name: "`FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag. Refer to [issue #27175](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27175) for details. diff --git a/data/removals/14_0/removals_runner_27218.yml b/data/removals/14_0/removals_runner_27218.yml index fb1e27c3f91..8fb7e800b0b 100644 --- a/data/removals/14_0/removals_runner_27218.yml +++ b/data/removals/14_0/removals_runner_27218.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image) from the GitLab Container Registry instead of Docker Hub. Refer to [issue #27218](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27218) for details. diff --git a/data/removals/14_0/removals_runner_27551.yml b/data/removals/14_0/removals_runner_27551.yml index 6f4ee52749c..43ecf3d72f6 100644 --- a/data/removals/14_0/removals_runner_27551.yml +++ b/data/removals/14_0/removals_runner_27551.yml @@ -1,6 +1,7 @@ -- name: "Remove support for Windows Server 1903 image" +- name: "Windows Server 1903 image support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In 14.0, we have removed Windows Server 1903. Microsoft ended support for this version on 2020-08-12. Refer to [issue #27551](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27551) for details. diff --git a/data/removals/14_0/removals_runner_27899.yml b/data/removals/14_0/removals_runner_27899.yml index 226520abda4..468e04dc677 100644 --- a/data/removals/14_0/removals_runner_27899.yml +++ b/data/removals/14_0/removals_runner_27899.yml @@ -1,6 +1,7 @@ -- name: "Remove support for Windows Server 1909 image" +- name: "Windows Server 1909 image support" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: deastman + breaking_change: true body: | In 14.0, we have removed Windows Server 1909. Microsoft ended support for this version on 2021-05-11. Refer to [issue #27899](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27899) for details. diff --git a/data/removals/14_0/remove-sql-elector.yml b/data/removals/14_0/remove-sql-elector.yml index d35fac0786c..6a306569d9f 100644 --- a/data/removals/14_0/remove-sql-elector.yml +++ b/data/removals/14_0/remove-sql-elector.yml @@ -1,7 +1,8 @@ -- name: "Gitaly Cluster SQL primary elector has been removed" +- name: "Gitaly Cluster SQL primary elector" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: mjwood + breaking_change: true body: | Now that Praefect supports a [primary election strategy](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#repository-specific-primary-nodes) for each repository, we have removed the `sql` election strategy. The `per_repository` election strategy is the new default, which is automatically used if no election strategy was specified. diff --git a/data/removals/14_0/remove_dast_env_variables.yml b/data/removals/14_0/remove_dast_env_variables.yml index f2bbe748af5..3a40c6518e0 100644 --- a/data/removals/14_0/remove_dast_env_variables.yml +++ b/data/removals/14_0/remove_dast_env_variables.yml @@ -2,6 +2,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson + breaking_change: true body: | GitLab 13.8 renamed multiple environment variables to support their broader usage in different workflows. In GitLab 14.0, the old variables have been permanently removed and will no longer work. Any configurations using these variables must be updated to the new variable names. Any scans using these variables in GitLab 14.0 and later will fail to be configured correctly. These variables are: diff --git a/data/removals/14_0/remove_dast_legacy_domain_validation.yml b/data/removals/14_0/remove_dast_legacy_domain_validation.yml index 61fb9002880..39acc3e7188 100644 --- a/data/removals/14_0/remove_dast_legacy_domain_validation.yml +++ b/data/removals/14_0/remove_dast_legacy_domain_validation.yml @@ -1,7 +1,8 @@ -- name: "Remove legacy DAST domain validation" +- name: "Legacy DAST domain validation" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson + breaking_change: true body: | The legacy method of DAST Domain Validation for CI/CD scans was deprecated in GitLab 13.8, and is removed in GitLab 14.0. This method of domain validation only disallows scans if the `DAST_FULL_SCAN_DOMAIN_VALIDATION_REQUIRED` environment variable is set to `true` in the `gitlab-ci.yml` file, and a `Gitlab-DAST-Permission` header on the site is not set to `allow`. This two-step method required users to opt in to using the variable before they could opt out from using the header. diff --git a/data/removals/14_0/remove_dast_legacy_report_fields.yml b/data/removals/14_0/remove_dast_legacy_report_fields.yml index ec98b173a24..e5fca1fa256 100644 --- a/data/removals/14_0/remove_dast_legacy_report_fields.yml +++ b/data/removals/14_0/remove_dast_legacy_report_fields.yml @@ -1,7 +1,8 @@ -- name: "Removal of legacy fields from DAST report" +- name: "Legacy fields from DAST report" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson + breaking_change: true body: | As a part of the migration to a common report format for all of the Secure scanners in GitLab, DAST is making changes to the DAST JSON report. Certain legacy fields were deprecated in 13.8 and have been completely removed in 14.0. These fields are `@generated`, `@version`, `site`, and `spider`. This should not affect any normal DAST operation, but does affect users who consume the JSON report in an automated way and use these fields. Anyone affected by these changes, and needs these fields for business reasons, is encouraged to open a new GitLab issue and explain the need. diff --git a/data/removals/14_0/remove_dast_spider_host_reset.yml b/data/removals/14_0/remove_dast_spider_host_reset.yml index de334618b88..53122f6071f 100644 --- a/data/removals/14_0/remove_dast_spider_host_reset.yml +++ b/data/removals/14_0/remove_dast_spider_host_reset.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson + breaking_change: true body: | In GitLab 14.0, DAST has removed the current method of resetting the scan to the hostname when starting to spider. Prior to GitLab 14.0, the spider would not begin at the specified target path for the URL but would instead reset the URL to begin crawling at the host root. GitLab 14.0 changes the default for the new variable `DAST_SPIDER_START_AT_HOST` to `false` to better support users' intention of beginning spidering and scanning at the specified target URL, rather than the host root URL. This change has an added benefit: scans can take less time, if the specified path does not contain links to the entire site. This enables easier scanning of smaller sections of an application, rather than crawling the entire app during every scan. diff --git a/data/removals/14_0/remove_dast_template_stages.yml b/data/removals/14_0/remove_dast_template_stages.yml index 0f72091735d..0995e09c3ed 100644 --- a/data/removals/14_0/remove_dast_template_stages.yml +++ b/data/removals/14_0/remove_dast_template_stages.yml @@ -1,6 +1,7 @@ -- name: "Remove DAST default template stages" +- name: "DAST default template stages" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: derekferguson + breaking_change: true body: | In GitLab 14.0, we've removed the stages defined in the current `DAST.gitlab-ci.yml` template to avoid the situation where the template overrides manual changes made by DAST users. We're making this change in response to customer issues where the stages in the template cause problems when used with customized DAST configurations. Because of this removal, `gitlab-ci.yml` configurations that do not specify a `dast` stage must be updated to include this stage. diff --git a/data/removals/14_0/remove_optimize_api.yml b/data/removals/14_0/remove_optimize_api.yml index 5df120858c6..a472e6a0d59 100644 --- a/data/removals/14_0/remove_optimize_api.yml +++ b/data/removals/14_0/remove_optimize_api.yml @@ -1,6 +1,7 @@ -- name: "Segments removed from DevOps Adoption API" +- name: "DevOps Adoption API Segments" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: ljlane + breaking_change: true body: | The first release of the DevOps Adoption report had a concept of **Segments**. Segments were [quickly removed from the report](https://gitlab.com/groups/gitlab-org/-/epics/5251) because they introduced an additional layer of complexity on top of **Groups** and **Projects**. Subsequent iterations of the DevOps Adoption report focus on comparing adoption across groups rather than segments. GitLab 14.0 removes all references to **Segments** [from the GraphQL API](https://gitlab.com/gitlab-org/gitlab/-/issues/324414) and replaces them with **Enabled groups**. diff --git a/data/removals/14_0/remove_terraform_template.yml b/data/removals/14_0/remove_terraform_template.yml index bc3b529f630..2d78eb1f59c 100644 --- a/data/removals/14_0/remove_terraform_template.yml +++ b/data/removals/14_0/remove_terraform_template.yml @@ -3,6 +3,7 @@ removal_date: "2021-06-22" removal_milestone: "14.0" issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/328500' + breaking_change: true body: | GitLab 14.0 renews the Terraform CI template to the latest version. The new template is set up for the GitLab Managed Terraform state, with a dependency on the GitLab `terraform-images` image, to provide a good user experience around GitLab's Infrastructure-as-Code features. diff --git a/data/removals/14_0/verify-ci-removal-parametertrace.yml b/data/removals/14_0/verify-ci-removal-parametertrace.yml index c37497c1a35..67d52827485 100644 --- a/data/removals/14_0/verify-ci-removal-parametertrace.yml +++ b/data/removals/14_0/verify-ci-removal-parametertrace.yml @@ -1,7 +1,8 @@ -- name: "Removal of deprecated `trace` parameter from `jobs` API endpoint" +- name: "`trace` parameter in `jobs` API" removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jreporter + breaking_change: true body: | GitLab Runner was updated in GitLab 13.4 to internally stop passing the `trace` parameter to the `/api/jobs/:id` endpoint. GitLab 14.0 deprecates the `trace` parameter entirely for all other requests of this endpoint. Make sure your [GitLab Runner version matches your GitLab version](https://docs.gitlab.com/runner/#gitlab-runner-versions) to ensure consistent behavior. diff --git a/data/removals/14_0/verify-ci-removalpipelineservice.yml b/data/removals/14_0/verify-ci-removalpipelineservice.yml index f3583bd0498..fe3d3f224d1 100644 --- a/data/removals/14_0/verify-ci-removalpipelineservice.yml +++ b/data/removals/14_0/verify-ci-removalpipelineservice.yml @@ -2,5 +2,6 @@ removal_date: "2021-06-22" removal_milestone: "14.0" reporter: jreporter + breaking_change: true body: | For self-managed instances using the experimental [external pipeline validation service](https://docs.gitlab.com/ee/administration/external_pipeline_validation.html), the range of error codes GitLab accepts will be reduced. Currently, pipelines are invalidated when the validation service returns a response code from `400` to `499`. In GitLab 14.0 and later, pipelines will be invalidated for the `406: Not Accepted` response code only. diff --git a/data/removals/14_1/removal-memory-prometheus-options-source.yml b/data/removals/14_1/removal-memory-prometheus-options-source.yml index afef081c348..57a5dfa5d69 100644 --- a/data/removals/14_1/removal-memory-prometheus-options-source.yml +++ b/data/removals/14_1/removal-memory-prometheus-options-source.yml @@ -2,6 +2,7 @@ removal_date: July 22, 2021 removal_milestone: "14.1" reporter: fzimmer + breaking_change: false body: | The support for `prometheus.listen_address` and `prometheus.enable` has been removed from `gitlab.yml`. Use `prometheus.enabled` and `prometheus.server_address` to set up Prometheus server that GitLab instance connects to. Refer to [our documentation](https://docs.gitlab.com/ee/install/installation.html#prometheus-server-setup) for details. diff --git a/data/removals/14_1/removal-outdated-browser-support.yml b/data/removals/14_1/removal-outdated-browser-support.yml index 1019b8fe2f3..281b8d65686 100644 --- a/data/removals/14_1/removal-outdated-browser-support.yml +++ b/data/removals/14_1/removal-outdated-browser-support.yml @@ -2,6 +2,7 @@ removal_date: July 22, 2021 removal_milestone: "14.1" reporter: leipert + breaking_change: false body: | In GitLab 14.1, we are cleaning up and [removing old code](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63994) that was specific for browsers that we no longer support. This has no impact on users when one of our [supported web browsers](https://docs.gitlab.com/ee/install/requirements.html#supported-web-browsers) is used. diff --git a/data/removals/14_2/removal-verify-build-log.yml b/data/removals/14_2/removal-verify-build-log.yml index 6b4e37c7c6e..10ffe8b7242 100644 --- a/data/removals/14_2/removal-verify-build-log.yml +++ b/data/removals/14_2/removal-verify-build-log.yml @@ -2,6 +2,7 @@ removal_date: August 22, 2021 # day the removal was released removal_milestone: "14.2" reporter: jreporter # GitLab username of the person reporting the removal + breaking_change: false body: | GitLab values efficiency for all users in our wider community of contributors, so we're always working hard to make sure the application performs at a high level with a lovable UX. In GitLab 14.2, we have introduced a [job log file size limit](https://docs.gitlab.com/ee/administration/instance_limits.html#maximum-file-size-for-job-logs), set to 100 megabytes by default. Administrators of self-managed GitLab instances can customize this to any value. All jobs that exceed this limit are dropped and marked as failed, helping prevent performance impacts or over-use of resources. This ensures that everyone using GitLab has the best possible experience. diff --git a/data/removals/14_3/removal-limit-tags-to-50.yml b/data/removals/14_3/removal-limit-tags-to-50.yml index db624656e6e..3395fc9b6ce 100644 --- a/data/removals/14_3/removal-limit-tags-to-50.yml +++ b/data/removals/14_3/removal-limit-tags-to-50.yml @@ -1,6 +1,7 @@ - name: "Introduced limit of 50 tags for jobs" removal_date: September 22nd, 2021 removal_milestone: "14.3" - reporter: jreporter + reporter: jreporter + breaking_change: false body: | GitLab values efficiency and is prioritizing reliability for [GitLab.com in FY22](https://about.gitlab.com/direction/#gitlab-hosted-first). In 14.3, GitLab CI/CD jobs must have less than 50 [tags](https://docs.gitlab.com/ee/ci/yaml/index.html#tags). If a pipeline contains a job with 50 or more tags, you will receive an error and the pipeline will not be created. diff --git a/data/removals/14_3/removal-verify-pe-pipelinefindername.yml b/data/removals/14_3/removal-verify-pe-pipelinefindername.yml index 979317f99df..df39a6cec38 100644 --- a/data/removals/14_3/removal-verify-pe-pipelinefindername.yml +++ b/data/removals/14_3/removal-verify-pe-pipelinefindername.yml @@ -2,5 +2,6 @@ removal_date: September 22, 2021 # day the removal was released removal_milestone: "14.3" reporter: jreporter # GitLab username of the person reporting the removal + breaking_change: false body: | In GitLab 14.3, we will remove the ability to filter by `name` in the [list project pipelines API endpoint](https://docs.gitlab.com/ee/api/pipelines.html#list-project-pipelines) to improve performance. If you currently use this parameter with this endpoint, you must switch to `username`. diff --git a/data/removals/14_3/removal_legacy_storage_setting.yml b/data/removals/14_3/removal_legacy_storage_setting.yml index b1f98e47554..5241861bf5a 100644 --- a/data/removals/14_3/removal_legacy_storage_setting.yml +++ b/data/removals/14_3/removal_legacy_storage_setting.yml @@ -2,6 +2,7 @@ removal_date: September 22nd, 2021 # day the removal was released removal_milestone: "14.3" reporter: dorrino # GitLab username of the person reporting the removal + breaking_change: false body: | # example (supports markdown) The support for [`gitlab_pages['use_legacy_storage']` setting](https://docs.gitlab.com/ee/administration/pages/index.html#domain-source-configuration-before-140) in Omnibus installations has been removed. diff --git a/data/removals/14_6/limit_trigger_pipelines.yml b/data/removals/14_6/limit_trigger_pipelines.yml new file mode 100644 index 00000000000..c69b7feecd2 --- /dev/null +++ b/data/removals/14_6/limit_trigger_pipelines.yml @@ -0,0 +1,6 @@ +- name: "Limit the number of triggered pipeline to 25K in free tier" + removal_date: Dec 22, 2021 # day the removal was released + removal_milestone: "14.6" + reporter: dhershkovitch # GitLab username of the person reporting the removal + body: | + A large amount of triggered pipelines in a single project impacts the performance of GitLab.com. In GitLab 14.6, we are limiting the number of triggered pipelines in a single project on GitLab.com at any given moment to 25,000. This change applies to projects in the free tier only, Premium and Ultimate are not affected by this change. diff --git a/data/removals/14_6/removal-release-cli-s3.yml b/data/removals/14_6/removal-release-cli-s3.yml new file mode 100644 index 00000000000..b92d8bb60f8 --- /dev/null +++ b/data/removals/14_6/removal-release-cli-s3.yml @@ -0,0 +1,6 @@ +- name: "Release CLI distributed as a generic package" + removal_date: Dec 22, 2021 # day the removal was released + removal_milestone: "14.6" + reporter: kbychu # GitLab username of the person reporting the removal + body: | + The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as a [generic package](https://gitlab.com/gitlab-org/release-cli/-/packages) starting in GitLab 14.2. We will continue to deploy it as a binary to S3 until GitLab 14.5 and stop distributing it in S3 in GitLab 14.6. diff --git a/data/removals/templates/_removal_template.md.erb b/data/removals/templates/_removal_template.md.erb index e227c6aa6e6..5243f4fdcd8 100644 --- a/data/removals/templates/_removal_template.md.erb +++ b/data/removals/templates/_removal_template.md.erb @@ -33,6 +33,7 @@ For removal reviewers (Technical Writers only): <%- entries.select{|entry| entry["removal_milestone"] == milestone}.each do |removal| %> ### <%= removal["name"]%> <% if removal["breaking_change"] -%> + WARNING: This feature was changed or removed in <%= removal["removal_milestone"]%> as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). diff --git a/data/removals/templates/example.yml b/data/removals/templates/example.yml index 78cbec2be28..0904c6a6d7a 100644 --- a/data/removals/templates/example.yml +++ b/data/removals/templates/example.yml @@ -9,13 +9,14 @@ # # Please delete this line and above before submitting your merge request. -- name: "Announcement headline" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0" - announcement_milestone: "XX.YY" # The milestone when this feature was deprecated. - announcement_date: "YYYY-MM-DD" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. - removal_milestone: "XX.YY" # The milestone when this feature is being removed. - removal_date: "YYYY-MM-DD" # This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed. - breaking_change: false # Change to true if this removal is a breaking change. - body: | # Do not modify this line, instead modify the lines below. +- name: "Feature name" # the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. + announcement_milestone: "XX.YY" # The milestone when this feature was deprecated. + announcement_date: "YYYY-MM-DD" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. + removal_milestone: "XX.YY" # The milestone when this feature is being removed. + removal_date: "YYYY-MM-DD" # This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed. + breaking_change: false # Change to true if this removal is a breaking change. + reporter: exampleuser # GitLab username of the person reporting the removal + body: | # Do not modify this line, instead modify the lines below. <!-- START OF BODY COMMENT This area supports markdown. Delete this entire comment and replace it with your markdown content. @@ -24,9 +25,9 @@ END OF BODY COMMENT --> # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth - tiers: # (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] - issue_url: # (optional) This is a link to the deprecation issue in GitLab - 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 + stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + tiers: # (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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + 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 diff --git a/data/whats_new/2021111800001_14_05.yml b/data/whats_new/2021111800001_14_05.yml index c38d4cfa9fa..5a7607478fc 100644 --- a/data/whats_new/2021111800001_14_05.yml +++ b/data/whats_new/2021111800001_14_05.yml @@ -16,7 +16,7 @@ self-managed: true gitlab-com: true packages: [Free, Premium, Ultimate] - url: 'https://docs.gitlab.com/ee/user/profile/#user-profile-readme' + url: 'https://docs.gitlab.com/ee/user/profile/#add-details-to-your-profile-with-a-readme' image_url: https://about.gitlab.com/images/14_5/user_profiles_readme.png published_at: 2021-11-22 release: 14.5 |