diff options
Diffstat (limited to 'doc/update')
| -rw-r--r-- | doc/update/deprecations.md | 908 | ||||
| -rw-r--r-- | doc/update/index.md | 493 | ||||
| -rw-r--r-- | doc/update/package/downgrade.md | 2 | ||||
| -rw-r--r-- | doc/update/package/index.md | 3 | ||||
| -rw-r--r-- | doc/update/plan_your_upgrade.md | 4 | ||||
| -rw-r--r-- | doc/update/upgrading_from_source.md | 4 | ||||
| -rw-r--r-- | doc/update/versions/gitlab_16_changes.md | 221 | ||||
| -rw-r--r-- | doc/update/zero_downtime.md | 2 |
8 files changed, 845 insertions, 792 deletions
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 804fcc77ea1..08a5a3a7549 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -55,8 +55,8 @@ For deprecation reviewers (Technical Writers only): ### Atlassian Crowd OmniAuth provider <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.3</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369117). </div> @@ -72,8 +72,8 @@ next major release, GitLab 16.0. This gem sees very little use and its ### Auto DevOps support for Herokuish is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/211643). </div> @@ -88,8 +88,8 @@ Because Cloud Native Buildpacks do not support automatic testing, the Auto Test ### CiRunner.projects default sort is changing to `id_desc` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/372117). </div> @@ -103,8 +103,8 @@ If you rely on the order of the returned projects to be `id_asc`, change your sc ### CiRunnerUpgradeStatusType GraphQL type renamed to CiRunnerUpgradeStatus <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/409332). </div> @@ -118,8 +118,8 @@ the aliasing for the `CiRunnerUpgradeStatusType` type will be removed. ### DAST ZAP advanced configuration variables deprecation <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383467). </div> @@ -134,9 +134,8 @@ These three variables will be removed in GitLab 17.0. ### Deprecate Windows CMD in GitLab Runner <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.1</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/414864). </div> @@ -149,9 +148,8 @@ In GitLab 11.11 the Windows Batch executor, the CMD shell was deprecated in GitL ### Deprecate `CiRunner` GraphQL fields duplicated in `CiRunnerManager` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.2</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.2</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/41518). </div> @@ -164,8 +162,8 @@ These fields (`architectureName`, `ipAddress`, `platformName`, `revision`, `vers ### Deprecate `message` field from Vulnerability Management features <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/411573). </div> @@ -176,11 +174,41 @@ The message field was removed from security reports schema in GitLab 16.0 and is <div class="deprecation " data-milestone="17.0"> +### Deprecate `terminationGracePeriodSeconds` in the GitLab Runner Kubernetes executor + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">16.3</span> +- End of Support in GitLab <span class="milestone">17.0</span> +- Removal in GitLab <span class="milestone">17.0</span> +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28165). +</div> + +The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings). + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + +### Deprecate field `hasSolutions` from GraphQL VulnerabilityType + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">16.3</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/414895). +</div> + +The GraphQL field `Vulnerability.hasSolutions` is deprecated and will be removed in GitLab 17.0. +Use `Vulnerability.hasRemediations` instead. + +</div> + +<div class="deprecation " data-milestone="17.0"> + ### Deprecate legacy shell escaping and quoting runner shell executor <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.11</span> -- End of Support: GitLab <span class="milestone">17.9</span> +- Announced in GitLab <span class="milestone">15.11</span> +- Removal in GitLab <span class="milestone">17.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/406679). </div> @@ -193,8 +221,8 @@ The runner's legacy escape sequence mechanism to handle variable expansion imple ### Deprecated parameters related to custom text in the sign-in page <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.2</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124461). </div> @@ -207,8 +235,8 @@ The parameters, `sign_in_text` and `help_text`, are deprecated in the [Settings ### DingTalk OmniAuth provider <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390855). </div> @@ -222,8 +250,8 @@ major release, GitLab 17.0. This gem sees very little use and is better suited f ### Filepath field in Releases and Release Links APIs <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/9661). </div> @@ -248,8 +276,8 @@ To avoid any disruptions, you should replace `filepath` with `direct_asset_path` ### GitLab Helm chart values `gitlab.kas.privateApi.*` are deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/4097). </div> @@ -269,8 +297,8 @@ Because the new values provide a streamlined, comprehensive method to enable TLS ### GitLab Runner platforms and setup instructions in GraphQL API <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387937). </div> @@ -285,9 +313,8 @@ are deprecated and will be removed from the GraphQL API. For installation instru ### GitLab Runner registration token in Runner Operator <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.6</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.6</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/382077). </div> @@ -309,8 +336,8 @@ This change is a breaking change. You should use an [authentication token](../ci ### GraphQL deprecation of `dependencyProxyTotalSizeInBytes` field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/414236). </div> @@ -325,8 +352,8 @@ Use `dependencyProxyTotalSizeBytes` instead, introduced in GitLab 16.1. ### GraphQL field `registrySizeEstimated` has been deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.2</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/416509). </div> @@ -338,11 +365,27 @@ Use `containerRegistrySizeIsEstimated` introduced in GitLab 16.2 instead. <div class="deprecation breaking-change" data-milestone="17.0"> +### GraphQL field `totalWeight` is deprecated + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">16.3</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/416219). +</div> + +You can use GraphQL to query the total weight of issues in an issue board. However, the `totalWeight` field is limited to the maximum size 2147483647. As a result, `totalWeight` is deprecated and will be removed in GitLab 17.0. + +Use `totalIssueWeight` instead, introduced in GitLab 16.2. + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### GraphQL type, `RunnerMembershipFilter` renamed to `CiRunnerMembershipFilter` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/409333). </div> @@ -356,8 +399,8 @@ the aliasing for the `RunnerMembershipFilter` type will be removed. ### GraphQL: The `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` enum is deprecated. Use `DISABLED_AND_OVERRIDABLE` instead <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385636). </div> @@ -370,8 +413,8 @@ In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` ### Maintainer role providing the ability to change Package settings using GraphQL API <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/370471). </div> @@ -392,8 +435,8 @@ settings for the group using either the GitLab UI or GraphQL API. ### OmniAuth Facebook is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.2</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/416000). </div> @@ -406,8 +449,8 @@ OmniAuth Facebook support will be removed in GitLab 17.0. The last gem release w ### Package pipelines in API payload is paginated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/289956). </div> @@ -422,8 +465,8 @@ In milestone 17.0, we will remove the `pipelines` attribute from the API respons ### PipelineSecurityReportFinding projectFingerprint GraphQL field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343475). </div> @@ -436,9 +479,8 @@ The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) a ### PostgreSQL 13 deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/9065). </div> @@ -457,9 +499,9 @@ PostgreSQL 14 will also be supported for instances that want to upgrade prior to ### Queue selector for running Sidekiq is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- End of Support in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390787). </div> @@ -476,9 +518,8 @@ While the above approach is recommended for most instances, Sidekiq can also be ### Registration tokens and server-side runner arguments in `POST /api/v4/runners` endpoint <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.6</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.6</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/379743). </div> @@ -506,9 +547,8 @@ This change is a breaking change. You should [create a runner in the UI](../ci/r ### Registration tokens and server-side runner arguments in `gitlab-runner register` command <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.6</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.6</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/380872). </div> @@ -534,8 +574,8 @@ This change is a breaking change. You should [create a runner in the UI](../ci/r ### Required Pipeline Configuration is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/389467). </div> @@ -551,8 +591,8 @@ that is available now. We recommend this alternative solution because it provide ### Running a single database is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/411239). </div> @@ -573,8 +613,8 @@ Before upgrading to GitLab 17.0, please ensure you have [migrated](https://docs. ### Self-managed certificate-based integration with Kubernetes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). </div> @@ -599,8 +639,8 @@ For updates and details about this deprecation, follow [this epic](https://gitla ### Single database connection is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387898). </div> @@ -622,9 +662,8 @@ automatically from GitLab 16.0 onwards. ### Slack notifications integration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/372411). </div> @@ -642,9 +681,8 @@ we'll be introducing support in [this epic](https://gitlab.com/groups/gitlab-org ### Support for REST API endpoints that reset runner registration tokens <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383341). </div> @@ -670,8 +708,8 @@ From GitLab 17.0 and later, the runner registration methods implemented by the n ### The GitLab legacy requirement IID is deprecated in favor of work item IID <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390263). </div> @@ -684,8 +722,8 @@ We will be transitioning to a new IID as a result of moving requirements to a [w ### The Visual Reviews tool is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387751). </div> @@ -698,9 +736,8 @@ Due to limited customer usage and capabilities, the Visual Reviews feature for R ### The `gitlab-runner exec` command is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385235). </div> @@ -713,8 +750,8 @@ The [`gitlab-runner exec`](https://docs.gitlab.com/runner/commands/#gitlab-runne ### The pull-based deployment features of the GitLab agent for Kubernetes is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.2</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/406545). </div> @@ -731,8 +768,8 @@ If you use the agent for pull-based deployments, you should [migrate to Flux](ht ### Trigger jobs can mirror downstream pipeline status exactly <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/285493). </div> @@ -742,11 +779,25 @@ In some cases, like when a downstream pipeline had the `passed with warnings` st <div class="deprecation breaking-change" data-milestone="17.0"> +### Twitter OmniAuth login option is deprecated from self-managed GitLab + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">16.3</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-com/Product/-/issues/11417). +</div> + +Twitter OAuth 1.0a OmniAuth is deprecated and will be removed for self-managed GitLab instances in GitLab 17.0 due to low use and lack of gem support. Use [another supported OmniAuth provider](https://docs.gitlab.com/ee/integration/omniauth.html#supported-providers) instead. + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### Unified approval rules are deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/9662). </div> @@ -765,8 +816,8 @@ You can still access unified approval rules with the API. ### Vulnerability confidence field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.4</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/372332). </div> @@ -782,9 +833,8 @@ removed in 17.0. ### `runnerRegistrationToken` parameter for GitLab Runner Helm Chart <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.6</span> -- End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.6</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/381111). </div> @@ -803,8 +853,8 @@ From GitLab 17.0 and later, the methods to register runners introduced by the ne ### `sidekiq` delivery method for `incoming_email` and `service_desk_email` is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/398132). </div> @@ -849,8 +899,8 @@ We hope this will simplify infrastructure setup and add several improvements to ### project.pipeline.securityReportFindings GraphQL query <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">17.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343475). </div> @@ -868,7 +918,8 @@ Previous work helped [align the vulnerabilities calls for pipeline security tabs ### Adding non-LDAP synced members to a locked LDAP group is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">16.5</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/213311). </div> @@ -881,8 +932,8 @@ Enabling the `ldap_settings_unlock_groups_by_owners` feature flag allowed non-LD ### HashiCorp Vault integration will no longer use CI_JOB_JWT by default <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.5</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/366798). </div> @@ -910,8 +961,8 @@ In GitLab 16.0 and later: ### Old versions of JSON web tokens are deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.5</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/366798). </div> @@ -957,9 +1008,8 @@ be available in CI/CD jobs. ### Bundled Grafana deprecated and disabled <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- End of Support: GitLab <span class="milestone">16.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">16.3</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7772). </div> @@ -983,8 +1033,8 @@ However, enabling the bundled Grafana will no longer work from GitLab 16.3. ### License Compliance CI Template <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.3</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387561). </div> @@ -999,6 +1049,20 @@ The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/licen | LS template is included but DS template is not | License data from LS job is used | License data from LS job is used | No license data | </div> + +<div class="deprecation breaking-change" data-milestone="16.3"> + +### Twitter OmniAuth login option is removed from GitLab.com + +<div class="deprecation-notes"> +- Announced in GitLab <span class="milestone">16.3</span> +- Removal in GitLab <span class="milestone">16.3</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-com/Product/-/issues/11417). +</div> + +Twitter OAuth 1.0a OmniAuth is being deprecated and removed on GitLab.com in GitLab 16.3 due to low use, lack of gem support, and the lack of a functional sign-in option for this feature. If you sign into GitLab.com with Twitter, you can sign in with a password or another [supported OmniAuth provider](https://gitlab.com/users/sign_in). + +</div> </div> <div class="milestone-wrapper" data-milestone="16.1"> @@ -1010,8 +1074,9 @@ The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/licen ### GitLab Runner images based on Alpine 3.12, 3.13, 3.14 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.11</span> -- End of Support: GitLab <span class="milestone">16.1</span> +- Announced in GitLab <span class="milestone">15.11</span> +- End of Support in GitLab <span class="milestone">16.1</span> +- Removal in GitLab <span class="milestone">16.1</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29639). </div> @@ -1033,8 +1098,8 @@ We will stop publishing runner images based on the following, end-of-life Alpine ### Auto DevOps no longer provisions a PostgreSQL database by default <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343988). </div> @@ -1052,8 +1117,8 @@ set the `POSTGRES_ENABLED` CI/CD variable to `true`. ### Azure Storage Driver defaults to the correct root prefix <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/container-registry/-/issues/854). </div> @@ -1070,8 +1135,8 @@ This breaking change will happen in GitLab 16.0. ### Bundled Grafana Helm Chart is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/4353). </div> @@ -1093,8 +1158,8 @@ and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration ### CAS OmniAuth provider <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.3</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369127). </div> @@ -1109,8 +1174,8 @@ release, GitLab 16.0. This gem sees very little use and its lack of upstream mai ### CI/CD jobs will fail when no secret is returned from Hashicorp Vault <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/353080). </div> @@ -1123,8 +1188,8 @@ When using the native HashiCorp Vault integration, CI/CD jobs will fail when no ### Changing MobSF-based SAST analyzer behavior in multi-module Android projects <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">16.0</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/408396). </div> @@ -1140,8 +1205,8 @@ Instead of changing which single module would be scanned, we [improved multi-mod ### Changing merge request approvals with the `/approvals` API endpoint <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.0</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/353097). </div> @@ -1156,8 +1221,8 @@ Instead, use the [`/approval_rules` endpoint](https://docs.gitlab.com/ee/api/mer ### Conan project-level search endpoint returns project-specific results <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/384455). </div> @@ -1172,9 +1237,8 @@ This unintended functionality is deprecated in GitLab 15.8 and will be removed i ### Configuration fields in GitLab Runner Helm Chart <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.6</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.6</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/379064). </div> @@ -1187,8 +1251,8 @@ From GitLab 13.6, users can [specify any runner configuration in the GitLab Runn ### Configuring Redis config file paths using environment variables is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388255). </div> @@ -1205,8 +1269,8 @@ config file locations instead, for example `config/redis.cache.yml` or ### Container Registry pull-through cache <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/container-registry/-/issues/842). </div> @@ -1219,8 +1283,8 @@ The Container Registry [pull-through cache](https://docs.docker.com/registry/rec ### Container Scanning variables that reference Docker <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.4</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/371840). </div> @@ -1233,8 +1297,8 @@ All Container Scanning variables that are prefixed by `DOCKER_` in variable name ### Cookie authorization in the GitLab for Jira Cloud app <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387299). </div> @@ -1249,8 +1313,8 @@ to continue to use the GitLab for Jira Cloud app. Without OAuth, you can't manag ### DAST API scans using DAST template is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/384198). </div> @@ -1263,8 +1327,8 @@ With the move to the new DAST API analyzer and the `DAST-API.gitlab-ci.yml` temp ### DAST API variables <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383467). </div> @@ -1283,8 +1347,8 @@ These two variables will be removed in GitLab 16.0. ### DAST report variables deprecation <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/384340). </div> @@ -1299,8 +1363,8 @@ These three variables will be removed in GitLab 16.0. ### Default CI/CD job token (`CI_JOB_TOKEN`) scope changed <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/395708). </div> @@ -1314,6 +1378,8 @@ 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. +In 16.3, the names of these settings were changed to clarify their meanings: the deprecated **Limit CI_JOB_TOKEN access** setting is now called **Limit access _from_ this project**, and the newer **Allow access to this project with a CI_JOB_TOKEN** setting is now called **Limit access _to_ this project**. + </div> <div class="deprecation breaking-change" data-milestone="16.0"> @@ -1321,8 +1387,8 @@ To prepare for this change, users on GitLab.com or self-managed GitLab 15.9 or l ### Dependency Scanning support for Java 13, 14, 15, and 16 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387560). </div> @@ -1335,8 +1401,8 @@ GitLab has deprecated Dependency Scanning support for Java versions 13, 14, 15, ### Deployment API returns error when `updated_at` and `updated_at` are not used together <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/328500). </div> @@ -1349,8 +1415,8 @@ The Deployment API will now return an error when `updated_at` filtering and `upd ### Deprecate legacy Gitaly configuration methods <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352609). </div> @@ -1367,8 +1433,8 @@ GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configu ### Deprecated Consul http metrics <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7278). </div> @@ -1387,9 +1453,8 @@ For more information, see [the deprecation notes for Consul 1.9.0](https://githu ### Deprecation and planned removal for `CI_PRE_CLONE_SCRIPT` variable on GitLab SaaS <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/391896). </div> @@ -1402,8 +1467,8 @@ The [`CI_PRE_CLONE_SCRIPT` variable](https://docs.gitlab.com/ee/ci/runners/saas/ ### Developer role providing the ability to import projects to a group <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387891). </div> @@ -1418,8 +1483,8 @@ will be able to import projects to that group. ### Development dependencies reported for PHP and Python <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/375505). </div> @@ -1432,8 +1497,8 @@ In GitLab 16.0 the GitLab Dependency Scanning analyzer will begin reporting deve ### Embedding Grafana panels in Markdown is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/389477). </div> @@ -1447,8 +1512,8 @@ We intend to replace this feature with the ability to [embed charts](https://git ### Enforced validation of CI/CD parameter character lengths <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/372770). </div> @@ -1469,8 +1534,8 @@ Users on self-managed instances should update their pipelines to ensure they do ### Environment search query requires at least three characters <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/382532). </div> @@ -1483,8 +1548,8 @@ From GitLab 16.0, when you search for environments with the API, you must use at ### External field in GraphQL ReleaseAssetLink type <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> In the [GraphQL API](https://docs.gitlab.com/ee/api/graphql/), the `external` field of [`ReleaseAssetLink` type](https://docs.gitlab.com/ee/api/graphql/reference/index.html#releaseassetlink) was used to indicate whether a [release link](https://docs.gitlab.com/ee/user/project/releases/release_fields.html#links) is internal or external to your GitLab instance. @@ -1498,8 +1563,8 @@ To avoid any disruptions to your workflow, please stop using the `external` fiel ### External field in Releases and Release Links APIs <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> In [Releases API](https://docs.gitlab.com/ee/api/releases/) and [Release Links API](https://docs.gitlab.com/ee/api/releases/links.html), the `external` field was used to indicate whether a [release link](https://docs.gitlab.com/ee/user/project/releases/release_fields.html#links) is internal or external to your GitLab instance. @@ -1513,7 +1578,8 @@ To avoid any disruptions to your workflow, please stop using the `external` fiel ### Geo: Project repository redownload is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.11</span> +- Announced in GitLab <span class="milestone">15.11</span> +- Removal in GitLab <span class="milestone">16.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388868). </div> @@ -1529,8 +1595,8 @@ GitLab 16.0. ### GitLab self-monitoring project <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/348909). </div> @@ -1543,7 +1609,8 @@ GitLab self-monitoring gives administrators of self-hosted GitLab instances the ### GitLab.com importer <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-com/Product/-/issues/4895). </div> @@ -1562,8 +1629,8 @@ See [migrated group items](https://docs.gitlab.com/ee/user/group/import/#migrate ### GraphQL API Runner status will not return `paused` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/344648). </div> @@ -1583,8 +1650,8 @@ When checking if a runner is `paused`, API users are advised to check the boolea ### GraphQL API legacyMode argument for Runner status <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.0</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/360545). </div> @@ -1602,8 +1669,8 @@ be present during the 16.x cycle to avoid breaking the API signature, and will b ### GraphQL field `confidential` changed to `internal` on notes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.5</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/371485). </div> @@ -1616,8 +1683,8 @@ The `confidential` field for a `Note` will be deprecated and renamed to `interna ### Jira DVCS connector for Jira Cloud <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/7508). </div> @@ -1632,9 +1699,8 @@ The Jira DVCS connector is also deprecated for Jira 8.13 and earlier. You can on ### KAS Metrics Port in GitLab Helm Chart <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383039). </div> @@ -1648,8 +1714,8 @@ This port is used for much more than just metrics, which warranted this change t ### Legacy Gitaly configuration method <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/393574). </div> @@ -1671,8 +1737,8 @@ You should update to the new configuration structure as soon as possible using ### Legacy Praefect configuration method <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390291). </div> @@ -1693,8 +1759,8 @@ didn't match. The change improves consistency between Omnibus GitLab and source ### Legacy URLs replaced or removed <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/214217). </div> @@ -1713,8 +1779,8 @@ Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are ### License-Check and the Policies tab on the License Compliance page <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390417). </div> @@ -1727,8 +1793,8 @@ The [License-Check feature](https://docs.gitlab.com/ee/user/compliance/license_c ### Limit personal access token and deploy token's access with external authorization <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387721). </div> @@ -1741,8 +1807,8 @@ With external authorization enabled, personal access tokens (PATs) and deploy to ### Major bundled Helm Chart updates for the GitLab Helm Chart <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/3442). </div> @@ -1763,8 +1829,8 @@ The full GitLab Helm Chart 7.0 upgrade steps will be available in the [upgrade d ### Managed Licenses API <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390417). </div> @@ -1777,7 +1843,8 @@ The [Managed Licenses API](https://docs.gitlab.com/ee/api/managed_licenses.html) ### Maximum number of active pipelines per project limit (`ci_active_pipelines`) <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> +- Announced in GitLab <span class="milestone">15.3</span> +- Removal in GitLab <span class="milestone">16.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/368195). </div> @@ -1793,8 +1860,8 @@ The [**Maximum number of active pipelines per project** limit](https://docs.gitl ### Monitor performance metrics through Prometheus <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346541). </div> @@ -1808,8 +1875,8 @@ However, since certificate-based integration with Kubernetes clusters is depreca ### Non-expiring access tokens <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.4</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369122). </div> @@ -1835,8 +1902,8 @@ default is applied: ### Non-standard default Redis ports are deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388269). </div> @@ -1856,8 +1923,8 @@ and `config/redis.shared_state.yml` files. ### Option to delete projects immediately is deprecated from deletion protection settings <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/389557). </div> @@ -1874,8 +1941,8 @@ The option to delete groups and projects immediately by default was deprecated t ### PipelineSecurityReportFinding name GraphQL field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346335). </div> @@ -1888,8 +1955,8 @@ Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https:/ ### PostgreSQL 12 deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.0</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/349185). </div> @@ -1908,8 +1975,8 @@ Support for PostgreSQL 13 was added to Geo in GitLab 15.2. ### Projects API field `operations_access_level` is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385798). </div> @@ -1922,7 +1989,8 @@ We are deprecating the `operations_access_level` field in the Projects API. This ### Rake task for importing bare repositories <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-com/Product/-/issues/5255). </div> @@ -1951,9 +2019,9 @@ Alternatives to using the `gitlab:import:repos` Rake task include: ### Redis 5 deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> -- End of Support: GitLab <span class="milestone">15.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.3</span> +- End of Support in GitLab <span class="milestone">15.6</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/331468). </div> @@ -1968,8 +2036,8 @@ If you are using your own Redis 5.0 instance, you should upgrade it to Redis 6.0 ### Remove `job_age` parameter from `POST /jobs/request` Runner endpoint <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.2</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/334253). </div> @@ -1984,8 +2052,8 @@ This could be a breaking change for anyone that developed their own runner that ### SAST analyzer coverage changing in GitLab 16.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390416). </div> @@ -2024,8 +2092,8 @@ Work to replace the PHPCS Security Audit-based analyzer is tracked in [issue 364 ### Secure analyzers major version update <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390912). </div> @@ -2067,8 +2135,8 @@ Specifically, the following are being deprecated and will no longer be updated a ### Secure scanning CI/CD templates will use new job `rules` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/391822). </div> @@ -2102,8 +2170,8 @@ However, due to compatibility issues [discussed in the deprecation issue](https: ### Security report schemas version 14.x.x <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.3</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/366477). </div> @@ -2122,9 +2190,8 @@ For more information, refer to [security report validation](https://docs.gitlab. ### Shimo integration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/377824). </div> @@ -2138,8 +2205,8 @@ and will be moved to the JiHu GitLab codebase. ### Starboard directive in the config for the GitLab Agent for Kubernetes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.4</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/368828). </div> @@ -2152,8 +2219,8 @@ GitLab's operational container scanning capabilities no longer require starboard ### Support for Praefect custom metrics endpoint configuration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.9</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390266). </div> @@ -2174,9 +2241,8 @@ This may require updating your metrics collection targets to also scrape `/db_me ### Support for periods (`.`) in Terraform state names might break existing states <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385564). </div> @@ -2199,8 +2265,8 @@ To use the full state name, including the period, [migrate to the full state fil ### The API no longer returns revoked tokens for the agent for Kubernetes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/382129). </div> @@ -2224,8 +2290,8 @@ This change affects the following REST and GraphQL API endpoints: ### The Phabricator task importer is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-com/Product/-/issues/4894). </div> @@ -2238,8 +2304,8 @@ The [Phabricator task importer](https://docs.gitlab.com/ee/user/project/import/p ### The latest Terraform templates will overwrite current stable templates <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/386001). </div> @@ -2261,8 +2327,8 @@ To accommodate the changes, you might need to adjust the [`rules`](https://docs. ### Toggle behavior of `/draft` quick action in merge requests <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.4</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/365365). </div> @@ -2275,8 +2341,8 @@ In order to make the behavior of toggling the draft status of a merge request mo ### Toggle notes confidentiality on APIs <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/350670). </div> @@ -2289,8 +2355,8 @@ Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. U ### Use of `id` field in vulnerabilityFindingDismiss mutation <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.3</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/367166). </div> @@ -2303,9 +2369,8 @@ You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status o ### Use of third party container registries is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376216). </div> @@ -2326,8 +2391,8 @@ Moving forward, we'll continue to invest in developing and releasing new feature ### Work items path with global ID at the end of the path is deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.10</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/393836). </div> @@ -2347,9 +2412,8 @@ In GitLab 16.0 we will remove the ability to use a global ID in the work items p ### ZenTao integration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/377825). </div> @@ -2363,8 +2427,8 @@ and will be moved to the JiHu GitLab codebase. ### `CI_BUILD_*` predefined variables <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352957). </div> @@ -2392,8 +2456,8 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G ### `POST ci/lint` API endpoint deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.7</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/381669). </div> @@ -2406,8 +2470,8 @@ The `POST ci/lint` API endpoint is deprecated in 15.7, and will be removed in 16 ### `environment_tier` parameter for DORA API <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/365939). </div> @@ -2420,8 +2484,8 @@ To avoid confusion and duplication, the `environment_tier` parameter is deprecat ### `started` iteration state <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/334018). </div> @@ -2440,8 +2504,8 @@ We plan to continue to support the `started` state in REST API version until the ### vulnerabilityFindingDismiss GraphQL mutation <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.5</span> +- Removal in GitLab <span class="milestone">16.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/375645). </div> @@ -2459,7 +2523,8 @@ The `VulnerabilityFindingDismiss` GraphQL mutation is being deprecated and will ### openSUSE Leap 15.3 packages <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">15.11</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7371). </div> @@ -2481,13 +2546,12 @@ Starting in GitLab 15.7 we started providing packages for openSUSE Leap 15.4, an ### Automatic backup upload using Openstack Swift and Rackspace APIs <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- End of Support: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">15.10</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387976). </div> -We are deprecating support for [uploading backups to remote storage](https://docs.gitlab.com/ee/raketasks/backup_gitlab.html#upload-backups-to-a-remote-cloud-storage) using Openstack Swift and Rackspace APIs. The support for these APIs depends on third-party libraries that are no longer actively maintained and have not been updated for Ruby 3. GitLab is switching over to Ruby 3 prior to EOL of Ruby 2 in order to stay up to date on security patches. +We are deprecating support for [uploading backups to remote storage](https://docs.gitlab.com/ee/raketasks/backup_gitlab.html#upload-backups-to-a-remote-cloud-storage) using Openstack Swift and Rackspace APIs. The support for these APIs depends on third-party libraries that are no longer actively maintained and have not been updated for Ruby 3. GitLab is switching over to Ruby 3 prior to EOL of Ruby 2 in order to stay up to date on security patches. - If you're using OpenStack, you need to change you configuration to use the S3 API instead of Swift. - If you're using Rackspace storage, you need to switch to a different provider or manually upload the backup file after the backup task is complete. @@ -2504,8 +2568,8 @@ We are deprecating support for [uploading backups to remote storage](https://doc ### Live Preview no longer available in the Web IDE <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.8</span> +- Removal in GitLab <span class="milestone">15.9</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383889). </div> @@ -2518,8 +2582,8 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr ### SaaS certificate-based integration with Kubernetes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.9</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). </div> @@ -2547,8 +2611,8 @@ GitLab self-managed customers can still use the feature [with a feature flag](ht ### File Type variable expansion in `.gitlab-ci.yml` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">15.5</span> +- Removal in GitLab <span class="milestone">15.7</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/29407). </div> @@ -2568,7 +2632,8 @@ This breaking change fixes this issue but could disrupt user workflows that work ### NFS for Git repository storage <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.0</span> +- Announced in GitLab <span class="milestone">14.0</span> +- Removal in GitLab <span class="milestone">15.6</span> </div> 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/#gitaly-and-nfs) for further information. @@ -2593,7 +2658,8 @@ We encourage customers currently using NFS for Git repositories to plan their mi ### Bundled Grafana deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.3</span> +- Announced in GitLab <span class="milestone">15.3</span> +- Removal in GitLab <span class="milestone">15.4</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6972). </div> @@ -2610,8 +2676,8 @@ This is not expected to cause any incompatibilities with the previous version of ### SAST analyzer consolidation and CI/CD template changes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.4</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352554). </div> @@ -2659,7 +2725,8 @@ If you applied customizations to any of the affected analyzers or if you current ### Vulnerability Report sort by State <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.0</span> +- Announced in GitLab <span class="milestone">15.0</span> +- Removal in GitLab <span class="milestone">15.3</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/360516). </div> @@ -2674,7 +2741,8 @@ by this value remains performant. Due to very low usage of the `State` column fo ### Vulnerability Report sort by Tool <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.1</span> +- Announced in GitLab <span class="milestone">15.1</span> +- Removal in GitLab <span class="milestone">15.3</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/362962). </div> @@ -2695,7 +2763,8 @@ GitLab 15.3 to simplify the codebase and prevent any unwanted performance degrad ### Deprecate support for Debian 9 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.1</span> </div> 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. @@ -2712,8 +2781,8 @@ Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](ht ### Audit events for repository push events <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.3</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/337993). </div> @@ -2730,8 +2799,8 @@ dramatically slow down GitLab instances. For this reason, they are being removed ### Background upload for object storage <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/26600). </div> @@ -2751,8 +2820,8 @@ GitLab will publish additional guidance to assist affected customers in migratin ### CI/CD job name length limit <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.6</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/342800). </div> @@ -2765,8 +2834,8 @@ In GitLab 15.0 we are going to limit the number of characters in CI/CD job names ### Changing an instance (shared) runner to a project (specific) runner <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345347). </div> @@ -2783,8 +2852,8 @@ Administrators who need to add runners for multiple projects can register a runn ### Container Network and Host Security <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> 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). @@ -2805,7 +2874,8 @@ For additional context, or to provide feedback regarding this change, please ref ### Container scanning schemas below 14.0.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> [Container scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -2826,7 +2896,8 @@ in the Vulnerability Report. ### Coverage guided fuzzing schemas below 14.0.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> [Coverage guided fuzzing report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -2850,7 +2921,8 @@ in the Vulnerability Report. ### DAST schemas below 14.0.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> [DAST report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -2874,8 +2946,8 @@ in the Vulnerability Report. ### Dependency Scanning Python 3.9 and 3.6 image deprecation <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/334060). </div> @@ -2906,8 +2978,8 @@ gemnasium-python-dependency_scanning: ### Dependency Scanning default Java version changed to 17 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.10</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> 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). @@ -2919,7 +2991,8 @@ In GitLab 15.0, for Dependency Scanning, the default version of Java that the sc ### Dependency scanning schemas below 14.0.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> [Dependency scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -2943,7 +3016,8 @@ in the Vulnerability Report. ### Deprecate Geo Admin UI Routes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351345). </div> @@ -2956,7 +3030,8 @@ In GitLab 13.0, we introduced new project and design replication details routes ### Deprecate custom Geo:db:* Rake tasks <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351945). </div> @@ -2988,8 +3063,8 @@ The following `geo:db:*` tasks will be replaced with their corresponding `db:*:g ### Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/262019). </div> @@ -3002,8 +3077,8 @@ The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 1 ### Elasticsearch 6.8 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/350275). </div> @@ -3020,7 +3095,8 @@ Elasticsearch 6.8 is also incompatible with Amazon OpenSearch, which we [plan to ### Enforced validation of security report schemas <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/6968). </div> @@ -3045,8 +3121,8 @@ in the Vulnerability Report. ### External status check API breaking changes <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The [external status check API](https://docs.gitlab.com/ee/api/status_checks.html) was originally implemented to @@ -3072,7 +3148,8 @@ To align with this change, API calls to list external status checks will also re ### GitLab Pages running as daemon <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> In 15.0, support for daemon mode for GitLab Pages will be removed. @@ -3084,8 +3161,8 @@ In 15.0, support for daemon mode for GitLab Pages will be removed. ### GitLab Serverless <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.3</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/configure/-/epics/6). </div> @@ -3100,7 +3177,8 @@ We decided to remove the GitLab Serverless features as they never really resonat ### Godep support in License Compliance <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/327057). </div> @@ -3116,8 +3194,8 @@ and will remove it in GitLab 15.0 ### GraphQL ID and GlobalID compatibility <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/257883). </div> @@ -3180,8 +3258,8 @@ an inline argument expression). ### GraphQL permissions change for Package settings <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The GitLab Package stage offers a Package Registry, Container Registry, and Dependency Proxy to help you manage all of your dependencies using GitLab. Each of these product categories has a variety of settings that can be adjusted using the API. @@ -3200,8 +3278,8 @@ The permissions model for GraphQL is being updated. After 15.0, users with the G ### Known host required for GitLab Runner SSH executor <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192). </div> @@ -3216,8 +3294,8 @@ In GitLab 15.0 and later, the default value for this configuration option will c ### Legacy approval status names from License Compliance API <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.6</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/335707). </div> @@ -3232,8 +3310,8 @@ If you are using our License Compliance API you should stop using the `approved` ### Legacy database configuration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.3</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/338182). </div> @@ -3250,8 +3328,8 @@ This deprecation mainly impacts users compiling GitLab from source because Omnib ### Logging in GitLab <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346485). </div> @@ -3264,7 +3342,8 @@ The logging features in GitLab allow users to install the ELK stack (Elasticsear ### Move `custom_hooks_dir` setting from GitLab Shell to Gitaly <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> 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. @@ -3276,8 +3355,8 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks. ### OAuth implicit grant <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.0</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> 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). @@ -3289,8 +3368,8 @@ The OAuth implicit grant authorization flow will be removed in our next major re ### OAuth tokens without expiration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> By default, all new applications expire access tokens after 2 hours. In GitLab 14.2 and earlier, OAuth access tokens @@ -3310,8 +3389,8 @@ tokens before GitLab 15.0 is released: ### OmniAuth Kerberos gem <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.3</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/337384). </div> @@ -3328,8 +3407,8 @@ Note that we are not deprecating the Kerberos SPNEGO integration, only the old p ### Optional enforcement of PAT expiration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351962). </div> @@ -3344,8 +3423,8 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de ### Optional enforcement of SSH expiration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351963). </div> @@ -3360,8 +3439,8 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de ### Out-of-the-box SAST support for Java 8 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352549). </div> @@ -3385,8 +3464,8 @@ If you rely on Java 8 being present in the analyzer environment, you must take a ### Outdated indices of Advanced Search migrations <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.10</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/359133). </div> @@ -3402,7 +3481,8 @@ time to remove backward compatibility for indices that have not been fully migra ### Pseudonymizer <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/219952). </div> @@ -3418,8 +3498,8 @@ It is now considered deprecated, and will be removed in GitLab 15.0. ### Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/332323). </div> @@ -3432,8 +3512,8 @@ The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTren ### Request profiling <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352488). </div> @@ -3452,8 +3532,8 @@ For more information, check the [summary section of the deprecation issue](https ### Required pipeline configurations in Premium tier <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The [required pipeline configuration](https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#required-pipeline-configuration) feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers. @@ -3470,8 +3550,8 @@ This change will also help GitLab remain consistent in its tiering strategy with ### Retire-JS Dependency Scanning tool <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/350510). </div> @@ -3486,7 +3566,8 @@ If you have explicitly excluded retire.js using DS_EXCLUDED_ANALYZERS you will n ### SAST schemas below 14.0.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> [SAST report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -3510,8 +3591,8 @@ in the Vulnerability Report. ### SAST support for .NET 2.1 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352553). </div> @@ -3542,7 +3623,8 @@ If you rely on .NET 2.1 support being present in the analyzer image by default, ### Secret Detection configuration variables deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352565). </div> @@ -3570,7 +3652,8 @@ For further details, see [the deprecation issue for this change](https://gitlab. ### Secret detection schemas below 14.0.0 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> </div> [Secret detection report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) @@ -3594,8 +3677,8 @@ in the Vulnerability Report. ### Secure and Protect analyzer images published in new location <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564). </div> @@ -3622,8 +3705,8 @@ See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564 ### Secure and Protect analyzer major version update <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/350936). </div> @@ -3667,8 +3750,8 @@ Specifically, the following are being deprecated and will no longer be updated a ### Sidekiq metrics and health checks configuration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/347509). </div> @@ -3699,7 +3782,8 @@ to serve the Sidekiq metrics, similar to the way Sidekiq will behave in 15.0. ### Static Site Editor <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/347137). </div> @@ -3714,8 +3798,8 @@ Current users of the Static Site Editor can view the [documentation](https://doc ### Support for SLES 12 SP2 <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> 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. @@ -3727,8 +3811,8 @@ Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 ### Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> Although not recommended or documented, it was possible to deploy a gRPC-aware proxy between Gitaly and @@ -3750,8 +3834,8 @@ the [relevant epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463). ### Test coverage project CI/CD setting <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> To simplify setting a test coverage pattern, in GitLab 15.0 the @@ -3768,8 +3852,8 @@ testing coverage results in merge requests. ### Tracing in GitLab <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346540). </div> @@ -3782,8 +3866,8 @@ Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distr ### Update to the Container Registry group-level API <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/336912). </div> @@ -3798,8 +3882,8 @@ The `GET /groups/:id/registry/repositories` endpoint will remain, but won't retu ### Value Stream Analytics filtering calculation change <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343210). </div> @@ -3814,8 +3898,8 @@ If you monitor Value Stream Analytics metrics and rely on the date filter, to av ### Vulnerability Check <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The vulnerability check feature is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. We encourage you to migrate to the new security approvals feature instead. You can do so by navigating to **Security & Compliance > Policies** and creating a new Scan Result Policy. @@ -3834,8 +3918,8 @@ The new security approvals feature is similar to vulnerability check. For exampl ### `Versions` on base `PackageType` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/327453). </div> @@ -3850,8 +3934,8 @@ In milestone 15.0, we will completely remove `Version` from `PackageType`. ### `artifacts:reports:cobertura` keyword <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.7</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/348980). </div> @@ -3867,8 +3951,8 @@ only supported report file in 15.0, but this is the first step towards GitLab su ### `defaultMergeCommitMessageWithDescription` GraphQL API field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345451). </div> @@ -3881,8 +3965,8 @@ The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprec ### `dependency_proxy_for_private_groups` feature flag <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/276777). </div> @@ -3897,8 +3981,8 @@ In milestone 15.0, we will remove the feature flag entirely. Moving forward, you ### `pipelines` field from the `version` field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/342882). </div> @@ -3916,8 +4000,8 @@ To mitigate possible performance problems, we will remove the `versions` field's ### `projectFingerprint` in `PipelineSecurityReportFinding` GraphQL <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The `projectFingerprint` field in the [PipelineSecurityReportFinding](https://docs.gitlab.com/ee/api/graphql/reference/index.html#pipelinesecurityreportfinding) @@ -3932,8 +4016,8 @@ exposed in the UUID field. Data previously available in the projectFingerprint f ### `promote-db` command from `gitlab-ctl` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345207). </div> @@ -3946,8 +4030,8 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge ### `promote-to-primary-node` command from `gitlab-ctl` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345207). </div> @@ -3960,8 +4044,8 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge ### `type` and `types` keyword in CI/CD configuration <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.6</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> 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. @@ -3973,8 +4057,8 @@ The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines ### apiFuzzingCiConfigurationCreate GraphQL mutation <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.6</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/333233). </div> @@ -3989,8 +4073,8 @@ which isn't being used in GitLab anymore. ### bundler-audit Dependency Scanning tool <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.6</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/289832). </div> @@ -4005,8 +4089,8 @@ If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you wi ### htpasswd Authentication for the Container Registry <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`. @@ -4020,8 +4104,8 @@ Since it isn't used in the context of GitLab (the product), `htpasswd` authentic ### user_email_lookup_limit API field <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">15.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The `user_email_lookup_limit` [API field](https://docs.gitlab.com/ee/api/settings.html) is deprecated and will be removed in GitLab 15.0. Until GitLab 15.0, `user_email_lookup_limit` is aliased to `search_rate_limit` and existing workflows will continue to work. @@ -4040,8 +4124,8 @@ Any API calls attempting to change the rate limits for `user_email_lookup_limit` ### Permissions change for downloading Composer dependencies <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). +- Announced in GitLab <span class="milestone">14.9</span> +- Removal in GitLab <span class="milestone">14.10</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) </div> The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies. @@ -4060,7 +4144,8 @@ Downloading Composer dependencies without authentication is deprecated in GitLab ### Configurable Gitaly `per_repository` election strategy <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.8</span> +- Announced in GitLab <span class="milestone">14.8</span> +- Removal in GitLab <span class="milestone">14.9</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352612). </div> @@ -4081,7 +4166,8 @@ This change is part of regular maintenance to keep our codebase clean. ### openSUSE Leap 15.2 packages <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.5</span> +- Announced in GitLab <span class="milestone">14.5</span> +- Removal in GitLab <span class="milestone">14.8</span> - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6427). </div> @@ -4101,7 +4187,8 @@ Starting in 14.5 we are providing packages for openSUSE Leap 15.3, and will stop ### Release CLI distributed as a generic package <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.2</span> +- Announced in GitLab <span class="milestone">14.2</span> +- Removal in GitLab <span class="milestone">14.6</span> </div> 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. @@ -4118,7 +4205,8 @@ The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as ### Rename Task Runner pod to Toolbox <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">14.2</span> +- Announced in GitLab <span class="milestone">14.2</span> +- Removal in GitLab <span class="milestone">14.5</span> </div> The Task Runner pod is used to execute periodic housekeeping tasks within the GitLab application and is often confused with the GitLab Runner. Thus, [Task Runner will be renamed to Toolbox](https://gitlab.com/groups/gitlab-org/charts/-/epics/25). diff --git a/doc/update/index.md b/doc/update/index.md index ced7ed86691..5a0fd0bdf31 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -16,7 +16,7 @@ The [maintenance policy documentation](../policy/maintenance.md) has additional information about upgrading, including: - How to interpret GitLab product versioning. -- Recommendations on the what release to run. +- Recommendations on what release to run. - How we use patch and security patch releases. - When we backport code changes. @@ -25,12 +25,12 @@ has additional information about upgrading, including: Depending on the installation method and your GitLab version, there are multiple official ways to upgrade GitLab: -- [Linux packages (Omnibus GitLab)](#linux-packages-omnibus-gitlab) -- [Source installations](#installation-from-source) +- [Linux packages (Omnibus)](#linux-packages-omnibus) +- [Self-compiled installations](#self-compiled-installation) - [Docker installations](#installation-using-docker) - [Kubernetes (Helm) installations](#installation-using-helm) -### Linux packages (Omnibus GitLab) +### Linux packages (Omnibus) The [package upgrade guide](package/index.md) contains the steps needed to upgrade a package installed by official GitLab @@ -39,7 +39,7 @@ repositories. There are also instructions when you want to [upgrade to a specific version](package/index.md#upgrade-to-a-specific-version-using-the-official-repositories). -### Installation from source +### Self-compiled installation - [Upgrading Community Edition and Enterprise Edition from source](upgrading_from_source.md) - The guidelines for upgrading Community Edition and Enterprise Edition from source. @@ -114,21 +114,25 @@ This section is only applicable if you have enabled the [Elasticsearch integrati Major releases require all [advanced search migrations](../integration/advanced_search/elasticsearch.md#advanced-search-migrations) to be finished from the most recent minor release in your current version before the major version upgrade. You can find pending migrations by -running the following command: +running the following command. -**For Omnibus installations** +::Tabs + +:::TabTitle Linux package (Omnibus) ```shell sudo gitlab-rake gitlab:elastic:list_pending_migrations ``` -**For installations from source** +:::TabTitle Self-compiled (source) ```shell cd /home/git/gitlab sudo -u git -H bundle exec rake gitlab:elastic:list_pending_migrations ``` +::EndTabs + ### What do you do if your advanced search migrations are stuck? In GitLab 15.0, an advanced search migration named `DeleteOrphanedCommit` can be permanently stuck @@ -176,30 +180,21 @@ A *major* upgrade requires the following steps: Upgrading across multiple GitLab versions in one go is *only possible by accepting downtime*. If you don't want any downtime, read how to [upgrade with zero downtime](zero_downtime.md). -For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). +For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) +maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share +feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). -Required upgrade stops are versions of GitLab that you must upgrade to before upgrading to later versions. Required upgrade stops allow required background -migrations to finish. +When upgrading: -During GitLab 16.x, we are scheduling two or three required upgrade stops. We will give at least two milestones of notice when we -schedule a required upgrade stop. +1. Find where your version sits in the upgrade path: -The first planned required upgrade stop is scheduled for GitLab 16.3. If nothing is introduced requiring an upgrade stop, GitLab 16.3 will be treated as a -regular upgrade. + - GitLab 14: [`14.0.12`](#1400) > [`14.3.6`](#1430) > [`14.9.5`](#1490) > [`14.10.5`](#14100). + - GitLab 15: [`15.0.5`](#1500) > [`15.1.6`](#1510) (for GitLab instances with multiple web nodes) > [`15.4.6`](#1540) > [`15.11.13`](#15110). + - GitLab 16: [`16.0.x`](versions/gitlab_16_changes.md#1600) (only [instances with lots of users](versions/gitlab_16_changes.md#long-running-user-type-data-change)) > [latest `16.Y.Z`](https://gitlab.com/gitlab-org/gitlab/-/releases). -Find where your version sits in the upgrade path below, and upgrade GitLab -accordingly, while also consulting the -[version-specific upgrade instructions](#version-specific-upgrading-instructions): - -- GitLab 8: `8.11.Z` > `8.12.0` > `8.17.7` -- GitLab 9: `9.0.13` > `9.5.10` -- GitLab 10: `10.0.7` > `10.8.7` -- GitLab 11: `11.0.6` > [`11.11.8`](#1200) -- GitLab 12: `12.0.12` > [`12.1.17`](#1210) > [`12.10.14`](#12100) -- GitLab 13: `13.0.14` > [`13.1.11`](#1310) > [`13.8.8`](#1388) > [`13.12.15`](#13120) -- GitLab 14: [`14.0.12`](#1400) > [`14.3.6`](#1430) > [`14.9.5`](#1490) > [`14.10.5`](#14100) -- GitLab 15: [`15.0.5`](#1500) > [`15.1.6`](#1510) (for GitLab instances with multiple web nodes) > [`15.4.6`](#1540) > [`15.11.x`](#15110) -- GitLab 16: [latest `16.Y.Z`](https://gitlab.com/gitlab-org/gitlab/-/releases) +1. Check for [required upgrade stops](#required-upgrade-stops). +1. Consult the [version-specific upgrade instructions](#version-specific-upgrading-instructions). +1. Upgrade GitLab accordingly. NOTE: When not explicitly specified, upgrade GitLab to the latest available patch @@ -209,6 +204,25 @@ be fixes for issues relating to the upgrade process. Specifically around a [major version](#upgrading-to-a-new-major-version), crucial database schema and migration patches may be included in the latest patch releases. +### Required upgrade stops + +Required upgrade stops are versions of GitLab that you must upgrade to before upgrading to later versions. Required +upgrade stops allow required background migrations to finish. + +During GitLab 16.x, we are scheduling two or three required upgrade stops. We will give at least two milestones of +notice when we schedule a required upgrade stop. + +The first planned required upgrade stop is scheduled for GitLab 16.3. If nothing is introduced requiring an upgrade stop, +GitLab 16.3 will be treated as a regular upgrade. + +### Earlier GitLab versions + +For information on upgrading to earlier GitLab versions, see the [documentation archives](https://archives.docs.gitlab.com). +The versions of the documentation in the archives contain version-specific information for even earlier versions of GitLab. + +For example, the [documentation for GitLab 15.11](https://archives.docs.gitlab.com/15.11/ee/update/#upgrade-paths) +contains information on versions back to GitLab 12. + ## Upgrading between editions GitLab comes in two flavors: [Community Edition](https://about.gitlab.com/features/#community) which is MIT licensed, @@ -271,42 +285,9 @@ NOTE: Specific information that follow related to Ruby and Git versions do not apply to [Omnibus installations](https://docs.gitlab.com/omnibus/) and [Helm Chart deployments](https://docs.gitlab.com/charts/). They come with appropriate Ruby and Git versions and are not using system binaries for Ruby and Git. There is no need to install Ruby or Git when utilizing these two approaches. -### 16.1.0 - -- A `MigrateHumanUserType` background migration will be finalized with - the `FinalizeUserTypeMigration` migration. - GitLab 16.0 introduced a [batched background migration](background_migrations.md#batched-background-migrations) to - [migrate `user_type` values from `NULL` to `0`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115849). This - migration may take multiple days to complete on larger GitLab instances. Make sure the migration - has completed successfully before upgrading to 16.1.0. -- A `BackfillPreparedAtMergeRequests` background migration will be finalized with - the `FinalizeBackFillPreparedAtMergeRequests` post-deploy migration. - GitLab 15.10.0 introduced a [batched background migration](background_migrations.md#batched-background-migrations) to - [backfill `prepared_at` values on the `merge_requests` table](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111865). This - migration may take multiple days to complete on larger GitLab instances. Make sure the migration - has completed successfully before upgrading to 16.1.0. -- Geo: Some project imports do not initialize wiki repositories on project creation. Since the migration of project wikis to SSF, [missing wiki repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/409704). This is not a result of an actual replication/verification failure but an invalid internal state for these missing repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for these wiki repositories. If you have not imported projects you are not impacted by this issue. - - Impacted versions: GitLab versions 15.11.x, 16.0.x, and 16.1.0 - 16.1.2. - - Versions containing fix: GitLab 16.1.3 and later. -- Geo: Since the migration of project designs to SSF, [missing design repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/414279). This is not a result of an actual replication/verification failure but an invalid internal state for these missing repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for these design repositories. You could be impacted by this issue even if you have not imported projects. - - Impacted versions: GitLab versions 16.1.x. - - Versions containing fix: GitLab 16.2.0 and later. -- For self-compiled installations: You must remove any settings related to Puma worker killer from the `puma.rb` configuration file, since those have been [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/118645). For more information, see the [`puma.rb.example`](https://gitlab.com/gitlab-org/gitlab/-/blob/16-0-stable-ee/config/puma.rb.example) file. - -### 16.0.0 - -- Sidekiq crashes if there are non-ASCII characters in the GitLab.rb file. You can fix this - by following the workaround in [issue 412767](https://gitlab.com/gitlab-org/gitlab/-/issues/412767#note_1404507549). -- Sidekiq jobs are only routed to `default` and `mailers` queues by default, and as a result, - every Sidekiq process also listens to those queues to ensure all jobs are processed across - all queues. This behavior does not apply if you have configured the [routing rules](../administration/sidekiq/processing_specific_job_classes.md#routing-rules). -- Docker 20.10.10 or later is required to run the GitLab Docker image. Older versions - [throw errors on startup](../install/docker.md#threaderror-cant-create-thread-operation-not-permitted). -- Geo: Some project imports do not initialize wiki repositories on project creation. Since the migration of project wikis to SSF, [missing wiki repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/409704). This is not a result of an actual replication/verification failure but an invalid internal state for these missing repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for these wiki repositories. If you have not imported projects you are not impacted by this issue. - - Impacted versions: GitLab versions 15.11.x, 16.0.x, and 16.1.0 - 16.1.2. - - Versions containing fix: GitLab 16.1.3 and later. -- Starting with 16.0, GitLab self-managed installations now have two database connections by default, instead of one. This change doubles the number of PostgreSQL connections. It makes self-managed versions of GitLab behave similarly to GitLab.com, and is a step toward enabling a separate database for CI features for self-managed versions of GitLab. Before upgrading to 16.0, determine if you need to [increase max connections for PostgreSQL](https://docs.gitlab.com/omnibus/settings/database.html#configuring-multiple-database-connections). - - This change applies to installation methods with Linux packages (Omnibus GitLab), GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source. +### GitLab 16 + +Before upgrading, see [GitLab 16 changes](versions/gitlab_16_changes.md). ### 15.11.1 @@ -318,28 +299,42 @@ and [Helm Chart deployments](https://docs.gitlab.com/charts/). They come with ap - Versions containing fix: GitLab 16.1.3 and later. - Geo: A [bug](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7841) in the built-in `pg-upgrade` tool prevents upgrading the bundled PostgreSQL database to version 13. This leaves the secondary site in a broken state, and prevents upgrading the Geo installation to GitLab 16.x ([PostgreSQL 12 support has removed in 16.0](deprecations.md#postgresql-12-deprecated) and later releases). This occurs on secondary sites using the bundled PostgreSQL software, running both the secondary main Rails database and tracking database on the same node. There is a manual [workaround](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7841#workaround) for those impacted until a fix is backported to 15.11. - Impacted versions: GitLab versions 15.2 - 15.11 + - Versions containing fix: 15.11.12 and later. - Version 16.0 and later are not impacted. Note, 15.11 is a mandatory upgrade stop on the way to 16.0. ### 15.11.0 -- Upgrades to GitLab 15.11 directly from GitLab versions 15.5.0 and earlier on self-managed installs will fail due to a missing migration until the fix for [issue 408304](https://gitlab.com/gitlab-org/gitlab/-/issues/408304) is released in version 15.11.3. Affected users wanting to upgrade to 15.11 can either: - - Perform an intermediate upgrade to any version between 15.5 and 15.10 before upgrading to 15.11, or - - Target version 15.11.3 or later. +- **Upgrade to patch release 15.11.3 or later**. This avoids [issue 408304](https://gitlab.com/gitlab-org/gitlab/-/issues/408304) when upgrading from 15.5.0 and earlier. - Geo: Some project imports do not initialize wiki repositories on project creation. Since the migration of project wikis to SSF, [missing wiki repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/409704). This is not a result of an actual replication/verification failure but an invalid internal state for these missing repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for these wiki repositories. If you have not imported projects you are not impacted by this issue. - Impacted versions: GitLab versions 15.11.x, 16.0.x, and 16.1.0 - 16.1.2. - Versions containing fix: GitLab 16.1.3 and later. - Geo: A [bug](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7841) in the built-in `pg-upgrade` tool prevents upgrading the bundled PostgreSQL database to version 13. This leaves the secondary site in a broken state, and prevents upgrading the Geo installation to GitLab 16.x ([PostgreSQL 12 support has removed in 16.0](deprecations.md#postgresql-12-deprecated) and later releases). This occurs on secondary sites using the bundled PostgreSQL software, running both the secondary main Rails database and tracking database on the same node. There is a manual [workaround](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7841#workaround) for those impacted until a fix is backported to 15.11. - - Impacted versions: GitLab versions 15.2 - 15.11 + - Impacted versions: GitLab versions 15.2 - 15.11.11. + - Versions containing fix: 15.11.12 and later. - Version 16.0 and later are not impacted. Note, 15.11 is a mandatory upgrade stop on the way to 16.0. +### 15.11.x + +- A [bug](https://gitlab.com/gitlab-org/gitlab/-/issues/411604) can cause new LDAP users signing in for the first time to be assigned a username based on their email address instead of their LDAP username attribute. A manual workaround is to set `gitlab_rails['omniauth_auto_link_ldap_user'] = true`, or upgrade to GitLab 16.1 or later where the bug has been fixed. + ### 15.10.5 +- A [bug with Elastic Indexer Cron Workers](https://gitlab.com/gitlab-org/gitlab/-/issues/408214) can cause saturation in Sidekiq. + - When this issue occurs, merge request merges, pipelines, Slack notifications, and other events are not created or take a long time to occur. + - This issue may not manifest immediately as it can take up to a week before the Sidekiq is saturated enough. + - Elasticsearch does not need to be enabled for this to occur. + - To resolve this issue, upgrade to 15.11 or use the workaround in the issue. - Many [project importers](../user/project/import/index.md) and [group importers](../user/group/import/index.md) now require the Maintainer role instead of only requiring the Developer role. For more information, see the documentation for any importers you use. ### 15.10.0 +- A [bug with Elastic Indexer Cron Workers](https://gitlab.com/gitlab-org/gitlab/-/issues/408214) can cause saturation in Sidekiq. + - When this issue occurs, merge request merges, pipelines, Slack notifications, and other events are not created or take a long time to occur. + - This issue may not manifest immediately as it can take up to a week before the Sidekiq is saturated enough. + - Elasticsearch does not need to be enabled for this to occur. + - To resolve this issue, upgrade to 15.11 or use the workaround in the issue. - Gitaly configuration changes significantly in Omnibus GitLab 16.0. You can begin migrating to the new structure in Omnibus GitLab 15.10 while backwards compatibility is maintained in the lead up to Omnibus GitLab 16.0. [Read more about this change](#gitaly-omnibus-gitlab-configuration-structure-change). - You might encounter the following error while upgrading to GitLab 15.10 or later: @@ -390,6 +385,11 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ ### 15.9.0 +- A [bug with Elastic Indexer Cron Workers](https://gitlab.com/gitlab-org/gitlab/-/issues/408214) can cause saturation in Sidekiq. + - When this issue occurs, merge request merges, pipelines, Slack notifications, and other events are not created or take a long time to occur. + - This issue may not manifest immediately as it can take up to a week before the Sidekiq is saturated enough. + - Elasticsearch does not need to be enabled for this to occur. + - To resolve this issue, upgrade to 15.11 or use the workaround in the issue. - **Upgrade to patch release 15.9.3 or later**. This provides fixes for two database migration bugs: - Patch releases 15.9.0, 15.9.1, 15.9.2 have [a bug that can cause data loss](#user-profile-data-loss-bug-in-159x) from the user profile fields. - The second [bug fix](https://gitlab.com/gitlab-org/gitlab/-/issues/394760) ensures it is possible to upgrade directly from 15.4.x. @@ -417,65 +417,65 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ ### 15.8.2 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. ### 15.8.1 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.8.0 -- Git 2.38.0 and later is required by Gitaly. For installations from source, you should use the [Git version provided by Gitaly](../install/installation.md#git). +- Git 2.38.0 and later is required by Gitaly. For self-compiled installations, you should use the [Git version provided by Gitaly](../install/installation.md#git). - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. ### 15.7.6 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.7.5 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.7.4 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.7.3 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.7.2 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the upgrades. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the upgrades. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.7.1 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. @@ -510,8 +510,8 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ For example, previously: - - Omnibus GitLab default (`sidekiq['max_concurrency']`): 50 - - From source installation default: 50 + - Linux package installation default (`sidekiq['max_concurrency']`): 50 + - Self-compiled installation default: 50 - Helm chart default (`gitlab.sidekiq.concurrency`): 25 Reference architectures still use a default of 10 as this is set specifically @@ -519,7 +519,7 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ Sites that have configured `max_concurrency` will not be affected by this change. [Read more about the Sidekiq concurrency setting](../administration/sidekiq/extra_sidekiq_processes.md#concurrency). -- GitLab Runner 15.7.0 introduced a breaking change that impacts CI/CD jobs: [Correctly handle expansion of job file variables](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3613). +- GitLab Runner 15.7.0 introduced a breaking change that affects CI/CD jobs: [Correctly handle expansion of job file variables](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3613). Previously, job-defined variables that referred to [file type variables](../ci/variables/index.md#use-file-type-cicd-variables) were expanded to the value of the file variable (its content). This behavior did not @@ -527,71 +527,71 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ that secrets or sensitive information could leak if the file variable and its contents printed. For example, if they were printed in an echo output. For more information, see [Understanding the file type variable expansion change in GitLab 15.7](https://about.gitlab.com/blog/2023/02/13/impact-of-the-file-type-variable-change-15-7/). -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. ### 15.6.7 - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.6 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.5 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.4 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6, and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6, and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.3 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.2 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.1 -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. ### 15.6.0 - You should use one of the [officially supported PostgreSQL versions](../administration/package_information/postgresql_versions.md). Some database migrations can cause stability and performance issues with older PostgreSQL versions. -- Git 2.37.0 and later is required by Gitaly. For installations from source, we recommend you use the [Git version provided by Gitaly](../install/installation.md#git). +- Git 2.37.0 and later is required by Gitaly. For self-compiled installations, you should use the [Git version provided by Gitaly](../install/installation.md#git). - A database change to modify the behavior of four indexes fails on instances where these indexes do not exist: @@ -606,9 +606,9 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ This issue was [fixed in GitLab 15.7](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/105375) and backported to GitLab 15.6.2. The issue can also be worked around: [read about how to create these indexes](https://gitlab.com/gitlab-org/gitlab/-/issues/378343#note_1199863087). -- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This impacts versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. +- Geo: [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - Geo: We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - - Impacted versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. + - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. - Versions containing fix: GitLab 15.8.3 and later. - Due to [a bug introduced in GitLab 15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/390155), if one or more Git repositories in Gitaly Cluster is [unavailable](../administration/gitaly/recovery.md#unavailable-repositories), then [Repository checks](../administration/repository_checks.md#repository-checks) and [Geo replication and verification](../administration/geo/index.md) stop running for all project or project wiki repositories in the affected Gitaly Cluster. The bug was fixed by [reverting the change in GitLab 15.9.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110823). Before upgrading to this version, check if you have any "unavailable" repositories. See [the bug issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390155) for more information. @@ -689,7 +689,7 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ - A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. - - Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: + - Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -699,7 +699,7 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ - A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. - - Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: + - Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -742,7 +742,7 @@ For more information, see [issue 415724](https://gitlab.com/gitlab-org/gitlab/-/ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. -- Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: +- Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -754,7 +754,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) - A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. - - Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: + - Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -764,7 +764,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. -- Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: +- Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -774,7 +774,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. -- Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: +- Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -788,7 +788,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) - A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. - - Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: + - Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -798,7 +798,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) prevents some premium features of GitLab from working correctly if you add a new license. Workarounds for this issue: - Restart all Rails, Sidekiq and Gitaly nodes after applying a new license. This clears the relevant license caches and allows all premium features to operate correctly. -- Upgrade to a version that is not impacted by this issue. The following upgrade paths are available for impacted versions: +- Upgrade to a version that is not affected by this issue. The following upgrade paths are available for affected versions: - 15.2.5 --> 15.3.5 - 15.3.0 - 15.3.4 --> 15.3.5 - 15.4.1 --> 15.4.3 @@ -837,6 +837,14 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) 1. Ensure all GitLab web nodes are running GitLab 15.1.Z. 1. [Enable the `active_support_hash_digest_sha256` feature flag](../administration/feature_flags.md#how-to-enable-and-disable-features-behind-flags) to switch `ActiveSupport::Digest` to use SHA256: + + 1. [Start the rails console](../administration/operations/rails_console.md) + 1. Enable the feature flag: + + ```ruby + Feature.enable(:active_support_hash_digest_sha256) + ``` + 1. Only then, continue to upgrade to later versions of GitLab. - Unauthenticated requests to the [`ciConfig` GraphQL field](../api/graphql/reference/index.md#queryciconfig) are no longer supported. Before you upgrade to GitLab 15.1, add an [access token](../api/rest/index.md#authentication) to your requests. @@ -1036,7 +1044,7 @@ that may remain stuck permanently in a **pending** state. ### 14.5.0 - When `make` is run, Gitaly builds are now created in `_build/bin` and no longer in the root directory of the source directory. If you -are using a source install, update paths to these binaries in your [systemd unit files](upgrading_from_source.md#configure-systemd-units) +are using a self-compiled installation, update paths to these binaries in your [systemd unit files](upgrading_from_source.md#configure-systemd-units) or [init scripts](upgrading_from_source.md#configure-sysv-init-script) by [following the documentation](upgrading_from_source.md). - Connections between Workhorse and Gitaly use the Gitaly `backchannel` protocol by default. If you deployed a gRPC proxy between Workhorse and Gitaly, @@ -1369,8 +1377,6 @@ Other issues: **GitLab 13.2 or older** directly to 14.0, this is [unsupported](#upgrading-to-a-new-major-version). You should instead follow a [supported upgrade path](#upgrade-paths). - See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-gitlab-139-to-144). -- See [Custom Rack Attack initializers](#custom-rack-attack-initializers) if you persist your own custom Rack Attack - initializers during upgrades. #### Upgrading to later 14.Y releases @@ -1382,263 +1388,6 @@ Other issues: 1. [Batched background migrations must finish](background_migrations.md#batched-background-migrations) before you upgrade to a later version [and may take longer than usual](#1400). -### 13.12.0 - -- See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-gitlab-139-to-144). - -- Check the GitLab database [has no references to legacy storage](../administration/raketasks/storage.md#on-legacy-storage). - The GitLab 14.0 pre-install check causes the package update to fail if unmigrated data exists: - - ```plaintext - Checking for unmigrated data on legacy storage - - Legacy storage is no longer supported. Please migrate your data to hashed storage. - ``` - -### 13.11.0 - -- Git 2.31.x and later is required. We recommend you use the - [Git version provided by Gitaly](../install/installation.md#git). - -- See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-gitlab-139-to-144). - -- GitLab 13.11 includes a faulty background migration ([`RescheduleArtifactExpiryBackfillAgain`](https://gitlab.com/gitlab-org/gitlab/-/blob/ccc70031b843ff8cff1185988c2e472a521c2701/db/post_migrate/20210413132500_reschedule_artifact_expiry_backfill_again.rb)) - that incorrectly sets the `expire_at` column in the `ci_job_artifacts` database table. - Incorrect `expire_at` values can potentially cause data loss. - - To prevent this risk of data loss, you must remove the content of the `RescheduleArtifactExpiryBackfillAgain` - migration, which makes it a no-op migration. You can repeat the changes from the - [commit that makes the migration no-op in 14.9 and later](https://gitlab.com/gitlab-org/gitlab/-/blob/42c3dfc5a1c8181767bbb5c76e7c5fa6fefbbc2b/db/post_migrate/20210413132500_reschedule_artifact_expiry_backfill_again.rb). - For more information, see [how to disable a data migration](../development/database/deleting_migrations.md#how-to-disable-a-data-migration). - -### 13.10.0 - -See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-gitlab-139-to-144). - -### 13.9.0 - -- We've detected an issue [with a column rename](https://gitlab.com/gitlab-org/gitlab/-/issues/324160) - that prevents upgrades to GitLab 13.9.0, 13.9.1, 13.9.2, and 13.9.3 when following the zero-downtime steps. It is necessary - to perform the following additional steps for the zero-downtime upgrade: - - 1. Before running the final `sudo gitlab-rake db:migrate` command on the deploy node, - execute the following queries using the PostgreSQL console (or `sudo gitlab-psql`) - to drop the problematic triggers: - - ```sql - drop trigger trigger_e40a6f1858e6 on application_settings; - drop trigger trigger_0d588df444c8 on application_settings; - drop trigger trigger_1572cbc9a15f on application_settings; - drop trigger trigger_22a39c5c25f3 on application_settings; - ``` - - 1. Run the final migrations: - - ```shell - sudo gitlab-rake db:migrate - ``` - - If you have already run the final `sudo gitlab-rake db:migrate` command on the deploy node and have - encountered the [column rename issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324160), you - see the following error: - - ```shell - -- remove_column(:application_settings, :asset_proxy_whitelist) - rake aborted! - StandardError: An error has occurred, all later migrations canceled: - PG::DependentObjectsStillExist: ERROR: cannot drop column asset_proxy_whitelist of table application_settings because other objects depend on it - DETAIL: trigger trigger_0d588df444c8 on table application_settings depends on column asset_proxy_whitelist of table application_settings - ``` - - To work around this bug, follow the previous steps to complete the upgrade. - More details are available [in this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324160). - -- See [Maintenance mode issue in GitLab 13.9 to 14.4](#maintenance-mode-issue-in-gitlab-139-to-144). - -- For GitLab Enterprise Edition customers, we noticed an issue when [subscription expiration is upcoming, and you create new subgroups and projects](https://gitlab.com/gitlab-org/gitlab/-/issues/322546). If you fall under that category and get 500 errors, you can work around this issue: - - 1. SSH into you GitLab server, and open a Rails console: - - ```shell - sudo gitlab-rails console - ``` - - 1. Disable the following features: - - ```ruby - Feature.disable(:subscribable_subscription_banner) - Feature.disable(:subscribable_license_banner) - ``` - - 1. Restart Puma or Unicorn: - - ```shell - #For installations using Puma - sudo gitlab-ctl restart puma - - #For installations using Unicorn - sudo gitlab-ctl restart unicorn - ``` - -### 13.8.8 - -GitLab 13.8 includes a background migration to address [an issue with duplicate service records](https://gitlab.com/gitlab-org/gitlab/-/issues/290008). If duplicate services are present, this background migration must complete before a unique index is applied to the services table, which was [introduced in GitLab 13.9](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52563). Upgrades from GitLab 13.8 and earlier to later versions must include an intermediate upgrade to GitLab 13.8.8 and [must wait until the background migrations complete](background_migrations.md) before proceeding. - -If duplicate services are still present, an upgrade to 13.9.x or later results in a failed upgrade with the following error: - -```console -PG::UniqueViolation: ERROR: could not create unique index "index_services_on_project_id_and_type_unique" -DETAIL: Key (project_id, type)=(NNN, ServiceName) is duplicated. -``` - -### 13.6.0 - -Ruby 2.7.2 is required. GitLab does not start with Ruby 2.6.6 or older versions. - -The required Git version is Git v2.29 or later. - -GitLab 13.6 includes a -[background migration `BackfillJiraTrackerDeploymentType2`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46368) -that may remain stuck permanently in a **pending** state despite completion of work -due to a bug. - -To clean up this stuck job, run the following in the [GitLab Rails Console](../administration/operations/rails_console.md): - -```ruby -Gitlab::Database::BackgroundMigrationJob.pending.where(class_name: "BackfillJiraTrackerDeploymentType2").find_each do |job| - puts Gitlab::Database::BackgroundMigrationJob.mark_all_as_succeeded("BackfillJiraTrackerDeploymentType2", job.arguments) -end -``` - -### 13.4.0 - -GitLab 13.4.0 includes a background migration to [move all remaining repositories in legacy storage to hashed storage](../administration/raketasks/storage.md#migrate-to-hashed-storage). There are [known issues with this migration](https://gitlab.com/gitlab-org/gitlab/-/issues/259605) which are fixed in GitLab 13.5.4 and later. If possible, skip 13.4.0 and upgrade to 13.5.4 or later instead. The migration can take quite a while to run, depending on how many repositories must be moved. Be sure to check that all background migrations have completed before upgrading further. - -### 13.3.0 - -The recommended Git version is Git v2.28. The minimum required version of Git -v2.24 remains the same. - -### 13.2.0 - -GitLab installations that have multiple web nodes must be -[upgraded to 13.1](#1310) before upgrading to 13.2 (and later) due to a -breaking change in Rails that can result in authorization issues. - -GitLab 13.2.0 [remediates](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35492) an [email verification bypass](https://about.gitlab.com/releases/2020/05/27/security-release-13-0-1-released/). -After upgrading, if some of your users are unexpectedly encountering 404 or 422 errors when signing in, -or "blocked" messages when using the command line, -their accounts may have been un-confirmed. -In that case, ask them to check their email for a re-confirmation link. -For more information, see our discussion of [Email confirmation issues](../user/upgrade_email_bypass.md). - -GitLab 13.2.0 relies on the `btree_gist` extension for PostgreSQL. For installations with an externally managed PostgreSQL setup, make sure to -[install the extension manually](https://www.postgresql.org/docs/11/sql-createextension.html) before upgrading GitLab if the database user for GitLab -is not a superuser. This is not necessary for installations using a GitLab managed PostgreSQL database. - -### 13.1.0 - -In 13.1.0, you must upgrade to either: - -- At least Git v2.24 (previously, the minimum required version was Git v2.22). -- The recommended Git v2.26. - -Failure to do so results in internal errors in the Gitaly service in some RPCs due -to the use of the new `--end-of-options` Git flag. - -Additionally, in GitLab 13.1.0, the version of -[Rails was upgraded from 6.0.3 to 6.0.3.1](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33454). -The Rails upgrade included a change to CSRF token generation which is -not backwards-compatible - GitLab servers with the new Rails version -generate CSRF tokens that are not recognizable by GitLab servers -with the older Rails version - which could cause non-GET requests to -fail for [multi-node GitLab installations](zero_downtime.md#multi-node--ha-deployment). - -So, if you are using multiple Rails servers and specifically upgrading from 13.0, -all servers must first be upgraded to 13.1.Z before upgrading to 13.2.0 or later: - -1. Ensure all GitLab web nodes are running GitLab 13.1.Z. -1. Enable the `global_csrf_token` feature flag to enable new - method of CSRF token generation: - - ```ruby - Feature.enable(:global_csrf_token) - ``` - -1. Only then, continue to upgrade to later versions of GitLab. - -#### Custom Rack Attack initializers - -From GitLab 13.1, custom Rack Attack initializers (`config/initializers/rack_attack.rb`) are replaced with initializers -supplied with GitLab during upgrades. You should use these GitLab-supplied initializers. - -If you persist your own Rack Attack initializers between upgrades, you might -[get `500` errors](https://gitlab.com/gitlab-org/gitlab/-/issues/334681) when [upgrading to GitLab 14.0 and later](#1400). - -For **self-compiled (source) installations**, the Rack Attack initializer on GitLab -was renamed from [`config/initializers/rack_attack_new.rb` to `config/initializers/rack_attack.rb`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33072). -The rename was part of [deprecating Rack Attack throttles on Omnibus GitLab](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4750). - -If `rack_attack.rb` has been created on your installation, consider creating a backup before updating: - -```shell -cd /home/git/gitlab -cp config/initializers/rack_attack.rb config/initializers/rack_attack_backup.rb -``` - -### 12.10.0 - -- The final patch release (12.10.14) - [has a regression affecting maven package uploads](https://about.gitlab.com/releases/2020/07/06/critical-security-release-gitlab-13-1-3-released/#maven-package-upload-broken-in-121014). - If you use this feature and must stay on 12.10 while preparing to upgrade to 13.0: - - - Upgrade to 12.10.13 instead. - - Upgrade to 13.0.14 as soon as possible. - -- [GitLab 13.0 requires PostgreSQL 11](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/#postgresql-11-is-now-the-minimum-required-version-to-install-gitlab). - - - 12.10 is the final release that shipped with PostgreSQL 9.6, 10, and 11. - - You should make sure that your database is PostgreSQL 11 on GitLab 12.10 before upgrading to 13.0. This upgrade requires downtime. - -### 12.2.0 - -In 12.2.0, we enabled Rails' authenticated cookie encryption. Old sessions are -automatically upgraded. - -However, session cookie downgrades are not supported. So after upgrading to 12.2.0, -any downgrades would result to all sessions being invalidated and users are logged out. - -### 12.1.0 - -- If you are planning to upgrade from `12.0.Z` to `12.10.Z`, it is necessary to - perform an intermediary upgrade to `12.1.Z` before upgrading to `12.10.Z` to - avoid issues like [#215141](https://gitlab.com/gitlab-org/gitlab/-/issues/215141). - -- Support for MySQL was removed in GitLab 12.1. Existing users using GitLab with - MySQL/MariaDB should - [migrate to PostgreSQL](https://gitlab.com/gitlab-org/gitlab/-/blob/v15.6.0-ee/doc/update/mysql_to_postgresql.md) - before upgrading. - -### 12.0.0 - -In 12.0.0 we made various database related changes. These changes require that -users first upgrade to the latest 11.11 patch release. After upgraded to 11.11.Z, -users can upgrade to 12.0.Z. Failure to do so may result in database migrations -not being applied, which could lead to application errors. - -It is also required that you upgrade to 12.0.Z before moving to a later version -of 12.Y. - -Example 1: you are currently using GitLab 11.11.8, which is the latest patch -release for 11.11.Z. You can upgrade as usual to 12.0.Z. - -Example 2: you are currently using a version of GitLab 10.Y. To upgrade, first -upgrade to the last 10.Y release (10.8.7) then the last 11.Y release (11.11.8). -After upgraded to 11.11.8 you can safely upgrade to 12.0.Z. - -See our [documentation on upgrade paths](../policy/maintenance.md#upgrade-recommendations) -for more information. - ### User profile data loss bug in 15.9.x There is a database migration bug in 15.9.0, 15.9.1, and 15.9.2 that can cause data loss from the user profile fields `linkedin`, `twitter`, `skype`, `website_url`, `location`, and `organization`. @@ -1658,7 +1407,7 @@ It is not then required to upgrade to 15.9.3 or later for this issue. ### Gitaly: Omnibus GitLab configuration structure change Gitaly configuration structure in Omnibus GitLab [changes](https://gitlab.com/gitlab-org/gitaly/-/issues/4467) in GitLab 16.0 to be consistent with the Gitaly configuration -structure used in source installs. +structure used in self-compiled installations. As a result of this change, a single hash under `gitaly['configuration']` holds most Gitaly configuration. Some `gitaly['..']` configuration options will continue to be used by Omnibus GitLab 16.0 and later: @@ -1680,6 +1429,8 @@ The new structure is documented below with the old keys described in a comment a 1. Skip any keys you haven't configured a value for previously. 1. Remove the old keys from the configuration once migrated. 1. Optional but recommended. Include a trailing comma for all hash keys so the hash remains valid when keys are re-ordered or additional keys are added. +1. When configuring `storage` to replace `git_data_dirs`, you must append `repositories` to the path as documented below. If you omit this step, your Git repositories are + inaccessible until the configuration is fixed. ```ruby gitaly['configuration'] = { @@ -1820,7 +1571,7 @@ gitaly['configuration'] = { ### Praefect: Omnibus GitLab configuration structure change Praefect configuration structure in Omnibus GitLab [changes](https://gitlab.com/gitlab-org/gitaly/-/issues/4467) in GitLab 16.0 to be consistent with the Praefect configuration -structure used in source installs. +structure used in self-compiled installations. As a result of this change, a single hash under `praefect['configuration']` holds most Praefect configuration. Some `praefect['..']` configuration options will continue to be used by Omnibus GitLab 16.0 and later: diff --git a/doc/update/package/downgrade.md b/doc/update/package/downgrade.md index 14b9bd981fd..0e01a1bfcd8 100644 --- a/doc/update/package/downgrade.md +++ b/doc/update/package/downgrade.md @@ -79,5 +79,5 @@ Steps: sudo gitlab-ctl reconfigure ``` -1. [Restore GitLab](../../administration/backup_restore/restore_gitlab.md#restore-for-omnibus-gitlab-installations) +1. [Restore GitLab](../../administration/backup_restore/restore_gitlab.md#restore-for-linux-package-installations) to complete the downgrade. diff --git a/doc/update/package/index.md b/doc/update/package/index.md index e61eaae5883..148791dbc75 100644 --- a/doc/update/package/index.md +++ b/doc/update/package/index.md @@ -42,9 +42,6 @@ check the version your are upgrading to: - [GitLab 16](https://docs.gitlab.com/omnibus/update/gitlab_16_changes.html) - [GitLab 15](https://docs.gitlab.com/omnibus/update/gitlab_15_changes.html) - [GitLab 14](https://docs.gitlab.com/omnibus/update/gitlab_14_changes.html) -- [GitLab 13](https://docs.gitlab.com/omnibus/update/gitlab_13_changes.html) -- [GitLab 12](https://docs.gitlab.com/omnibus/update/gitlab_12_changes.html) -- [GitLab 11](https://docs.gitlab.com/omnibus/update/gitlab_11_changes.html) ## Back up before upgrading diff --git a/doc/update/plan_your_upgrade.md b/doc/update/plan_your_upgrade.md index 634c430e251..0bb760ec47e 100644 --- a/doc/update/plan_your_upgrade.md +++ b/doc/update/plan_your_upgrade.md @@ -104,8 +104,8 @@ to your instance and then upgrade it for any relevant features you're using. - Generate an upgrade plan by reading and understanding the relevant documentation: - upgrade based on the installation method: - - [Linux package (Omnibus)](index.md#linux-packages-omnibus-gitlab) - - [Compiled from source](index.md#installation-from-source) + - [Linux package (Omnibus)](index.md#linux-packages-omnibus) + - [Self-compiled](index.md#self-compiled-installation) - [Docker](index.md#installation-using-docker) - [Helm Charts](index.md#installation-using-helm) - [Zero-downtime upgrades](zero_downtime.md) (if possible and desired) diff --git a/doc/update/upgrading_from_source.md b/doc/update/upgrading_from_source.md index d9641e18e8e..21f509ebd33 100644 --- a/doc/update/upgrading_from_source.md +++ b/doc/update/upgrading_from_source.md @@ -327,10 +327,6 @@ cd /home/git/gitlab sudo -u git -H bundle exec rake "gitlab:workhorse:install[/home/git/gitlab-workhorse]" RAILS_ENV=production ``` -NOTE: -If you get any errors concerning Rack attack, see the [13.1](index.md#custom-rack-attack-initializers) -specific changes. - ### 13. Update Gitaly If Gitaly is located on its own server, or you use Gitaly Cluster, see [Gitaly or Gitaly Cluster](zero_downtime.md#gitaly-or-gitaly-cluster) diff --git a/doc/update/versions/gitlab_16_changes.md b/doc/update/versions/gitlab_16_changes.md new file mode 100644 index 00000000000..cd51ca2a518 --- /dev/null +++ b/doc/update/versions/gitlab_16_changes.md @@ -0,0 +1,221 @@ +--- +stage: Systems +group: Distribution +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments +--- + +# GitLab 16 changes + +This page contains upgrade information for minor and patch versions of GitLab 16. +Ensure you review these instructions for: + +- Your installation type. +- All versions between your current version and your target version. + +Some GitLab installations must upgrade to GitLab 16.0 before upgrading to any other version. For more information, see +[Long-running user type data change](#long-running-user-type-data-change). + +For more information about upgrading GitLab Helm Chart, see [the release notes for 7.0](https://docs.gitlab.com/charts/releases/7_0.html). + +## 16.3.0 + +- For Go applications, [`crypto/tls`: verifying certificate chains containing large RSA keys is slow (CVE-2023-29409)](https://github.com/golang/go/issues/61460) + introduced a hard limit of 8192 bits for RSA keys. In the context of Go applications at GitLab, RSA keys can be configured for: + + - [Container Registry](../../administration/packages/container_registry.md) + - [Gitaly](../../administration/gitaly/configure_gitaly.md#enable-tls-support) + - [GitLab Pages](../../user/project/pages/custom_domains_ssl_tls_certification/index.md#manual-addition-of-ssltls-certificates) + - [Workhorse](../../development/workhorse/configuration.md#tls-support) + + You should check the size of your RSA keys (`openssl rsa -in <your-key-file> -text -noout | grep "Key:"`) + for any of the applications above before + upgrading. + +### Linux package installations + +Specific information applies to Linux package installations: + +- In GitLab 16.0, we [announced](https://about.gitlab.com/releases/2023/05/22/gitlab-16-0-released/#omnibus-improvements) an upgraded base Docker image, + which has a new version of OpenSSH Server. An unintended consequence of the new version is that it disables accepting SSH RSA SHA-1 signatures by default. This issue should only + impact users using very outdated SSH clients. + + To avoid problems with SHA-1 signatures being unavailable, users should update their SSH clients because using SHA-1 signatures is discouraged by the upstream library for security + reasons. + + To allow for a transition period where users can't immediately upgrade their SSH clients, GitLab 16.3 and later has support for a `GITLAB_ALLOW_SHA1_RSA` environment variable in + the `Dockerfile`. If `GITLAB_ALLOW_SHA1_RSA` is set to `true`, this deprecated support is reactivated. + + Because we want to foster security best practices and follow the upstream recommendation, this environment variable will only be available until GitLab 17.0, when we plan to + drop support for it. + + For more information, see: + + - [OpenSSH 8.8 release notes](https://www.openssh.com/txt/release-8.8). + - [An informal explanation](https://gitlab.com/gitlab-org/gitlab/-/issues/416714#note_1482388504). + - `omnibus-gitlab` [merge request 7035](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/7035), which introduces the environment variable. + +## 16.2.0 + +- Legacy LDAP configuration settings may cause + [`NoMethodError: undefined method 'devise' for User:Class` errors](https://gitlab.com/gitlab-org/gitlab/-/issues/419485). + This error occurs if you have TLS options (such as `ca_file`) not specified + in the `tls_options` hash, or use the legacy `gitlab_rails['ldap_host']` option. + See the [configuration workarounds](https://gitlab.com/gitlab-org/gitlab/-/issues/419485#workarounds) + for more details. +- New job artifacts are not replicated if job artifacts are configured to be stored in object storage and `direct_upload` is enabled. This bug is fixed in GitLab versions 16.1.4, + 16.2.3, 16.3.0, and later. + - Impacted versions: GitLab versions 16.1.0 - 16.1.3 and 16.2.0 - 16.2.2. + - If you deployed an affected version, after upgrading to a fixed GitLab version, follow [these instructions](https://gitlab.com/gitlab-org/gitlab/-/issues/419742#to-fix-data) + to resync the affected job artifacts. +- You might encounter the following error while upgrading to GitLab 16.2 or later: + + ```plaintext + main: == 20230620134708 ValidateUserTypeConstraint: migrating ======================= + main: -- execute("ALTER TABLE users VALIDATE CONSTRAINT check_0dd5948e38;") + rake aborted! + StandardError: An error has occurred, all later migrations canceled: + PG::CheckViolation: ERROR: check constraint "check_0dd5948e38" of relation "users" is violated by some row + ``` + + For more information, see [issue 421629](https://gitlab.com/gitlab-org/gitlab/-/issues/421629). + +### Linux package installations + +Specific information applies to Linux package installations: + +- In 16.2, we are upgrading Redis from 6.2.11 to 7.0.12. This upgrade is expected to be fully backwards compatible. + + Redis is not automatically restarted as part of `gitlab-ctl reconfigure`. + Hence, users are manually required to run `sudo gitlab-ctl restart redis` after + the reconfigure run so that the new Redis version gets used. A warning + mentioning that the installed Redis version is different than the one running is + displayed at the end of reconfigure run until the restart is performed. + + If your instance has Redis HA with Sentinel, follow the upgrade steps mentioned in + [Zero Downtime documentation](../zero_downtime.md#redis-ha-using-sentinel). + +### Self-compiled installations + +- Git 2.41.0 and later is required by Gitaly. You should use the [Git version provided by Gitaly](../../install/installation.md#git). + +## 16.1.0 + +- A `BackfillPreparedAtMergeRequests` background migration is finalized with + the `FinalizeBackFillPreparedAtMergeRequests` post-deploy migration. + GitLab 15.10.0 introduced a [batched background migration](../background_migrations.md#batched-background-migrations) to + [backfill `prepared_at` values on the `merge_requests` table](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111865). This + migration may take multiple days to complete on larger GitLab instances. Make sure the migration + has completed successfully before upgrading to 16.1.0. +- New job artifacts are not replicated if job artifacts are configured to be stored in object storage and `direct_upload` is enabled. This bug is fixed in GitLab versions 16.1.4, + 16.2.3, 16.3.0, and later. + - Impacted versions: GitLab versions 16.1.0 - 16.1.3 and 16.2.0 - 16.2.2. + - If you deployed an affected version, after upgrading to a fixed GitLab version, follow [these instructions](https://gitlab.com/gitlab-org/gitlab/-/issues/419742#to-fix-data) + to resync the affected job artifacts. + +### Self-compiled installations + +- You must remove any settings related to Puma worker killer from the `puma.rb` configuration file, because those have been + [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/118645). For more information, see the + [`puma.rb.example`](https://gitlab.com/gitlab-org/gitlab/-/blob/16-0-stable-ee/config/puma.rb.example) file. + +### Geo installations + +Specific information applies to installations using Geo: + +- Some project imports do not initialize wiki repositories on project creation. Because of the migration of project wikis to + SSF, [missing wiki repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/409704). + This issue is not a result of an actual replication/verification failure but an invalid internal state for these missing + repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for + these wiki repositories. If you have not imported projects you are not impacted by this issue. + - Impacted versions: GitLab versions 15.11.x, 16.0.x, and 16.1.0 - 16.1.2. + - Versions containing fix: GitLab 16.1.3 and later. +- Because of the migration of project designs to SSF, [missing design repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/414279). + This issue is not a result of an actual replication/verification failure but an invalid internal state for these missing + repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for + these design repositories. You could be impacted by this issue even if you have not imported projects. + - Impacted versions: GitLab versions 16.1.x. + - Versions containing fix: GitLab 16.2.0 and later. + +## 16.0.0 + +- Sidekiq crashes if there are non-ASCII characters in the `/etc/gitlab/gitlab.rb` file. You can fix this + by following the workaround in [issue 412767](https://gitlab.com/gitlab-org/gitlab/-/issues/412767#note_1404507549). +- Sidekiq jobs are only routed to `default` and `mailers` queues by default, and as a result, + every Sidekiq process also listens to those queues to ensure all jobs are processed across + all queues. This behavior does not apply if you have configured the [routing rules](../../administration/sidekiq/processing_specific_job_classes.md#routing-rules). +- Docker 20.10.10 or later is required to run the GitLab Docker image. Older versions + [throw errors on startup](../../install/docker.md#threaderror-cant-create-thread-operation-not-permitted). +- Starting with 16.0, GitLab self-managed installations now have two database connections by default, instead of one. This change doubles the number of PostgreSQL connections. It makes self-managed versions of GitLab behave similarly to GitLab.com, and is a step toward enabling a separate database for CI features for self-managed versions of GitLab. Before upgrading to 16.0, determine if you need to [increase max connections for PostgreSQL](https://docs.gitlab.com/omnibus/settings/database.html#configuring-multiple-database-connections). + - This change applies to installation methods with Linux packages (Omnibus), GitLab Helm chart, GitLab Operator, GitLab Docker images, and self-compiled installations. + +### Linux package installations + +Specific information applies to Linux package installations: + +- The binaries for PostgreSQL 12 have been removed. + + Prior to upgrading, administrators of Linux package installations must ensure the installation is using + [PostgreSQL 13](https://docs.gitlab.com/omnibus/settings/database.html#upgrade-packaged-postgresql-server). + +- Bundled Grafana is deprecated and is no longer supported. It is removed in GitLab 16.3. + + For more information, see [deprecation notes](../../administration/monitoring/performance/grafana_configuration.md#deprecation-of-bundled-grafana). + +- This upgrades `openssh-server` to `1:8.9p1-3`. + + Using `ssh-keyscan -t rsa` with older OpenSSH clients to obtain public key information is no longer viable because of + the deprecations listed in [OpenSSH 8.7 Release Notes](https://www.openssh.com/txt/release-8.7). + + Workaround is to make use of a different key type, or upgrade the client OpenSSH to a version >= 8.7. + +### Geo installations + +Specific information applies to installations using Geo: + +- Some project imports do not initialize wiki repositories on project creation. Because of the migration of project wikis to + SSF, [missing wiki repositories are being incorrectly flagged as failing verification](https://gitlab.com/gitlab-org/gitlab/-/issues/409704). + This issue is not a result of an actual replication/verification failure but an invalid internal state for these missing + repositories inside Geo and results in errors in the logs and the verification progress reporting a failed state for + these wiki repositories. If you have not imported projects you are not impacted by this issue. + + - Impacted versions: GitLab versions 15.11.x, 16.0.x, and 16.1.0 - 16.1.2. + - Versions containing fix: GitLab 16.1.3 and later. + +## Long-running user type data change + +GitLab 16.0 is a required stop for large GitLab instances with a lot of records in the `users` table. + +The threshold is **30,000 users**, which includes: + +- Developers and other users in any state, including active, blocked, and pending approval. +- Bot accounts for project and group access tokens. + +GitLab 16.0 introduced a [batched background migration](../background_migrations.md#batched-background-migrations) to +[migrate `user_type` values from `NULL` to `0`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115849). This +migration might take multiple days to complete on larger GitLab instances. Make sure the migration +has completed successfully before upgrading to 16.1.0 or later. + +GitLab 16.1 introduces the `FinalizeUserTypeMigration` migration which ensures the +16.0 `MigrateHumanUserType` background migration is completed, making the 16.0 changes synchronously +during the upgrade if it's not completed. + +GitLab 16.2 [implements a `NOT NULL` database constraint](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122454) +which fails if the 16.0 migration is not complete. + +If 16.0 has been skipped (or the 16.0 migration is not complete) subsequent +Linux package (Omnibus) and Docker upgrades might fail +after an hour: + +```plaintext +FATAL: Mixlib::ShellOut::CommandTimeout: rails_migration[gitlab-rails] +[..] +Mixlib::ShellOut::CommandTimeout: Command timed out after 3600s: +``` + +[There is a fix-forward workaround for this issue](../package/index.md#mixlibshelloutcommandtimeout-rails_migrationgitlab-rails--command-timed-out-after-3600s). + +While the workaround is completing the database changes, GitLab is likely to be in +an unusable state, generating `500` errors. The errors are caused by Sidekiq and Puma running +application code that is incompatible with the database schema. + +At the end of the workaround process, Sidekiq and Puma are restarted to resolve that issue. diff --git a/doc/update/zero_downtime.md b/doc/update/zero_downtime.md index c815087b0b3..7a0f49b6fe7 100644 --- a/doc/update/zero_downtime.md +++ b/doc/update/zero_downtime.md @@ -15,7 +15,7 @@ there are the following requirements: sequence [and leave the database schema in a broken state](https://gitlab.com/gitlab-org/gitlab/-/issues/321542). - You have to use [post-deployment migrations](../development/database/post_deployment_migrations.md). - You are using PostgreSQL. Starting from GitLab 12.1, MySQL is not supported. -- You have set up a multi-node GitLab instance. Single-node instances do not support zero-downtime upgrades. +- You have set up a multi-node GitLab instance. Cloud Native Hybrid installations do [not support zero-downtime upgrades](../administration/reference_architectures/index.md#zero-downtime-upgrades). If you want to upgrade multiple releases or do not meet the other requirements: |