diff --git a/.gitlab/ci/docs.gitlab-ci.yml b/.gitlab/ci/docs.gitlab-ci.yml index 6c426749af38fa9792623dc29b6ff7049704c27c..1ad030a377140700aa29f5b31c74808fbeb2789a 100644 --- a/.gitlab/ci/docs.gitlab-ci.yml +++ b/.gitlab/ci/docs.gitlab-ci.yml @@ -11,7 +11,7 @@ # See https://gitlab.com/gitlab-org/gitlab/issues/191273 GIT_DEPTH: 1 # By default, deploy the Review App using the `main` branch of the `gitlab-org/gitlab-docs` project - DOCS_BRANCH: main + DOCS_BRANCH: connorgilbert/deprecationsjs-on-removals environment: name: review-docs/mr-${CI_MERGE_REQUEST_IID} # DOCS_REVIEW_APPS_DOMAIN and DOCS_GITLAB_REPO_SUFFIX are CI variables diff --git a/data/removals/templates/_removal_template.md.erb b/data/removals/templates/_removal_template.md.erb index aa2ae993f45861074a448f60b2b497fe75985de0..086b31a6ce6fb3a13f69c9a7ba2257df2b25dc29 100644 --- a/data/removals/templates/_removal_template.md.erb +++ b/data/removals/templates/_removal_template.md.erb @@ -2,6 +2,7 @@ stage: none group: none info: "See the Technical Writers assigned to Development Guidelines: https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines" +toc: false --- # Removals by version @@ -35,10 +36,14 @@ For removal reviewers (Technical Writers only): --> {::options parse_block_html="true" /} -<% if milestones.any? -%> - <%- milestones.each do |milestone| %> +<% if milestones.any? -%>
+<%- milestones.each do |milestone| %> +
+ ## Removed in <%= milestone %> - <%- entries.select{|entry| entry["removal_milestone"] == milestone}.each do |removal| %> + <%- entries.select{|entry| entry["removal_milestone"] == milestone}.each do |removal| %> +
breaking-change<% end %>" data-milestone="<%= milestone %>"> + ### <%= removal["title"]%>
@@ -51,7 +56,12 @@ For removal reviewers (Technical Writers only): <%- end -%>
-<%= removal["body"] -%><%- end -%><%- end -%> +<%= removal["body"] -%> + +
+ <%- end -%> +
+<%- end -%> <%- else -%> Features scheduled for removal will be listed here, sorted by GitLab version. <% end -%> diff --git a/doc/update/removals.md b/doc/update/removals.md index 4f60674a0a276dd24bb713d0fbb8f66849d1fc55..ac0fb63c01b921b2ecd1ee63fbb0f5ec6daaf04f 100644 --- a/doc/update/removals.md +++ b/doc/update/removals.md @@ -2,6 +2,7 @@ stage: none group: none info: "See the Technical Writers assigned to Development Guidelines: https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines" +toc: false --- # Removals by version @@ -35,9 +36,14 @@ For removal reviewers (Technical Writers only): --> {::options parse_block_html="true" /} +
+ +
## Removed in 16.0 +
+ ### Auto DevOps no longer provisions a database by default
@@ -53,6 +59,10 @@ change supports production deployments that require more robust database managem If you want Auto DevOps to provision an in-cluster database, set the `POSTGRES_ENABLED` CI/CD variable to `true`. +
+ +
+ ### Azure Storage Driver defaults to the correct root prefix
@@ -65,6 +75,10 @@ The Azure Storage Driver used to write to `//` as the default root directory. Th In GitLab 16.0, the new default configuration for the storage driver uses `trimlegacyrootprefix: true`, and `/` is the default root directory. You can set your configuration to `trimlegacyrootprefix: false` if needed, to revert to the previous behavior. +
+ +
+ ### Bundled Grafana Helm Chart
@@ -83,6 +97,10 @@ or a Grafana Operator from a trusted provider. In your new Grafana instance, [configure the GitLab provided Prometheus as a data source](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#configure-grafana) and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integrate-with-gitlab-ui). +
+ +
+ ### CAS OmniAuth provider is removed
@@ -93,6 +111,10 @@ and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration The `omniauth-cas3` gem that provides GitLab with the CAS OmniAuth provider is being removed. You can no longer authenticate into a GitLab instance through CAS. This gem sees very little use. [The gem](https://rubygems.org/gems/omniauth-cas3/) has not had a new release in almost 5 years, which means that its dependencies are out of date and required manual patching during GitLab's [upgrade to OmniAuth 2.0](https://gitlab.com/gitlab-org/gitlab/-/issues/30073). +
+ +
+ ### CiCdSettingsUpdate mutation renamed to ProjectCiCdSettingsUpdate
@@ -106,6 +128,10 @@ 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. +
+ +
+ ### Conan project-level search returns only project-specific results"
@@ -116,6 +142,10 @@ instead. The [GitLab Conan repository](https://docs.gitlab.com/ee/user/packages/conan_repository/) supports the `conan search` command, but when searching a project-level endpoint, instance-level Conan packages could have been returned. This unintended functionality is removed in GitLab 16.0. The search endpoint for the project level now only returns packages from the target project. +
+ +
+ ### Configuring Redis config file paths using environment variables is no longer supported
@@ -130,6 +160,10 @@ using the environment variables like `GITLAB_REDIS_CACHE_CONFIG_FILE` or configuration file locations instead, for example `config/redis.cache.yml` or `config/redis.queues.yml`. +
+ +
+ ### Container Registry pull-through cache is removed
@@ -140,6 +174,10 @@ configuration file locations instead, for example `config/redis.cache.yml` or The Container Registry [pull-through cache](https://docs.docker.com/registry/recipes/mirror/) was deprecated in GitLab 15.8 and removed in GitLab 16.0. This feature is part of the upstream [Docker Distribution project](https://github.com/distribution/distribution) but we are removing that code in favor of the GitLab Dependency Proxy. Use the GitLab Dependency Proxy to proxy and cache container images from Docker Hub. +
+ +
+ ### Container Scanning variables that reference Docker removed
@@ -162,6 +200,10 @@ Instead, use the [new variable names](https://docs.gitlab.com/ee/user/applicatio - `CS_REGISTRY_USER` - `CS_DOCKERFILE_PATH` +
+ +
+ ### Default value of `ttl_days` now 30 days
@@ -172,6 +214,10 @@ Instead, use the [new variable names](https://docs.gitlab.com/ee/user/applicatio From GitLab 16.0, any personal, project, or group access token [must have an expiration date](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96594). If you create a personal access token with the GitLab Shell command `personal_access_token` without specifying `ttl_days`, a default value of 30 days is now applied. +
+ +
+ ### Dependency Scanning ends support for Java 13, 14, 15, and 16
@@ -182,6 +228,10 @@ From GitLab 16.0, any personal, project, or group access token [must have an exp Dependency Scanning no longer supports projects that use Java versions 13, 14, 15, and 16. +
+ +
+ ### Developer role providing the ability to import projects to a group
@@ -195,6 +245,10 @@ The ability for users with the Developer role for a group to import projects to From GitLab 16.0, only users with at least the Maintainer role for a group can import projects to that group. +
+ +
+ ### Embedding Grafana panels in Markdown is removed
@@ -207,6 +261,10 @@ The ability to add Grafana panels in GitLab Flavored Markdown is removed. We intend to replace this feature with the ability to [embed charts](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/33) with the [GitLab Observability UI](https://gitlab.com/gitlab-org/opstrace/opstrace-ui). +
+ +
+ ### Enforced validation of CI/CD parameter character lengths
@@ -225,6 +283,10 @@ The following to 255 characters are now strictly limited to 255 characters: Users on self-managed instances should update their pipelines to ensure they do not use parameters that exceed 255 characters. Users on GitLab.com do not need to make any changes, as these parameters are already limited in that database. +
+ +
+ ### GitLab administrators must have permission to modify protected branches or tags
@@ -235,6 +297,10 @@ Users on self-managed instances should update their pipelines to ensure they do GitLab administrators can no longer perform actions on protected branches or tags unless they have been explicitly granted that permission. These actions include pushing and merging into a [protected branch](https://docs.gitlab.com/ee/user/project/protected_branches.html), unprotecting a branch, and creating [protected tags](https://docs.gitlab.com/ee/user/project/protected_tags.html). +
+ +
+ ### GitLab.com importer
@@ -251,6 +317,10 @@ supersedes the GitLab.com importer and provides a more cohesive importing functi See [migrated group items](https://docs.gitlab.com/ee/user/group/import/#migrated-group-items) and [migrated project items](https://docs.gitlab.com/ee/user/group/import/#migrated-project-items) for an overview. +
+ +
+ ### GraphQL API: Runner status no longer returns `PAUSED` and `ACTIVE` values
@@ -264,6 +334,10 @@ In GitLab 16.0 and later, the GraphQL query for runners will no longer return th - `PAUSED` has been replaced with the field, `paused: true`. - `ACTIVE` has been replaced with the field, `paused: false`. +
+ +
+ ### Jira DVCS connector for Jira Cloud and Jira 8.13 and earlier
@@ -275,6 +349,10 @@ In GitLab 16.0 and later, the GraphQL query for runners will no longer return th The [Jira DVCS connector](https://docs.gitlab.com/ee/integration/jira/dvcs/) for Jira Cloud was deprecated in GitLab 15.1 and has been removed in 16.0. Use the [GitLab for Jira Cloud app](https://docs.gitlab.com/ee/integration/jira/connect-app.html) instead. The Jira DVCS connector was also deprecated for Jira 8.13 and earlier. You can only use the Jira DVCS connector with Jira Data Center or Jira Server in Jira 8.14 and later. Upgrade your Jira instance to Jira 8.14 or later, and reconfigure the Jira integration in your GitLab instance. If you cannot upgrade your Jira instance in time and are on GitLab self-managed version, we offer a workaround until GitLab 16.6. This breaking change is deployed in GitLab 16.0 behind a feature flag named `jira_dvcs_end_of_life_amnesty`. The flag is disabled by default, but you can ask an administrator to enable the flag at any time. For questions related to this announcement, see the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/408185). +
+ +
+ ### Legacy Gitaly configuration method
@@ -293,6 +371,10 @@ method. Before upgrading to GitLab 16.0, administrators must migrate to the new single configuration structure. For instructions, see [Gitaly - Omnibus GitLab configuration structure change](https://docs.gitlab.com/ee/update/#gitaly-omnibus-gitlab-configuration-structure-change). +
+ +
+ ### Legacy Gitaly configuration methods with variables
@@ -308,6 +390,10 @@ in GitLab 16.0. These variables are replaced with standard GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configure Gitaly must switch to configuring using `config.toml`. +
+ +
+ ### Legacy Praefect configuration method
@@ -326,6 +412,10 @@ method. Before upgrading to GitLab 16.0, administrators must migrate to the new single configuration structure. For instructions, see [Praefect - Omnibus GitLab configuration structure change](https://docs.gitlab.com/ee/update/#praefect-omnibus-gitlab-configuration-structure-change). +
+ +
+ ### Legacy routes removed
@@ -342,6 +432,10 @@ URLs that do not use the `/-/` delimiter are planned for removal in GitLab 16.0. Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are not affected by this change. +
+ +
+ ### License-Check and the Policies tab on the License Compliance page
@@ -352,6 +446,10 @@ Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are The License Check Policies feature has been removed. Additionally, the Policies tab on the License Compliance page and all APIs related to the License Check feature have been removed. To enforce approvals based on detected licenses, use the [License Approval policy](https://docs.gitlab.com/ee/user/compliance/license_approval_policies.html) feature instead. +
+ +
+ ### Limit CI_JOB_TOKEN scope is disabled
@@ -370,6 +468,10 @@ In 17.0, we plan to remove the **Limit** setting completely, and set the **Allow To prepare for this change, users on GitLab.com or self-managed GitLab 15.9 or later can enable the **Allow access** setting now and add the other projects. It will not be possible to disable the setting in 17.0 or later. +
+ +
+ ### Managed Licenses API
@@ -384,6 +486,10 @@ Our [GraphQL APIs](https://docs.gitlab.com/ee/api/graphql/reference/) can be use To query a list of dependencies and components, use our [Dependencies REST API](https://docs.gitlab.com/ee/api/dependencies.html) or [export from the Dependency List](https://docs.gitlab.com/ee/user/application_security/dependency_list/). +
+ +
+ ### Maximum number of active pipelines per project limit (`ci_active_pipelines`)
@@ -396,6 +502,10 @@ The [**Maximum number of active pipelines per project** limit](https://docs.gitl - [**Pipelines rate limits**](https://docs.gitlab.com/ee/user/admin_area/settings/rate_limit_on_pipelines_creation.html). - [**Total number of jobs in currently active pipelines**](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#set-cicd-limits). +
+ +
+ ### Monitoring performance metrics through Prometheus is removed
@@ -419,6 +529,10 @@ This removal only refers to the GitLab Metrics capabilities, and **does not** in - Deprecating [alerts for Prometheus](https://gitlab.com/gitlab-org/gitlab/-/issues/338834). - [Capabilities that GitLab comes with that allow operators of GitLab to retrieve metrics from those instances](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_metrics.html). +
+ +
+ ### Non-expiring access tokens no longer supported
@@ -432,6 +546,10 @@ divulged. Because expiring access tokens are better, from GitLab 15.4 we [popula In GitLab 16.0, any personal, project, or group access token that does not have an expiration date will automatically have an expiration date set at 365 days later than the current date. +
+ +
+ ### Non-standard default Redis ports are no longer supported
@@ -449,6 +567,10 @@ If you want to keep using the three servers, you must configure the Redis URLs by editing the `config/redis.cache.yml`,`config/redis.queues.yml`, and `config/redis.shared_state.yml` files. +
+ +
+ ### PipelineSecurityReportFinding name GraphQL field
@@ -459,6 +581,10 @@ and `config/redis.shared_state.yml` files. Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https://gitlab.com/gitlab-org/gitlab/-/issues/335372) to include a new `title` field. This field is an alias for the current `name` field, making the less specific `name` field redundant. The `name` field is removed from the PipelineSecurityReportFinding type in GitLab 16.0. +
+ +
+ ### PostgreSQL 12 compatibility
@@ -475,6 +601,10 @@ Before upgrading to GitLab 16.0, if you are: - Using an externally-provided PostgreSQL 12, you must upgrade to PostgreSQL 13 or later to meet the [minimum version requirements](https://docs.gitlab.com/ee/install/requirements.html#postgresql-requirements). +
+ +
+ ### Praefect custom metrics endpoint configuration
@@ -489,6 +619,10 @@ All metrics that scrape the Praefect database are now exported to the `/db_metri You must update your metrics collection targets to use the `/db_metrics` endpoint. +
+ +
+ ### Project REST API field `operations_access_level` removed
@@ -506,6 +640,10 @@ is removed in favor of more specialized fields like: - `infrastructure_access_level` - `monitor_access_level` +
+ +
+ ### Rake task for importing bare repositories
@@ -531,6 +669,10 @@ Alternatives to using the `gitlab:import:repos` Rake task include: - Importing a [repository by URL](https://docs.gitlab.com/ee/user/project/import/repo_by_url.html). - Importing a [repositories from a non-GitLab source](https://docs.gitlab.com/ee/user/project/import/). +
+ +
+ ### Redis 5 compatibility
@@ -544,6 +686,10 @@ In GitLab 13.9, we updated the Omnibus GitLab package and GitLab Helm chart 4.9 GitLab 16.0, we have removed support for Redis 5. If you are using your own Redis 5.0 instance, you must upgrade it to Redis 6.0 or later before upgrading to GitLab 16.0 or later. +
+ +
+ ### Removal of job_age parameter in `POST /jobs/request` Runner endpoint
@@ -556,6 +702,10 @@ The `job_age` parameter, returned from the `POST /jobs/request` API endpoint use This could be a breaking change for anyone that developed their own runner that relies on this parameter being returned by the endpoint. This is not a breaking change for anyone using an officially released version of GitLab Runner, including public shared runners on GitLab.com. +
+ +
+ ### Remove legacy configuration fields in GitLab Runner Helm Chart
@@ -595,6 +745,10 @@ In GitLab 13.6 and later, users can [specify any runner configuration in the Git - `runners.podAnnotations` - `runners.env` +
+ +
+ ### Remove the deprecated `environment_tier` parameter from the DORA API
@@ -607,6 +761,10 @@ The `environment_tier` parameter has been superseded by the `environment_tiers` If you use the `environment_tier` parameter in your integration (REST or GraphQL) then you need to replace it with the `environment_tiers` parameter which accepts an array of strings. +
+ +
+ ### Removed `external` field from GraphQL `ReleaseAssetLink` type
@@ -617,6 +775,10 @@ If you use the `environment_tier` parameter in your integration (REST or GraphQL From GitLab 15.9, all Release links are external. The `external` field of the `ReleaseAssetLink` type was deprecated in 15.9, and removed in GitLab 16.0. +
+ +
+ ### Removed `external` field from Releases and Release link APIs
@@ -627,6 +789,10 @@ From GitLab 15.9, all Release links are external. The `external` field of the `R From GitLab 15.9, all Release links are external. The `external` field in the Releases and Release link APIs was deprecated in 15.9, and removed in GitLab 16.0. +
+ +
+ ### Secure JWT token setting is removed
@@ -639,6 +805,10 @@ As part of [the deprecation of old versions of JSON web tokens](https://docs.git The old `CI_JOB_JWT*` tokens will be completely removed in GitLab 16.5, so you must switch to ID tokens before that release. +
+ +
+ ### Secure scanning `_DISABLED` variables now require the value `"true"`
@@ -667,6 +837,10 @@ The following templates have been updated: If you currently use the `_DISABLED` variables but set a value other than `"true"` to disable scanning, change the value to `"true"`. +
+ +
+ ### Security report schemas version 14.x.x
@@ -678,6 +852,10 @@ If you currently use the `_DISABLED` variables but set a value other than `"true Version 14.x.x [security report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas) have been removed. Security reports that use schema version 14.x.x will cause an error in the pipeline's **Security** tab. For more information, refer to [security report validation](https://docs.gitlab.com/ee/user/application_security/#security-report-validation). +
+ +
+ ### Self-monitoring project is removed
@@ -688,6 +866,10 @@ Security reports that use schema version 14.x.x will cause an error in the pipel GitLab self-monitoring project was meant to enable self-hosted GitLab administrators to visualize performance metrics of GitLab within GitLab itself. This feature relied on GitLab Metrics dashboards. With metrics dashboard being removed, self-monitoring project is also removed. We recommended that self-hosted users monitor their GitLab instance with alternative visualization tools, such as Grafana. +
+ +
+ ### Starboard directive in the config for the GitLab agent for Kubernetes removed
@@ -698,6 +880,10 @@ GitLab self-monitoring project was meant to enable self-hosted GitLab administra The GitLab operational container scanning feature no longer requires you to install Starboard. The `starboard:` directive in configuration files for the GitLab agent for Kubernetes has been removed. Use the `container_scanning:` directive instead. +
+ +
+ ### Stop publishing GitLab Runner images based on Windows Server 2004 and 20H2
@@ -707,6 +893,10 @@ The GitLab operational container scanning feature no longer requires you to inst As of GitLab 16.0, GitLab Runner images based on Windows Server 2004 and 20H2 will not be provided as these operating systems are end-of-life. +
+ +
+ ### The Phabricator task importer
@@ -721,6 +911,10 @@ GitLab 15.7 and is removed in 16.0. The Phabricator project hasn't been actively maintained since June 1, 2021. We haven't observed imports using this tool. There has been no activity on the open related issues on GitLab. +
+ +
+ ### The Security Code Scan-based GitLab SAST analyzer is now removed
@@ -743,6 +937,10 @@ If you've already dismissed a vulnerability finding from the deprecated analyzer If you customize the behavior of GitLab SAST by disabling the Semgrep-based analyzer or depending on specific SAST jobs in your pipelines, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/390416#actions-required). +
+ +
+ ### The stable Terraform CI/CD template has been replaced with the latest template
@@ -765,6 +963,10 @@ However, we may introduce them later on, which may break your Terraform pipeline To accommodate the changes, you might need to adjust the [`rules`](https://docs.gitlab.com/ee/ci/yaml/#rules) in your `.gitlab-ci.yml` file. +
+ +
+ ### Two DAST API variables have been removed
@@ -779,6 +981,10 @@ The variables `DAST_API_HOST_OVERRIDE` and `DAST_API_SPECIFICATION` have been re `DAST_API_SPECIFICATION` has been removed in favor of `DAST_API_OPENAPI`. To continue using an OpenAPI specification to guide the test, users must replace the `DAST_API_SPECIFICATION` variable with the `DAST_API_OPENAPI` variable. The value can remain the same, but the variable name must be replaced. +
+ +
+ ### Use of `id` field in vulnerabilityFindingDismiss mutation
@@ -789,6 +995,10 @@ The variables `DAST_API_HOST_OVERRIDE` and `DAST_API_SPECIFICATION` have been re You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status of a vulnerability finding to `Dismissed`. Previously, this mutation used the `id` field to identify findings uniquely. However, this did not work for dismissing findings from the pipeline security tab. Therefore, using the `id` field as an identifier has been dropped in favor of the `uuid` field. Using the 'uuid' field as an identifier allows you to dismiss the finding from the pipeline security tab. +
+ +
+ ### Vulnerability confidence field
@@ -801,6 +1011,10 @@ In GitLab 15.3, [security report schemas below version 15 were deprecated](https The `confidence` attribute on vulnerability findings exists only in schema versions before `15-0-0` and in GitLab prior to 15.4. To maintain consistency between the reports and our public APIs, the `confidence` attribute on any vulnerability-related components of our GraphQL API is now removed. +
+ +
+ ### `CI_BUILD_*` predefined variables removed
@@ -826,6 +1040,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` | +
+ +
+ ### `CI_PRE_CLONE_SCRIPT` variable on GitLab SaaS Runners has been removed
@@ -836,6 +1054,10 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G In GitLab 16.0 and later, the `CI_PRE_CLONE_SCRIPT` variable option on GitLab SaaS Runners has been removed. The `CI_PRE_CLONE_SCRIPT` variable enabled you to run commands in your CI/CD job before the runner executed `git-init` and `git-fetch`. You should use the `pre_get_sources_script` hook instead. For more information, see the blog post, [Guide to pre_clone_script changes on GitLab SaaS Linux Runners](https://about.gitlab.com/blog/2023/03/27/changes-to-the-preclonescript/). +
+ +
+ ### `POST /projects/:id/merge_requests/:merge_request_iid/approvals` removed
@@ -846,6 +1068,10 @@ In GitLab 16.0 and later, the `CI_PRE_CLONE_SCRIPT` variable option on GitLab Sa The `/approvals` endpoint was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/11132) in GitLab 12.3. To change the approvals required for a merge request via the API, use the `/approval_rules` endpoint described in [Create merge request level rule](https://docs.gitlab.com/ee/api/merge_request_approvals.html#create-merge-request-level-rule). +
+ +
+ ### `POST ci/lint` API endpoint removed
@@ -856,6 +1082,10 @@ The `/approvals` endpoint was [deprecated](https://gitlab.com/gitlab-org/gitlab/ The `POST ci/lint` API endpoint was deprecated in 15.7, and removed in 16.0. This endpoint did not validate the full range of CI/CD configuration options. Instead, use [`POST /projects/:id/ci/lint`](https://docs.gitlab.com/ee/api/lint.html#validate-a-ci-yaml-configuration-with-a-namespace), which properly validates CI/CD configuration. +
+ +
+ ### `docker-ssh` and `docker-ssh+machine` executors are removed
@@ -865,6 +1095,10 @@ The `POST ci/lint` API endpoint was deprecated in 15.7, and removed in 16.0. Thi In GitLab 16.0 and later, the `docker-ssh` and `docker+machine-ssh` executors for GitLab Runner have been removed from the GitLab Runner [code base](https://gitlab.com/gitlab-org/gitlab-runner). +
+ +
+ ### vulnerabilityFindingDismiss GraphQL mutation
@@ -875,8 +1109,15 @@ In GitLab 16.0 and later, the `docker-ssh` and `docker+machine-ssh` executors fo The `VulnerabilityFindingDismiss` GraphQL mutation has been removed. This mutation was not used often as the Vulnerability Finding ID was not available to users (this field was [deprecated in 15.3](https://docs.gitlab.com/ee/update/deprecations.html#use-of-id-field-in-vulnerabilityfindingdismiss-mutation)). Instead of `VulnerabilityFindingDismiss`, you should use `VulnerabilityDismiss` to dismiss vulnerabilities in the Vulnerability Report or `SecurityFindingDismiss` for security findings in the CI Pipeline Security tab. +
+
+ +
+ ## Removed in 15.11 +
+ ### Exporting and importing projects in JSON format not supported
@@ -891,6 +1132,10 @@ relevant feature flags. From GitLab 15.11, importing a JSON-formatted project file exports is not supported. +
+ +
+ ### openSUSE Leap 15.3 packages
@@ -904,8 +1149,15 @@ Starting in GitLab 15.7 we started providing packages for openSUSE Leap 15.4, an To continue using GitLab, [upgrade](https://en.opensuse.org/SDB:System_upgrade) to openSUSE Leap 15.4. +
+
+ +
+ ## Removed in 15.9 +
+ ### Live Preview no longer available in the Web IDE
@@ -916,6 +1168,10 @@ To continue using GitLab, [upgrade](https://en.opensuse.org/SDB:System_upgrade) The Live Preview feature of the Web IDE was intended to provide a client-side preview of static web applications. However, complex configuration steps and a narrow set of supported project types have limited its utility. With the introduction of the Web IDE Beta in GitLab 15.7, you can now connect to a full server-side runtime environment. With upcoming support for installing extensions in the Web IDE, we’ll also support more advanced workflows than those available with Live Preview. As of GitLab 15.9, Live Preview is no longer available in the Web IDE. +
+ +
+ ### `omniauth-authentiq` gem no longer available
@@ -926,6 +1182,10 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr `omniauth-authentiq` is an OmniAuth strategy gem that was part of GitLab. The company providing authentication services, Authentiq, has shut down. Therefore the gem is being removed. +
+ +
+ ### `omniauth-shibboleth` gem no longer available
@@ -936,8 +1196,15 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr `omniauth-shibboleth` is an OmniAuth strategy gem that was part of GitLab. The gem has not received security updates and does not meet GitLab quality guidance criteria. This gem was originally scheduled for removal by 14.1, but it was not removed at that time. The gem is being removed now. +
+
+ +
+ ## Removed in 15.8 +
+ ### CiliumNetworkPolicy within the auto deploy Helm chart is removed
@@ -952,6 +1219,10 @@ If you want to preserve this functionality, you can follow one of these two path 1. Fork the [GitLab Auto Deploy Helm chart](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image/-/tree/master/assets/auto-deploy-app) into the `chart/` path within your project 1. Set `AUTO_DEPLOY_IMAGE_VERSION` and `DAST_AUTO_DEPLOY_IMAGE_VERSION` to the most recent version of the image that included the CiliumNetworkPolicy +
+ +
+ ### Exporting and importing groups in JSON format not supported
@@ -966,6 +1237,10 @@ relevant feature flags. From GitLab 15.8, importing a JSON-formatted group file exports is not supported. +
+ +
+ ### `artifacts:public` CI/CD keyword refactored
@@ -980,8 +1255,15 @@ If you have projects that use this setting, you should delete artifacts that mus In GitLab 15.10, this feature's code was refactored. On instances with this feature enabled, new artifacts created with `public:false` are now working as expected, though still disabled by default. Avoid testing this feature with production data until it is enabled by default and made generally available. +
+
+ +
+ ## Removed in 15.7 +
+ ### File Type variable expansion in `.gitlab-ci.yml`
@@ -994,6 +1276,10 @@ Prior to this change, variables that referenced or applied alias file variables In 15.7, we are removing file type variable expansion from GitLab. It is essential to check your CI pipelines to confirm if your scripts reference a file variable. If your CI job relies on the previous expansion functionality, that CI job will not work and generate an error as of 15.7. The new behavior is that variable expansion that reference or apply alias file variables expand to the file name or path of the `File` type variable, instead of its value, such as the file contents. +
+ +
+ ### Flowdock integration
@@ -1003,8 +1289,15 @@ In 15.7, we are removing file type variable expansion from GitLab. It is essenti As of December 22, 2022, we are removing the Flowdock integration because the service was shut down on August 15, 2022. +
+
+ +
+ ## Removed in 15.6 +
+ ### NFS as Git repository storage is no longer supported
@@ -1028,8 +1321,15 @@ Gitaly Cluster offers tremendous benefits for our customers such as: We encourage customers currently using NFS for Git repositories to migrate as soon as possible by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/index.html#migrate-to-gitaly-cluster). +
+
+ +
+ ## Removed in 15.4 +
+ ### SAST analyzer consolidation and CI/CD template changes
@@ -1054,8 +1354,15 @@ We won't delete container images previously published for these analyzers, so ol If you changed the default GitLab SAST configuration, you may need to update your configuration as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352554#actions-required). +
+
+ +
+ ## Removed in 15.3 +
+ ### Support for Debian 9
@@ -1064,6 +1371,10 @@ If you changed the default GitLab SAST configuration, you may need to update you Long term service and support (LTSS) for [Debian 9 Stretch ended 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. +
+ +
+ ### Vulnerability Report sort by State
@@ -1075,6 +1386,10 @@ The ability to sort the Vulnerability Report by the `State` column was disabled 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 is instead removed in 15.3 to simplify the codebase and prevent any unwanted performance degradation. +
+ +
+ ### Vulnerability Report sort by Tool
@@ -1087,8 +1402,15 @@ of the underlying data model. The feature flag has remained off by default as fu by this value remains performant. Due to very low usage of the `Tool` column for sorting, the feature flag is instead removed in GitLab 15.3 to simplify the codebase and prevent any unwanted performance degradation. +
+
+ +
+ ## Removed in 15.2 +
+ ### Support for older browsers
@@ -1110,8 +1432,15 @@ The minimum supported browser versions are: - Chromium 92. - Microsoft Edge 92. +
+
+ +
+ ## Removed in 15.0 +
+ ### API: `stale` status returned instead of `offline` or `not_connected`
@@ -1127,6 +1456,10 @@ The `stale` status was introduced in 14.6. The `not_connected` status is no longer valid. It was replaced with `never_contacted`. Available statuses are `online`, `offline`, `stale`, and `never_contacted`. +
+ +
+ ### Audit events for repository push events
@@ -1142,6 +1475,10 @@ Enabling them could slow down GitLab instances by generating too many events. Th Please note that we will add high-volume audit events in the future as part of [streaming audit events](https://docs.gitlab.com/ee/administration/audit_event_streaming.html). An example of this is how we will send [Git fetch actions](https://gitlab.com/gitlab-org/gitlab/-/issues/343984) as a streaming audit event. If you would be interested in seeing repository push events or some other action as a streaming audit event, please reach out to us! +
+ +
+ ### Background upload for object storage
@@ -1190,6 +1527,10 @@ If you have set a prefix, you can use a workaround to revert to background uploa Support for prefixes was restored in GitLab 15.2 via [this MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/91307). Support for setting `GITLAB_LEGACY_BACKGROUND_UPLOADS` will be removed in GitLab 15.4. +
+ +
+ ### Container Network and Host Security
@@ -1209,6 +1550,10 @@ As part of this change, the following capabilities within GitLab are scheduled f For additional context, or to provide feedback regarding this change, please reference our [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/7476). +
+ +
+ ### Container registry authentication with htpasswd
@@ -1220,7 +1565,11 @@ 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. -### Custom `geo:db:*` Rake tasks are no longer available +
+ +
+ +### Custom `geo:db:*` Rake tasks are no longer available
- Announced in: GitLab 14.8 @@ -1248,6 +1597,10 @@ The following `geo:db:*` tasks have been removed from GitLab 15.0 and have been - `geo:db:test:load` -> `db:test:load:geo` - `geo:db:test:purge` -> `db:test:purge:geo` +
+ +
+ ### DS_DEFAULT_ANALYZERS environment variable
@@ -1258,6 +1611,10 @@ The following `geo:db:*` tasks have been removed from GitLab 15.0 and have been We are removing the `DS_DEFAULT_ANALYZERS` environment variable from Dependency Scanning on May 22, 2022 in 15.0. After this removal, this variable's value will be ignored. To configure which analyzers to run with the default configuration, you should use the `DS_EXCLUDED_ANALYZERS` variable instead. +
+ +
+ ### Dependency Scanning default Java version changed to 17
@@ -1267,6 +1624,10 @@ We are removing the `DS_DEFAULT_ANALYZERS` environment variable from Dependency 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). Please note that consequently the default version of Gradle is now 7.3.3. +
+ +
+ ### ELK stack logging
@@ -1277,6 +1638,10 @@ For Dependency Scanning, the default version of Java that the scanner expects wi The logging features in GitLab allow users to install the ELK stack (Elasticsearch, Logstash, and Kibana) to aggregate and manage application logs. Users could search for relevant logs in GitLab directly. However, since deprecating certificate-based integration with Kubernetes clusters and GitLab Managed Apps, this feature is no longer available. For more information on the future of logging and observability, you can follow the issue for [integrating Opstrace with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976). +
+ +
+ ### Elasticsearch 6.8.x in GitLab 15.0
@@ -1291,6 +1656,10 @@ You should not upgrade to Elasticsearch 8 until you have completed the GitLab 15 View the [version requirements](https://docs.gitlab.com/ee/integration/advanced_search/elasticsearch.html#version-requirements) for details. +
+ +
+ ### End of support for Python 3.6 in Dependency Scanning
@@ -1301,6 +1670,10 @@ View the [version requirements](https://docs.gitlab.com/ee/integration/advanced_ For those using Dependency Scanning for Python projects, we are removing support for 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). +
+ +
+ ### External status check API breaking changes
@@ -1325,6 +1698,10 @@ and set to `passed`. Requests that: To align with this change, API calls to list external status checks also return the value of `passed` rather than `approved` for status checks that have passed. +
+ +
+ ### GitLab Serverless
@@ -1340,6 +1717,10 @@ All functionality related to GitLab Serverless was deprecated in GitLab 14.3 and For additional context, or to provide feedback regarding this change, please reference our [deprecation issue](https://gitlab.com/groups/gitlab-org/configure/-/epics/6). +
+ +
+ ### Gitaly nodes in virtual storage
@@ -1349,6 +1730,10 @@ For additional context, or to provide feedback regarding this change, please ref Configuring the Gitaly nodes directly in the virtual storage's root configuration object has been deprecated in GitLab 13.12 and is no longer supported in GitLab 15.0. You must move the Gitaly nodes under the `'nodes'` key as described in [the Praefect configuration](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#praefect). +
+ +
+ ### GraphQL permissions change for Package settings
@@ -1367,6 +1752,10 @@ The permissions model for GraphQL is being updated. After 15.0, users with the G The issue for this removal is [GitLab-#350682](https://gitlab.com/gitlab-org/gitlab/-/issues/350682) +
+ +
+ ### Jaeger integration
@@ -1377,6 +1766,10 @@ The issue for this removal is [GitLab-#350682](https://gitlab.com/gitlab-org/git Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distributed tracing system. GitLab users could previously 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 was deprecated in GitLab 14.7, and removed 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). +
+ +
+ ### Known host required for GitLab Runner SSH executor
@@ -1389,6 +1782,10 @@ In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/30 In GitLab 15.0, the default value for this configuration option has changed from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor. +
+ +
+ ### Legacy Geo Admin UI routes
@@ -1398,6 +1795,10 @@ In GitLab 15.0, the default value for this configuration option has changed from 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. These legacy routes `/admin/geo/projects` and `/admin/geo/designs` have been removed in GitLab 15.0. Please update any bookmarks or scripts that may use the legacy routes. +
+ +
+ ### Legacy approval status names in License Compliance API
@@ -1407,6 +1808,10 @@ In GitLab 13.0, we introduced new project and design replication details routes We have now removed the deprecated legacy names for approval status of license policy (`blacklisted`, `approved`) in the API queries and responses. 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 may need to adjust any of your custom tools. +
+ +
+ ### Move Gitaly Cluster Praefect `database_host_no_proxy` and `database_port_no_proxy configs`
@@ -1417,6 +1822,10 @@ We have now removed the deprecated legacy names for approval status of license p The Gitaly Cluster configuration keys for `praefect['database_host_no_proxy']` and `praefect['database_port_no_proxy']` are replaced with `praefect['database_direct_host']` and `praefect['database_direct_port']`. +
+ +
+ ### Move `custom_hooks_dir` setting from GitLab Shell to Gitaly
@@ -1427,6 +1836,10 @@ The Gitaly Cluster configuration keys for `praefect['database_host_no_proxy']` a 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 is removed from GitLab Shell in GitLab 15.0. +
+ +
+ ### OAuth implicit grant
@@ -1436,6 +1849,10 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks. The OAuth implicit grant authorization flow is no longer supported. Any applications that use OAuth implicit grant must switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html). +
+ +
+ ### OAuth tokens without an expiration
@@ -1447,6 +1864,10 @@ GitLab no longer supports OAuth tokens [without an expiration](https://docs.gitl Any existing token without an expiration has one automatically generated and applied. +
+ +
+ ### Optional enforcement of SSH expiration
@@ -1459,6 +1880,10 @@ Disabling SSH expiration enforcement is unusual from a security perspective and key is unintentionally able to be used. Unexpected behavior in a security feature is inherently dangerous and so now we enforce expiration on all SSH keys. +
+ +
+ ### Optional enforcement of personal access token expiration
@@ -1470,6 +1895,10 @@ expiration on all SSH keys. Allowing expired personal access tokens to be used is unusual from a security perspective and could create unusual situations where an expired key is unintentionally able to be used. Unexpected behavior in a security feature is inherently dangerous and so we now do not let expired personal access tokens be used. +
+ +
+ ### Out-of-the-box SAST (SpotBugs) support for Java 8
@@ -1491,6 +1920,10 @@ As of GitLab 15.0, we've: 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). +
+ +
+ ### Pipelines field from the version field
@@ -1506,6 +1939,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 GitLab 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. +
+ +
+ ### Pseudonymizer
@@ -1517,6 +1954,10 @@ To mitigate possible performance problems, we will remove the `versions` field's The Pseudonymizer feature is generally unused, can cause production issues with large databases, and can interfere with object storage development. It was removed in GitLab 15.0. +
+ +
+ ### Request profiling
@@ -1533,6 +1974,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). +
+ +
+ ### Required pipeline configurations in Premium tier
@@ -1549,6 +1994,10 @@ This change also helps GitLab remain consistent in our tiering strategy with the - [Security policies](https://docs.gitlab.com/ee/user/application_security/policies/). - [Compliance framework pipelines](https://docs.gitlab.com/ee/user/project/settings/index.html#compliance-pipeline-configuration). +
+ +
+ ### Retire-JS Dependency Scanning tool
@@ -1561,6 +2010,10 @@ We have removed support for retire.js from Dependency Scanning as of May 22, 202 If you have explicitly excluded retire.js using the `DS_EXCLUDED_ANALYZERS` variable, then you will be able to remove the reference to retire.js. If you have customized your pipeline’s Dependency Scanning configuration related to the `retire-js-dependency_scanning` job, then you will want to switch to `gemnasium-dependency_scanning`. 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 any action. +
+ +
+ ### Runner status `not_connected` API value
@@ -1575,6 +2028,10 @@ starting in GitLab 15.0. Runners that have never contacted the GitLab instance will also return `stale` if created more than 3 months ago. +
+ +
+ ### SAST support for .NET 2.1
@@ -1601,6 +2058,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). +
+ +
+ ### SUSE Linux Enterprise Server 12 SP2
@@ -1610,6 +2071,10 @@ If you rely on .NET 2.1 support being present in the analyzer image by default, 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. +
+ +
+ ### Secret Detection configuration variables
@@ -1633,6 +2098,10 @@ You can still customize the behavior of the Secret Detection analyzer using the For further details, see [the deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352565). +
+ +
+ ### Self-managed certificate-based integration with Kubernetes feature flagged
@@ -1651,6 +2120,10 @@ In GitLab 16.0, we will [remove the feature, its related code, and the feature f For updates and details, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). +
+ +
+ ### Sidekiq configuration for metrics and health checks
@@ -1673,6 +2146,10 @@ To prevent this error, choose different ports for the metrics and health check s If you installed GitLab from source, verify manually that both servers are configured to bind to separate addresses and ports. +
+ +
+ ### Static Site Editor
@@ -1682,6 +2159,10 @@ If you installed GitLab from source, verify manually that both servers are confi The Static Site Editor was deprecated in GitLab 14.7 and the feature is being removed in GitLab 15.0. Incoming requests to the Static Site Editor will be redirected and open the target file to edit in the Web IDE. Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/web_ide/index.html) for more information, including how to remove the configuration files from existing projects. We will continue investing in improvements to the Markdown editing experience by [maturing the Content Editor](https://gitlab.com/groups/gitlab-org/-/epics/5401) and making it available as a way to edit content across GitLab. +
+ +
+ ### Support for `gitaly['internal_socket_dir']`
@@ -1692,6 +2173,10 @@ The Static Site Editor was deprecated in GitLab 14.7 and the feature is being re Gitaly introduced a new directory that holds all runtime data Gitaly requires to operate correctly. This new directory replaces the old internal socket directory, and consequentially the usage of `gitaly['internal_socket_dir']` was deprecated in favor of `gitaly['runtime_dir']`. +
+ +
+ ### Support for legacy format of `config/database.yml`
@@ -1708,6 +2193,10 @@ The `main:` database needs to be defined as a first configuration item. This change only impacts users compiling GitLab from source, all the other installation methods handle this configuration automatically. Instructions are available [in the source update documentation](https://docs.gitlab.com/ee/update/upgrading_from_source.html#new-configuration-options-for-databaseyml). +
+ +
+ ### Test coverage project CI/CD setting
@@ -1722,6 +2211,10 @@ has been removed. To set test coverage parsing, use the project’s `.gitlab-ci.yml` file by providing a regular expression with the [`coverage` keyword](https://docs.gitlab.com/ee/ci/yaml/index.html#coverage). +
+ +
+ ### The `promote-db` command is no longer available from `gitlab-ctl`
@@ -1732,6 +2225,10 @@ To set test coverage parsing, use the project’s `.gitlab-ci.yml` file by provi 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. The `gitlab-ctl promote-db` command has been removed in GitLab 15.0. +
+ +
+ ### Update to the Container Registry group-level API
@@ -1744,6 +2241,10 @@ In GitLab 15.0, support for the `tags` and `tags_count` parameters will be remov 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. +
+ +
+ ### Versions from `PackageType`
@@ -1756,6 +2257,10 @@ As part of the work to create a [Package Registry GraphQL API](https://gitlab.co In GitLab 15.0, we will completely remove `Version` from `PackageType`. +
+ +
+ ### Vulnerability Check
@@ -1773,6 +2278,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. +
+ +
+ ### `Managed-Cluster-Applications.gitlab-ci.yml`
@@ -1783,6 +2292,10 @@ The new security approvals feature is similar to vulnerability check. For exampl The `Managed-Cluster-Applications.gitlab-ci.yml` CI/CD template is being removed. If you need an alternative, try the [Cluster Management project template](https://gitlab.com/gitlab-org/gitlab/-/issues/333610) instead. If your are not ready to move, you can copy the [last released version](https://gitlab.com/gitlab-org/gitlab-foss/-/blob/v14.10.1/lib/gitlab/ci/templates/Managed-Cluster-Applications.gitlab-ci.yml) of the template into your project. +
+ +
+ ### `artifacts:reports:cobertura` keyword
@@ -1796,6 +2309,10 @@ keyword has been [replaced](https://gitlab.com/gitlab-org/gitlab/-/issues/344533 [`artifacts:reports:coverage_report`](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportscoverage_report). Cobertura is the only supported report file, but this is the first step towards GitLab supporting other report types. +
+ +
+ ### `defaultMergeCommitMessageWithDescription` GraphQL API field
@@ -1806,6 +2323,10 @@ Cobertura is the only supported report file, but this is the first step towards The GraphQL API field `defaultMergeCommitMessageWithDescription` has been removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template. +
+ +
+ ### `dependency_proxy_for_private_groups` feature flag
@@ -1818,6 +2339,10 @@ A feature flag was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/11 In GitLab 15.0, we will remove the feature flag, and you must always authenticate when you use the Dependency Proxy. +
+ +
+ ### `omniauth-kerberos` gem
@@ -1832,6 +2357,10 @@ to upgrade from the removed integration to the new supported one. We are not removing Kerberos SPNEGO integration. We are removing the old password-based Kerberos. +
+ +
+ ### `promote-to-primary-node` command from `gitlab-ctl`
@@ -1842,6 +2371,10 @@ We are not removing Kerberos SPNEGO integration. We are removing the old passwor 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` has been removed in GitLab 15.0. +
+ +
+ ### `push_rules_supersede_code_owners` feature flag
@@ -1852,6 +2385,10 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge The `push_rules_supersede_code_owners` feature flag has been removed in GitLab 15.0. From now on, push rules will supersede the `CODEOWNERS` file. Even if Code Owner approval is required, a push rule that explicitly allows a specific user to push code supersedes the Code Owners setting. +
+ +
+ ### `type` and `types` keyword from CI/CD configuration
@@ -1861,6 +2398,10 @@ The `push_rules_supersede_code_owners` feature flag has been removed in GitLab 1 The `type` and `types` CI/CD keywords is removed in GitLab 15.0, so pipelines that use these keywords fail with a syntax error. Switch to `stage` and `stages`, which have the same behavior. +
+ +
+ ### bundler-audit Dependency Scanning tool
@@ -1873,8 +2414,15 @@ We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. If you have explicitly excluded bundler-audit using the `DS_EXCLUDED_ANALYZERS` variable, then you will be able to remove the reference to bundler-audit. If you have customized your pipeline’s Dependency Scanning configuration related to the `bundler-audit-dependency_scanning` job, then you will want to switch to `gemnasium-dependency_scanning`. 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 any action. +
+
+ +
+ ## Removed in 14.10 +
+ ### Permissions change for downloading Composer dependencies
@@ -1886,8 +2434,15 @@ 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. +
+
+ +
+ ## Removed in 14.9 +
+ ### Integrated error tracking disabled by default
@@ -1900,8 +2455,15 @@ In GitLab 14.4, GitLab released an integrated error tracking backend that replac For additional background on this removal, please reference [Disable Integrated Error Tracking by Default](https://gitlab.com/groups/gitlab-org/-/epics/7580). If you have feedback please add a comment to [Feedback: Removal of Integrated Error Tracking](https://gitlab.com/gitlab-org/gitlab/-/issues/355493). +
+
+ +
+ ## Removed in 14.6 +
+ ### Limit the number of triggered pipeline to 25K in free tier
@@ -1910,6 +2472,10 @@ For additional background on this removal, please reference [Disable Integrated 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. +
+ +
+ ### Release CLI distributed as a generic package
@@ -1918,8 +2484,15 @@ A large amount of triggered pipelines in a single project impacts the performanc 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. +
+
+ +
+ ## Removed in 14.3 +
+ ### Introduced limit of 50 tags for jobs
@@ -1928,6 +2501,10 @@ The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as 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. +
+ +
+ ### List project pipelines API endpoint removes `name` support in 14.3
@@ -1936,6 +2513,10 @@ GitLab values efficiency and is prioritizing reliability for [GitLab.com in FY22 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`. +
+ +
+ ### Use of legacy storage setting
@@ -1946,8 +2527,15 @@ The support for [`gitlab_pages['use_legacy_storage']` setting](https://docs.gitl In 14.0 we removed [`domain_config_source`](https://docs.gitlab.com/ee/administration/pages/index.html#domain-source-configuration-before-140) which had been previously deprecated, and allowed users to specify disk storage. In 14.0 we added `use_legacy_storage` as a **temporary** flag to unblock upgrades, and allow us to debug issues with our users and it was deprecated and communicated for removal in 14.3. +
+
+ +
+ ## Removed in 14.2 +
+ ### Max job log file size of 100 MB
@@ -1957,8 +2545,15 @@ In 14.0 we removed [`domain_config_source`](https://docs.gitlab.com/ee/administr 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. +
+
+ +
+ ## Removed in 14.1 +
+ ### Remove support for `prometheus.listen_address` and `prometheus.enable`
@@ -1969,6 +2564,10 @@ The support for `prometheus.listen_address` and `prometheus.enable` has been rem This only affects new installations from source where users might use the old configurations. +
+ +
+ ### Remove support for older browsers
@@ -1991,8 +2590,15 @@ The minimum supported browser versions are: - Chromium 84. - Microsoft Edge 84. +
+
+ +
+ ## Removed in 14.0 +
+ ### Auto Deploy CI template v1
@@ -2005,6 +2611,10 @@ In GitLab 14.0, we will update the [Auto Deploy](https://docs.gitlab.com/ee/topi 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). +
+ +
+ ### Breaking changes to Terraform CI template
@@ -2017,6 +2627,10 @@ GitLab 14.0 renews the Terraform CI template to the latest version. The new temp The current stable and latest templates are not compatible, and the current latest template becomes the stable template beginning with GitLab 14.0, your Terraform pipeline might encounter an unexpected failure if you run a custom `init` job. +
+ +
+ ### Code Quality RuboCop support changed
@@ -2028,6 +2642,10 @@ By default, the Code Quality feature has not provided support for Ruby 2.6+ if y Relevant Issue: [Default `codeclimate-rubocop` engine does not support Ruby 2.6+](https://gitlab.com/gitlab-org/ci-cd/codequality/-/issues/28) +
+ +
+ ### Container Scanning Engine Clair
@@ -2037,6 +2655,10 @@ Relevant Issue: [Default `codeclimate-rubocop` engine does not support Ruby 2.6+ 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. +
+ +
+ ### DAST default template stages
@@ -2046,6 +2668,10 @@ Clair, the default container scanning engine, was deprecated in GitLab 13.9 and 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. +
+ +
+ ### DAST environment variable renaming and removal
@@ -2064,6 +2690,10 @@ GitLab 13.8 renamed multiple environment variables to support their broader usag - `DAST_ZAP_USE_AJAX_SPIDER` will now be `DAST_USE_AJAX_SPIDER`. - `DAST_FULL_SCAN_DOMAIN_VALIDATION_REQUIRED` will be removed, since the feature is being removed. +
+ +
+ ### Default Browser Performance testing job renamed in GitLab 14.0
@@ -2075,6 +2705,10 @@ Browser Performance Testing has run in a job named `performance` by default. Wit Relevant Issue: [Rename default Browser Performance Testing job](https://gitlab.com/gitlab-org/gitlab/-/issues/225914) +
+ +
+ ### Default DAST spider begins crawling at target URL
@@ -2084,6 +2718,10 @@ Relevant Issue: [Rename default Browser Performance Testing job](https://gitlab. 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. +
+ +
+ ### Default branch name for new repositories now `main`
@@ -2097,6 +2735,10 @@ GitLab has already introduced changes that allow you to change the default branc For more information, check out our [blog post](https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/). +
+ +
+ ### Dependency Scanning
@@ -2110,6 +2752,10 @@ Previously, to exclude a DS analyzer, you needed to remove it from the default l Previously, to prevent the Gemnasium analyzers to fetch the advisory database at runtime, you needed to set the `GEMNASIUM_DB_UPDATE` variable. However, this is not documented properly, and its naming is inconsistent with the equivalent `BUNDLER_AUDIT_UPDATE_DISABLED` variable. As a result, we ask you to migrate from `GEMNASIUM_DB_UPDATE` to `GEMNASIUM_UPDATE_DISABLED` when it is available. Read about it in [issue #215483](https://gitlab.com/gitlab-org/gitlab/-/issues/215483). +
+ +
+ ### Deprecated GraphQL fields
@@ -2126,6 +2772,10 @@ In accordance with our [GraphQL deprecation and removal process](https://docs.gi - `DeprecatedMutations (concern**)` - `AddAwardEmoji`, `RemoveAwardEmoji`, `ToggleAwardEmoji` - `EE::Types::DeprecatedMutations (concern***)` - `Mutations::Pipelines::RunDastScan`, `Mutations::Vulnerabilities::Dismiss`, `Mutations::Vulnerabilities::RevertToDetected` +
+ +
+ ### DevOps Adoption API Segments
@@ -2135,6 +2785,10 @@ In accordance with our [GraphQL deprecation and removal process](https://docs.gi 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**. +
+ +
+ ### Disk source configuration for GitLab Pages
@@ -2145,6 +2799,10 @@ The first release of the DevOps Adoption report had a concept of **Segments**. S 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. +
+ +
+ ### Experimental prefix in Sidekiq queue selector options
@@ -2156,6 +2814,10 @@ GitLab supports a [queue selector](https://docs.gitlab.com/ee/administration/ope As announced in the [13.6 release post](https://about.gitlab.com/releases/2020/11/22/gitlab-13-6-released/#sidekiq-cluster-queue-selector-configuration-option-has-been-renamed), the 'experimental' prefix is no longer supported. Instead, `queue_selector` for Omnibus and `queueSelector` in Helm charts should be used. +
+ +
+ ### External Pipeline Validation Service Code Changes
@@ -2165,6 +2827,10 @@ As announced in the [13.6 release post](https://about.gitlab.com/releases/2020/1 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. +
+ +
+ ### Geo Foreign Data Wrapper settings
@@ -2179,6 +2845,10 @@ As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitla - `geo_postgresql['fdw_external_password']` - `gitlab-_rails['geo_migrated_local_files_clean_up_worker_cron']` +
+ +
+ ### GitLab OAuth implicit grant
@@ -2191,6 +2861,10 @@ GitLab is deprecating the [OAuth 2 implicit grant flow](https://docs.gitlab.com/ Migrate your existing applications to other supported [OAuth2 flows](https://docs.gitlab.com/ee/api/oauth2.html#supported-oauth2-flows). +
+ +
+ ### GitLab Runner helper image in GitLab.com Container Registry
@@ -2200,6 +2874,10 @@ Migrate your existing applications to other supported [OAuth2 flows](https://doc 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. +
+ +
+ ### GitLab Runner installation to ignore the `skel` directory
@@ -2209,6 +2887,10 @@ In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab 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. +
+ +
+ ### Gitaly Cluster SQL primary elector
@@ -2221,6 +2903,10 @@ The `per_repository` election strategy is the new default, which is automaticall If you had configured the `sql` election strategy, you must follow the [migration instructions](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#migrate-to-repository-specific-primary-gitaly-nodes) before upgrading to 14.0. +
+ +
+ ### Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template
@@ -2235,6 +2921,10 @@ Each analyzer job now has a scoped `SAST_ANALYZER_IMAGE_TAG` variable, which wil If you override or maintain custom versions of `SAST.gitlab-ci.yml`, update your CI templates to stop referencing the global `SAST_ANALYZER_IMAGE_TAG`, and move it to a scoped analyzer job tag. 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. This change allows you to more granularly control future analyzer updates with a pinned `major.minor` version. This deprecation and removal changes our [previously announced plan](https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#pin-static-analysis-analyzers-and-tools-to-minor-versions) to pin the Static Analysis tools. +
+ +
+ ### Hardcoded `master` in CI/CD templates
@@ -2244,6 +2934,10 @@ This deprecation and removal changes our [previously announced plan](https://abo 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). +
+ +
+ ### Helm v2 support
@@ -2255,6 +2949,10 @@ Helm v2 was [officially deprecated](https://helm.sh/blog/helm-v2-deprecation-tim Users of the chart should [upgrade to Helm v3](https://helm.sh/docs/topics/v2_v3_migration/) to deploy GitLab 14.0 and later. +
+ +
+ ### Legacy DAST domain validation
@@ -2266,6 +2964,10 @@ The legacy method of DAST Domain Validation for CI/CD scans was deprecated in Gi For more information, see the [removal issue](https://gitlab.com/gitlab-org/gitlab/-/issues/293595). +
+ +
+ ### Legacy feature flags
@@ -2276,6 +2978,10 @@ For more information, see the [removal issue](https://gitlab.com/gitlab-org/gitl 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. +
+ +
+ ### Legacy fields from DAST report
@@ -2287,6 +2993,10 @@ As a part of the migration to a common report format for all of the Secure scann For more information, see [the removal issue](https://gitlab.com/gitlab-org/gitlab/-/issues/33915). +
+ +
+ ### Legacy storage
@@ -2296,6 +3006,10 @@ For more information, see [the removal issue](https://gitlab.com/gitlab-org/gitl 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. +
+ +
+ ### License Compliance
@@ -2305,6 +3019,10 @@ As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitla 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/). +
+ +
+ ### Limit projects returned in `GET /groups/:id/`
@@ -2315,6 +3033,10 @@ In 13.0, we deprecated the License-Management CI template and renamed it License 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. +
+ +
+ ### Make `pwsh` the default shell for newly-registered Windows Runners
@@ -2324,6 +3046,10 @@ To improve performance, we are limiting the number of projects returned from the 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. +
+ +
+ ### Migrate from `SAST_DEFAULT_ANALYZERS` to `SAST_EXCLUDED_ANALYZERS`
@@ -2335,6 +3061,10 @@ In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor. 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. +
+ +
+ ### Off peak time mode configuration for Docker Machine autoscaling
@@ -2344,6 +3074,10 @@ Beginning with 13.9, [we migrated](https://gitlab.com/gitlab-org/gitlab/-/blob/1 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). +
+ +
+ ### OpenSUSE Leap 15.1
@@ -2353,6 +3087,10 @@ In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner 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. +
+ +
+ ### PostgreSQL 11 support
@@ -2364,6 +3102,10 @@ GitLab 14.0 requires PostgreSQL 12 or later. It offers [significant improvements Starting in GitLab 13.7, all new installations default to PostgreSQL version 12. From GitLab 13.8, single-node instances are automatically upgraded as well. If you aren't ready to upgrade, you can [opt out of automatic upgrades](https://docs.gitlab.com/omnibus/settings/database.html#opt-out-of-automatic-postgresql-upgrades). +
+ +
+ ### Redundant timestamp field from DORA metrics API payload
@@ -2374,6 +3116,10 @@ Starting in GitLab 13.7, all new installations default to PostgreSQL version 12. The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora/metrics.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`). +
+ +
+ ### Release description in the Tags API
@@ -2384,6 +3130,10 @@ The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora 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. +
+ +
+ ### Ruby version changed in `Ruby.gitlab-ci.yml`
@@ -2397,6 +3147,10 @@ To better support the latest versions of Ruby, the template is changed to use `r Relevant Issue: [Updates Ruby version 2.5 to 3.0](https://gitlab.com/gitlab-org/gitlab/-/issues/329160) +
+ +
+ ### SAST analyzer `SAST_GOSEC_CONFIG` variable
@@ -2408,6 +3162,10 @@ Relevant Issue: [Updates Ruby version 2.5 to 3.0](https://gitlab.com/gitlab-org/ 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. +
+ +
+ ### Service Templates
@@ -2419,6 +3177,10 @@ Service Templates are [removed in GitLab 14.0](https://gitlab.com/groups/gitlab- While they solved part of the problem, _updating_ those values later proved to be a major pain point. [Project Integration Management](https://docs.gitlab.com/ee/user/admin_area/settings/project_integration_management.html) solves this problem by enabling you to create settings at the Group or Instance level, and projects within that namespace inheriting those settings. +
+ +
+ ### Success and failure for finished build metric conversion
@@ -2428,6 +3190,10 @@ While they solved part of the problem, _updating_ those values later proved to b 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. +
+ +
+ ### Terraform template version
@@ -2449,6 +3215,10 @@ doesn't need additional setup to work with the [GitLab managed Terraform state]( To check the new changes, see the [new "major version" template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml). +
+ +
+ ### Ubuntu 16.04 support
@@ -2460,6 +3230,10 @@ Ubuntu 16.04 [reached end-of-life in April 2021](https://ubuntu.com/about/releas GitLab 13.12 will be the last release with Ubuntu 16.04 support. +
+ +
+ ### Ubuntu 19.10 (Eoan Ermine) package
@@ -2469,6 +3243,10 @@ GitLab 13.12 will be the last release with Ubuntu 16.04 support. 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. +
+ +
+ ### Unicorn in GitLab self-managed
@@ -2478,6 +3256,10 @@ Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitL [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. +
+ +
+ ### WIP merge requests renamed 'draft merge requests'
@@ -2487,6 +3269,10 @@ Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitL 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. +
+ +
+ ### Web Application Firewall (WAF)
@@ -2496,6 +3282,10 @@ The WIP (work in progress) status for merge requests signaled to reviewers that 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). +
+ +
+ ### Windows Server 1903 image support
@@ -2505,6 +3295,10 @@ The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed 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. +
+ +
+ ### Windows Server 1909 image support
@@ -2514,6 +3308,10 @@ In 14.0, we have removed Windows Server 1903. Microsoft ended support for this v 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. +
+ +
+ ### `/usr/lib/gitlab-runner` symlink from package
@@ -2523,6 +3321,10 @@ In 14.0, we have removed Windows Server 1909. Microsoft ended support for this v 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. +
+ +
+ ### `?w=1` URL parameter to ignore whitespace changes
@@ -2532,6 +3334,10 @@ In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab- 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. +
+ +
+ ### `CI_PROJECT_CONFIG_PATH` variable
@@ -2545,6 +3351,10 @@ has been removed in favor of `CI_CONFIG_PATH`, which is functionally the same. If you are using `CI_PROJECT_CONFIG_PATH` in your pipeline configurations, please update them to use `CI_CONFIG_PATH` instead. +
+ +
+ ### `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag
@@ -2554,6 +3364,10 @@ please update them to use `CI_CONFIG_PATH` instead. 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. +
+ +
+ ### `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag
@@ -2563,6 +3377,10 @@ In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag 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. +
+ +
+ ### `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag
@@ -2572,6 +3390,10 @@ In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitl 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. +
+ +
+ ### `secret_detection_default_branch` job
@@ -2583,6 +3405,10 @@ GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature fla 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. +
+ +
+ ### `trace` parameter in `jobs` API
@@ -2591,3 +3417,6 @@ If you override or maintain custom versions of `SAST.gitlab-ci.yml` or `Secret-D
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. + +
+