diff options
Diffstat (limited to 'doc/update/deprecations.md')
| -rw-r--r-- | doc/update/deprecations.md | 717 |
1 files changed, 539 insertions, 178 deletions
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 7e8eaef2b4c..903ae9c714c 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -36,14 +36,112 @@ For deprecation reviewers (Technical Writers only): https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc --> +{::options parse_block_html="true" /} + View deprecations by the product versions in which they were announced. Each deprecation has a **planned removal milestone** and indicates whether it is a breaking change. Most of the deprecations are **planned for removal in 15.0**, and many of them are **breaking changes**. +<div class="js-deprecation-filters"></div> + +<div class="announcement-milestone"> + +## 15.0 + +<div class="deprecation removal-160 breaking-change"> + +### CiCdSettingsUpdate mutation renamed to ProjectCiCdSettingsUpdate + +WARNING: +This feature will be changed or removed in 16.0 +as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). +Before updating GitLab, review the details carefully to determine if you need to make any +changes to your code, settings, or workflow. + +The `CiCdSettingsUpdate` mutation was renamed to `ProjectCiCdSettingsUpdate` in GitLab 15.0. +The `CiCdSettingsUpdate` mutation will be removed in GitLab 16.0. +Any user scripts that use the `CiCdSettingsUpdate` mutation must be updated to use `ProjectCiCdSettingsUpdate` +instead. + +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> + +### GraphQL API legacyMode argument for Runner status + +WARNING: +This feature will be changed or removed in 16.0 +as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). +Before updating GitLab, review the details carefully to determine if you need to make any +changes to your code, settings, or workflow. + +The `legacyMode` argument to the `status` field in `RunnerType` will be rendered non-functional in the 16.0 release +as part of the deprecations details in the [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351109). + +In GitLab 16.0 and later, the `status` field will act as if `legacyMode` is null. The `legacyMode` argument will +be present during the 16.x cycle to avoid breaking the API signature, and will be removed altogether in the +17.0 release. + +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> + +### PostgreSQL 12 deprecated + +WARNING: +This feature will be changed or removed in 16.0 +as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). +Before updating GitLab, review the details carefully to determine if you need to make any +changes to your code, settings, or workflow. + +Support for PostgreSQL 12 is scheduled for removal in GitLab 16.0. +In GitLab 16.0, PostgreSQL 13 becomes the minimum required PostgreSQL version. + +PostgreSQL 12 will be supported for the full GitLab 15 release cycle. +PostgreSQL 13 will also be supported for instances that want to upgrade prior to GitLab 16.0. + +Upgrading to PostgreSQL 13 is not yet supported for GitLab instances with Geo enabled. Geo support for PostgreSQL 13 will be announced in a minor release version of GitLab 15, after the process is fully supported and validated. For more information, read the Geo related verifications on the [support epic for PostgreSQL 13](https://gitlab.com/groups/gitlab-org/-/epics/3832). + +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> + +<div class="deprecation removal-152"> + +### Vulnerability Report sort by State + +The ability to sort the Vulnerability Report by the `State` column was disabled and put behind a feature flag in GitLab 14.10 due to a refactor +of the underlying data model. The feature flag has remained off by default as further refactoring will be required to ensure sorting +by this value remains performant. Due to very low usage of the `State` column for sorting, the feature flag will instead be removed in +GitLab 15.2 to simplify the codebase and prevent any unwanted performance degradation. + +**Planned removal milestone: <span class="removal-milestone">15.2</span> (2022-07-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.10 +<div class="deprecation removal-150 breaking-change"> + +### Dependency Scanning default Java version changed to 17 + +WARNING: +This feature will be changed or removed in 15.0 +as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). +Before updating GitLab, review the details carefully to determine if you need to make any +changes to your code, settings, or workflow. + +In GitLab 15.0, for Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_Java_Version` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning). + +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2021-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> + ### Manual iteration management WARNING: @@ -72,7 +170,10 @@ arguments will be removed: For more information about iteration cadences, you can refer to [the documentation of the feature](https://docs.gitlab.com/ee/user/group/iterations/#iteration-cadences). -**Planned removal milestone: 16.0 (2023-04-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-04-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Outdated indices of Advanced Search migrations @@ -84,7 +185,10 @@ changes to your code, settings, or workflow. As Advanced Search migrations usually require support multiple code paths for a long period of time, it’s important to clean those up when we safely can. We use GitLab major version upgrades as a safe time to remove backward compatibility for indices that have not been fully migrated. See the [upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details. -**Planned removal milestone: 15.0 (2021-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2021-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### Toggle notes confidentiality on APIs @@ -96,10 +200,16 @@ changes to your code, settings, or workflow. Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. Updating notes confidential attribute is no longer supported by any means. We are changing this to simplify the experience and prevent private information from being unintentionally exposed. -**Planned removal milestone: 16.0 (2023-05-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.9 +<div class="deprecation removal-150 breaking-change"> + ### Background upload for object storage WARNING: @@ -117,19 +227,28 @@ This impacts a small subset of object storage providers: GitLab will publish additional guidance to assist affected customers in migrating. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-151"> ### Deprecate support for Debian 9 Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](https://wiki.debian.org/LTS). Therefore, we will no longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11. -**Planned removal milestone: 15.1 (2022-06-22)** +**Planned removal milestone: <span class="removal-milestone">15.1</span> (2022-06-22)** +</div> + +<div class="deprecation removal-150"> ### GitLab Pages running as daemon In 15.0, support for daemon mode for GitLab Pages will be removed. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### GitLab self-monitoring project @@ -141,7 +260,10 @@ changes to your code, settings, or workflow. GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 16.0. -**Planned removal milestone: 16.0 (2023-05-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### GraphQL permissions change for Package settings @@ -160,18 +282,24 @@ The permissions model for GraphQL is being updated. After 15.0, users with the G - [Dependency Proxy time-to-live policy](https://docs.gitlab.com/ee/api/graphql/reference/#dependencyproxyimagettlgrouppolicy) - [Enabling the Dependency Proxy for your group](https://docs.gitlab.com/ee/api/graphql/reference/#dependencyproxysetting) -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Move `custom_hooks_dir` setting from GitLab Shell to Gitaly The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks.html#create-a-global-server-hook-for-all-repositories) setting is now configured in Gitaly, and will be removed from GitLab Shell in GitLab 15.0. -**Planned removal milestone: 15.0 ()** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-1410 breaking-change"> ### Permissions change for downloading Composer dependencies WARNING: -This feature will be changed or removed in 15.0 +This feature will be changed or removed in 14.10 as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). Before updating GitLab, review the details carefully to determine if you need to make any changes to your code, settings, or workflow. @@ -180,7 +308,10 @@ The GitLab Composer repository can be used to push, search, fetch metadata about Downloading Composer dependencies without authentication is deprecated in GitLab 14.9, and will be removed in GitLab 15.0. Starting with GitLab 15.0, you must authenticate to download Composer dependencies. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">14.10</span> (2022-04-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### htpasswd Authentication for the Container Registry @@ -194,7 +325,10 @@ The Container Registry supports [authentication](https://gitlab.com/gitlab-org/c Since it isn't used in the context of GitLab (the product), `htpasswd` authentication will be deprecated in GitLab 14.9 and removed in GitLab 15.0. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### user_email_lookup_limit API field @@ -208,21 +342,15 @@ The `user_email_lookup_limit` [API field](https://docs.gitlab.com/ee/api/setting Any API calls attempting to change the rate limits for `user_email_lookup_limit` should use `search_rate_limit` instead. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> +</div> -## 14.8 - -### Changes to the `CI_JOB_JWT` - -WARNING: -This feature will be changed or removed in 15.0 -as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). -Before updating GitLab, review the details carefully to determine if you need to make any -changes to your code, settings, or workflow. +<div class="announcement-milestone"> -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`. +## 14.8 -**Planned removal milestone: 15.0 (2022-05-22)** +<div class="deprecation removal-149"> ### Configurable Gitaly `per_repository` election strategy @@ -231,7 +359,10 @@ Configuring the `per_repository` Gitaly election strategy is [deprecated](https: This change is part of regular maintenance to keep our codebase clean. -**Planned removal milestone: 14.9 (2022-03-22)** +**Planned removal milestone: <span class="removal-milestone">14.9</span> (2022-03-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Container Network and Host Security @@ -241,7 +372,7 @@ as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#brea Before updating GitLab, review the details carefully to determine if you need to make any changes to your code, settings, or workflow. -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). +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 GitLab [CI/CD](https://docs.gitlab.com/ee/user/clusters/agent/ci_cd_workflow.html). As part of this change, the following specific capabilities within GitLab are now deprecated, and are scheduled for removal in GitLab 15.0: @@ -252,7 +383,10 @@ As part of this change, the following specific capabilities within GitLab are no For additional context, or to provide feedback regarding this change, please reference our open [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/7476). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Dependency Scanning Python 3.9 and 3.6 image deprecation @@ -282,13 +416,19 @@ gemnasium-python-dependency_scanning: name: registry.gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python:2-python-3.9 ``` -**Planned removal milestone: 15.0 (2021-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2021-05-22)** +</div> + +<div class="deprecation removal-150"> ### Deprecate Geo Admin UI Routes 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Deprecate custom Geo:db:* Rake tasks @@ -313,7 +453,10 @@ The following `geo:db:*` tasks will be replaced with their corresponding `db:*:g - `geo:db:test:load` -> `db:test:load:geo` - `geo:db:test:purge` -> `db:test:purge:geo` -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS @@ -325,7 +468,10 @@ changes to your code, settings, or workflow. 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Deprecate legacy Gitaly configuration methods @@ -341,7 +487,10 @@ These variables are being replaced with standard [`config.toml` Gitaly configura GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configure Gitaly should switch to configuring using `config.toml`. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Elasticsearch 6.8 @@ -357,7 +506,10 @@ We recommend using the latest version of Elasticsearch 7 to benefit from all Ela 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). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### External status check API breaking changes @@ -383,7 +535,10 @@ and set to `passed`. Requests that: To align with this change, API calls to list external status checks will also return the value of `passed` rather than `approved` for status checks that have passed. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### GraphQL ID and GlobalID compatibility @@ -445,7 +600,10 @@ You should convert any queries in the first form (using `ID` as a named type in to one of the other two forms (using the correct appropriate type in the signature, or using an inline argument expression). -**Planned removal milestone: 15.0 (2022-04-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-04-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### OAuth tokens without expiration @@ -465,7 +623,10 @@ 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Optional enforcement of PAT expiration @@ -479,7 +640,10 @@ The feature to disable enforcement of PAT expiration is unusual from a security 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Optional enforcement of SSH expiration @@ -493,7 +657,10 @@ The feature to disable enforcement of SSH expiration is unusual from a security 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Out-of-the-box SAST support for Java 8 @@ -516,7 +683,10 @@ In GitLab 15.0, we will: 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). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node @@ -528,7 +698,10 @@ changes to your code, settings, or workflow. 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`. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### REST API Runner will not accept `status` filter values of `active` or `paused` @@ -546,7 +719,10 @@ Status values `paused` or `active` will no longer be accepted and will be replac 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`. -**Planned removal milestone: 16.0 (2023-04-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-04-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### REST API endpoint to list group runners no longer accepts `project_type` value for `type` argument @@ -558,7 +734,10 @@ changes to your code, settings, or workflow. The `GET /groups/:id/runners?type=project_type` endpoint will be removed in GitLab 16.0. The endpoint always returned an empty collection. -**Planned removal milestone: 16.0 (2023-04-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-04-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### REST and GraphQL API Runner usage of `active` replaced by `paused` @@ -588,7 +767,10 @@ The 16.0 release of the GitLab Runner will start using the `paused` property whe will only be compatible with GitLab 16.0 and later. Until 16.0, GitLab will accept the deprecated `active` flag from existing runners. -**Planned removal milestone: 16.0 (2023-04-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-04-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Request profiling @@ -606,7 +788,10 @@ It also depends on a few third-party gems that are not actively maintained anymo For more information, check the [summary section of the deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352488#deprecation-summary). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Required pipeline configurations in Premium tier @@ -623,7 +808,10 @@ This change to move the feature to GitLab's Ultimate tier is intended to help ou 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). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Retire-JS Dependency Scanning tool @@ -637,12 +825,15 @@ As of 14.8 the retire.js job is being deprecated from Dependency Scanning. It wi 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-152 breaking-change"> ### SAST analyzer consolidation and CI/CD template changes WARNING: -This feature will be changed or removed in 15.0 +This feature will be changed or removed in 15.2 as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). Before updating GitLab, review the details carefully to determine if you need to make any changes to your code, settings, or workflow. @@ -652,12 +843,15 @@ GitLab SAST uses various [analyzers](https://docs.gitlab.com/ee/user/application 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: +In GitLab 15.2, 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) +NOTE: +This change was originally planned for GitLab 15.0 and has been postponed. + 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). @@ -666,9 +860,12 @@ We will also remove Java from the scope of the [SpotBugs](https://gitlab.com/git 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). +If you applied customizations to any of the affected analyzers or if you currently disable the Semgrep analyzer in your pipelines, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352554#breaking-change). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.2</span> (2022-07-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### SAST support for .NET 2.1 @@ -698,7 +895,10 @@ Version 3 was [announced in GitLab 14.6](https://about.gitlab.com/releases/2021/ 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). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Secret Detection configuration variables deprecated @@ -719,7 +919,10 @@ You'll still be able to configure historical scanning of your commit history by For further details, see [the deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352565). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Secure and Protect analyzer images published in new location @@ -745,7 +948,10 @@ Otherwise, you won't receive further updates. See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564) for more details. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Secure and Protect analyzer major version update @@ -788,7 +994,10 @@ Specifically, the following are being deprecated and will no longer be updated a - `sobelow`: version 2 - `spotbugs`: version 2 -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab @@ -810,7 +1019,10 @@ By sending some of our internal RPC traffic through a custom protocol (instead o 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). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Test coverage project CI/CD setting @@ -821,13 +1033,16 @@ Before updating GitLab, review the details carefully to determine if you need to changes to your code, settings, or workflow. 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-using-project-settings-deprecated) +[project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-using-project-settings-removed) 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Vulnerability Check @@ -846,7 +1061,10 @@ The new security approvals feature is similar to vulnerability check. For exampl - 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### `CI_BUILD_*` predefined variables @@ -873,7 +1091,10 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G | `CI_BUILD_TOKEN` | `CI_JOB_TOKEN` | | `CI_BUILD_TRIGGERED` | `CI_PIPELINE_TRIGGERED` | -**Planned removal milestone: 16.0 (2023-04-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-04-22)** +</div> + +<div class="deprecation removal-150"> ### `fixup!` commit messages setting draft status of associated Merge Request @@ -885,7 +1106,10 @@ messages, as part of our streamlining of the feature. Support for `fixup!` is now considered deprecated, and will be removed in GitLab 15.0. -**Planned removal milestone: 15.0 (2022-06-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-06-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `projectFingerprint` in `PipelineSecurityReportFinding` GraphQL @@ -900,7 +1124,10 @@ GraphQL object is being deprecated. This field contains a "fingerprint" of secur 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `started` iterations API field @@ -912,10 +1139,16 @@ changes to your code, settings, or workflow. 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. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.7 +<div class="deprecation removal-150"> + ### Container scanning schemas below 14.0.0 [Container scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -929,7 +1162,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will displ [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Coverage guided fuzzing schemas below 14.0.0 @@ -947,7 +1183,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will displ [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### DAST schemas below 14.0.0 @@ -965,7 +1204,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will cause [warning to be displayed](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Dependency scanning schemas below 14.0.0 @@ -983,7 +1225,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will cause [warning to be displayed](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Enforced validation of security report schemas @@ -1001,7 +1246,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will displ [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Godep support in License Compliance @@ -1010,7 +1258,10 @@ has been replaced with Go modules. To reduce our maintenance cost we are deprecating License Compliance for Godep projects as of 14.7 and will remove it in GitLab 15.0 -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Logging in GitLab @@ -1022,7 +1273,10 @@ changes to your code, settings, or workflow. The logging features in GitLab allow users to install the ELK stack (Elasticsearch, Logstash, and Kibana) to aggregate and manage application logs. Users can search for relevant logs in GitLab. However, since deprecating certificate-based integration with Kubernetes clusters and GitLab Managed Apps, we don't have a recommended solution for logging within GitLab. For more information, you can follow the issue for [integrating Opstrace with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### Monitor performance metrics through Prometheus @@ -1035,7 +1289,10 @@ changes to your code, settings, or workflow. By displaying data stored in a Prometheus instance, GitLab allows users to view performance metrics. GitLab also displays visualizations of these metrics in dashboards. The user can connect to a previously-configured external Prometheus instance, or set up Prometheus as a GitLab Managed App. However, since certificate-based integration with Kubernetes clusters is deprecated in GitLab, the metrics functionality in GitLab that relies on Prometheus is also deprecated. This includes the metrics visualizations in dashboards. GitLab is working to develop a single user experience based on [Opstrace](https://about.gitlab.com/press/releases/2021-12-14-gitlab-acquires-opstrace-to-expand-its-devops-platform-with-open-source-observability-solution.html). An [issue exists](https://gitlab.com/groups/gitlab-org/-/epics/6976) for you to follow work on the Opstrace integration. -**Planned removal milestone: 16.0 (2023-05-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> + +<div class="deprecation removal-150"> ### Pseudonymizer @@ -1044,7 +1301,10 @@ can cause production issues with large databases, and can interfere with object storage development. It is now considered deprecated, and will be removed in GitLab 15.0. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### SAST schemas below 14.0.0 @@ -1062,7 +1322,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will displ [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Secret detection schemas below 14.0.0 @@ -1080,7 +1343,10 @@ To help with the transition, from GitLab 14.10, non-compliant reports will displ [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791) in the Vulnerability Report. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Sidekiq metrics and health checks configuration @@ -1110,13 +1376,21 @@ and only run one server (not changing the current behaviour). Only if they are both set and a different port is provided, a separate metrics server will spin up to serve the Sidekiq metrics, similar to the way Sidekiq will behave in 15.0. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### Static Site Editor -The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver smiliar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the Web IDE. Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/static_site_editor/) for more information, including how to remove the configuration files from existing projects. +The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver smiliar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the [Web IDE](https://docs.gitlab.com/ee/user/project/web_ide/index.html). + +Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/static_site_editor/) for more information, including how to remove the configuration files from existing projects. + +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> -**Planned removal milestone: 15.0 (2022-05-22)** +<div class="deprecation removal-150 breaking-change"> ### Tracing in GitLab @@ -1128,7 +1402,10 @@ changes to your code, settings, or workflow. Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distributed tracing system. GitLab users can navigate to their Jaeger instance to gain insight into the performance of a deployed application, tracking each function or microservice that handles a given request. Tracing in GitLab is deprecated in GitLab 14.7, and scheduled for removal in 15.0. To track work on a possible replacement, see the issue for [Opstrace integration with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150"> ### `artifacts:report:cobertura` keyword @@ -1137,7 +1414,10 @@ Currently, test coverage visualizations in GitLab only support Cobertura reports [`artifacts:reports:coverage_report`](https://gitlab.com/gitlab-org/gitlab/-/issues/344533). Cobertura will be the only supported report file in 15.0, but this is the first step towards GitLab supporting other report types. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### merged_by API field @@ -1149,23 +1429,15 @@ changes to your code, settings, or workflow. 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. -**Planned removal milestone: 15.0 (2022-05-22)** - -## 14.6 +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> +</div> -### API: `stale` status returned instead of `offline` or `not_connected` +<div class="announcement-milestone"> -WARNING: -This feature will be changed or removed in 15.0 -as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). -Before updating GitLab, review the details carefully to determine if you need to make any -changes to your code, settings, or workflow. - -A breaking change will occur for the Runner [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints in 15.0. - -Instead of the GitLab Runner API endpoints returning `offline` and `not_connected` for runners that have not contacted the GitLab instance in the past three months, the API endpoints will return the `stale` value, which was introduced in 14.6. +## 14.6 -**Planned removal milestone: 15.0 (2022-05-22)** +<div class="deprecation removal-150 breaking-change"> ### CI/CD job name length limit @@ -1177,7 +1449,10 @@ changes to your code, settings, or workflow. In GitLab 15.0 we are going to limit the number of characters in CI/CD job names to 255. Any pipeline with job names that exceed the 255 character limit will stop working after the 15.0 release. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Legacy approval status names from License Compliance API @@ -1191,36 +1466,10 @@ We deprecated legacy names for approval status of license policy (blacklisted, a If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release. -**Planned removal milestone: 15.0 (2022-05-22)** - -### Runner status `not_connected` API value - -WARNING: -This feature will be changed or removed in 15.0 -as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). -Before updating GitLab, review the details carefully to determine if you need to make any -changes to your code, settings, or workflow. - -The GitLab Runner REST and GraphQL [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints -will return `never_contacted` instead of `not_connected` as the status values in 15.0. +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> -Runners that have never contacted the GitLab instance will also return `stale` if created more than 3 months ago. - -**Planned removal milestone: 15.0 (2022-05-22)** - -### `pipelines` fields in the Package GraphQL types - -WARNING: -This feature will be changed or removed in 15.0 -as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). -Before updating GitLab, review the details carefully to determine if you need to make any -changes to your code, settings, or workflow. - -As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `pipelines` fields in all Package-related GraphQL types. As of GitLab 14.6, the `pipelines` field is deprecated in [`Package`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#package) and [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype) due to scalability and performance concerns. - -In milestone 15.0, we will completely remove `pipelines` from `Package` and `PackageDetailsType`. You can follow and contribute to work on a replacement in the epic [GitLab-#7214](https://gitlab.com/groups/gitlab-org/-/epics/7214). - -**Planned removal milestone: 15.0 (2022-05-22)** +<div class="deprecation removal-150 breaking-change"> ### `type` and `types` keyword in CI/CD configuration @@ -1232,7 +1481,10 @@ changes to your code, settings, or workflow. The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### apiFuzzingCiConfigurationCreate GraphQL mutation @@ -1246,7 +1498,10 @@ The API Fuzzing configuration snippet is now being generated client-side and doe API request anymore. We are therefore deprecating the `apiFuzzingCiConfigurationCreate` mutation which isn't being used in GitLab anymore. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### bundler-audit Dependency Scanning tool @@ -1260,48 +1515,34 @@ As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will c If you have explicitly excluded bundler-audit 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, for example to edit the `bundler-audit-dependency_scanning` job, you will want to switch to gemnasium-dependency_scanning before removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference bundler-audit, or customized your template specifically for bundler-audit, you will not need to take action. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.5 -### Certificate-based integration with Kubernetes +<div class="deprecation removal-150 breaking-change"> + +### Changing an instance (shared) runner to a project (specific) runner WARNING: -This feature will be changed or removed in 15.6 +This feature will be changed or removed in 15.0 as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). Before updating GitLab, review the details carefully to determine if you need to make any changes to your code, settings, or workflow. -[The certificate-based integration with Kubernetes will be deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). - -If you are a self-managed customer, in GitLab 15.0, a feature flag will be introduced so you can keep -certificate-based integration enabled. The flag will be disabled by default. -The flag and the related code will be removed in GitLab 15.6. - -Until the final removal in 15.6, features built on the integration will continue to work, and -GitLab will continue to fix security and critical issues. - -If you use GitLab.com, certificate-based integrations will cease functioning in 15.0. - -For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the -[agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. -See the documentation for [how to migrate](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html). - -For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). - -**Planned removal milestone: 15.6 (2022-11-22)** +In GitLab 15.0, you can no longer change an instance (shared) runner to a project (specific) runner. -### Converting an instance (shared) runner to a project (specific) runner +Users often accidentally change instance runners to project runners, and they're unable to change them back. GitLab does not allow you to change a project runner to a shared runner because of the security implications. A runner meant for one project could be set to run jobs for an entire instance. -WARNING: -This feature will be changed or removed in 15.0 -as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). -Before updating GitLab, review the details carefully to determine if you need to make any -changes to your code, settings, or workflow. +Administrators who need to add runners for multiple projects can register a runner for one project, then go to the Admin view and choose additional projects. -In GitLab 15.0, we will remove the feature that enables you to convert an instance (shared) runner to a project (specific) runner. Users who need to add a runner to only a particular project can register a runner to the project directly. +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> -**Planned removal milestone: 15.0 (2022-05-22)** +<div class="deprecation removal-150 breaking-change"> ### Known host required for GitLab Runner SSH executor @@ -1315,7 +1556,10 @@ In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/30 In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Must explicitly assign `AuthenticationType` for `[runners.cache.s3]` @@ -1329,21 +1573,27 @@ In GitLab 15.0 and later, to access the AWS S3 cache, you must specify the `Auth Prior to 14.5, if you did not define the `AuthenticationType`, GitLab Runner chose a type for you. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> ### Package pipelines in API payload is paginated WARNING: -This feature will be changed or removed in 15.0 +This feature will be changed or removed in 16.0 as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). Before updating GitLab, review the details carefully to determine if you need to make any changes to your code, settings, or workflow. A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines. -In milestone 15.0, we will remove the `pipelines` attribute from the API response. +In milestone 16.0, we will remove the `pipelines` attribute from the API response. + +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> -**Planned removal milestone: 15.0 (2022-05-22)** +<div class="deprecation removal-160 breaking-change"> ### REST and GraphQL API Runner status will not return `paused` @@ -1361,7 +1611,56 @@ A runner's status will only relate to runner contact status, such as: When checking if a runner is `paused`, API users are advised to check the boolean attribute `paused` to be `true` instead. When checking if a runner is `active`, check if `paused` is `false`. -**Planned removal milestone: 16.0 (2023-04-22)** +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-04-22)** +</div> + +<div class="deprecation removal-156 breaking-change"> + +### SaaS certificate-based integration with Kubernetes + +WARNING: +This feature will be changed or removed in 15.6 +as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). +Before updating GitLab, review the details carefully to determine if you need to make any +changes to your code, settings, or workflow. + +The certificate-based integration with Kubernetes will be [deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). As a GitLab SaaS customer, on new namespaces, you will no longer be able to integrate GitLab and your cluster using the certificate-based approach as of GitLab 15.0. The integration for current users will be enabled per namespace. The integrations are expected to be switched off completely on GitLab SaaS around 2022 November 22. + +For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the +[agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html) + +For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). + +GitLab self-managed customers can still use the feature [with a feature flag](https://docs.gitlab.com/ee/update/deprecations.html#self-managed-certificate-based-integration-with-kubernetes). + +**Planned removal milestone: <span class="removal-milestone">15.6</span> (2022-11-22)** +</div> + +<div class="deprecation removal-160 breaking-change"> + +### Self-managed certificate-based integration with Kubernetes + +WARNING: +This feature will be changed or removed in 16.0 +as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). +Before updating GitLab, review the details carefully to determine if you need to make any +changes to your code, settings, or workflow. + +The certificate-based integration with Kubernetes [will be deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). + +As a self-managed customer, we are introducing a feature flag in GitLab 15.0 so you can keep your certificate-based integration enabled. However, the feature flag will be disabled by default, so this change is a **breaking change**. + +In GitLab 16.0 we will remove both the feature and its related code. Until the final removal in 16.0, features built on this integration will continue to work, if you enable the feature flag. Until the feature is removed, GitLab will continue to fix security and critical issues as they arise. + +For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the +[agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html) + +For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). + +**Planned removal milestone: <span class="removal-milestone">16.0</span> (2023-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Support for SLES 12 SP2 @@ -1373,7 +1672,10 @@ changes to your code, settings, or workflow. Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Update to the Container Registry group-level API @@ -1387,7 +1689,10 @@ In milestone 15.0, support for the `tags` and `tags_count` parameters will be re The `GET /groups/:id/registry/repositories` endpoint will remain, but won't return any info about tags. To get the info about tags, you can use the existing `GET /registry/repositories/:id` endpoint, which will continue to support the `tags` and `tag_count` options as it does today. The latter must be called once per image repository. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Value Stream Analytics filtering calculation change @@ -1401,7 +1706,10 @@ We are changing how the date filter works in Value Stream Analytics. Instead of If you monitor Value Stream Analytics metrics and rely on the date filter, to avoid losing data, you must save the data prior to this change. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `Versions` on base `PackageType` @@ -1415,7 +1723,10 @@ As part of the work to create a [Package Registry GraphQL API](https://gitlab.co In milestone 15.0, we will completely remove `Version` from `PackageType`. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `defaultMergeCommitMessageWithDescription` GraphQL API field @@ -1427,7 +1738,10 @@ changes to your code, settings, or workflow. The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprecated and will be removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `dependency_proxy_for_private_groups` feature flag @@ -1441,7 +1755,10 @@ We added a feature flag because [GitLab-#11582](https://gitlab.com/gitlab-org/gi In milestone 15.0, we will remove the feature flag entirely. Moving forward, you must authenticate when using the Dependency Proxy. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `pipelines` field from the `version` field @@ -1458,7 +1775,10 @@ In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDeta To mitigate possible performance problems, we will remove the `versions` field's `pipelines` field in milestone 15.0. Although you will no longer be able to get all pipelines for all versions of a package, you can still get the pipelines of a single version through the remaining `pipelines` field for that version. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `promote-db` command from `gitlab-ctl` @@ -1470,7 +1790,10 @@ changes to your code, settings, or workflow. In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-db` which is used to promote database nodes in multi-node Geo secondary sites. `gitlab-ctl promote-db` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### `promote-to-primary-node` command from `gitlab-ctl` @@ -1482,7 +1805,10 @@ changes to your code, settings, or workflow. In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-to-primary-node` which was only usable for single-node Geo sites. `gitlab-ctl promote-to-primary-node` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-148"> ### openSUSE Leap 15.2 packages @@ -1490,10 +1816,16 @@ Distribution support and security updates for openSUSE Leap 15.2 are [ending Dec Starting in 14.5 we are providing packages for openSUSE Leap 15.3, and will stop providing packages for openSUSE Leap 15.2 in the 14.8 milestone. -**Planned removal milestone: 14.8 (2022-02-22)** +**Planned removal milestone: <span class="removal-milestone">14.8</span> (2022-02-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.3 +<div class="deprecation removal-150 breaking-change"> + ### Audit events for repository push events WARNING: @@ -1502,13 +1834,16 @@ as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#brea Before updating GitLab, review the details carefully to determine if you need to make any changes to your code, settings, or workflow. -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. +Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#removed-events) 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 dramatically slow down GitLab instances. For this reason, they are being removed. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### GitLab Serverless @@ -1522,7 +1857,10 @@ changes to your code, settings, or workflow. We decided to remove the GitLab Serverless features as they never really resonated with our users. Besides, given the continuous development of Kubernetes and Knative, our current implementations do not even work with recent versions. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### Legacy database configuration @@ -1538,7 +1876,10 @@ supported using a single PostgreSQL adapter, whereas the new format is changing This deprecation mainly impacts users compiling GitLab from source because Omnibus will handle this configuration automatically. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### OmniAuth Kerberos gem @@ -1554,15 +1895,24 @@ This gem has not been maintained and has very little usage. We therefore plan to Note that we are not deprecating the Kerberos SPNEGO integration, only the old password-based Kerberos integration. -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.2 +<div class="deprecation removal-146"> + ### Release CLI distributed as a generic package 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. -**Planned removal milestone: 14.6 (2021-12-22)** +**Planned removal milestone: <span class="removal-milestone">14.6</span> (2021-12-22)** +</div> + +<div class="deprecation removal-145"> ### Rename Task Runner pod to Toolbox @@ -1570,10 +1920,16 @@ The Task Runner pod is used to execute periodic housekeeping tasks within the Gi This will result in the rename of the sub-chart: `gitlab/task-runner` to `gitlab/toolbox`. Resulting pods will be named along the lines of `{{ .Release.Name }}-toolbox`, which will often be `gitlab-toolbox`. They will be locatable with the label `app=toolbox`. -**Planned removal milestone: 14.5 (2021-11-22)** +**Planned removal milestone: <span class="removal-milestone">14.5</span> (2021-11-22)** +</div> +</div> + +<div class="announcement-milestone"> ## 14.0 +<div class="deprecation removal-156"> + ### NFS for Git repository storage With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information. @@ -1586,7 +1942,10 @@ Gitaly Cluster offers tremendous benefits for our customers such as: 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/index.html#migrate-to-gitaly-cluster). -**Planned removal milestone: 15.6 (2022-11-22)** +**Planned removal milestone: <span class="removal-milestone">15.6</span> (2022-11-22)** +</div> + +<div class="deprecation removal-150 breaking-change"> ### OAuth implicit grant @@ -1598,4 +1957,6 @@ changes to your code, settings, or workflow. 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). -**Planned removal milestone: 15.0 (2022-05-22)** +**Planned removal milestone: <span class="removal-milestone">15.0</span> (2022-05-22)** +</div> +</div> |