diff options
Diffstat (limited to 'data')
163 files changed, 468 insertions, 314 deletions
diff --git a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml index b0746502713..31d98169730 100644 --- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml +++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml @@ -1,8 +1,6 @@ - title: "NFS for Git repository storage" # The name of the feature to be deprecated announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "15.6" # The milestone when this feature is planned to be removed - removal_date: "2022-11-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed breaking_change: false body: | # Do not modify this line, instead modify the lines below. With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support/#gitaly-and-nfs) for further information. diff --git a/data/deprecations/14-10-dependency-scanning-default-java-version.yml b/data/deprecations/14-10-dependency-scanning-default-java-version.yml index c0ef84a562e..7379ac662d8 100644 --- a/data/deprecations/14-10-dependency-scanning-default-java-version.yml +++ b/data/deprecations/14-10-dependency-scanning-default-java-version.yml @@ -1,8 +1,6 @@ - title: "Dependency Scanning default Java version changed to 17" announcement_milestone: "14.10" - announcement_date: "2022-04-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: NicoleSchwartz body: | diff --git a/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml b/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml index 8a4dcd47e2c..6cce38a0b39 100644 --- a/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml +++ b/data/deprecations/14-10-deprecate-toggle-notes-confidentiality.yml @@ -1,8 +1,6 @@ - title: "Toggle notes confidentiality on APIs" announcement_milestone: "14.10" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-03-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # 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 # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. Updating notes confidential attribute is no longer supported by any means. We are changing this to simplify the experience and prevent private information from being unintentionally exposed. diff --git a/data/deprecations/14-10-old-search-migration-removal.yml b/data/deprecations/14-10-old-search-migration-removal.yml index dd6161c2414..1991c0ef177 100644 --- a/data/deprecations/14-10-old-search-migration-removal.yml +++ b/data/deprecations/14-10-old-search-migration-removal.yml @@ -1,8 +1,6 @@ - title: "Outdated indices of Advanced Search migrations" announcement_milestone: "14.10" - announcement_date: "2021-04-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | 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. diff --git a/data/deprecations/14-2-deprecation-release-cli.yml b/data/deprecations/14-2-deprecation-release-cli.yml index f937728b944..205817a7b47 100644 --- a/data/deprecations/14-2-deprecation-release-cli.yml +++ b/data/deprecations/14-2-deprecation-release-cli.yml @@ -1,8 +1,6 @@ - title: "Release CLI distributed as a generic package" # The name of the feature to be deprecated announcement_milestone: "14.2" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "14.6" # The milestone when this feature is planned to be removed - removal_date: "2021-12-22" # the date of the milestone release when this feature is planned to be removed breaking_change: false body: | # Do not modify this line, instead modify the lines below. The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as a [generic package](https://gitlab.com/gitlab-org/release-cli/-/packages) starting in GitLab 14.2. We will continue to deploy it as a binary to S3 until GitLab 14.5 and stop distributing it in S3 in GitLab 14.6. diff --git a/data/deprecations/14-2-deprecation-task-runner.yml b/data/deprecations/14-2-deprecation-task-runner.yml index b69fb0969d5..c84cd40e33e 100644 --- a/data/deprecations/14-2-deprecation-task-runner.yml +++ b/data/deprecations/14-2-deprecation-task-runner.yml @@ -1,8 +1,6 @@ - title: "Rename Task Runner pod to Toolbox" # The name of the feature to be deprecated announcement_milestone: "14.2" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated removal_milestone: "14.5" # The milestone when this feature is planned to be removed - removal_date: "2021-11-22" # the date of the milestone release when this feature is planned to be removed breaking_change: false body: | # Do not modify this line, instead modify the lines below. The Task Runner pod is used to execute periodic housekeeping tasks within the GitLab application and is often confused with the GitLab Runner. Thus, [Task Runner will be renamed to Toolbox](https://gitlab.com/groups/gitlab-org/charts/-/epics/25). diff --git a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml index 829e1b39b0f..97af3e39009 100644 --- a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml +++ b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml @@ -1,8 +1,6 @@ - title: "Legacy database configuration" announcement_milestone: "14.3" - announcement_date: "2021-09-22" removal_milestone: "15.0" - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html) diff --git a/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml index 5f28497e982..31ac99335b5 100644 --- a/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml +++ b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml @@ -1,8 +1,6 @@ - title: "OmniAuth Kerberos gem" announcement_milestone: "14.3" - announcement_date: "2021-09-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. The `omniauth-kerberos` gem will be removed in our next major release, GitLab 15.0. diff --git a/data/deprecations/14-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml index bec376121da..4f8ace11a3e 100644 --- a/data/deprecations/14-3-repository-push-audit-events.yml +++ b/data/deprecations/14-3-repository-push-audit-events.yml @@ -1,8 +1,6 @@ - title: "Audit events for repository push events" announcement_milestone: "14.3" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-09-22" # https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69024 removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#removed-events) are now deprecated and will be removed in GitLab 15.0. diff --git a/data/deprecations/14-3-serverless.yml b/data/deprecations/14-3-serverless.yml index 55a702c4d27..28e942cc65f 100644 --- a/data/deprecations/14-3-serverless.yml +++ b/data/deprecations/14-3-serverless.yml @@ -1,8 +1,6 @@ - title: "GitLab Serverless" announcement_milestone: "14.3" - announcement_date: "2021-09-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | GitLab Serverless is a feature set to support Knative-based serverless development with automatic deployments and monitoring. diff --git a/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml b/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml index 32e9f61db0c..216568b6d19 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml @@ -1,8 +1,6 @@ - title: "SaaS certificate-based integration with Kubernetes" announcement_milestone: "14.5" - announcement_date: "2021-11-15" removal_milestone: "15.9" - removal_date: "2023-02-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | The certificate-based integration with Kubernetes will be [deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). As a GitLab SaaS customer, on new namespaces, you will no longer be able to integrate GitLab and your cluster using the certificate-based approach as of GitLab 15.0. The integration for current users will be enabled per namespace. diff --git a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml index 44098f83c20..85b006e6768 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml @@ -1,8 +1,6 @@ - title: "Self-managed certificate-based integration with Kubernetes" announcement_milestone: "14.5" - announcement_date: "2021-11-15" removal_milestone: "17.0" - removal_date: "2024-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | The certificate-based integration with Kubernetes [will be deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). diff --git a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml index 953af3634f7..91f96e87703 100644 --- a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml +++ b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml @@ -1,8 +1,6 @@ - title: "Changing an instance (shared) runner to a project (specific) runner" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. In GitLab 15.0, you can no longer change an instance (shared) runner to a project (specific) runner. diff --git a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml index 447fb4e3ef5..a993fa0897c 100644 --- a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml +++ b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml @@ -1,8 +1,6 @@ - title: "`defaultMergeCommitMessageWithDescription` GraphQL API field" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprecated and will be removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template. diff --git a/data/deprecations/14-5-deprecate-opensuse-15-2.yml b/data/deprecations/14-5-deprecate-opensuse-15-2.yml index abc30980c7f..ff1702b7de5 100644 --- a/data/deprecations/14-5-deprecate-opensuse-15-2.yml +++ b/data/deprecations/14-5-deprecate-opensuse-15-2.yml @@ -1,8 +1,6 @@ - title: "openSUSE Leap 15.2 packages" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "14.8" # The milestone when this feature is planned to be removed - removal_date: "2022-02-22" # the date of the milestone release when this feature is planned to be removed breaking_change: false body: | # Do not modify this line, instead modify the lines below. Distribution support and security updates for openSUSE Leap 15.2 are [ending December 2021](https://en.opensuse.org/Lifetime#openSUSE_Leap). diff --git a/data/deprecations/14-5-deprecate-sles-12sp2.yml b/data/deprecations/14-5-deprecate-sles-12sp2.yml index cc5bef6f203..37a0e917eb9 100644 --- a/data/deprecations/14-5-deprecate-sles-12sp2.yml +++ b/data/deprecations/14-5-deprecate-sles-12sp2.yml @@ -1,8 +1,6 @@ - title: "Support for SLES 12 SP2" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. 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. diff --git a/data/deprecations/14-5-deprecation-versions-packagetype.yml b/data/deprecations/14-5-deprecation-versions-packagetype.yml index 110bb9f218f..88b0133d4d3 100644 --- a/data/deprecations/14-5-deprecation-versions-packagetype.yml +++ b/data/deprecations/14-5-deprecation-versions-packagetype.yml @@ -1,8 +1,6 @@ - title: "`Versions` on base `PackageType`" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype). diff --git a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml index 10ed8ff8ad6..c1b48e79386 100644 --- a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml +++ b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml @@ -1,8 +1,6 @@ - title: "Value Stream Analytics filtering calculation change" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. We are changing how the date filter works in Value Stream Analytics. Instead of filtering by the time that the issue or merge request was created, the date filter will filter by the end event time of the given stage. This will result in completely different figures after this change has rolled out. diff --git a/data/deprecations/14-5-disable_strict_host_key_checking.yml b/data/deprecations/14-5-disable_strict_host_key_checking.yml index c5677dd8c3c..33e1da0206b 100644 --- a/data/deprecations/14-5-disable_strict_host_key_checking.yml +++ b/data/deprecations/14-5-disable_strict_host_key_checking.yml @@ -1,8 +1,6 @@ - title: "Known host required for GitLab Runner SSH executor" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor. diff --git a/data/deprecations/14-5-geo-deprecate-promote-db.yml b/data/deprecations/14-5-geo-deprecate-promote-db.yml index 4aedc7a8876..d08ff45ad0b 100644 --- a/data/deprecations/14-5-geo-deprecate-promote-db.yml +++ b/data/deprecations/14-5-geo-deprecate-promote-db.yml @@ -1,8 +1,6 @@ - title: "`promote-db` command from `gitlab-ctl`" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-db` which is used to promote database nodes in multi-node Geo secondary sites. `gitlab-ctl promote-db` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures. diff --git a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml index 048a78aedc7..09048c33d39 100644 --- a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml +++ b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml @@ -1,8 +1,6 @@ - title: "`promote-to-primary-node` command from `gitlab-ctl`" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-to-primary-node` which was only usable for single-node Geo sites. `gitlab-ctl promote-to-primary-node` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures. diff --git a/data/deprecations/14-5-package-container-registry-api-group-update.yml b/data/deprecations/14-5-package-container-registry-api-group-update.yml index 40174c02e50..d7dbf841c72 100644 --- a/data/deprecations/14-5-package-container-registry-api-group-update.yml +++ b/data/deprecations/14-5-package-container-registry-api-group-update.yml @@ -1,8 +1,6 @@ - title: "Update to the Container Registry group-level API" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. In milestone 15.0, support for the `tags` and `tags_count` parameters will be removed from the Container Registry API that [gets registry repositories from a group](../api/container_registry.md#within-a-group). diff --git a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml index 0d9fe9c9539..075f518c3af 100644 --- a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml +++ b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml @@ -1,8 +1,6 @@ - title: "`dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. We added a feature flag because [GitLab-#11582](https://gitlab.com/gitlab-org/gitlab/-/issues/11582) changed how public groups use the Dependency Proxy. Prior to this change, you could use the Dependency Proxy without authentication. The change requires authentication to use the Dependency Proxy. diff --git a/data/deprecations/14-5-remove-package-pipelines-api.yml b/data/deprecations/14-5-remove-package-pipelines-api.yml index 0cf2201d6e3..f6a091c7c4b 100644 --- a/data/deprecations/14-5-remove-package-pipelines-api.yml +++ b/data/deprecations/14-5-remove-package-pipelines-api.yml @@ -1,8 +1,6 @@ - title: "Package pipelines in API payload is paginated" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines. diff --git a/data/deprecations/14-5-remove-pipelines-from-version-field.yml b/data/deprecations/14-5-remove-pipelines-from-version-field.yml index 0470bba35cc..815a08550b2 100644 --- a/data/deprecations/14-5-remove-pipelines-from-version-field.yml +++ b/data/deprecations/14-5-remove-pipelines-from-version-field.yml @@ -1,8 +1,6 @@ - title: "`pipelines` field from the `version` field" # The name of the feature to be deprecated announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype) to get the pipelines for package versions: diff --git a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml index 9cf1294467a..0daa5fb24c9 100644 --- a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml +++ b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml @@ -1,8 +1,6 @@ - title: "GraphQL API Runner status will not return `paused`" announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-11-22" removal_milestone: "16.0" # the milestone when this feature is planned to be removed - removal_date: "2023-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. The GitLab Runner GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 16.0. diff --git a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml index 614a1bc73d5..7c7096335f8 100644 --- a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml +++ b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml @@ -1,8 +1,6 @@ - title: "Enforced validation of security report schemas" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [Security report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-6-container-scanning-schemas-below-14.yml b/data/deprecations/14-6-container-scanning-schemas-below-14.yml index 244c5662b25..910d42631ce 100644 --- a/data/deprecations/14-6-container-scanning-schemas-below-14.yml +++ b/data/deprecations/14-6-container-scanning-schemas-below-14.yml @@ -1,8 +1,6 @@ - title: "Container scanning schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [Container scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml index dcb643d5787..fa663523a3a 100644 --- a/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml +++ b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml @@ -1,8 +1,6 @@ - title: "Coverage guided fuzzing schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [Coverage guided fuzzing report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) below version 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-6-dast-schemas-below-14.yml b/data/deprecations/14-6-dast-schemas-below-14.yml index 8ff3d899951..07dd822ffa8 100644 --- a/data/deprecations/14-6-dast-schemas-below-14.yml +++ b/data/deprecations/14-6-dast-schemas-below-14.yml @@ -1,8 +1,6 @@ - title: "DAST schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [DAST report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml index 5255779f5a8..da666ab3b6a 100644 --- a/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml +++ b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml @@ -1,8 +1,6 @@ - title: "Dependency scanning schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [Dependency scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-6-deprecate-types.yml b/data/deprecations/14-6-deprecate-types.yml index c2afcc8226d..1b46f593264 100644 --- a/data/deprecations/14-6-deprecate-types.yml +++ b/data/deprecations/14-6-deprecate-types.yml @@ -1,8 +1,6 @@ - title: "`type` and `types` keyword in CI/CD configuration" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-12-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. 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. diff --git a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml index 03bfd5e1a7b..ac74fe5e84f 100644 --- a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml +++ b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml @@ -1,6 +1,5 @@ - title: "Legacy approval status names from License Compliance API" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-12-22" # 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: "15.0" # The milestone when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. @@ -14,4 +13,3 @@ documentation_url: # (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 - removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed diff --git a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml index 5321c23e797..952f3267723 100644 --- a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml +++ b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml @@ -1,6 +1,5 @@ - title: "bundler-audit Dependency Scanning tool" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-12-22" # 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: "15.0" # The milestone when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. @@ -14,4 +13,3 @@ documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.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 - removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed diff --git a/data/deprecations/14-6-job_char_limit.yml b/data/deprecations/14-6-job_char_limit.yml index a1422f57506..4b94650fe23 100644 --- a/data/deprecations/14-6-job_char_limit.yml +++ b/data/deprecations/14-6-job_char_limit.yml @@ -1,8 +1,6 @@ - title: "CI/CD job name length limit" # The name of the feature to be deprecated announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-12-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. In GitLab 15.0 we are going to limit the number of characters in CI/CD job names to 255. Any pipeline with job names that exceed the 255 character limit will stop working after the 15.0 release. diff --git a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml index 639c48f7302..9ee015c9883 100644 --- a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml +++ b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml @@ -1,8 +1,6 @@ - title: "apiFuzzingCiConfigurationCreate GraphQL mutation" announcement_milestone: "14.6" - announcement_date: "2021-12-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | The API Fuzzing configuration snippet is now being generated client-side and does not require an diff --git a/data/deprecations/14-6-sast-schemas-below-14.yml b/data/deprecations/14-6-sast-schemas-below-14.yml index 9afab73e316..0d1f25bdfa3 100644 --- a/data/deprecations/14-6-sast-schemas-below-14.yml +++ b/data/deprecations/14-6-sast-schemas-below-14.yml @@ -1,8 +1,6 @@ - title: "SAST schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [SAST report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-6-secret-detection-schemas-below-14.yml b/data/deprecations/14-6-secret-detection-schemas-below-14.yml index 53c9cf89795..4a0bd69c433 100644 --- a/data/deprecations/14-6-secret-detection-schemas-below-14.yml +++ b/data/deprecations/14-6-secret-detection-schemas-below-14.yml @@ -1,8 +1,6 @@ - title: "Secret detection schemas below 14.0.0" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | # Do not modify this line, instead modify the lines below. [Secret detection report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases) versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation diff --git a/data/deprecations/14-7-deprecate-artifacts-keyword.yml b/data/deprecations/14-7-deprecate-artifacts-keyword.yml index e4c82ebcc24..17692f4b556 100644 --- a/data/deprecations/14-7-deprecate-artifacts-keyword.yml +++ b/data/deprecations/14-7-deprecate-artifacts-keyword.yml @@ -1,8 +1,6 @@ - title: "`artifacts:reports:cobertura` keyword" announcement_milestone: "14.7" - announcement_date: "2022-01-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | Currently, test coverage visualizations in GitLab only support Cobertura reports. Starting 15.0, the diff --git a/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml index 080853e6f1e..9b1282e7ca0 100644 --- a/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml +++ b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml @@ -1,8 +1,6 @@ - title: "Godep support in License Compliance" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed. body: | # Do not modify this line, instead modify the lines below. The Godep dependency manager for Golang was deprecated in 2020 by Go and has been replaced with Go modules. diff --git a/data/deprecations/14-7-deprecate-merged_by-api-field.yml b/data/deprecations/14-7-deprecate-merged_by-api-field.yml index 623a544052a..b49b8bf5271 100644 --- a/data/deprecations/14-7-deprecate-merged_by-api-field.yml +++ b/data/deprecations/14-7-deprecate-merged_by-api-field.yml @@ -12,9 +12,7 @@ - title: "merged_by API field" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # the date of the milestone release when this feature is planned to be removed breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-requests) has been deprecated in favor of the `merge_user` field which more correctly identifies who merged a merge request when performing actions (merge when pipeline succeeds, add to merge train) other than a simple merge. API users are encouraged to use the new `merge_user` field instead. The `merged_by` field will be removed in v5 of the GitLab REST API. diff --git a/data/deprecations/14-7-deprecate-static-site-editor.yml b/data/deprecations/14-7-deprecate-static-site-editor.yml index f44f4f3f256..ee87dfb2ed2 100644 --- a/data/deprecations/14-7-deprecate-static-site-editor.yml +++ b/data/deprecations/14-7-deprecate-static-site-editor.yml @@ -1,8 +1,6 @@ - title: "Static Site Editor" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed. body: | # Do not modify this line, instead modify the lines below. The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver smiliar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the [Web IDE](https://docs.gitlab.com/ee/user/project/web_ide/index.html). diff --git a/data/deprecations/14-7-pseudonymizer.yml b/data/deprecations/14-7-pseudonymizer.yml index 43987332210..be52b467337 100644 --- a/data/deprecations/14-7-pseudonymizer.yml +++ b/data/deprecations/14-7-pseudonymizer.yml @@ -1,8 +1,6 @@ - title: "Pseudonymizer" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed. body: | # Do not modify this line, instead modify the lines below. The Pseudonymizer feature is generally unused, can cause production issues with large databases, diff --git a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml index 324339a45ea..3b812068b30 100644 --- a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml +++ b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml @@ -1,8 +1,6 @@ - title: "Sidekiq metrics and health checks configuration" announcement_milestone: "14.7" - announcement_date: "2021-01-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. Exporting Sidekiq metrics and health checks using a single process and port is deprecated. diff --git a/data/deprecations/14-8-Elasticsearch-6-8.yml b/data/deprecations/14-8-Elasticsearch-6-8.yml index d9b7f607f27..3c35475c4a8 100644 --- a/data/deprecations/14-8-Elasticsearch-6-8.yml +++ b/data/deprecations/14-8-Elasticsearch-6-8.yml @@ -1,8 +1,6 @@ - title: "Elasticsearch 6.8" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | Elasticsearch 6.8 is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. diff --git a/data/deprecations/14-8-ci-build-variables.yml b/data/deprecations/14-8-ci-build-variables.yml index f12f6dda5a6..1dda7e8b32a 100644 --- a/data/deprecations/14-8-ci-build-variables.yml +++ b/data/deprecations/14-8-ci-build-variables.yml @@ -1,8 +1,6 @@ - title: "`CI_BUILD_*` predefined variables" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: dhershkovitch body: | diff --git a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml index 1b262c98d40..cd94adca75f 100644 --- a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml +++ b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml @@ -1,8 +1,6 @@ - title: "Required pipeline configurations in Premium tier" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: sam.white body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-compliance-status-check-api-field.yml b/data/deprecations/14-8-compliance-status-check-api-field.yml index 6493905a6d5..77b12142a9a 100644 --- a/data/deprecations/14-8-compliance-status-check-api-field.yml +++ b/data/deprecations/14-8-compliance-status-check-api-field.yml @@ -1,8 +1,6 @@ - title: "External status check API breaking changes" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: sam.white body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml index f2fd11ceb28..fdd8b355dca 100644 --- a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml +++ b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml @@ -1,8 +1,6 @@ - title: "`projectFingerprint` in `PipelineSecurityReportFinding` GraphQL" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: matt_wilson # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml index 070262707a9..0deb0e9e788 100644 --- a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml +++ b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml @@ -1,6 +1,5 @@ - title: "Retire-JS Dependency Scanning tool" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed breaking_change: true body: | # Do not modify this line, instead modify the lines below. @@ -14,4 +13,3 @@ documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.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 - removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed diff --git a/data/deprecations/14-8-enforce-pat-expiration.yml b/data/deprecations/14-8-enforce-pat-expiration.yml index 6f165bbdb19..37cf4d827d1 100644 --- a/data/deprecations/14-8-enforce-pat-expiration.yml +++ b/data/deprecations/14-8-enforce-pat-expiration.yml @@ -1,8 +1,6 @@ - title: "Optional enforcement of PAT expiration" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: djensen # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-enforce-ssh-expiration.yml b/data/deprecations/14-8-enforce-ssh-expiration.yml index d772adf1b4c..6a67eee4b5f 100644 --- a/data/deprecations/14-8-enforce-ssh-expiration.yml +++ b/data/deprecations/14-8-enforce-ssh-expiration.yml @@ -1,8 +1,6 @@ - title: "Optional enforcement of SSH expiration" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: djensen # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml index 0390632968a..333ae5b3a75 100644 --- a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml +++ b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml @@ -1,8 +1,6 @@ - title: "Deprecate custom Geo:db:* Rake tasks" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: false reporter: nhxnguyen body: | diff --git a/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml index c4a4117f0cd..84f502b2089 100644 --- a/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml +++ b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml @@ -1,8 +1,6 @@ - title: "Deprecate Geo Admin UI Routes" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: false reporter: nhxnguyen body: | diff --git a/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml b/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml index 0273559a268..68ef00e5cd9 100644 --- a/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml +++ b/data/deprecations/14-8-gitaly-deprecate-legacy-config-options.yml @@ -1,8 +1,6 @@ - title: "Deprecate legacy Gitaly configuration methods" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: mjwood # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-gitaly-remove-per-repository-election.yml b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml index 88412780048..e2d9eafe0e1 100644 --- a/data/deprecations/14-8-gitaly-remove-per-repository-election.yml +++ b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml @@ -1,8 +1,6 @@ - title: "Configurable Gitaly `per_repository` election strategy" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "14.9" # The milestone when this feature is planned to be removed - removal_date: "2022-03-22" # 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: false # If this deprecation is a breaking change, set this value to true reporter: mjwood # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-graphql-ids.yml b/data/deprecations/14-8-graphql-ids.yml index 599748652f6..03987176e33 100644 --- a/data/deprecations/14-8-graphql-ids.yml +++ b/data/deprecations/14-8-graphql-ids.yml @@ -1,8 +1,6 @@ - title: "GraphQL ID and GlobalID compatibility" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: alexkalderimis body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-grpc-proxy.yml b/data/deprecations/14-8-grpc-proxy.yml index 9f7a044d154..d2787d5d449 100644 --- a/data/deprecations/14-8-grpc-proxy.yml +++ b/data/deprecations/14-8-grpc-proxy.yml @@ -1,8 +1,6 @@ - title: "Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab" announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: jacobvosmaer-gitlab # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-iteration-started-field.yml b/data/deprecations/14-8-iteration-started-field.yml index a4401632682..a3c693001c1 100644 --- a/data/deprecations/14-8-iteration-started-field.yml +++ b/data/deprecations/14-8-iteration-started-field.yml @@ -1,8 +1,6 @@ - title: "`started` iterations API field" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. The `started` field in the [iterations API](https://docs.gitlab.com/ee/api/iterations.html#list-project-iterations) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `current` field (already available) which aligns with the naming for other time-based entities, such as milestones. diff --git a/data/deprecations/14-8-protect-cns-chs.yml b/data/deprecations/14-8-protect-cns-chs.yml index 098b571f9fb..7f0befa77c5 100644 --- a/data/deprecations/14-8-protect-cns-chs.yml +++ b/data/deprecations/14-8-protect-cns-chs.yml @@ -1,8 +1,6 @@ - title: "Container Network and Host Security" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: sam.white body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-protect-vulnerability-check.yml b/data/deprecations/14-8-protect-vulnerability-check.yml index 737756ae8ac..fd8e467d222 100644 --- a/data/deprecations/14-8-protect-vulnerability-check.yml +++ b/data/deprecations/14-8-protect-vulnerability-check.yml @@ -1,8 +1,6 @@ - title: "Vulnerability Check" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: sam.white body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml index 24e192e7f33..b43671c4969 100644 --- a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml +++ b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml @@ -1,8 +1,6 @@ - title: "Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: sarahwaldner # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-request-profiling.yml b/data/deprecations/14-8-request-profiling.yml index eb7ab356d27..ed080993abc 100644 --- a/data/deprecations/14-8-request-profiling.yml +++ b/data/deprecations/14-8-request-profiling.yml @@ -1,8 +1,6 @@ - title: "Request profiling" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: iroussos body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml index a8173a80047..22cc199c704 100644 --- a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml +++ b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml @@ -1,8 +1,6 @@ - title: "REST and GraphQL API Runner usage of `active` replaced by `paused`" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: pedropombeiro body: | diff --git a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml index cf0476ae768..ce372a36f69 100644 --- a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml +++ b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml @@ -1,8 +1,6 @@ - title: "GraphQL API Runner will not accept `status` filter values of `active` or `paused`" announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. The GitLab Runner GraphQL endpoints will stop accepting `paused` or `active` as a status value in GitLab 16.0. diff --git a/data/deprecations/14-8-sast-analyzer-removals.yml b/data/deprecations/14-8-sast-analyzer-removals.yml index 0ad3920669a..3ebfd23beb5 100644 --- a/data/deprecations/14-8-sast-analyzer-removals.yml +++ b/data/deprecations/14-8-sast-analyzer-removals.yml @@ -1,8 +1,6 @@ - title: "SAST analyzer consolidation and CI/CD template changes" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.4" - removal_date: "2022-09-22" breaking_change: true reporter: connorgilbert body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-sast-dotnet-21.yml b/data/deprecations/14-8-sast-dotnet-21.yml index 1a09329244d..581c579e90a 100644 --- a/data/deprecations/14-8-sast-dotnet-21.yml +++ b/data/deprecations/14-8-sast-dotnet-21.yml @@ -1,8 +1,6 @@ - title: "SAST support for .NET 2.1" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: connorgilbert body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-sast-secret-analyzer-image.yml b/data/deprecations/14-8-sast-secret-analyzer-image.yml index e774941ace4..113fd9bb1bc 100644 --- a/data/deprecations/14-8-sast-secret-analyzer-image.yml +++ b/data/deprecations/14-8-sast-secret-analyzer-image.yml @@ -1,8 +1,6 @@ - title: "Secure and Protect analyzer images published in new location" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: connorgilbert body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-sast-spotbugs-java-8.yml b/data/deprecations/14-8-sast-spotbugs-java-8.yml index 58d1e205aad..75e4ffc94bc 100644 --- a/data/deprecations/14-8-sast-spotbugs-java-8.yml +++ b/data/deprecations/14-8-sast-spotbugs-java-8.yml @@ -1,8 +1,6 @@ - title: "Out-of-the-box SAST support for Java 8" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: connorgilbert body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-secret-detection-configurations.yml b/data/deprecations/14-8-secret-detection-configurations.yml index 8078d7c6fa0..1b4197c2792 100644 --- a/data/deprecations/14-8-secret-detection-configurations.yml +++ b/data/deprecations/14-8-secret-detection-configurations.yml @@ -1,8 +1,6 @@ - title: "Secret Detection configuration variables deprecated" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: false reporter: connorgilbert body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml b/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml index e1616cd1f6e..2db3d7190cc 100644 --- a/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml +++ b/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml @@ -1,8 +1,6 @@ - title: "Secure and Protect analyzer major version update" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: NicoleSchwartz # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-8-secure-ca-python-deprecation.yml b/data/deprecations/14-8-secure-ca-python-deprecation.yml index fab7455fe1c..79d1fb4cd34 100644 --- a/data/deprecations/14-8-secure-ca-python-deprecation.yml +++ b/data/deprecations/14-8-secure-ca-python-deprecation.yml @@ -1,8 +1,6 @@ - title: "Dependency Scanning Python 3.9 and 3.6 image deprecation" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. For those using Dependency Scanning for Python projects, we are deprecating the default `gemnasium-python:2` image which uses Python 3.6 as well as the custom `gemnasium-python:2-python-3.9` image which uses Python 3.9. The new default image as of GitLab 15.0 will be for Python 3.9 as it is a [supported version](https://endoflife.date/python) and 3.6 [is no longer supported](https://endoflife.date/python). diff --git a/data/deprecations/14-9-background-upload.yml b/data/deprecations/14-9-background-upload.yml index e336cb7d39c..ece2f7d0fdc 100644 --- a/data/deprecations/14-9-background-upload.yml +++ b/data/deprecations/14-9-background-upload.yml @@ -1,8 +1,6 @@ - title: "Background upload for object storage" announcement_milestone: "14.9" - announcement_date: "2022-03-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: fzimmer body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-deprecate-composer-download-permissions.yml b/data/deprecations/14-9-deprecate-composer-download-permissions.yml index 47e1502c466..22b2bc2b585 100644 --- a/data/deprecations/14-9-deprecate-composer-download-permissions.yml +++ b/data/deprecations/14-9-deprecate-composer-download-permissions.yml @@ -1,8 +1,6 @@ - title: "Permissions change for downloading Composer dependencies" announcement_milestone: "14.9" - announcement_date: "2022-03-22" removal_milestone: "14.10" - removal_date: "2022-04-22" breaking_change: true reporter: trizzi body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-deprecate-debian-9.yml b/data/deprecations/14-9-deprecate-debian-9.yml index 7057ceb4176..11ffc640489 100644 --- a/data/deprecations/14-9-deprecate-debian-9.yml +++ b/data/deprecations/14-9-deprecate-debian-9.yml @@ -1,7 +1,5 @@ - title: "Deprecate support for Debian 9" announcement_milestone: "14.9" - announcement_date: "2022-03-22" removal_milestone: "15.1" - removal_date: "2022-06-22" body: | Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](https://wiki.debian.org/LTS). Therefore, we will no longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11. diff --git a/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml index 9e6da8c8776..8f2aaf3b743 100644 --- a/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml +++ b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml @@ -1,8 +1,6 @@ - title: "GraphQL permissions change for Package settings" announcement_milestone: "14.9" - announcement_date: "2022-03-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: trizzi body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-deprecate-testcoveragesetting.yml b/data/deprecations/14-9-deprecate-testcoveragesetting.yml index 9532a34b568..1f50aab1c27 100644 --- a/data/deprecations/14-9-deprecate-testcoveragesetting.yml +++ b/data/deprecations/14-9-deprecate-testcoveragesetting.yml @@ -1,8 +1,6 @@ - title: "Test coverage project CI/CD setting" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: jreporter # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml b/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml index 0090a960417..9dbe6c24968 100644 --- a/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml +++ b/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml @@ -1,8 +1,6 @@ - title: "htpasswd Authentication for the Container Registry" announcement_milestone: "14.9" - announcement_date: "2022-03-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: trizzi body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml b/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml index f69ac6e9a82..667995981e2 100644 --- a/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml +++ b/data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml @@ -1,8 +1,6 @@ - title: "user_email_lookup_limit API field" announcement_milestone: "14.9" - announcement_date: "2022-03-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true reporter: fzimmer body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-pages-daemon.yml b/data/deprecations/14-9-pages-daemon.yml index 827daf18c21..1e2a1c998ad 100644 --- a/data/deprecations/14-9-pages-daemon.yml +++ b/data/deprecations/14-9-pages-daemon.yml @@ -1,8 +1,6 @@ - title: "GitLab Pages running as daemon" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-03-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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: false # If this deprecation is a breaking change, set this value to true reporter: cbalane # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/14-9-system_monitoring.yml b/data/deprecations/14-9-system_monitoring.yml index 10d0a6db422..a621619f375 100644 --- a/data/deprecations/14-9-system_monitoring.yml +++ b/data/deprecations/14-9-system_monitoring.yml @@ -1,8 +1,6 @@ - title: "GitLab self-monitoring project" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-03-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: abellucci # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml b/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml index 4f8fc40fd73..b506816a54b 100644 --- a/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml +++ b/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml @@ -1,8 +1,6 @@ - title: "CiCdSettingsUpdate mutation renamed to ProjectCiCdSettingsUpdate" announcement_milestone: "15.0" - announcement_date: "2022-05-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: pedropombeiro stage: Verify diff --git a/data/deprecations/15-0-deprecate-monitor-logging.yml b/data/deprecations/15-0-deprecate-monitor-logging.yml index 62f889e666f..e7a77dd1c14 100644 --- a/data/deprecations/15-0-deprecate-monitor-logging.yml +++ b/data/deprecations/15-0-deprecate-monitor-logging.yml @@ -1,8 +1,6 @@ - title: "Logging in GitLab" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. The logging features in GitLab allow users to install the ELK stack (Elasticsearch, Logstash, and Kibana) to aggregate and manage application logs. Users can search for relevant logs in GitLab. However, since deprecating certificate-based integration with Kubernetes clusters and GitLab Managed Apps, we don't have a recommended solution for logging within GitLab. For more information, you can follow the issue for [integrating Opstrace with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976). diff --git a/data/deprecations/15-0-deprecate-monitor-metrics.yml b/data/deprecations/15-0-deprecate-monitor-metrics.yml index 652845f0090..e10dba0c8e0 100644 --- a/data/deprecations/15-0-deprecate-monitor-metrics.yml +++ b/data/deprecations/15-0-deprecate-monitor-metrics.yml @@ -1,8 +1,6 @@ - title: "Monitor performance metrics through Prometheus" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. By displaying data stored in a Prometheus instance, GitLab allows users to view performance metrics. GitLab also displays visualizations of these metrics in dashboards. The user can connect to a previously-configured external Prometheus instance, or set up Prometheus as a GitLab Managed App. diff --git a/data/deprecations/15-0-deprecate-monitor-tracing.yml b/data/deprecations/15-0-deprecate-monitor-tracing.yml index 3989ea2ed68..5a7e06a96e9 100644 --- a/data/deprecations/15-0-deprecate-monitor-tracing.yml +++ b/data/deprecations/15-0-deprecate-monitor-tracing.yml @@ -1,8 +1,6 @@ - title: "Tracing in GitLab" # The name of the feature to be deprecated announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-01-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distributed tracing system. GitLab users can navigate to their Jaeger instance to gain insight into the performance of a deployed application, tracking each function or microservice that handles a given request. Tracing in GitLab is deprecated in GitLab 14.7, and scheduled for removal in 15.0. To track work on a possible replacement, see the issue for [Opstrace integration with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976). diff --git a/data/deprecations/15-0-deprecate-postgresql-12.yml b/data/deprecations/15-0-deprecate-postgresql-12.yml index 1cf463d9411..ec8e32f1c1d 100644 --- a/data/deprecations/15-0-deprecate-postgresql-12.yml +++ b/data/deprecations/15-0-deprecate-postgresql-12.yml @@ -1,8 +1,6 @@ - title: "PostgreSQL 12 deprecated" announcement_milestone: "15.0" - announcement_date: "2022-05-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: iroussos body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml index 5d2527094f9..53a9a2dda5d 100644 --- a/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml +++ b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml @@ -1,8 +1,6 @@ - title: "Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node" announcement_milestone: "14.8" - announcement_date: "2022-02-22" removal_milestone: "15.0" - removal_date: "2022-05-22" breaking_change: true body: | # Do not modify this line, instead modify the lines below. The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTrendsMeasurements` in 13.10 and the old field name has been marked as deprecated. To fix the existing GraphQL queries, replace `instanceStatisticsMeasurements` with `usageTrendsMeasurements`. diff --git a/data/deprecations/15-0-oauth-noexpiry.yml b/data/deprecations/15-0-oauth-noexpiry.yml index 88ccb7702b8..e27ac4d8725 100644 --- a/data/deprecations/15-0-oauth-noexpiry.yml +++ b/data/deprecations/15-0-oauth-noexpiry.yml @@ -1,8 +1,6 @@ - title: "OAuth tokens without expiration" # The name of the feature to be deprecated announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-02-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. By default, all new applications expire access tokens after 2 hours. In GitLab 14.2 and earlier, OAuth access tokens diff --git a/data/deprecations/15-0-oauth.yml b/data/deprecations/15-0-oauth.yml index b7af6b51afc..db962abfe87 100644 --- a/data/deprecations/15-0-oauth.yml +++ b/data/deprecations/15-0-oauth.yml @@ -1,8 +1,6 @@ - title: "OAuth implicit grant" # The name of the feature to be deprecated announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-06-22" # 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: "15.0" # The milestone when this feature is planned to be removed - removal_date: "2022-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. 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). diff --git a/data/deprecations/15-0-runner-status-legacy-mode.yml b/data/deprecations/15-0-runner-status-legacy-mode.yml index dfdbf6e5f58..dcc74703e49 100644 --- a/data/deprecations/15-0-runner-status-legacy-mode.yml +++ b/data/deprecations/15-0-runner-status-legacy-mode.yml @@ -1,8 +1,6 @@ - title: "GraphQL API legacyMode argument for Runner status" # The name of the feature to be deprecated announcement_milestone: "15.0" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-05-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # 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 # If this deprecation is a breaking change, set this value to true reporter: pedropombeiro # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/15-1-deprecate-maintainer_note.yml b/data/deprecations/15-1-deprecate-maintainer_note.yml index fc35244827d..175f85e997f 100644 --- a/data/deprecations/15-1-deprecate-maintainer_note.yml +++ b/data/deprecations/15-1-deprecate-maintainer_note.yml @@ -1,8 +1,6 @@ - title: "REST API Runner maintainer_note" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: pedropombeiro # (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 diff --git a/data/deprecations/15-1-jira-github-enterprise-dvcs.yml b/data/deprecations/15-1-jira-github-enterprise-dvcs.yml index 69606c3dd2d..88b1b41953c 100644 --- a/data/deprecations/15-1-jira-github-enterprise-dvcs.yml +++ b/data/deprecations/15-1-jira-github-enterprise-dvcs.yml @@ -1,8 +1,6 @@ - title: "Jira GitHub Enterprise DVCS integration" # The name of the feature to be deprecated announcement_milestone: "15.1" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-06-22" # 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: "16.0" # The milestone when this feature is planned to be removed - removal_date: "2023-05-22" # 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. breaking_change: true # If this deprecation is a breaking change, set this value to true body: | # Do not modify this line, instead modify the lines below. The [Jira DVCS Connector](https://docs.gitlab.com/ee/integration/jira/dvcs.html) (which enables the [Jira Development Panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/)), will no longer support Jira Cloud users starting with GitLab 16.0. The [GitLab for Jira App](https://docs.gitlab.com/ee/integration/jira/connect-app.html) has always been recommended for Jira Cloud users, and it will be required instead of the DVCS connector. If you are a Jira Cloud user, we recommended you begin migrating to the GitLab for Jira App. diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml index aa6b9ea06db..a77b39c3c7e 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-name.yml @@ -1,8 +1,6 @@ - title: "PipelineSecurityReportFinding name GraphQL field" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: matt_wilson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml index e127a258f4f..7e444ed1436 100644 --- a/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml +++ b/data/deprecations/15-1-pipelinesecurityreportfinding-projectfingerprint.yml @@ -1,8 +1,6 @@ - title: "PipelineSecurityReportFinding projectFingerprint GraphQL field" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: matt_wilson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-1-project-pipeline-securityReportFindings.yml b/data/deprecations/15-1-project-pipeline-securityReportFindings.yml index bb46a9b90dd..1bb60adb812 100644 --- a/data/deprecations/15-1-project-pipeline-securityReportFindings.yml +++ b/data/deprecations/15-1-project-pipeline-securityReportFindings.yml @@ -1,8 +1,6 @@ - title: "project.pipeline.securityReportFindings GraphQL query" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: matt_wilson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml index 2bcf1e114b4..4bec4ff1fd0 100644 --- a/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml +++ b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml @@ -1,8 +1,6 @@ - title: "Vulnerability Report sort by State" # (required) The name of the feature to be deprecated announcement_milestone: "15.0" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-05-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: "15.3" # (required) The milestone when this feature is planned to be removed - removal_date: "2022-08-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: false # (required) If this deprecation is a breaking change, set this value to true reporter: matt_wilson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-2-job_age-deprecation.yml b/data/deprecations/15-2-job_age-deprecation.yml index b550f10920e..c4b2d5bb683 100644 --- a/data/deprecations/15-2-job_age-deprecation.yml +++ b/data/deprecations/15-2-job_age-deprecation.yml @@ -19,9 +19,7 @@ # - title: "Remove `job_age` parameter from `POST /jobs/request` Runner endpoint" # (required) The name of the feature to be deprecated announcement_milestone: "15.2" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-07-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: jheimbuck_gl # (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 @@ -34,7 +32,6 @@ # OPTIONAL FIELDS # end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. tiers: # (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 image_url: # (optional) This is a link to a thumbnail image depicting the feature diff --git a/data/deprecations/15-3-deprecate-redis-5.yml b/data/deprecations/15-3-deprecate-redis-5.yml index b94539061e5..da970bbef3b 100644 --- a/data/deprecations/15-3-deprecate-redis-5.yml +++ b/data/deprecations/15-3-deprecate-redis-5.yml @@ -1,8 +1,6 @@ - title: "Redis 5 deprecated" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-08-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: tnir stage: Enablement @@ -12,5 +10,4 @@ Redis 5 has reached the end of life in April 2022 and will no longer be supported as of GitLab 15.6. If you are using your own Redis 5.0 instance, you should upgrade it to Redis 6.0 or higher before upgrading to GitLab 16.0 or higher. end_of_support_milestone: "15.6" - end_of_support_date: "2022-11-22" documentation_url: https://docs.gitlab.com/ee/install/requirements.html diff --git a/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml b/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml index a3965f7d0cb..4650173fcc6 100644 --- a/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml +++ b/data/deprecations/15-3-deprecation-vulnerability-report-tool-sort.yml @@ -1,8 +1,6 @@ - title: "Vulnerability Report sort by Tool" # (required) The name of the feature to be deprecated announcement_milestone: "15.1" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-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: "15.3" # (required) The milestone when this feature is planned to be removed - removal_date: "2022-08-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: false # (required) If this deprecation is a breaking change, set this value to true reporter: matt_wilson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-3-omniauth-cas3.yml b/data/deprecations/15-3-omniauth-cas3.yml index 70290a3fc51..070e1e24431 100644 --- a/data/deprecations/15-3-omniauth-cas3.yml +++ b/data/deprecations/15-3-omniauth-cas3.yml @@ -3,9 +3,7 @@ # - title: "CAS OmniAuth provider" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-08-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: hsutor # (required) GitLab username of the person reporting the deprecation stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-3-omniauth-crowd.yml b/data/deprecations/15-3-omniauth-crowd.yml index e14b40a1505..ae883bd9140 100644 --- a/data/deprecations/15-3-omniauth-crowd.yml +++ b/data/deprecations/15-3-omniauth-crowd.yml @@ -3,9 +3,7 @@ # - title: "Atlassian Crowd OmniAuth provider" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-08-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: hsutor # (required) GitLab username of the person reporting the deprecation stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-3-pipeline_activity_limit.yml b/data/deprecations/15-3-pipeline_activity_limit.yml index 5374e2d7972..ea7d0476910 100644 --- a/data/deprecations/15-3-pipeline_activity_limit.yml +++ b/data/deprecations/15-3-pipeline_activity_limit.yml @@ -19,9 +19,7 @@ # - title: "Maximum number of active pipelines per project limit (`ci_active_pipelines`)" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-08-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: false # (required) If this deprecation is a breaking change, set this value to true reporter: jheimbuck_gl # (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 diff --git a/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml b/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml index 691196a892b..1050b0e8327 100644 --- a/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml +++ b/data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml @@ -3,9 +3,7 @@ # - title: "Use of `id` field in vulnerabilityFindingDismiss mutation" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-08-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: 2023-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: matt_wilson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth @@ -16,7 +14,6 @@ # OPTIONAL FIELDS # end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. tiers: # (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/api/graphql/reference/index.html#mutationvulnerabilityfindingdismiss image_url: # (optional) This is a link to a thumbnail image depicting the feature diff --git a/data/deprecations/15-4-confidence-field-in-graphql.yml b/data/deprecations/15-4-confidence-field-in-graphql.yml index 90e9a452a43..7f6e0d64c2e 100644 --- a/data/deprecations/15-4-confidence-field-in-graphql.yml +++ b/data/deprecations/15-4-confidence-field-in-graphql.yml @@ -1,8 +1,6 @@ - title: "Vulnerability confidence field" announcement_milestone: "15.4" - announcement_date: "2022-09-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: matt_wilson stage: govern diff --git a/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml b/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml index 8cb2a5a0b93..e68286960aa 100644 --- a/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml +++ b/data/deprecations/15-4-create-deprecation-draft-quick-action-toggle.yml @@ -1,8 +1,6 @@ - title: "Toggle behavior of `/draft` quick action in merge requests" # (required) The name of the feature to be deprecated announcement_milestone: "15.4" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-09-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: phikai # (required) GitLab username of the person reporting the deprecation stage: create # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-4-cs-docker-variables.yml b/data/deprecations/15-4-cs-docker-variables.yml index 9bd0acff5b0..9cdf23f4112 100644 --- a/data/deprecations/15-4-cs-docker-variables.yml +++ b/data/deprecations/15-4-cs-docker-variables.yml @@ -1,8 +1,6 @@ - title: "Container Scanning variables that reference Docker" announcement_milestone: "15.4" - announcement_date: "2022-09-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: sam.white stage: secure diff --git a/data/deprecations/15-4-deprecate-bundled-grafana.yml b/data/deprecations/15-4-deprecate-bundled-grafana.yml index 1a78691c475..8bc2cf84031 100644 --- a/data/deprecations/15-4-deprecate-bundled-grafana.yml +++ b/data/deprecations/15-4-deprecate-bundled-grafana.yml @@ -1,8 +1,6 @@ - title: "Bundled Grafana deprecated" announcement_milestone: "15.3" - announcement_date: "2022-08-22" removal_milestone: "15.4" - removal_date: "2022-09-22" breaking_change: false reporter: dorrino body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/15-4-non-expiring-access-tokens.yml b/data/deprecations/15-4-non-expiring-access-tokens.yml index a302c39bde6..651c170ae4b 100644 --- a/data/deprecations/15-4-non-expiring-access-tokens.yml +++ b/data/deprecations/15-4-non-expiring-access-tokens.yml @@ -1,8 +1,6 @@ - title: "Non-expiring access tokens" announcement_milestone: "15.4" - announcement_date: "2022-09-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: hsutor body: | # Do not modify this line, instead modify the lines below. diff --git a/data/deprecations/15-4-starboard-directive.yml b/data/deprecations/15-4-starboard-directive.yml index e83f240eef4..2a8e0cfe212 100644 --- a/data/deprecations/15-4-starboard-directive.yml +++ b/data/deprecations/15-4-starboard-directive.yml @@ -1,8 +1,6 @@ - title: "Starboard directive in the config for the GitLab Agent for Kubernetes" announcement_milestone: "15.4" - announcement_date: "2022-09-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: sam.white stage: secure diff --git a/data/deprecations/15-5-confidential-field-on-notes.yml b/data/deprecations/15-5-confidential-field-on-notes.yml index ad68eecf04e..f9a9afba0ed 100644 --- a/data/deprecations/15-5-confidential-field-on-notes.yml +++ b/data/deprecations/15-5-confidential-field-on-notes.yml @@ -1,8 +1,6 @@ - title: 'GraphQL field `confidential` changed to `internal` on notes' announcement_milestone: '15.5' - announcement_date: '2022-10-22' removal_milestone: '16.0' - removal_date: '2023-05-22' breaking_change: true reporter: nicolasdular stage: plan diff --git a/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml b/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml index fe05cbfd62f..61f60ece3d4 100644 --- a/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml +++ b/data/deprecations/15-5-disable-file-type-var-expansion-ci-pipeline.yml @@ -1,8 +1,6 @@ - title: "File Type variable expansion in `.gitlab-ci.yml`" # (required) The name of the feature to be deprecated announcement_milestone: "15.5" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-10-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: "15.7" # (required) The milestone when this feature is planned to be removed - removal_date: "2022-12-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 diff --git a/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml b/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml index 56479933f94..cd9fa8796df 100644 --- a/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml +++ b/data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml @@ -1,8 +1,6 @@ - title: "vulnerabilityFindingDismiss GraphQL mutation" announcement_milestone: "15.5" - announcement_date: "2022-10-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: matt_wilson stage: govern diff --git a/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml b/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml index 5690bc0763f..b93e2513c68 100644 --- a/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml +++ b/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml @@ -1,8 +1,6 @@ - title: "Configuration fields in GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-11-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: ratchade # (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 @@ -10,4 +8,3 @@ body: | # (required) Do not modify this line, instead modify the lines below. From GitLab 13.6, users can [specify any runner configuration in the GitLab Runner Helm chart](https://docs.gitlab.com/runner/install/kubernetes.html). When we implemented this feature, we deprecated values in the GitLab Helm Chart configuration that were specific to GitLab Runner. These fields are deprecated and we plan to remove them in v1.0 of the GitLab Runner Helm chart. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. diff --git a/data/deprecations/15-6-deprecate-merge_status-api-field.yml b/data/deprecations/15-6-deprecate-merge_status-api-field.yml index 7d7b160d6bd..48b7824a13d 100644 --- a/data/deprecations/15-6-deprecate-merge_status-api-field.yml +++ b/data/deprecations/15-6-deprecate-merge_status-api-field.yml @@ -1,8 +1,6 @@ - title: "merge_status API field" announcement_milestone: "15.6" - announcement_date: "2022-11-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true body: | The `merge_status` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#merge-status) has been deprecated in favor of the `detailed_merge_status` field which more correctly identifies all of the potential statuses that a merge request can be in. API users are encouraged to use the new `detailed_merge_status` field instead. The `merge_status` field will be removed in v5 of the GitLab REST API. 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 07590296096..fd1e13321eb 100644 --- a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml +++ b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml @@ -1,8 +1,6 @@ - title: "Registration tokens and server-side runner arguments in `POST /api/v4/runners` endpoint" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-11-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: pedropombeiro # (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 @@ -19,6 +17,5 @@ [runner registration token](https://docs.gitlab.com/ee/security/token_overview.html#runner-registration-tokens). From GitLab 17.0 and later, the runner registration methods implemented by the new GitLab Runner token architecture will be the only supported methods. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. tiers: # (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/api/runners.html#register-a-new-runner # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml b/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml index f93ffb05014..9df458024d4 100644 --- a/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml +++ b/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml @@ -1,8 +1,6 @@ - title: "`runnerRegistrationToken` parameter for GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-11-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: pedropombeiro # (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 @@ -16,4 +14,3 @@ - A unique system ID saved to the `config.toml`, which will ensure traceability between jobs and runners. From GitLab 17.0 and later, the methods to register runners introduced by the new GitLab Runner token architecture will be the only supported methods. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. diff --git a/data/deprecations/15-6-deprecate-runner-register-command.yml b/data/deprecations/15-6-deprecate-runner-register-command.yml index d2633ffacc9..709edc0afa2 100644 --- a/data/deprecations/15-6-deprecate-runner-register-command.yml +++ b/data/deprecations/15-6-deprecate-runner-register-command.yml @@ -1,8 +1,6 @@ - title: "Registration tokens and server-side runner arguments in `gitlab-runner register` command" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-11-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: pedropombeiro # (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 @@ -16,4 +14,3 @@ [runner authentication token](https://docs.gitlab.com/ee/security/token_overview.html#runner-authentication-tokens-also-called-runner-tokens) to the `gitlab-runner register` command. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. 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 ec128c1aad1..4aed53f5ffd 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 @@ -1,8 +1,6 @@ - title: "GitLab Runner registration token in Runner Operator" # (required) The name of the feature to be deprecated announcement_milestone: "15.6" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-11-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: ratchade # (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 @@ -10,7 +8,6 @@ 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 k8s Vanilla Operator to install a runner on Kubernetes is deprecated. GitLab plans to introduce a new [GitLab Runner token architecture](https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/) in GitLab 15.8, which introduces a new method for registering runners and eliminates the legacy runner registration token. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. tiers: # (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/runner/install/operator.html#install-the-kubernetes-operator # (optional) This is a link to the current documentation page image_url: # (optional) This is a link to a thumbnail image depicting the feature diff --git a/data/deprecations/15-7-dast-api-variable-deprecation.yml b/data/deprecations/15-7-dast-api-variable-deprecation.yml index 724c24cf440..7f1e25d3541 100644 --- a/data/deprecations/15-7-dast-api-variable-deprecation.yml +++ b/data/deprecations/15-7-dast-api-variable-deprecation.yml @@ -1,8 +1,6 @@ - title: "DAST API variables" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: derekferguson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth 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 17336c0d2c8..3f77a9f3d8f 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 @@ -1,8 +1,6 @@ - title: "Support for REST API endpoints that reset runner registration tokens" # (required) The name of the feature to be deprecated announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: pedropombeiro # (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 @@ -22,6 +20,5 @@ [runner registration token](https://docs.gitlab.com/ee/security/token_overview.html#runner-registration-tokens). From GitLab 16.0 and later, the runner registration methods implemented by the new GitLab Runner token architecture will be the only supported methods. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. tiers: # (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/api/runners.html#register-a-new-runner # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-7-deprecate-dast-api-scan-in-dast-template.yml b/data/deprecations/15-7-deprecate-dast-api-scan-in-dast-template.yml index 172683dcb86..805deff50c7 100644 --- a/data/deprecations/15-7-deprecate-dast-api-scan-in-dast-template.yml +++ b/data/deprecations/15-7-deprecate-dast-api-scan-in-dast-template.yml @@ -1,8 +1,6 @@ - title: "DAST API scans using DAST template is deprecated" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: derekferguson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-7-deprecate-dast-zap-variables.yml b/data/deprecations/15-7-deprecate-dast-zap-variables.yml index 764d74b00bb..b57a27fa126 100644 --- a/data/deprecations/15-7-deprecate-dast-zap-variables.yml +++ b/data/deprecations/15-7-deprecate-dast-zap-variables.yml @@ -1,8 +1,6 @@ - title: "DAST ZAP advanced configuration variables deprecation" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: derekferguson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml b/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml index d535e58fc36..b1a8e2e3999 100644 --- a/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml +++ b/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml @@ -1,8 +1,6 @@ - title: "The `gitlab-runner exec` command is deprecated" # (required) The name of the feature to be deprecated announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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 @@ -10,7 +8,6 @@ body: | # (required) Do not modify this line, instead modify the lines below. The [`gitlab-runner exec`](https://docs.gitlab.com/runner/commands/#gitlab-runner-exec) command is deprecated and will be fully removed from GitLab Runner in 16.0. The `gitlab-runner exec` feature was initially developed to provide the ability to validate a GitLab CI pipeline on a local system without needing to commit the updates to a GitLab instance. However, with the continued evolution of GitLab CI, replicating all GitLab CI features into `gitlab-runner exec` was no longer viable. Pipeline syntax and validation [simulation](https://docs.gitlab.com/ee/ci/pipeline_editor/#simulate-a-cicd-pipeline) are available in the GitLab pipeline editor. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. # OTHER OPTIONAL FIELDS diff --git a/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml b/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml index 2b747a2fead..ce26849879a 100644 --- a/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml +++ b/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml @@ -1,8 +1,6 @@ - title: "KAS Metrics Port in GitLab Helm Chart" # (required) The name of the feature to be deprecated announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: timofurrer # (required) GitLab username of the person reporting the deprecation stage: Configure # (required) String value of the stage that the feature was created in. e.g., Growth @@ -11,7 +9,6 @@ The `gitlab.kas.metrics.port` has been deprecated in favor of the new `gitlab.kas.observability.port` configuration field for the [GitLab Helm Chart](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/2839). This port is used for much more than just metrics, which warranted this change to avoid confusion in configuration. end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. # OTHER OPTIONAL FIELDS diff --git a/data/deprecations/15-7-deprecate-phabricator-importer.yml b/data/deprecations/15-7-deprecate-phabricator-importer.yml index 42958a05b1d..fa2c643e9b7 100644 --- a/data/deprecations/15-7-deprecate-phabricator-importer.yml +++ b/data/deprecations/15-7-deprecate-phabricator-importer.yml @@ -1,8 +1,6 @@ - title: 'The Phabricator task importer is deprecated' announcement_milestone: '15.7' - announcement_date: '2022-12-22' removal_milestone: '16.0' - removal_date: '2023-05-22' breaking_change: true body: | The [Phabricator task importer](https://docs.gitlab.com/ee/user/project/import/phabricator.html) is being deprecated. Phabricator itself as a project is no longer actively maintained since June 1, 2021. We haven't observed imports using this tool. There has been no activity on the open related issues on GitLab. diff --git a/data/deprecations/15-7-deprecate-shimo-integration.yml b/data/deprecations/15-7-deprecate-shimo-integration.yml index 11ccbae41de..95bb4ec141d 100644 --- a/data/deprecations/15-7-deprecate-shimo-integration.yml +++ b/data/deprecations/15-7-deprecate-shimo-integration.yml @@ -1,8 +1,6 @@ - title: "Shimo integration" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "The maximum number of characters in a job name will be limited to 250." announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: arturoherrero # (required) GitLab username of the person reporting the deprecation stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth @@ -17,7 +15,6 @@ # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. # end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. # # OTHER OPTIONAL FIELDS # diff --git a/data/deprecations/15-7-deprecate-single-merge-request-changes-api-endpoint.yml b/data/deprecations/15-7-deprecate-single-merge-request-changes-api-endpoint.yml index 4dcefc617c0..9e567322eca 100644 --- a/data/deprecations/15-7-deprecate-single-merge-request-changes-api-endpoint.yml +++ b/data/deprecations/15-7-deprecate-single-merge-request-changes-api-endpoint.yml @@ -1,8 +1,6 @@ - title: 'Single merge request changes API endpoint' announcement_milestone: '15.7' - announcement_date: '2022-12-22' removal_milestone: '16.0' - removal_date: '2023-05-22' breaking_change: true body: | The endpoint to get [changes from a single merge request](https://docs.gitlab.com/ee/api/merge_requests.html#get-single-merge-request-changes) has been deprecated in favor the [list merge request diffs](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-request-diffs) endpoint. API users are encouraged to switch to the new diffs endpoint instead. The `changes from a single merge request` endpoint will be removed in v5 of the GitLab REST API. diff --git a/data/deprecations/15-7-deprecate-zentao-integration.yml b/data/deprecations/15-7-deprecate-zentao-integration.yml index 5fc7e9da5fc..0925be8de60 100644 --- a/data/deprecations/15-7-deprecate-zentao-integration.yml +++ b/data/deprecations/15-7-deprecate-zentao-integration.yml @@ -1,8 +1,6 @@ - title: "ZenTao integration" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "The maximum number of characters in a job name will be limited to 250." announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: arturoherrero # (required) GitLab username of the person reporting the deprecation stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth @@ -17,7 +15,6 @@ # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. # end_of_support_milestone: "16.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: "2023-05-22" # (optional) The date of the milestone release when support for this feature will end. # # OTHER OPTIONAL FIELDS # diff --git a/data/deprecations/15-7-enable-period-in-terraform-state-name.yml b/data/deprecations/15-7-enable-period-in-terraform-state-name.yml index e9db80ea34c..f56505ed2bc 100644 --- a/data/deprecations/15-7-enable-period-in-terraform-state-name.yml +++ b/data/deprecations/15-7-enable-period-in-terraform-state-name.yml @@ -1,8 +1,6 @@ - title: "Support for periods (`.`) in Terraform state names might break existing states" announcement_milestone: "15.7" - announcement_date: "2022-12-22" removal_milestone: "16.0" - removal_date: "2023-05-22" breaking_change: true reporter: nagyv-gitlab stage: configure @@ -20,6 +18,5 @@ To use the full state name, including the period, [migrate to the full state file](https://docs.gitlab.com/ee/user/infrastructure/iac/terraform_state.html#migrate-to-a-gitlab-managed-terraform-state). end_of_support_milestone: 16.0 - end_of_support_date: 2023-05-22 tiers: [Free, Silver, Gold, Core, Premium, Ultimate] documentation_url: 'https://docs.gitlab.com/ee/user/infrastructure/iac/troubleshooting.html#troubleshooting-terraform-state' diff --git a/data/deprecations/15-8-azure-storage-driver-root-prefix.yml b/data/deprecations/15-8-azure-storage-driver-root-prefix.yml new file mode 100644 index 00000000000..16f848c0193 --- /dev/null +++ b/data/deprecations/15-8-azure-storage-driver-root-prefix.yml @@ -0,0 +1,13 @@ +- title: "Azure Storage Driver defaults to the correct root prefix" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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/container-registry/-/issues/854 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The Azure Storage Driver writes to `//` as the default root directory. This default root directory appears in some places within the Azure UI as `/<no-name>/`. We have maintained this legacy behavior to support older deployments using this storage driver. However, when moving to Azure from another storage driver, this behavior hides all your data until you configure the storage driver to build root paths without an extra leading slash by setting `trimlegacyrootprefix: true`. + + The new default configuration for the storage driver will set `trimlegacyrootprefix: true`, and `/` will be the default root directory. You can add `trimlegacyrootprefix: false` to your current configuration to avoid any disruptions. + + This breaking change will happen in GitLab 16.0. diff --git a/data/deprecations/15-8-conan-search-limited-to-project.yml b/data/deprecations/15-8-conan-search-limited-to-project.yml new file mode 100644 index 00000000000..872652be69e --- /dev/null +++ b/data/deprecations/15-8-conan-search-limited-to-project.yml @@ -0,0 +1,11 @@ +- title: "Conan project-level search endpoint returns project-specific results" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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/384455 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + You can use the GitLab Conan repository with [project-level](https://docs.gitlab.com/ee/user/packages/conan_repository/#add-a-remote-for-your-project) or [instance-level](https://docs.gitlab.com/ee/user/packages/conan_repository/#add-a-remote-for-your-instance) endpoints. Each level supports the conan search command. However, the search endpoint for the project level is also returning packages from outside the target project. + + This unintended functionality is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. The search endpoint for the project level will only return packages from the target project. diff --git a/data/deprecations/15-8-dast-report-variables-deprecation.yml b/data/deprecations/15-8-dast-report-variables-deprecation.yml index 21416e0d009..28a2c366c44 100644 --- a/data/deprecations/15-8-dast-report-variables-deprecation.yml +++ b/data/deprecations/15-8-dast-report-variables-deprecation.yml @@ -1,8 +1,6 @@ - title: "DAST report variables deprecation" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: derekferguson # (required) GitLab username of the person reporting the deprecation stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth diff --git a/data/deprecations/15-8-default-private-user-profile.yml b/data/deprecations/15-8-default-private-user-profile.yml new file mode 100644 index 00000000000..d07163e1ca9 --- /dev/null +++ b/data/deprecations/15-8-default-private-user-profile.yml @@ -0,0 +1,9 @@ +- title: "Null value for `private_profile` attribute in User API 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: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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: lohrc # (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/387005 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + When creating and updating users through the API, `null` was a valid value for the `private_profile` attribute, which would internally be converted to the default value. Starting with 16.0, `null` will no longer be a valid value for this parameter, and the response will be a 400 if used. Now the only valid values are `true` and `false`. diff --git a/data/deprecations/15-8-dependency-scanning-java-versions.yml b/data/deprecations/15-8-dependency-scanning-java-versions.yml new file mode 100644 index 00000000000..ad8f87a7fbe --- /dev/null +++ b/data/deprecations/15-8-dependency-scanning-java-versions.yml @@ -0,0 +1,9 @@ +- title: "Dependency Scanning support for Java 13, 14, 15, and 16" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: sam.white + stage: secure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387560 + body: | + GitLab has deprecated Dependency Scanning support for Java versions 13, 14, 15, and 16 and plans to remove that support in the upcoming GitLab 16.0 release. This is consistent with [Oracle's support policy](https://www.oracle.com/java/technologies/java-se-support-roadmap.html) as Oracle Premier and Extended Support for these versions has ended. This also allows GitLab to focus Dependency Scanning Java support on LTS versions moving forward. diff --git a/data/deprecations/15-8-deprecate-auto-deploy-postgres-enabled.yml b/data/deprecations/15-8-deprecate-auto-deploy-postgres-enabled.yml new file mode 100644 index 00000000000..048ae337924 --- /dev/null +++ b/data/deprecations/15-8-deprecate-auto-deploy-postgres-enabled.yml @@ -0,0 +1,16 @@ +- title: "Auto DevOps no longer provisions a PostgreSQL database by default" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: tigerwnz + stage: Configure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/343988 + body: | + Currently, Auto DevOps provisions an in-cluster PostgreSQL database by default. + In GitLab 16.0, databases will be provisioned only for users who opt in. This + change supports production deployments that require more robust database management. + + If you want Auto DevOps to provision an in-cluster database, + set the `POSTGRES_ENABLED` CI/CD variable to `true`. + tiers: [Core, Premium, Ultimate] + documentation_url: https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-deploy diff --git a/data/deprecations/15-8-deprecate-deploy-PAT-with-external-auth.yml b/data/deprecations/15-8-deprecate-deploy-PAT-with-external-auth.yml new file mode 100644 index 00000000000..f1b93f725b0 --- /dev/null +++ b/data/deprecations/15-8-deprecate-deploy-PAT-with-external-auth.yml @@ -0,0 +1,9 @@ +- title: "Limit personal access token and deploy token's access with external authorization" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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: adil.farrukh # (required) GitLab username of the person reporting the deprecation + 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/387721 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + With external authorization enabled, personal access tokens (PATs) and deploy tokens must no longer be able to access container or package registries. This defense-in-depth security measure will be deployed in 16.0. For users that use PATs and deploy tokens to access these registries, this measure breaks this use of these tokens. Disable external authorization to use tokens with container or package registries. diff --git a/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml b/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml new file mode 100644 index 00000000000..db93f0cadcc --- /dev/null +++ b/data/deprecations/15-8-deprecate-disabled-with-override-runner-setting-value.yml @@ -0,0 +1,18 @@ +# +# REQUIRED FIELDS +# +- title: "GraphQL: The `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` enum is deprecated. Use `DISABLED_AND_OVERRIDABLE` instead" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-01-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: "16.0" # (required) The milestone when this feature is planned to be removed + removal_date: "2023-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: tschmitke # (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/385636 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + In GitLab 16.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` GraphQL enum type will be replaced with the value, `DISABLED_AND_OVERRIDABLE`. + # + # OTHER OPTIONAL FIELDS + # + documentation_url: "https://docs.gitlab.com/ee/api/graphql/reference/#sharedrunnerssetting" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-8-deprecate-gitlabcom-importer.yml b/data/deprecations/15-8-deprecate-gitlabcom-importer.yml new file mode 100644 index 00000000000..bb5d44a83a9 --- /dev/null +++ b/data/deprecations/15-8-deprecate-gitlabcom-importer.yml @@ -0,0 +1,18 @@ +- title: 'GitLab.com importer' + announcement_milestone: '15.8' + announcement_date: '2023-01-22' + removal_milestone: '16.0' + removal_date: '2023-05-22' + breaking_change: false + body: | + The [GitLab.com importer](https://docs.gitlab.com/ee/user/project/import/gitlab_com.html) is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. + + The GitLab.com importer was introduced in 2015 for importing a project from GitLab.com to a self-managed GitLab instance through the UI. + This feature is available on self-managed instances only. [Migrating GitLab groups and projects by direct transfer](https://docs.gitlab.com/ee/user/group/import/#migrate-groups-by-direct-transfer-recommended) + supersedes the GitLab.com importer and provides a more cohesive importing functionality. + + See [migrated group items](https://docs.gitlab.com/ee/user/group/import/#migrated-group-items) and [migrated project items](https://docs.gitlab.com/ee/user/group/import/#migrated-project-items) for an overview. + stage: manage + tiers: + issue_url: https://gitlab.com/gitlab-com/Product/-/issues/4895 + documentation_url: https://docs.gitlab.com/ee/user/project/import/gitlab_com.html diff --git a/data/deprecations/15-8-deprecate-herokuish.yml b/data/deprecations/15-8-deprecate-herokuish.yml new file mode 100644 index 00000000000..78155095764 --- /dev/null +++ b/data/deprecations/15-8-deprecate-herokuish.yml @@ -0,0 +1,12 @@ +- title: "Auto DevOps support for Herokuish is deprecated" + announcement_milestone: "15.8" + removal_milestone: "17.0" + breaking_change: true + reporter: nagyv-gitlab + stage: configure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/211643 + body: | + Auto DevOps support for Herokuish is deprecated in favor of [Cloud Native Buildpacks](https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-build-using-cloud-native-buildpacks). You should [migrate your builds from Herokuish to Cloud Native Buildpacks](https://docs.gitlab.com/ee/topics/autodevops/stages.html#moving-from-herokuish-to-cloud-native-buildpacks). From GitLab 14.0, Auto Build uses Cloud Native Buildpacks by default. + + Because Cloud Native Buildpacks do not support automatic testing, the Auto Test feature of Auto DevOps is also deprecated. + documentation_url: https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-build-using-cloud-native-buildpacks diff --git a/data/deprecations/15-8-deprecate-import-bare-repositories-rake-task.yml b/data/deprecations/15-8-deprecate-import-bare-repositories-rake-task.yml new file mode 100644 index 00000000000..5619a52ef34 --- /dev/null +++ b/data/deprecations/15-8-deprecate-import-bare-repositories-rake-task.yml @@ -0,0 +1,28 @@ +- title: 'Rake task for importing bare repositories' + announcement_milestone: '15.8' + announcement_date: '2023-01-22' + removal_milestone: '16.0' + removal_date: '2023-05-22' + breaking_change: false + body: | + The [Rake task for importing bare repositories](https://docs.gitlab.com/ee/raketasks/import.html) `gitlab:import:repos` is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. + + This Rake task imports a directory tree of repositories into a GitLab instance. These repositories must have been + managed by GitLab previously, because the Rake task relies on the specific directory structure or a specific custom Git setting in order to work (`gitlab.fullpath`). + + Importing repositories using this Rake task has limitations. The Rake task: + + - Only knows about project and project wiki repositories and doesn't support repositories for designs, group wikis, or snippets. + - Permits you to import non-hashed storage projects even though these aren't supported. + - Relies on having Git config `gitlab.fullpath` set. [Epic 8953](https://gitlab.com/groups/gitlab-org/-/epics/8953) proposes removing support for this setting. + + Alternatives to using the `gitlab:import:repos` Rake task include: + + - Migrating projects using either [an export file](https://docs.gitlab.com/ee/user/project/settings/import_export.html) or + [direct transfer](https://docs.gitlab.com/ee/user/group/import/#migrate-groups-by-direct-transfer-recommended) migrate repositories as well. + - Importing a [repository by URL](https://docs.gitlab.com/ee/user/project/import/repo_by_url.html). + - Importing a [repositories from a non-GitLab source](https://docs.gitlab.com/ee/user/project/import/). + stage: manage + tiers: + issue_url: https://gitlab.com/gitlab-com/Product/-/issues/5255 + documentation_url: https://docs.gitlab.com/ee/raketasks/import.html diff --git a/data/deprecations/15-8-deprecate-merge-request-approvals-fields.yml b/data/deprecations/15-8-deprecate-merge-request-approvals-fields.yml new file mode 100644 index 00000000000..3e0e10b54db --- /dev/null +++ b/data/deprecations/15-8-deprecate-merge-request-approvals-fields.yml @@ -0,0 +1,14 @@ +- title: 'Approvers and Approver Group fields in Merge Request Approval API' + announcement_milestone: '15.8' + announcement_date: '2023-01-22' + removal_milestone: '16.0' + removal_date: '2023-05-22' + breaking_change: true + body: | + The endpoint to get the configuration of approvals for a project returns empty arrays for `approvers` and `approval_groups`. These fields were deprecated in favor of the endpoint to [get project-level rules](https://docs.gitlab.com/ee/api/merge_request_approvals.html#get-project-level-rules) for a merge request. API users are encouraged to switch to this endpoint instead. These fields will be removed from the `get configuration` endpoint in v5 of the GitLab REST API. + stage: create + tiers: + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/353097 + documentation_url: https://docs.gitlab.com/ee/api/merge_request_approvals.html#get-project-level-rules + image_url: + video_url: diff --git a/data/deprecations/15-8-deprecate-opensuse-15-3.yml b/data/deprecations/15-8-deprecate-opensuse-15-3.yml new file mode 100644 index 00000000000..54eca3fe014 --- /dev/null +++ b/data/deprecations/15-8-deprecate-opensuse-15-3.yml @@ -0,0 +1,14 @@ +- title: "openSUSE Leap 15.3 packages" # (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: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "15.11" # (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: twk3 # (required) GitLab username of the person reporting the change + stage: distribution # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7371 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Distribution support and security updates for openSUSE Leap 15.3 [ended December 2022](https://en.opensuse.org/Lifetime#Discontinued_distributions). + + Starting in GitLab 15.7 we started providing packages for openSUSE Leap 15.4, and will stop providing packages for openSUSE Leap 15.3 in the 15.11 milestone. + + - Switch from the openSUSE Leap 15.3 packages to the provided 15.4 packages. + documentation_url: https://docs.gitlab.com/ee/administration/package_information/supported_os.html diff --git a/data/deprecations/15-8-deprecate-updated-at-error.yml b/data/deprecations/15-8-deprecate-updated-at-error.yml new file mode 100644 index 00000000000..9b4c5c3e007 --- /dev/null +++ b/data/deprecations/15-8-deprecate-updated-at-error.yml @@ -0,0 +1,45 @@ +# This is a template for announcing a feature deprecation or other important planned change. +# +# Please refer to the deprecation guidelines to confirm your understanding of GitLab's definitions. +# https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology +# +# Deprecations and other future breaking changes must be announced at least +# three releases prior to removal. +# +# Breaking changes must happen in a major release. +# +# See the OPTIONAL END OF SUPPORT FIELDS section below if an End of Support period also applies. +# +# For more information please refer to the handbook documentation here: +# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-and-other-planned-breaking-change-announcements +# +# Please delete this line and above before submitting your merge request. +# +# REQUIRED FIELDS +# +- title: "Deployment API returns error when `updated_at` and `updated_at` are not used together" # (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: "15.8" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-01-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: "16.0" # (required) The milestone when this feature is planned to be removed + removal_date: 2023-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) Change to false if this is not a breaking change. + reporter: cbalane # (required) GitLab username of the person reporting the change + stage: Release # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/328500 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The Deployment API will now return an error when `updated_at` filtering and `updated_at` sorting are not used together. Some users were using filtering by `updated_at` to fetch "latest" deployment without using `updated_at` sorting, which may produce wrong results. You should instead use them together, or migrate to filtering by `finished_at` and sorting by `finished_at` which will give you "latest deployments" in a consistent way. +# +# 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. + end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. + # + # OTHER OPTIONAL FIELDS + # + tiers: # (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 + 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/15-8-live-preview.yml b/data/deprecations/15-8-live-preview.yml new file mode 100644 index 00000000000..05ec5111e4a --- /dev/null +++ b/data/deprecations/15-8-live-preview.yml @@ -0,0 +1,11 @@ +- title: "Live Preview no longer available in the Web IDE" # (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: "15.8" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-01-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: "15.9" # (required) The milestone when this feature is planned to be removed + removal_date: "2023-02-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) Change to false if this is not a breaking change. + reporter: ericschurter # (required) GitLab username of the person reporting the change + stage: create # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/383889 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The Live Preview feature of the Web IDE was intended to provide a client-side preview of static web applications. However, complex configuration steps and a narrow set of supported project types have limited its utility. With the introduction of the Web IDE Beta in GitLab 15.7, you can now connect to a full server-side runtime environment. With upcoming support for installing extensions in the Web IDE, we'll also support more advanced workflows than those available with Live Preview. As of GitLab 15.9, Live Preview is no longer available in the Web IDE. diff --git a/data/deprecations/15-8-projects-api-ops-access-level.yml b/data/deprecations/15-8-projects-api-ops-access-level.yml new file mode 100644 index 00000000000..4e0fbbe63ab --- /dev/null +++ b/data/deprecations/15-8-projects-api-ops-access-level.yml @@ -0,0 +1,45 @@ +# This is a template for announcing a feature deprecation or other important planned change. +# +# Please refer to the deprecation guidelines to confirm your understanding of GitLab's definitions. +# https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology +# +# Deprecations and other future breaking changes must be announced at least +# three releases prior to removal. +# +# Breaking changes must happen in a major release. +# +# See the OPTIONAL END OF SUPPORT FIELDS section below if an End of Support period also applies. +# +# For more information please refer to the handbook documentation here: +# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-and-other-planned-breaking-change-announcements +# +# Please delete this line and above before submitting your merge request. +# +# REQUIRED FIELDS +# +- title: "Projects API field `operations_access_level` 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: "15.8" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-01-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: "16.0" # (required) The milestone when this feature is planned to be removed + removal_date: 2023-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) Change to false if this is not a breaking change. + reporter: cbalane # (required) GitLab username of the person reporting the change + stage: Release # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/385798 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + We are deprecating the `operations_access_level` field in the Projects API. This field has been replaced by fields to control specific features: `releases_access_level`, `environments_access_level`, `feature_flags_access_level`, `infrastructure_access_level`, and `monitor_access_level`. +# +# 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. + end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. + # + # OTHER OPTIONAL FIELDS + # + tiers: # (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 + 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/15-8-pull-through-cache-container-registry.yml b/data/deprecations/15-8-pull-through-cache-container-registry.yml new file mode 100644 index 00000000000..60a759517e0 --- /dev/null +++ b/data/deprecations/15-8-pull-through-cache-container-registry.yml @@ -0,0 +1,9 @@ +- title: "Container Registry pull-through cache" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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/container-registry/-/issues/842 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The Container Registry pull-through cache is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. While the Container Registry pull-through cache functionality is useful, we have not made significant changes to this feature. You can use the upstream version of the container registry to achieve the same functionality. Removing the pull-through cache allows us also to remove the upstream client code without sacrificing functionality. diff --git a/data/deprecations/15-8-raise-permissions-settings-package-stage.yml b/data/deprecations/15-8-raise-permissions-settings-package-stage.yml new file mode 100644 index 00000000000..72b53ee8c9b --- /dev/null +++ b/data/deprecations/15-8-raise-permissions-settings-package-stage.yml @@ -0,0 +1,17 @@ +- title: "Maintainer role providing the ability to change Package settings using GraphQL API" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: trizzi + stage: Package + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/370471 + body: | + The ability for users with the Maintainer role to change the **Packages and registries** settings for a group using + the GraphQL API is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. These settings include: + + - [Allowing or preventing duplicate package uploads](https://docs.gitlab.com/ee/user/packages/maven_repository/#do-not-allow-duplicate-maven-packages). + - [Package request forwarding](https://docs.gitlab.com/ee/user/packages/maven_repository/#request-forwarding-to-maven-central). + - [Enabling lifecycle rules for the Dependency Proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/reduce_dependency_proxy_storage.html). + + In GitLab 16.0 and later, you must have Owner role for a group to change the **Packages and registries** + settings for the group using either the GitLab UI or GraphQL API. diff --git a/data/deprecations/15-8-redis-config-env.yml b/data/deprecations/15-8-redis-config-env.yml new file mode 100644 index 00000000000..473b97518c2 --- /dev/null +++ b/data/deprecations/15-8-redis-config-env.yml @@ -0,0 +1,13 @@ +- title: "Configuring Redis config file paths using environment variables is deprecated" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: jacobvosmaer-gitlab + stage: platforms + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/388255 + body: | + You can no longer specify Redis configuration file locations + using the environment variables like `GITLAB_REDIS_CACHE_CONFIG_FILE` or + `GITLAB_REDIS_QUEUES_CONFIG_FILE`. Use the default + config file locations instead, for example `config/redis.cache.yml` or + `config/redis.queues.yml`. diff --git a/data/deprecations/15-8-redis-localhost.yml b/data/deprecations/15-8-redis-localhost.yml new file mode 100644 index 00000000000..b18fcdc4318 --- /dev/null +++ b/data/deprecations/15-8-redis-localhost.yml @@ -0,0 +1,16 @@ +- title: "Non-standard default Redis ports are deprecated" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: jacobvosmaer-gitlab + stage: platforms # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/388269 + body: | + If GitLab starts without any Redis configuration file present, + GitLab assumes it can connect to three Redis servers at `localhost:6380`, + `localhost:6381` and `localhost:6382`. We are changing this behavior + so GitLab assumes there is one Redis server at `localhost:6379`. + + Administrators who want to keep the three servers must configure + the Redis URLs by editing the `config/redis.cache.yml`,`config/redis.queues.yml` + and `config/redis.shared_state.yml` files. diff --git a/data/deprecations/15-8-remove-deprecated-environment-tier-param-from-dora-api.yml b/data/deprecations/15-8-remove-deprecated-environment-tier-param-from-dora-api.yml new file mode 100644 index 00000000000..f46b2159bf4 --- /dev/null +++ b/data/deprecations/15-8-remove-deprecated-environment-tier-param-from-dora-api.yml @@ -0,0 +1,9 @@ +- title: "`environment_tier` parameter for DORA API" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "The maximum number of characters in a job name will be limited to 250." + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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: hsnir1 # (required) GitLab username of the person reporting the deprecation + stage: plan # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/365939 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + To avoid confusion and duplication, the `environment_tier` parameter is deprecated in favor of the `environment_tiers` parameter. The new `environment_tiers` parameter allows DORA APIs to return aggregated data for multiple tiers at the same time. The `environment_tier` parameter will be removed in GitLab 16.0. diff --git a/data/deprecations/15-8-restrict-gitlab-projects-imports-to-maintainers-and-above.yml b/data/deprecations/15-8-restrict-gitlab-projects-imports-to-maintainers-and-above.yml new file mode 100644 index 00000000000..4d27974cd0b --- /dev/null +++ b/data/deprecations/15-8-restrict-gitlab-projects-imports-to-maintainers-and-above.yml @@ -0,0 +1,13 @@ +- title: 'Developer role providing the ability to import projects to a group' + announcement_milestone: '15.8' + announcement_date: '2023-01-22' + removal_milestone: '16.0' + removal_date: '2023-05-22' + breaking_change: true + body: | + The ability for users with the Developer role for a group to import projects to that group is deprecated in GitLab + 15.8 and will be removed in GitLab 16.0. From GitLab 16.0, only users with at least the Maintainer role for a group + will be able to import projects to that group. + stage: manage + tiers: + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387891 diff --git a/data/deprecations/15-8-revoked-agent-tokens-api-change.yml b/data/deprecations/15-8-revoked-agent-tokens-api-change.yml new file mode 100644 index 00000000000..f5122974844 --- /dev/null +++ b/data/deprecations/15-8-revoked-agent-tokens-api-change.yml @@ -0,0 +1,20 @@ +- title: "The API no longer returns revoked tokens for the agent for Kubernetes" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: nagyv-gitlab + stage: configure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/382129 + body: | + Currently, GET requests to the [Cluster Agents API](https://docs.gitlab.com/ee/api/cluster_agents.html#list-tokens-for-an-agent) + endpoints can return revoked tokens. In GitLab 16.0, GET requests will not return revoked tokens. + + You should review your calls to these endpoints and ensure you do not use revoked tokens. + + This change affects the following REST and GraphQL API endpoints: + + - REST API: + - [List tokens](https://docs.gitlab.com/ee/api/cluster_agents.html#list-tokens-for-an-agent) + - [Get a single token](https://docs.gitlab.com/ee/api/cluster_agents.html#get-a-single-agent-token) + - GraphQL: + - [`ClusterAgent.tokens`](https://docs.gitlab.com/ee/api/graphql/reference/#clusteragenttokens) diff --git a/data/deprecations/15-8-terraform-latest-stable-change.yml b/data/deprecations/15-8-terraform-latest-stable-change.yml new file mode 100644 index 00000000000..60e9a509252 --- /dev/null +++ b/data/deprecations/15-8-terraform-latest-stable-change.yml @@ -0,0 +1,18 @@ +- title: "The latest Terraform templates will overwrite current stable templates" + announcement_milestone: "15.8" + removal_milestone: "16.0" + breaking_change: true + reporter: nagyv-gitlab + stage: configure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/386001 + body: | # (required) Do not modify this line, instead modify the lines below. + With every major GitLab version, we update the stable Terraform templates with the current latest templates. + This change affects the [quickstart](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml) + and the [base](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform/Base.gitlab-ci.yml) templates. + + Because the new templates ship with default rules, the update might break your Terraform pipelines. + For example, if your Terraform jobs are triggered as a downstream pipeline, the rules won't trigger your jobs + in GitLab 16.0. + + To accommodate the changes, you might need to adjust the [`rules`](https://docs.gitlab.com/ee/ci/yaml/#rules) in your + `.gitlab-ci.yml` file. diff --git a/data/deprecations/15-8-third-party-registries.yml b/data/deprecations/15-8-third-party-registries.yml new file mode 100644 index 00000000000..6da3e550bb3 --- /dev/null +++ b/data/deprecations/15-8-third-party-registries.yml @@ -0,0 +1,13 @@ +- title: "Support for third party registries" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.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/376216 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Support for third-party container registries is deprecated in GitLab 15.8 and will be [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/376217) in GitLab 16.0. Supporting both GitLab's Container Registry and third-party container registries is challenging for maintenance, code quality, and backward compatibility. This hinders our ability to stay [efficient](https://about.gitlab.com/handbook/values/#efficiency). + + Since we released the new [GitLab Container Registry](https://gitlab.com/groups/gitlab-org/-/epics/5523) version for GitLab.com, we've started to implement additional features that are not available in third-party container registries. These new features have allowed us to achieve significant performance improvements, such as [cleanup policies](https://gitlab.com/groups/gitlab-org/-/epics/8379). We are focusing on delivering [new features](https://gitlab.com/groups/gitlab-org/-/epics/5136), most of which will require functionalities only available on the GitLab Container Registry. This deprecation allows us to reduce fragmentation and user frustration in the long term by focusing on delivering a more robust integrated registry experience and feature set. + + Moving forward, we'll continue to invest in developing and releasing new features that will only be available in the GitLab Container Registry. diff --git a/data/deprecations/15-8-visual-review-tool.yml b/data/deprecations/15-8-visual-review-tool.yml new file mode 100644 index 00000000000..4833bc314d8 --- /dev/null +++ b/data/deprecations/15-8-visual-review-tool.yml @@ -0,0 +1,23 @@ +- title: "The Visual Reviews tool 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: "15.8" # (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: jocelynjane # (required) GitLab username of the person reporting the change + 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/387751 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Due to limited customer usage and capabilities, the Visual Reviews feature for Review Apps is deprecated and will be removed. There is no planned replacement and users should stop using Visual Reviews before GitLab 17.0. +# +# 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 # (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/review_apps/#visual-reviews # (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/15.8-kas-private-tls.yml b/data/deprecations/15.8-kas-private-tls.yml new file mode 100644 index 00000000000..3d1a6e7830f --- /dev/null +++ b/data/deprecations/15.8-kas-private-tls.yml @@ -0,0 +1,16 @@ +- title: "GitLab Helm chart values `gitlab.kas.privateApi.*` are deprecated" + announcement_milestone: "15.8" + removal_milestone: "17.0" + breaking_change: true + reporter: nagyv-gitlab + stage: configure + issue_url: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/4097 + body: | # (required) Do not modify this line, instead modify the lines below. + We introduced the `global.kas.tls.*` Helm values to facilitate TLS communication between KAS and your Helm chart components. + The old values `gitlab.kas.privateApi.tls.enabled` and `gitlab.kas.privateApi.tls.secretName` are deprecated and scheduled for removal in GitLab 17.0. + + Because the new values provide a streamlined, comprehensive method to enable TLS for KAS, you should use `global.kas.tls.*` instead of `gitlab.kas.privateApi.tls.*`. The `gitlab.kas.privateApi.tls.*` For more information, see: + + - The [merge request](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/2888) that introduces the `global.kas.tls.*` values. + - The [deprecated `gitlab.kas.privateApi.tls.*` documentation](https://docs.gitlab.com/charts/charts/gitlab/kas/index.html#enable-tls-communication-through-the-gitlabkasprivateapi-attributes-deprecated). + - The [new `global.kas.tls.*` documentation](https://docs.gitlab.com/charts/charts/globals.html#tls-settings-1). diff --git a/data/deprecations/16-0-post-ci-lint.yml b/data/deprecations/16-0-post-ci-lint.yml index 3bea4201bc0..42c9d29a3d5 100644 --- a/data/deprecations/16-0-post-ci-lint.yml +++ b/data/deprecations/16-0-post-ci-lint.yml @@ -18,9 +18,7 @@ # - title: "`POST ci/lint` API endpoint deprecated" # (required) The name of the feature to be deprecated announcement_milestone: "15.7" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "2022-12-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: "16.0" # (required) The milestone when this feature is planned to be removed - removal_date: "2023-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: dhershkovitch # (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 @@ -34,7 +32,6 @@ # 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. - end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. # # OTHER OPTIONAL FIELDS # diff --git a/data/deprecations/16-0-security_report_schemas_v14-x-x.yml b/data/deprecations/16-0-security_report_schemas_v14-x-x.yml index 5001bd490b0..0cc6a10ca76 100644 --- a/data/deprecations/16-0-security_report_schemas_v14-x-x.yml +++ b/data/deprecations/16-0-security_report_schemas_v14-x-x.yml @@ -3,9 +3,7 @@ # - title: "Security report schemas version 14.x.x" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. announcement_milestone: "15.3" # (required) The milestone when this feature was deprecated. - announcement_date: "2022-08-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "16.0" # (required) The milestone when this feature is being removed. - removal_date: "2023-05-22" # (required) This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed. breaking_change: true # (required) Change to true if this removal is a breaking change. reporter: matt_wilson # (required) GitLab username of the person reporting the removal stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth @@ -22,7 +20,6 @@ # OPTIONAL FIELDS # end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. 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 image_url: # (optional) This is a link to a thumbnail image depicting the feature diff --git a/data/deprecations/distribution_deprecations_14-4.yml b/data/deprecations/distribution_deprecations_14-4.yml index 8dc948918c1..d8b8de929d7 100644 --- a/data/deprecations/distribution_deprecations_14-4.yml +++ b/data/deprecations/distribution_deprecations_14-4.yml @@ -1,7 +1,5 @@ - title: "Move `custom_hooks_dir` setting from GitLab Shell to Gitaly" # The name of the feature to be deprecated announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. - announcement_date: "2022-03-22" removal_milestone: "15.0" # the milestone when this feature is planned to be removed - removal_date: "2022-05-22" body: | # Do not modify this line, instead modify the lines below. The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks.html#create-a-global-server-hook-for-all-repositories) setting is now configured in Gitaly, and will be removed from GitLab Shell in GitLab 15.0. diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index 7712790d166..89e14c20050 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -56,9 +56,9 @@ sole discretion of GitLab Inc. ### <%= deprecation["title"] %> <% if deprecation["end_of_support_milestone"] -%> -End of Support: GitLab <span class="removal-milestone"><%= deprecation["end_of_support_milestone"]%></span> (<%= deprecation["end_of_support_date"]%>)<br /> +End of Support: GitLab <span class="removal-milestone"><%= deprecation["end_of_support_milestone"]%></span> <span class="support-end-date"></span><br /> <% end -%> -Planned removal: GitLab <span class="removal-milestone"><%= deprecation["removal_milestone"]%></span> (<%= deprecation["removal_date"]%>) +Planned removal: GitLab <span class="removal-milestone"><%= deprecation["removal_milestone"]%></span> <span class="removal-date"></span> <% if deprecation["breaking_change"] -%> WARNING: diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml index 619810f1e7e..dcb78fa434b 100644 --- a/data/deprecations/templates/example.yml +++ b/data/deprecations/templates/example.yml @@ -1,28 +1,27 @@ -# This is a template for a feature deprecation. +# This is a template for announcing a feature deprecation or other important planned change. # -# Please refer to the deprecation guidelines to confirm your understanding of the -# definitions for "Deprecation", "End of Support", and "Removal": +# Please refer to the deprecation guidelines to confirm your understanding of GitLab's definitions. # https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology # -# Deprecations must be announced at least three releases prior to removal. -# See the OPTIONAL END OF SUPPORT FIELDS section below if an End of Support period also applies. +# Deprecations and other future breaking changes must be announced at least +# three releases prior to removal. # # Breaking changes must happen in a major release. # +# See the OPTIONAL END OF SUPPORT FIELDS section below if an End of Support period also applies. +# # For more information please refer to the handbook documentation here: -# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations +# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-and-other-planned-breaking-change-announcements # # Please delete this line and above before submitting your merge request. # # REQUIRED FIELDS # -- title: "Feature A is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "The maximum number of characters in a job name will be limited to 250." +- title: "Feature A 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: "XX.YY" # (required) The milestone when this feature was first announced as deprecated. - announcement_date: "YYYY-MM-DD" # (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: "XX.YY" # (required) The milestone when this feature is planned to be removed - removal_date: # (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: false # (required) If this deprecation is a breaking change, set this value to true - reporter: exampleuser # (required) GitLab username of the person reporting the deprecation + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: exampleuser # (required) GitLab username of the person reporting the change stage: stage # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/000000 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. @@ -33,7 +32,7 @@ Additionally, deprecations and other planned changes should be actionable, so add details that explain what users need to do to address the change. For example: - "Use the `internal` keyword instead of `confidential`." - - "Reduce the number of characters in all jobs to be 250 characters or less." + - "Reduce the number of characters in all job names to be 250 characters or less." - "Give an expiration date to any access tokens that have no expiration date." - "Stop using the `omniauth_crowd` gem. It will be removed and will not be replaced." @@ -49,7 +48,6 @@ # 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. - end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. # # OTHER OPTIONAL FIELDS # diff --git a/data/removals/templates/example.yml b/data/removals/templates/example.yml index e7c0268c182..3645c407e25 100644 --- a/data/removals/templates/example.yml +++ b/data/removals/templates/example.yml @@ -1,43 +1,42 @@ -# This is a template for a feature removal. +# This is a template for announcing a feature removal or other important change. # # Please refer to the deprecation guidelines to confirm your understanding of GitLab's definitions. # https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology # -# If this removal is a breaking change, it must take place in a major release. +# If this is a breaking change, it must happen in a major release. # # For more information please refer to the handbook documentation here: -# https://about.gitlab.com/handbook/marketing/blog/release-posts/#removals +# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-and-other-planned-breaking-change-announcements # # Please delete this line and above before submitting your merge request. # # REQUIRED FIELDS # -- title: "X is removed. Do Y instead." # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. +- title: "Feature A is removed." # (required) Clearly explain the change. For example, "The `confidential` field for a `Note` is removed" or "CI/CD job names are limited to 250 characters." announcement_milestone: "XX.YY" # (required) The milestone when this feature was deprecated. announcement_date: "YYYY-MM-DD" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. removal_milestone: "XX.YY" # (required) The milestone when this feature is being removed. removal_date: "YYYY-MM-DD" # (required) This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed. - breaking_change: false # (required) Change to true if this removal is a breaking change. + breaking_change: true # (required) Change to false if this is not a breaking change. reporter: exampleuser # (required) GitLab username of the person reporting the removal stage: stage # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/000000 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. <!-- START OF BODY COMMENT - This area supports markdown. Delete this entire comment and replace it with your markdown content. + Be clear and concise. Give a brief explanation of the details or reasons for the change. - Removals must be actionable. + Additionally, removals and other planned changes should be actionable, so add details that explain what users need to do to address the change. For example: - Use terms such as "removed in favor of" or "use X instead." If no replacement is available, the action would be, "Discontinue use of foo immediately." - - For example: - - - The `confidential` field for a `Note` is removed. Use `internal` instead. - - The `merge_status` field in the merge request API has been removed in favor of `detailed_merge_status`. - - The `notable` endpoint has been removed. Discontinue use of `notable` immediately. + - "Use the `internal` keyword instead of `confidential`." + - "Reduce the number of characters in all job names to be 250 characters or less." + - "Give an expiration date to any access tokens that have no expiration date." + - "Stop using the `omniauth_crowd` gem. It has been removed and will not be replaced." When ready, assign to your tech writer for review. When ready, they will run `bin/rake gitlab:docs:compile_removals` to update the removals doc, then merge. + This area supports markdown. Delete this entire comment and replace it with your markdown content. + END OF BODY COMMENT --> # # OPTIONAL FIELDS diff --git a/data/whats_new/202212200001_15_07.yml b/data/whats_new/202212200001_15_07.yml index ac192218d3e..937a4f76375 100644 --- a/data/whats_new/202212200001_15_07.yml +++ b/data/whats_new/202212200001_15_07.yml @@ -4,7 +4,7 @@ To support more developers where they're already working, we've adopted the open source project `glab`, which will form the foundation of GitLab's native CLI experience. The GitLab CLI brings GitLab together with Git and your code, with no application or tab switching required. - You can read about our adoption of `glab`, our partnership with 1Password, and how to contribute to the project in our [blog post](/blog/2022/12/07/introducing-the-gitlab-cli/). + You can read about our adoption of `glab`, our partnership with 1Password, and how to contribute to the project in our [blog post](https://about.gitlab.com/blog/2022/12/07/introducing-the-gitlab-cli/). A special thank you to [Clement Sam](https://gitlab.com/profclems) for creating `glab` and trusting us with its future. stage: create @@ -53,7 +53,7 @@ Self-managed instances have access to the Web IDE Beta where it is behind a [feature flag](https://docs.gitlab.com/ee/user/project/web_ide_beta/) disabled by default in GitLab 15.7. - Learn more about the Web IDE Beta and what's coming next in our [recent blog post](/blog/2022/12/15/get-ready-for-new-gitlab-web-ide/). + Learn more about the Web IDE Beta and what's coming next in our [recent blog post](https://about.gitlab.com/blog/2022/12/15/get-ready-for-new-gitlab-web-ide/). stage: configure self-managed: true gitlab-com: true @@ -136,7 +136,7 @@ self-managed: true gitlab-com: true available_in: [Free, Premium, Ultimate] - documentation_link: https://docs.gitlab.com/ee/ci/variables/#expand-cicd-variables + documentation_link: https://docs.gitlab.com/ee/ci/variables/#prevent-cicd-variable-expansion image_url: https://about.gitlab.com/images/15_7/raw.png published_at: 2022-12-22 release: 15.7 |