diff options
Diffstat (limited to 'data/deprecations')
17 files changed, 101 insertions, 40 deletions
diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml index 576b8a195c5..6d6d2ec137a 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml @@ -6,7 +6,7 @@ stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/343475 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 17.0. + The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) attribute of vulnerability findings is being deprecated in favor of a `uuid` attribute. By using UUIDv5 values to identify findings, we can easily associate any related entity with a finding. The `project_fingerprint` attribute is no longer being used to track findings, and will be removed in GitLab 17.0. Starting in 16.1, the output of `project_fingerprint` returns the same value as the `uuid` field. # The following items are not published on the docs page, but may be used in the future. tiers: Ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-10-grafana-chart.yml b/data/deprecations/15-10-grafana-chart.yml index 48070560bfb..ac66aca7910 100644 --- a/data/deprecations/15-10-grafana-chart.yml +++ b/data/deprecations/15-10-grafana-chart.yml @@ -33,5 +33,5 @@ If you're using the bundled Grafana, you should switch to the [newer chart version from Grafana Labs](https://artifacthub.io/packages/helm/grafana/grafana) or a Grafana Operator from a trusted provider. - In your new Grafana instance, you can [configure the GitLab provided Prometheus as a data source](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integration-with-gitlab-ui) - and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integration-with-gitlab-ui). + In your new Grafana instance, you can [configure the GitLab provided Prometheus as a data source](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#configure-grafana) + and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integrate-with-gitlab-ui). diff --git a/data/deprecations/15-4-confidence-field-in-graphql.yml b/data/deprecations/15-4-confidence-field-in-graphql.yml index 7f6e0d64c2e..375549a2515 100644 --- a/data/deprecations/15-4-confidence-field-in-graphql.yml +++ b/data/deprecations/15-4-confidence-field-in-graphql.yml @@ -1,6 +1,6 @@ - title: "Vulnerability confidence field" announcement_milestone: "15.4" - removal_milestone: "16.0" + removal_milestone: "17.0" breaking_change: true reporter: matt_wilson stage: govern @@ -9,4 +9,4 @@ In GitLab 15.3, [security report schemas below version 15 were deprecated](https://docs.gitlab.com/ee/update/deprecations.html#security-report-schemas-version-14xx). The `confidence` attribute on vulnerability findings exists only in schema versions before `15-0-0`, and therefore is effectively deprecated since GitLab 15.4 supports schema version `15-0-0`. To maintain consistency between the reports and our public APIs, the `confidence` attribute on any vulnerability-related components of our GraphQL API is now deprecated and will be - removed in 16.0. + removed in 17.0. diff --git a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml index 8c2931faf78..786132b19b5 100644 --- a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml +++ b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml @@ -10,7 +10,9 @@ The support for registration tokens and certain runner configuration arguments in the `POST` method operation on the `/api/v4/runners` endpoint is deprecated. This endpoint [registers](https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner) a runner with a GitLab instance at the instance, group, or project level through the API. Registration tokens, and support for certain configuration arguments, - will be disabled behind a feature flag in GitLab 16.6 and removed in GitLab 17.0. The configuration arguments disabled for authentication tokens are: + will start returning the HTTP `410 Gone` status code in GitLab 17.0. For more information, see [Migrating to the new runner registration workflow](../ci/runners/new_creation_workflow.md). + + The configuration arguments disabled for authentication tokens are: - `--locked` - `--access-level` diff --git a/data/deprecations/15-6-deprecate-runner-register-command.yml b/data/deprecations/15-6-deprecate-runner-register-command.yml index cb9b9f517cd..81e0f46078f 100644 --- a/data/deprecations/15-6-deprecate-runner-register-command.yml +++ b/data/deprecations/15-6-deprecate-runner-register-command.yml @@ -9,7 +9,8 @@ body: | # (required) Do not modify this line, instead modify the lines below. Registration tokens and certain configuration arguments in the command `gitlab-runner register` that [registers](https://docs.gitlab.com/runner/register/) a runner, are deprecated. Authentication tokens will be used to register runners instead. Registration tokens, and support for certain configuration arguments, - will be disabled behind a feature flag in GitLab 16.6 and removed in GitLab 17.0. The configuration arguments disabled for authentication tokens are: + will be removed in GitLab 17.0. For more information, see [Migrating to the new runner registration workflow](../ci/runners/new_creation_workflow.md). + The configuration arguments disabled for authentication tokens are: - `--locked` - `--access-level` diff --git a/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml b/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml index da184cfbe43..61b117feb35 100644 --- a/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml +++ b/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml @@ -8,7 +8,8 @@ issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/382077 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The [`runner-registration-token`](https://docs.gitlab.com/runner/install/operator.html#install-the-kubernetes-operator) parameter that uses the OpenShift and Kubernetes Vanilla Operator to install a runner on Kubernetes is deprecated. Authentication tokens will be used to register runners instead. Registration tokens, and support for certain configuration arguments, - will be disabled behind a feature flag in GitLab 16.6 and removed in GitLab 17.0. The configuration arguments disabled for authentication tokens are: + will be removed in GitLab 17.0. For more information, see [Migrating to the new runner registration workflow](../ci/runners/new_creation_workflow.md). + The configuration arguments disabled for authentication tokens are: - `--locked` - `--access-level` diff --git a/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml b/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml index b3031850ca3..3a9690e0836 100644 --- a/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml +++ b/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml @@ -8,7 +8,7 @@ issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/383341 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The support for runner registration tokens is deprecated. As a consequence, the REST API endpoints to reset a registration token are also deprecated and will - be removed in GitLab 17.0. + return the HTTP `410 Gone` status code in GitLab 17.0. The deprecated endpoints are: - `POST /runners/reset_registration_token` diff --git a/data/deprecations/15-9-database-single-database-connection-conf.yml b/data/deprecations/15-9-database-single-database-connection-conf.yml index c7d59e860ca..de4ae51d615 100644 --- a/data/deprecations/15-9-database-single-database-connection-conf.yml +++ b/data/deprecations/15-9-database-single-database-connection-conf.yml @@ -6,6 +6,8 @@ stage: Enablement issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387898 body: | + This deprecation is now superseded by another [deprecation notice](#running-a-single-database-is-deprecated). + Previously, [GitLab's database](https://docs.gitlab.com/omnibus/settings/database.html) configuration had a single `main:` section. This is being deprecated. The new configuration has both a `main:` and a `ci:` section. diff --git a/data/deprecations/15-9-rails-error-tracking.yml b/data/deprecations/15-9-rails-error-tracking.yml deleted file mode 100644 index 4d9fc371213..00000000000 --- a/data/deprecations/15-9-rails-error-tracking.yml +++ /dev/null @@ -1,16 +0,0 @@ -- title: "Error Tracking UI in GitLab Rails is deprecated" - announcement_milestone: "15.9" - removal_milestone: "16.6" - breaking_change: true - reporter: kbychu - stage: monitor - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/389991 - body: | - The [Error Tracking UI](https://docs.gitlab.com/ee/operations/error_tracking.html) is deprecated in 15.9 and will be removed in 16.6 (milestone might change) once GitLab Observability UI is made available. In future versions, you should use the [GitLab Observability UI](https://gitlab.com/gitlab-org/opstrace/opstrace-ui/), which will gradually be made available on GitLab.com over the next few releases. - - During the transition to the GitLab Observability UI, we will migrate the [GitLab Observability Backend](https://gitlab.com/gitlab-org/opstrace/opstrace) from a per-cluster deployment model to a per-tenant deployment model. Because [Integrated Error Tracking](https://docs.gitlab.com/ee/operations/error_tracking.html#integrated-error-tracking) is in Open Beta, we will not migrate any existing user data. For more details about the migration, see the direction pages for: - - - [Observability](https://about.gitlab.com/direction/monitor/observability/data-visualization/). - - The [Observability Backend](https://about.gitlab.com/direction/monitor/observability/data-management/). - - [Data visualization](https://about.gitlab.com/direction/monitor/observability/data-visualization/). - documentation_url: https://docs.gitlab.com/ee/operations/error_tracking.html diff --git a/data/deprecations/15-9-secure-template-changes.yml b/data/deprecations/15-9-secure-template-changes.yml index 9129f17b562..390e31a0290 100644 --- a/data/deprecations/15-9-secure-template-changes.yml +++ b/data/deprecations/15-9-secure-template-changes.yml @@ -22,7 +22,7 @@ - Dependency Scanning: [`Dependency-Scanning.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Dependency-Scanning.gitlab-ci.yml) - IaC Scanning: [`SAST-IaC.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST-IaC.gitlab-ci.yml) - SAST: [`SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST.gitlab-ci.yml) - - Secret Detection: [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Secret-Detction.gitlab-ci.yml) + - Secret Detection: [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Secret-Detection.gitlab-ci.yml) We recommend that you test your pipelines before the 16.0 release if you use one of the templates listed above and you use the `_DISABLED` variables but set a value other than `"true"`. diff --git a/data/deprecations/16-0-deprecate-omnibus-grafana.yml b/data/deprecations/16-0-deprecate-omnibus-grafana.yml index 815c60099e9..93fd5c54071 100644 --- a/data/deprecations/16-0-deprecate-omnibus-grafana.yml +++ b/data/deprecations/16-0-deprecate-omnibus-grafana.yml @@ -7,8 +7,8 @@ issue_url: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7772 body: | # (required) Do not modify this line, instead modify the lines below. The version of [Grafana bundled with Omnibus GitLab](https://docs.gitlab.com/omnibus/settings/grafana.html) is - disabled in 16.0 and will be removed in 16.3. - If you are using the bundled Grafana, you must migrate to either: + [deprecated and disabled](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#deprecation-of-bundled-grafana) + in 16.0 and will be removed in 16.3. If you are using the bundled Grafana, you must migrate to either: - Another implementation of Grafana. For more information, see [Switch to new Grafana instance](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#switch-to-new-grafana-instance). diff --git a/data/deprecations/16-0-ldap_settings_unlock_groups_by_owners-deprecation.yml b/data/deprecations/16-0-ldap_settings_unlock_groups_by_owners-deprecation.yml new file mode 100644 index 00000000000..eadcd657994 --- /dev/null +++ b/data/deprecations/16-0-ldap_settings_unlock_groups_by_owners-deprecation.yml @@ -0,0 +1,9 @@ +- title: "Adding non-LDAP synced members to a locked LDAP group is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." + announcement_milestone: "16.0" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.5" # (required) The milestone when this feature is planned to be removed + breaking_change: false # (required) Change to false if this is not a breaking change. + reporter: hsutor # (required) GitLab username of the person reporting the change + stage: manage # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/213311 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Enabling the `ldap_settings_unlock_groups_by_owners` feature flag allowed non-LDAP synced users to be added to a locked LDAP group. This [feature](https://gitlab.com/gitlab-org/gitlab/-/issues/1793) has always been disabled by default and behind a feature flag. We are removing this feature to keep continuity with our SAML integration, and because allowing non-synced group members defeats the "single source of truth" principle of using a directory service. Once this feature is removed, any LDAP group members that are not synced with LDAP will lose access to that group. diff --git a/data/deprecations/16-1-dependency-proxy-graphql-field.yml b/data/deprecations/16-1-dependency-proxy-graphql-field.yml new file mode 100644 index 00000000000..80b43e33f41 --- /dev/null +++ b/data/deprecations/16-1-dependency-proxy-graphql-field.yml @@ -0,0 +1,11 @@ +- title: "GraphQL deprecation of `dependencyProxyTotalSizeInBytes` field" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "16.1" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: trizzi # (required) GitLab username of the person reporting the deprecation + stage: Package # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/414236 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + You can use GraphQL to query the amount of storage used by the GitLab Dependency Proxy. However, the `dependencyProxyTotalSizeInBytes` field is limited to ~2Gb (in bytes), which is not always large enough for the Dependency Proxy. As a result, `dependencyProxyTotalSizeInBytes` is deprecated and will be removed in GitLab 17.0. + + Use `dependencyProxyTotalSizeBytes` instead, introduced in GitLab 16.1. diff --git a/data/deprecations/16-1-non-decomposed-mode-deprecation.yml b/data/deprecations/16-1-non-decomposed-mode-deprecation.yml new file mode 100644 index 00000000000..963fc0d8230 --- /dev/null +++ b/data/deprecations/16-1-non-decomposed-mode-deprecation.yml @@ -0,0 +1,9 @@ +- title: "Running a single database is deprecated" + removal_milestone: "17.0" + announcement_milestone: "16.1" + breaking_change: true + reporter: lohrc + stage: data_stores + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/411239 + body: | + 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. diff --git a/data/deprecations/16-1-unified-approval-rules.yml b/data/deprecations/16-1-unified-approval-rules.yml new file mode 100644 index 00000000000..8622ed86d5f --- /dev/null +++ b/data/deprecations/16-1-unified-approval-rules.yml @@ -0,0 +1,29 @@ +- title: "Unified approval rules are deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." + announcement_milestone: "16.1" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: nagyv-gitlab # (required) GitLab username of the person reporting the change + stage: deploy # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/groups/gitlab-org/-/epics/9662 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Unified approval rules are deprecated in favor of multiple approval rules, which provide more flexibility. + You might not be able to migrate your Unified approval rules to multiple approval rules without breaking changes. + To help you migrate manually, we introduced migration documentation. If you don't migrate manually before unified approval + rules are removed, GitLab will automatically migrate your settings. + + In GitLab 15.11, UI support for unified approval rules was removed. + You can still access unified approval rules with the API. +# +# OPTIONAL END OF SUPPORT FIELDS +# +# If an End of Support period applies, the announcement should be shared with GitLab Support +# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. +# + end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. + # + # OTHER OPTIONAL FIELDS + # + tiers: [Premium, Ultimate] # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: https://docs.gitlab.com/ee/ci/environments/deployment_approvals.html # (optional) This is a link to the current documentation page + image_url: # (optional) This is a link to a thumbnail image depicting the feature + video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml b/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml new file mode 100644 index 00000000000..6e892a02a9b --- /dev/null +++ b/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml @@ -0,0 +1,13 @@ +- title: "Deprecate Windows CMD in GitLab Runner" # (required) The name of the feature to be deprecated + announcement_milestone: "16.1" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-06-22" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + removal_date: "2024-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: DarrenEastman # (required) GitLab username of the person reporting the deprecation + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/414864 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + In GitLab 11.11 the Windows Batch executor, the CMD shell was deprecated in GitLab Runner in favor of PowerShell. Since then, the CMD shell has continued to be supported in GitLab Runner. However this has resulted in additional complexity for both the engineering team and customers using the Runner on Windows. We plan to fully remove support for Windows CMD from GitLab Runner in 17.0. Customers should plan to use PowerShell when using the runner on Windows with the shell executor. Customers can provide feedback or ask questions in the removal issue, [issue 29479](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29479). + end_of_support_milestone: "17.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. + end_of_support_date: "2024-05-22" # (optional) The date of the milestone release when support for this feature will end. diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index bbca07fbd3c..1817942eac5 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -7,6 +7,18 @@ toc: false # Deprecations by version +These 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. + +On GitLab.com, deprecated features can be removed at any time during the month leading up to the release. + +**{rss}** **To be notified of upcoming breaking changes**, +add this URL to your RSS feed reader: `https://about.gitlab.com/breaking-changes.xml` + +You can also view [REST API](https://docs.gitlab.com/ee/api/rest/deprecations.html) +and [GraphQL](https://docs.gitlab.com/ee/api/graphql/removed_items.html) deprecations/removals. + <!-- vale off --> <!-- @@ -31,18 +43,6 @@ For deprecation reviewers (Technical Writers only): {::options parse_block_html="true" /} -These 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. - -On GitLab.com, deprecated features can be removed at any time during the month leading up to the release. - -**{rss}** **To be notified of upcoming breaking changes**, -add this URL to your RSS feed reader: `https://about.gitlab.com/breaking-changes.xml` - -You can also view [REST API](https://docs.gitlab.com/ee/api/rest/deprecations.html) -and [GraphQL](https://docs.gitlab.com/ee/api/graphql/removed_items.html) deprecations/removals. - <% if milestones.any? -%><div class="js-deprecation-filters"></div><%- end -%> <%- milestones.each do |milestone| %> <div class="milestone-wrapper" data-milestone="<%= milestone %>"> |