diff options
Diffstat (limited to 'doc/update/deprecations.md')
| -rw-r--r-- | doc/update/deprecations.md | 565 |
1 files changed, 315 insertions, 250 deletions
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index ecf0f68de0e..804fcc77ea1 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -5,9 +5,9 @@ info: "See the Technical Writers assigned to Development Guidelines: https://abo toc: false --- -# Deprecations by version +# Deprecations and removals by version -These GitLab features are deprecated and no longer recommended for use. +The following GitLab features are deprecated and no longer recommended for use. Each deprecated feature will be removed in a future release. Some features cause breaking changes when they are removed. @@ -24,8 +24,10 @@ and [GraphQL](https://docs.gitlab.com/ee/api/graphql/removed_items.html) depreca <!-- DO NOT EDIT THIS PAGE DIRECTLY -This page is automatically generated from the YAML files in `/data/deprecations` by the rake task -located at `lib/tasks/gitlab/docs/compile_deprecations.rake`. +This page is automatically generated from the template located at +`data/deprecations/templates/_deprecation_template.md.erb`, using +the YAML files in `/data/deprecations` by the rake task +located at `lib/tasks/gitlab/docs/compile_deprecations.rake`, For deprecation authors (usually Product Managers and Engineering Managers): @@ -50,25 +52,11 @@ For deprecation reviewers (Technical Writers only): <div class="deprecation breaking-change" data-milestone="17.0"> -### Accessibility Testing 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/development/deprecation_guidelines/). -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390424). -</div> - -Due to low customer usage, Accessibility Testing is deprecated and will be removed. There is no planned replacement and users should stop using Accessibility Testing before GitLab 17.0. - -</div> - -<div class="deprecation breaking-change" data-milestone="17.0"> - ### 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/development/deprecation_guidelines/). +- This is a [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> @@ -85,7 +73,7 @@ next major release, GitLab 16.0. This gem sees very little use and its <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -97,25 +85,11 @@ Because Cloud Native Buildpacks do not support automatic testing, the Auto Test <div class="deprecation breaking-change" data-milestone="17.0"> -### Browser Performance Testing 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/development/deprecation_guidelines/). -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388719). -</div> - -Due to limited customer usage, Browser Performance Testing is deprecated and will be removed. There is no planned replacement and users should stop using Browser Performance Testing before GitLab 17.0. - -</div> - -<div class="deprecation breaking-change" data-milestone="17.0"> - ### 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/development/deprecation_guidelines/). +- This is a [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> @@ -130,7 +104,7 @@ If you rely on the order of the returned projects to be `id_asc`, change your sc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -145,7 +119,7 @@ the aliasing for the `CiRunnerUpgradeStatusType` type will be removed. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -162,7 +136,7 @@ These three variables will be removed in GitLab 17.0. <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/development/deprecation_guidelines/). +- This is a [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> @@ -170,6 +144,36 @@ In GitLab 11.11 the Windows Batch executor, the CMD shell was deprecated in GitL </div> +<div class="deprecation breaking-change" data-milestone="17.0"> + +### 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). +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/41518). +</div> + +These fields (`architectureName`, `ipAddress`, `platformName`, `revision`, `version`) are now deprecated from the [GraphQL `CiRunner`](https://docs.gitlab.com/ee/api/graphql/reference/#cirunner) type as they are duplicated with the introduction of runner managers grouped within a runner configuration. + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + +### 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). +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/411573). +</div> + +This MR deprecates the `message` field on the `VulnerabilityCreate` GraphQL mutation, and in the `AdditionalInfo` column of the vulnerability export. +The message field was removed from security reports schema in GitLab 16.0 and is no longer being used elsewhere. + +</div> + <div class="deprecation " data-milestone="17.0"> ### Deprecate legacy shell escaping and quoting runner shell executor @@ -186,11 +190,25 @@ The runner's legacy escape sequence mechanism to handle variable expansion imple <div class="deprecation breaking-change" data-milestone="17.0"> +### 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). +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124461). +</div> + +The parameters, `sign_in_text` and `help_text`, are deprecated in the [Settings API](https://docs.gitlab.com/ee/api/settings.html). To add a custom text to the sign-in and sign-up pages, use the `description` field in the [Appearance API](https://docs.gitlab.com/ee/api/appearance.html). + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### 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/development/deprecation_guidelines/). +- This is a [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> @@ -205,7 +223,7 @@ major release, GitLab 17.0. This gem sees very little use and is better suited f <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -231,7 +249,7 @@ To avoid any disruptions, you should replace `filepath` with `direct_asset_path` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -252,7 +270,7 @@ Because the new values provide a streamlined, comprehensive method to enable TLS <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -269,7 +287,7 @@ are deprecated and will be removed from the GraphQL API. For installation instru <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/development/deprecation_guidelines/). +- This is a [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> @@ -292,7 +310,7 @@ This change is a breaking change. You should use an [authentication token](../ci <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -304,44 +322,46 @@ Use `dependencyProxyTotalSizeBytes` instead, introduced in GitLab 16.1. <div class="deprecation breaking-change" data-milestone="17.0"> -### GraphQL type, `RunnerMembershipFilter` renamed to `CiRunnerMembershipFilter` +### GraphQL field `registrySizeEstimated` has been deprecated <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/409333). +- Announced in: GitLab <span class="milestone">16.2</span> +- This is a [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> -The GraphQL type, `RunnerMembershipFilter`, has been renamed to `CiRunnerMembershipFilter`. In GitLab 17.0, -the aliasing for the `RunnerMembershipFilter` type will be removed. +For clarity, the GraphQL field `registrySizeEstimated` was renamed to `containerRegistrySizeIsEstimated`, to match its counterpart. +`registrySizeEstimated` was deprecated in GitLab 16.2 and will be removed in GitLab 17.0. +Use `containerRegistrySizeIsEstimated` introduced in GitLab 16.2 instead. </div> <div class="deprecation breaking-change" data-milestone="17.0"> -### GraphQL: The `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` enum is deprecated. Use `DISABLED_AND_OVERRIDABLE` instead +### GraphQL type, `RunnerMembershipFilter` renamed to `CiRunnerMembershipFilter` <div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385636). +- Announced in: GitLab <span class="milestone">16.0</span> +- This is a [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> -In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be replaced with the value, `DISABLED_AND_OVERRIDABLE`. +The GraphQL type, `RunnerMembershipFilter`, has been renamed to `CiRunnerMembershipFilter`. In GitLab 17.0, +the aliasing for the `RunnerMembershipFilter` type will be removed. </div> <div class="deprecation breaking-change" data-milestone="17.0"> -### Load Performance Testing is deprecated +### 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.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388723). +- Announced in: GitLab <span class="milestone">15.8</span> +- This is a [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> -Due to low customer usage, Load Performance Testing is deprecated and will be removed. There is no planned replacement and users should stop using Load Performance Testing before GitLab 17.0. +In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be replaced with the value, `DISABLED_AND_OVERRIDABLE`. </div> @@ -351,7 +371,7 @@ Due to low customer usage, Load Performance Testing is deprecated and will be re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -369,11 +389,25 @@ settings for the group using either the GitLab UI or GraphQL API. <div class="deprecation breaking-change" data-milestone="17.0"> +### 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). +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/416000). +</div> + +OmniAuth Facebook support will be removed in GitLab 17.0. The last gem release was in 2021 and it is currently unmaintained. The current usage is less than 0.1%. If you use OmniAuth Facebook, switch to a [supported provider](https://docs.gitlab.com/ee/integration/omniauth.html#supported-providers) in advance of support removal. + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### 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/development/deprecation_guidelines/). +- This is a [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> @@ -389,7 +423,7 @@ In milestone 17.0, we will remove the `pipelines` attribute from the API respons <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -404,7 +438,7 @@ The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) a <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/development/deprecation_guidelines/). +- This is a [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> @@ -425,7 +459,7 @@ PostgreSQL 14 will also be supported for instances that want to upgrade prior to <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/development/deprecation_guidelines/). +- This is a [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> @@ -444,7 +478,7 @@ While the above approach is recommended for most instances, Sidekiq can also be <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/development/deprecation_guidelines/). +- This is a [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> @@ -474,7 +508,7 @@ This change is a breaking change. You should [create a runner in the UI](../ci/r <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/development/deprecation_guidelines/). +- This is a [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> @@ -501,7 +535,7 @@ This change is a breaking change. You should [create a runner in the UI](../ci/r <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -518,11 +552,19 @@ that is available now. We recommend this alternative solution because it provide <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> -The option to run self-managed installations of GitLab on a single database is now deprecated. From GitLab 17.0, we will require a [separate database for CI features](https://gitlab.com/groups/gitlab-org/-/epics/7509). With this change, self-managed versions of GitLab will behave similarly to GitLab.com. This change applies to installation methods with Omnibus GitLab, GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source. Before upgrading to GitLab 17.0, please ensure [migration](https://docs.gitlab.com/ee/administration/postgresql/multiple_databases.html) to two databases. +From GitLab 17.0, we will require a [separate database for CI features](https://gitlab.com/groups/gitlab-org/-/epics/7509). +We recommend running both databases on the same Postgres instance(s) due to ease of management for most deployments. + +We are providing this as an informational advance notice but we do not recommend taking action yet. +We will have another update communicated (as well as the deprecation note) when we recommend admins to start the migration process. + +This change provides additional scalability for the largest of GitLab instances, like GitLab.com. +This change applies to all installation methods: Omnibus GitLab, GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source. +Before upgrading to GitLab 17.0, please ensure you have [migrated](https://docs.gitlab.com/ee/administration/postgresql/multiple_databases.html) to two databases. </div> @@ -532,7 +574,7 @@ The option to run self-managed installations of GitLab on a single database is n <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -558,7 +600,7 @@ For updates and details about this deprecation, follow [this epic](https://gitla <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -582,7 +624,7 @@ automatically from GitLab 16.0 onwards. <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/development/deprecation_guidelines/). +- This is a [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> @@ -602,7 +644,7 @@ we'll be introducing support in [this epic](https://gitlab.com/groups/gitlab-org <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/development/deprecation_guidelines/). +- This is a [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> @@ -629,7 +671,7 @@ From GitLab 17.0 and later, the runner registration methods implemented by the n <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -643,7 +685,7 @@ We will be transitioning to a new IID as a result of moving requirements to a [w <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -658,7 +700,7 @@ Due to limited customer usage and capabilities, the Visual Reviews feature for R <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/development/deprecation_guidelines/). +- This is a [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> @@ -668,11 +710,29 @@ The [`gitlab-runner exec`](https://docs.gitlab.com/runner/commands/#gitlab-runne <div class="deprecation breaking-change" data-milestone="17.0"> +### 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). +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/406545). +</div> + +We are deprecating the built-in pull-based deployment features of the GitLab agent for Kubernetes in favor of Flux and related integrations. + +The GitLab agent for Kubernetes **is not deprecated**. This change affects only the pull-based functionality of the agent. All other functionality will remain intact, and GitLab will continue to support the agent for Kubernetes. + +If you use the agent for pull-based deployments, you should [migrate to Flux](https://docs.gitlab.com/ee/user/clusters/agent/gitops/agent.html#migrate-to-flux). Because Flux is a mature CNCF project for GitOps, we decided to [integrate Flux with GitLab in February 2023](https://about.gitlab.com/blog/2023/02/08/why-did-we-choose-to-integrate-fluxcd-with-gitlab/). + +</div> + +<div class="deprecation breaking-change" data-milestone="17.0"> + ### 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/development/deprecation_guidelines/). +- This is a [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> @@ -686,7 +746,7 @@ In some cases, like when a downstream pipeline had the `passed with warnings` st <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -706,7 +766,7 @@ You can still access unified approval rules with the API. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -724,7 +784,7 @@ removed in 17.0. <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/development/deprecation_guidelines/). +- This is a [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> @@ -744,7 +804,7 @@ From GitLab 17.0 and later, the methods to register runners introduced by the ne <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -776,9 +836,12 @@ echo $( ruby -rsecurerandom -e "puts SecureRandom.base64(32)" ) > ~/.gitlab-mail If you run GitLab on more than one machine, you need to provide the secret key file for each machine. -We highly encourage GitLab administrators to start using the `webhook` delivery method for +We encourage GitLab administrators to switch to the webhook delivery method for `incoming_email_delivery_method` and `service_desk_email_delivery_method` instead of `sidekiq`. +[Issue 393157](https://gitlab.com/gitlab-org/gitlab/-/issues/393157) tracks improving email ingestion in general. +We hope this will simplify infrastructure setup and add several improvements to how you manage GitLab in the near future. + </div> <div class="deprecation breaking-change" data-milestone="17.0"> @@ -787,7 +850,7 @@ We highly encourage GitLab administrators to start using the `webhook` delivery <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -819,7 +882,7 @@ Enabling the `ldap_settings_unlock_groups_by_owners` feature flag allowed non-LD <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -848,7 +911,7 @@ In GitLab 16.0 and later: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -896,7 +959,7 @@ be available in CI/CD jobs. <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/development/deprecation_guidelines/). +- This is a [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> @@ -914,6 +977,28 @@ In GitLab versions 16.0 to 16.2, you can still [re-enable the bundled Grafana](h However, enabling the bundled Grafana will no longer work from GitLab 16.3. </div> + +<div class="deprecation breaking-change" data-milestone="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). +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387561). +</div> + +**Update:** We previously announced we would remove the existing License Compliance CI template in GitLab 16.0. However, due to performance issues with the [license scanning of CycloneDX files](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/) we will do this change in 16.3 instead. + +The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/license_compliance/) CI template is now deprecated and is scheduled for removal in the GitLab 16.1 release. Users who wish to continue using GitLab for License Compliance should remove the License Compliance template from their CI pipeline and add the [Dependency Scanning template](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuration). The Dependency Scanning template is now capable of gathering the required license information so it is no longer necessary to run a separate License Compliance job. The License Compliance CI template should not be removed prior to verifying that the `license_scanning_sbom_scanner` and `package_metadata_synchronization` flags are enabled for the instance and that the instance has been upgraded to a version that supports [the new method of license scanning](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/). + +| CI Pipeline Includes | GitLab <= 15.8 | 15.9 <= GitLab < 16.3 | GitLab >= 16.3 | +| ------------- | ------------- | ------------- | ------------- | +| Both DS and LS templates | License data from LS job is used | License data from LS job is used | License data from DS job is used | +| DS template is included but LS template is not | No license data | License data from DS job is used | License data from DS job is used | +| 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> <div class="milestone-wrapper" data-milestone="16.1"> @@ -937,28 +1022,6 @@ We will stop publishing runner images based on the following, end-of-life Alpine - Alpine 3.14 (end-of-life on 2023-05-23) </div> - -<div class="deprecation breaking-change" data-milestone="16.1"> - -### 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/development/deprecation_guidelines/). -- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387561). -</div> - -**Update:** We previously announced we would remove the existing License Compliance CI template in GitLab 16.0. However, due to performance issues with the [license scanning of CycloneDX files](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/) we will do this change in 16.1 instead. - -The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/license_compliance/) CI template is now deprecated and is scheduled for removal in the GitLab 16.1 release. Users who wish to continue using GitLab for License Compliance should remove the License Compliance template from their CI pipeline and add the [Dependency Scanning template](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuration). The Dependency Scanning template is now capable of gathering the required license information so it is no longer necessary to run a separate License Compliance job. The License Compliance CI template should not be removed prior to verifying that the `license_scanning_sbom_scanner` and `package_metadata_synchronization` flags are enabled for the instance and that the instance has been upgraded to a version that supports [the new method of license scanning](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/). - -| CI Pipeline Includes | GitLab <= 15.8 | 15.9 <= GitLab < 16.1 | GitLab >= 16.1 | -| ------------- | ------------- | ------------- | ------------- | -| Both DS and LS templates | License data from LS job is used | License data from LS job is used | License data from DS job is used | -| DS template is included but LS template is not | No license data | License data from DS job is used | License data from DS job is used | -| 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> <div class="milestone-wrapper" data-milestone="16.0"> @@ -971,7 +1034,7 @@ The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/licen <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -990,7 +1053,7 @@ set the `POSTGRES_ENABLED` CI/CD variable to `true`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1008,7 +1071,7 @@ This breaking change will happen in GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1031,7 +1094,7 @@ and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1047,7 +1110,7 @@ release, GitLab 16.0. This gem sees very little use and its lack of upstream mai <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1061,7 +1124,7 @@ When using the native HashiCorp Vault integration, CI/CD jobs will fail when no <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1078,7 +1141,7 @@ Instead of changing which single module would be scanned, we [improved multi-mod <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1094,7 +1157,7 @@ Instead, use the [`/approval_rules` endpoint](https://docs.gitlab.com/ee/api/mer <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1111,7 +1174,7 @@ This unintended functionality is deprecated in GitLab 15.8 and will be removed i <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/development/deprecation_guidelines/). +- This is a [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> @@ -1125,7 +1188,7 @@ From GitLab 13.6, users can [specify any runner configuration in the GitLab Runn <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1143,7 +1206,7 @@ config file locations instead, for example `config/redis.cache.yml` or <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1157,7 +1220,7 @@ The Container Registry [pull-through cache](https://docs.docker.com/registry/rec <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1171,7 +1234,7 @@ All Container Scanning variables that are prefixed by `DOCKER_` in variable name <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1187,7 +1250,7 @@ to continue to use the GitLab for Jira Cloud app. Without OAuth, you can't manag <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1201,7 +1264,7 @@ With the move to the new DAST API analyzer and the `DAST-API.gitlab-ci.yml` temp <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1221,7 +1284,7 @@ These two variables will be removed in GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1237,7 +1300,7 @@ These three variables will be removed 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/development/deprecation_guidelines/). +- This is a [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> @@ -1259,7 +1322,7 @@ To prepare for this change, users on GitLab.com or self-managed GitLab 15.9 or l <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1273,7 +1336,7 @@ GitLab has deprecated Dependency Scanning support for Java versions 13, 14, 15, <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1287,7 +1350,7 @@ The Deployment API will now return an error when `updated_at` filtering and `upd <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1305,7 +1368,7 @@ GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configu <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1326,7 +1389,7 @@ For more information, see [the deprecation notes for Consul 1.9.0](https://githu <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/development/deprecation_guidelines/). +- This is a [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> @@ -1340,7 +1403,7 @@ The [`CI_PRE_CLONE_SCRIPT` variable](https://docs.gitlab.com/ee/ci/runners/saas/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1356,7 +1419,7 @@ will be able to import projects to that group. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1370,7 +1433,7 @@ In GitLab 16.0 the GitLab Dependency Scanning analyzer will begin reporting deve <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1385,7 +1448,7 @@ We intend to replace this feature with the ability to [embed charts](https://git <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1407,7 +1470,7 @@ Users on self-managed instances should update their pipelines to ensure they do <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1421,7 +1484,7 @@ From GitLab 16.0, when you search for environments with the API, you must use at <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -1436,7 +1499,7 @@ To avoid any disruptions to your workflow, please stop using the `external` fiel <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -1467,7 +1530,7 @@ GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1500,7 +1563,7 @@ See [migrated group items](https://docs.gitlab.com/ee/user/group/import/#migrate <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1521,7 +1584,7 @@ When checking if a runner is `paused`, API users are advised to check the boolea <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1540,7 +1603,7 @@ be present during the 16.x cycle to avoid breaking the API signature, and will b <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1554,7 +1617,7 @@ The `confidential` field for a `Note` will be deprecated and renamed to `interna <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1571,7 +1634,7 @@ The Jira DVCS connector is also deprecated for Jira 8.13 and earlier. You can on <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/development/deprecation_guidelines/). +- This is a [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> @@ -1586,7 +1649,7 @@ This port is used for much more than just metrics, which warranted this change t <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1609,7 +1672,7 @@ You should update to the new configuration structure as soon as possible using <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1631,7 +1694,7 @@ didn't match. The change improves consistency between Omnibus GitLab and source <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1651,7 +1714,7 @@ Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1665,7 +1728,7 @@ The [License-Check feature](https://docs.gitlab.com/ee/user/compliance/license_c <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1679,7 +1742,7 @@ With external authorization enabled, personal access tokens (PATs) and deploy to <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1701,7 +1764,7 @@ The full GitLab Helm Chart 7.0 upgrade steps will be available in the [upgrade d <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1718,10 +1781,10 @@ The [Managed Licenses API](https://docs.gitlab.com/ee/api/managed_licenses.html) - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/368195). </div> -The [**Maximum number of active pipelines per project** limit](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#set-cicd-limits) was never enabled by default and will be removed in GitLab 16.0. This limit can also be configured in the Rails console under [`ci_active_pipelines`](https://docs.gitlab.com/ee/administration/instance_limits.html#number-of-pipelines-running-concurrently). Instead, use the other recommended rate limits that offer similar protection: +The [**Maximum number of active pipelines per project** limit](https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#set-cicd-limits) was never enabled by default and will be removed in GitLab 16.0. This limit can also be configured in the Rails console under [`ci_active_pipelines`](https://docs.gitlab.com/ee/administration/instance_limits.html#number-of-pipelines-running-concurrently). Instead, use the other recommended rate limits that offer similar protection: -- [**Pipelines rate limits**](https://docs.gitlab.com/ee/user/admin_area/settings/rate_limit_on_pipelines_creation.html). -- [**Total number of jobs in currently active pipelines**](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#set-cicd-limits). +- [**Pipelines rate limits**](https://docs.gitlab.com/ee/administration/settings/rate_limit_on_pipelines_creation.html). +- [**Total number of jobs in currently active pipelines**](https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#set-cicd-limits). </div> @@ -1731,7 +1794,7 @@ The [**Maximum number of active pipelines per project** limit](https://docs.gitl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1746,7 +1809,7 @@ However, since certificate-based integration with Kubernetes clusters is depreca <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1773,7 +1836,7 @@ default is applied: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1794,7 +1857,7 @@ and `config/redis.shared_state.yml` files. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1812,7 +1875,7 @@ The option to delete groups and projects immediately by default was deprecated t <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1826,7 +1889,7 @@ Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https:/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1846,7 +1909,7 @@ Support for PostgreSQL 13 was added to Geo in GitLab 15.2. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1890,7 +1953,7 @@ Alternatives to using the `gitlab:import:repos` Rake task include: <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/development/deprecation_guidelines/). +- This is a [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> @@ -1906,7 +1969,7 @@ If you are using your own Redis 5.0 instance, you should upgrade it to Redis 6.0 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1922,7 +1985,7 @@ This could be a breaking change for anyone that developed their own runner that <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -1962,7 +2025,7 @@ Work to replace the PHPCS Security Audit-based analyzer is tracked in [issue 364 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2005,7 +2068,7 @@ Specifically, the following are being deprecated and will no longer be updated a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2040,7 +2103,7 @@ However, due to compatibility issues [discussed in the deprecation issue](https: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2061,7 +2124,7 @@ For more information, refer to [security report validation](https://docs.gitlab. <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/development/deprecation_guidelines/). +- This is a [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> @@ -2076,7 +2139,7 @@ and will be moved to the JiHu GitLab codebase. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2090,7 +2153,7 @@ GitLab's operational container scanning capabilities no longer require starboard <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2113,7 +2176,7 @@ This may require updating your metrics collection targets to also scrape `/db_me <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/development/deprecation_guidelines/). +- This is a [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> @@ -2137,7 +2200,7 @@ To use the full state name, including the period, [migrate to the full state fil <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2162,7 +2225,7 @@ This change affects the following REST and GraphQL API endpoints: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2176,7 +2239,7 @@ The [Phabricator task importer](https://docs.gitlab.com/ee/user/project/import/p <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2199,7 +2262,7 @@ To accommodate the changes, you might need to adjust the [`rules`](https://docs. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2213,7 +2276,7 @@ In order to make the behavior of toggling the draft status of a merge request mo <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2227,7 +2290,7 @@ Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. U <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2242,7 +2305,7 @@ You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status o <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/development/deprecation_guidelines/). +- This is a [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> @@ -2264,7 +2327,7 @@ Moving forward, we'll continue to invest in developing and releasing new feature <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2286,7 +2349,7 @@ In GitLab 16.0 we will remove the ability to use a global ID in the work items p <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/development/deprecation_guidelines/). +- This is a [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> @@ -2301,7 +2364,7 @@ and will be moved to the JiHu GitLab codebase. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2330,7 +2393,7 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2344,7 +2407,7 @@ The `POST ci/lint` API endpoint is deprecated in 15.7, and will be removed in 16 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2358,7 +2421,7 @@ To avoid confusion and duplication, the `environment_tier` parameter is deprecat <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2378,7 +2441,7 @@ We plan to continue to support the `started` state in REST API version until the <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2420,7 +2483,7 @@ Starting in GitLab 15.7 we started providing packages for openSUSE Leap 15.4, an <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/development/deprecation_guidelines/). +- This is a [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> @@ -2442,7 +2505,7 @@ We are deprecating support for [uploading backups to remote storage](https://doc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2456,7 +2519,7 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2485,7 +2548,7 @@ GitLab self-managed customers can still use the feature [with a feature flag](ht <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2548,7 +2611,7 @@ This is not expected to cause any incompatibilities with the previous version of <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2565,7 +2628,6 @@ In GitLab 15.4, GitLab SAST will no longer use the following analyzers: NOTE: This change was originally planned for GitLab 15.0 and was postponed to GitLab 15.4. -See [the removal notice](./removals.md#sast-analyzer-consolidation-and-cicd-template-changes) for further details. These analyzers will be removed from the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml) and replaced with the [Semgrep-based analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/semgrep). Effective immediately, they will receive only security updates; other routine improvements or updates are not guaranteed. @@ -2578,8 +2640,8 @@ This change will be reflected in the automatic language detection portion of the If you've already dismissed a vulnerability finding from one of the deprecated analyzers, the replacement attempts to respect your previous dismissal. The system behavior depends on: -- whether you’ve excluded the Semgrep-based analyzer from running in the past. -- which analyzer first discovered the vulnerabilities shown in the project’s Vulnerability Report. +- whether you've excluded the Semgrep-based analyzer from running in the past. +- which analyzer first discovered the vulnerabilities shown in the project's Vulnerability Report. See [Vulnerability translation documentation](https://docs.gitlab.com/ee/user/application_security/sast/analyzers.html#vulnerability-translation) for further details. @@ -2651,7 +2713,7 @@ Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](ht <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2669,7 +2731,7 @@ dramatically slow down GitLab instances. For this reason, they are being removed <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2690,7 +2752,7 @@ GitLab will publish additional guidance to assist affected customers in migratin <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2704,7 +2766,7 @@ In GitLab 15.0 we are going to limit the number of characters in CI/CD job names <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2722,7 +2784,7 @@ Administrators who need to add runners for multiple projects can register a runn <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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). @@ -2813,7 +2875,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2845,7 +2907,7 @@ gemnasium-python-dependency_scanning: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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). @@ -2927,7 +2989,7 @@ The following `geo:db:*` tasks will be replaced with their corresponding `db:*:g <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2941,7 +3003,7 @@ The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -2984,7 +3046,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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 @@ -3023,7 +3085,7 @@ In 15.0, support for daemon mode for GitLab Pages will be removed. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3055,7 +3117,7 @@ and will remove it in GitLab 15.0 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3119,7 +3181,7 @@ an inline argument expression). <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -3139,7 +3201,7 @@ The permissions model for GraphQL is being updated. After 15.0, users with the G <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3155,7 +3217,7 @@ In GitLab 15.0 and later, the default value for this configuration option will c <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3171,7 +3233,7 @@ If you are using our License Compliance API you should stop using the `approved` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3189,7 +3251,7 @@ This deprecation mainly impacts users compiling GitLab from source because Omnib <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3215,7 +3277,7 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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). @@ -3228,7 +3290,7 @@ The OAuth implicit grant authorization flow will be removed in our next major re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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 @@ -3239,7 +3301,7 @@ You should [opt in](https://docs.gitlab.com/ee/integration/oauth_provider.html#e tokens before GitLab 15.0 is released: 1. Edit the application. -1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don’t expire. +1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don't expire. </div> @@ -3249,7 +3311,7 @@ tokens before GitLab 15.0 is released: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3267,7 +3329,7 @@ Note that we are not deprecating the Kerberos SPNEGO integration, only the old p <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3283,7 +3345,7 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3299,7 +3361,7 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3324,11 +3386,14 @@ If you rely on Java 8 being present in the analyzer environment, you must take a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> -As Advanced Search migrations usually require support multiple code paths for a long period of time, it’s important to clean those up when we safely can. We use GitLab major version upgrades as a safe time to remove backward compatibility for indices that have not been fully migrated. See the [upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details. +As Advanced Search migrations usually require support multiple code paths for a long period of time, +it's important to clean those up when we safely can. We use GitLab major version upgrades as a safe +time to remove backward compatibility for indices that have not been fully migrated. See the +[upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details. </div> @@ -3354,7 +3419,7 @@ It is now considered deprecated, and will be removed in GitLab 15.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3368,7 +3433,7 @@ The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTren <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3388,10 +3453,10 @@ For more information, check the [summary section of the deprecation issue](https <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> -The [required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers. +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. This change to move the feature to GitLab's Ultimate tier is intended to help our features better align with our [pricing philosophy](https://about.gitlab.com/company/pricing/#three-tiers) as we see demand for this feature originating primarily from executives. @@ -3406,7 +3471,7 @@ This change will also help GitLab remain consistent in its tiering strategy with <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3446,7 +3511,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3530,7 +3595,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3558,7 +3623,7 @@ See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3603,7 +3668,7 @@ Specifically, the following are being deprecated and will no longer be updated a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3650,7 +3715,7 @@ Current users of the Static Site Editor can view the [documentation](https://doc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -3663,7 +3728,7 @@ Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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 @@ -3686,14 +3751,14 @@ the [relevant epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463). <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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 [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-using-project-settings-removed) is being removed. -Instead, using the project’s `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set +Instead, using the project's `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set testing coverage results in merge requests. </div> @@ -3704,7 +3769,7 @@ testing coverage results in merge requests. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3718,7 +3783,7 @@ Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3734,7 +3799,7 @@ The `GET /groups/:id/registry/repositories` endpoint will remain, but won't retu <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3750,7 +3815,7 @@ If you monitor Value Stream Analytics metrics and rely on the date filter, to av <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -3770,7 +3835,7 @@ The new security approvals feature is similar to vulnerability check. For exampl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3786,7 +3851,7 @@ In milestone 15.0, we will completely remove `Version` from `PackageType`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3803,7 +3868,7 @@ only supported report file in 15.0, but this is the first step towards GitLab su <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3817,7 +3882,7 @@ The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprec <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3833,7 +3898,7 @@ In milestone 15.0, we will remove the feature flag entirely. Moving forward, you <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3852,7 +3917,7 @@ To mitigate possible performance problems, we will remove the `versions` field's <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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) @@ -3868,7 +3933,7 @@ exposed in the UUID field. Data previously available in the projectFingerprint f <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3882,7 +3947,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3896,7 +3961,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -3909,7 +3974,7 @@ The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3925,7 +3990,7 @@ which isn't being used in GitLab anymore. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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> @@ -3941,7 +4006,7 @@ If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you wi <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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`. @@ -3956,7 +4021,7 @@ Since it isn't used in the context of GitLab (the product), `htpasswd` authentic <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. @@ -3976,7 +4041,7 @@ Any API calls attempting to change the rate limits for `user_email_lookup_limit` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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. |