diff options
Diffstat (limited to 'data/deprecations')
38 files changed, 189 insertions, 123 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 28e58a0c60d..5a0fc88dad9 100644 --- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml +++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml @@ -16,7 +16,7 @@ We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/index.html#migrate-to-gitaly-cluster). reporter: mjwood - stage: create # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + stage: create 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] issue_url: # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-10-dependency-scanning-default-java-version.yml b/data/deprecations/14-10-dependency-scanning-default-java-version.yml new file mode 100644 index 00000000000..c589f2bb3ac --- /dev/null +++ b/data/deprecations/14-10-dependency-scanning-default-java-version.yml @@ -0,0 +1,16 @@ +- name: "Dependency Scanning default Java version changed to 17" + announcement_milestone: "14.10" + announcement_date: "2022-04-22" + removal_milestone: "15.0" + removal_date: "2021-05-22" + breaking_change: true + reporter: NicoleSchwartz + body: | + In GitLab 15.0, for Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_Java_Version` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning). +# The following items are not published on the docs page, but may be used in the future. + stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + 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] + issue_url: # (optional) This is a link to the deprecation issue in GitLab + documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning + 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/14-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml index 587dc98d03c..033fa957320 100644 --- a/data/deprecations/14-3-repository-push-audit-events.yml +++ b/data/deprecations/14-3-repository-push-audit-events.yml @@ -5,7 +5,7 @@ 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#repository-push-deprecated) are now deprecated and will be removed in GitLab 15.0. + 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. These events have always been disabled by default and had to be manually enabled with a feature flag. Enabling them can cause too many events to be generated which can @@ -13,4 +13,4 @@ stage: Manage tiers: Premium issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/337993 - documentation_url: https://docs.gitlab.com/ee/administration/audit_events.html#repository-push-deprecated + documentation_url: https://docs.gitlab.com/ee/administration/audit_events.html#removed-events 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 new file mode 100644 index 00000000000..774b41a4170 --- /dev/null +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes-saas.yml @@ -0,0 +1,19 @@ +- name: "SaaS certificate-based integration with Kubernetes" + announcement_milestone: "14.5" + announcement_date: "2021-11-15" + removal_milestone: "15.6" + removal_date: "2022-11-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. The integrations are expected to be switched off completely on GitLab SaaS around 2022 November 22. + + For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the + [agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html) + + For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). + + GitLab self-managed customers can still use the feature [with a feature flag](https://docs.gitlab.com/ee/update/deprecations.html#self-managed-certificate-based-integration-with-kubernetes). + stage: Configure + tiers: [Free, Premium, Ultimate] + issue_url: 'https://gitlab.com/groups/gitlab-org/configure/-/epics/8' + documentation_url: 'https://docs.gitlab.com/ee/user/infrastructure/clusters/#certificate-based-kubernetes-integration-deprecated' 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 5cf9354cd05..6ab678c4199 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml @@ -1,27 +1,21 @@ -- name: "Certificate-based integration with Kubernetes" +- name: "Self-managed certificate-based integration with Kubernetes" announcement_milestone: "14.5" announcement_date: "2021-11-15" - removal_milestone: "15.6" - removal_date: "2022-11-22" # the date of the milestone release when this feature is planned to be removed + removal_milestone: "16.0" + removal_date: "2023-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/). + 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/). - If you are a self-managed customer, in GitLab 15.0, a feature flag will be introduced so you can keep - certificate-based integration enabled. The flag will be disabled by default. - The flag and the related code will be removed in GitLab 15.6. + As a self-managed customer, we are introducing a feature flag in GitLab 15.0 so you can keep your certificate-based integration enabled. However, the feature flag will be disabled by default, so this change is a **breaking change**. - Until the final removal in 15.6, features built on the integration will continue to work, and - GitLab will continue to fix security and critical issues. - - If you use GitLab.com, certificate-based integrations will cease functioning in 15.0. + In GitLab 16.0 we will remove both the feature and its related code. Until the final removal in 16.0, features built on this integration will continue to work, if you enable the feature flag. Until the feature is removed, GitLab will continue to fix security and critical issues as they arise. For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the - [agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. - See the documentation for [how to migrate](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html). + [agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. [How do I migrate?](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html) For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). stage: Configure - tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + tiers: [Core, Premium, Ultimate] issue_url: 'https://gitlab.com/groups/gitlab-org/configure/-/epics/8' documentation_url: 'https://docs.gitlab.com/ee/user/infrastructure/clusters/#certificate-based-kubernetes-integration-deprecated' 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 9b45454fef8..f6b47162a36 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,11 +1,15 @@ -- name: "Converting an instance (shared) runner to a project (specific) runner" +- name: "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, we will remove the feature that enables you to convert an instance (shared) runner to a project (specific) runner. Users who need to add a runner to only a particular project can register a runner to the project directly. + In GitLab 15.0, you can no longer change an instance (shared) runner to a project (specific) runner. + + Users often accidentally change instance runners to project runners, and they're unable to change them back. GitLab does not allow you to change a project runner to a shared runner because of the security implications. A runner meant for one project could be set to run jobs for an entire instance. + + Administrators who need to add runners for multiple projects can register a runner for one project, then go to the Admin view and choose additional projects. stage: Verify tiers: [Core, Premium, Ultimate] diff --git a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml index 2dfc20ae14e..85cb235f445 100644 --- a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml +++ b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml @@ -7,7 +7,8 @@ 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. # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + stage: create + reporter: phikai 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] issue_url: # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-5-deprecate-sles-12sp2.yml b/data/deprecations/14-5-deprecate-sles-12sp2.yml index 69f8eb73bfd..adfbea4ce42 100644 --- a/data/deprecations/14-5-deprecate-sles-12sp2.yml +++ b/data/deprecations/14-5-deprecate-sles-12sp2.yml @@ -6,3 +6,5 @@ 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. + stage: enablement + reporter: dorrino diff --git a/data/deprecations/14-5-remove-package-pipelines-api.yml b/data/deprecations/14-5-remove-package-pipelines-api.yml index 392636f90a0..91b2971297f 100644 --- a/data/deprecations/14-5-remove-package-pipelines-api.yml +++ b/data/deprecations/14-5-remove-package-pipelines-api.yml @@ -1,13 +1,13 @@ - name: "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: "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 + 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. - In milestone 15.0, we will remove the `pipelines` attribute from the API response. + In milestone 16.0, we will remove the `pipelines` attribute from the API response. stage: package tiers: Free issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/289956 diff --git a/data/deprecations/14-6-deprecate-types.yml b/data/deprecations/14-6-deprecate-types.yml index 3db9f574d38..7f6c1a4cfa5 100644 --- a/data/deprecations/14-6-deprecate-types.yml +++ b/data/deprecations/14-6-deprecate-types.yml @@ -7,7 +7,8 @@ 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. # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + stage: verify + reporter: dhershkovitch 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] issue_url: # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-6-job_char_limit.yml b/data/deprecations/14-6-job_char_limit.yml index ee3efafe9f6..b7dff12da5f 100644 --- a/data/deprecations/14-6-job_char_limit.yml +++ b/data/deprecations/14-6-job_char_limit.yml @@ -7,7 +7,8 @@ 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. # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + reporter: dhershkovitch + stage: verify 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] issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/342800 # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml deleted file mode 100644 index 14892d2bbae..00000000000 --- a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml +++ /dev/null @@ -1,13 +0,0 @@ -- name: "`pipelines` fields in the Package GraphQL types" - 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. - 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 `pipelines` fields in all Package-related GraphQL types. As of GitLab 14.6, the `pipelines` field is deprecated in [`Package`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#package) and [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype) due to scalability and performance concerns. - - In milestone 15.0, we will completely remove `pipelines` from `Package` and `PackageDetailsType`. You can follow and contribute to work on a replacement in the epic [GitLab-#7214](https://gitlab.com/groups/gitlab-org/-/epics/7214). - stage: package - tiers: Free - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347219 diff --git a/data/deprecations/14-6-runner-api-status-renames-not_connected.yml b/data/deprecations/14-6-runner-api-status-renames-not_connected.yml deleted file mode 100644 index a2aba7cadbe..00000000000 --- a/data/deprecations/14-6-runner-api-status-renames-not_connected.yml +++ /dev/null @@ -1,15 +0,0 @@ -- name: "Runner status `not_connected` API value" - announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. - 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. - The GitLab Runner REST and GraphQL [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints - will return `never_contacted` instead of `not_connected` as the status values in 15.0. - - Runners that have never contacted the GitLab instance will also return `stale` if created more than 3 months ago. - stage: Verify - tiers: [Core, Premium, Ultimate] - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347305 - documentation_url: https://docs.gitlab.com/ee/api/runners.html - announcement_date: "2021-12-22" diff --git a/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml b/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml deleted file mode 100644 index 0f21318d329..00000000000 --- a/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml +++ /dev/null @@ -1,14 +0,0 @@ -- name: "API: `stale` status returned instead of `offline` or `not_connected`" - announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated. - announcement_date: "2021-12-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. - A breaking change will occur for the Runner [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints in 15.0. - - Instead of the GitLab Runner API endpoints returning `offline` and `not_connected` for runners that have not contacted the GitLab instance in the past three months, the API endpoints will return the `stale` value, which was introduced in 14.6. - stage: Verify - tiers: [Core, Premium, Ultimate] - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347303 - documentation_url: https://docs.gitlab.com/ee/api/runners.html#runners-api diff --git a/data/deprecations/14-7-deprecate-static-site-editor.yml b/data/deprecations/14-7-deprecate-static-site-editor.yml index 18f2ec26645..0960bffe4cf 100644 --- a/data/deprecations/14-7-deprecate-static-site-editor.yml +++ b/data/deprecations/14-7-deprecate-static-site-editor.yml @@ -4,7 +4,9 @@ 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. Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/static_site_editor/) for more information, including how to remove the configuration files from existing projects. + 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). + + Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/static_site_editor/) for more information, including how to remove the configuration files from existing projects. # The following items are not published on the docs page, but may be used in the future. stage: Create # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth tiers: [Free, Premium, Ultimate] # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] 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 0638f86968a..36104ad15d8 100644 --- a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml +++ b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml @@ -11,7 +11,7 @@ The method for calculating fingerprints has changed, resulting in different values. Going forward, the new values will be exposed in the UUID field. Data previously available in the projectFingerprint field will eventually be removed entirely. # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + stage: secure 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] issue_url: # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-enforce-pat-expiration.yml b/data/deprecations/14-8-enforce-pat-expiration.yml index bb5155984ef..bc8e35a4e2c 100644 --- a/data/deprecations/14-8-enforce-pat-expiration.yml +++ b/data/deprecations/14-8-enforce-pat-expiration.yml @@ -9,5 +9,6 @@ The feature to disable enforcement of PAT expiration is unusual from a security perspective. We have become concerned that this unusual feature could create unexpected behavior for users. Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature. + stage: manage issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351962" # (optional) This is a link to the deprecation issue in GitLab documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-personal-access-tokens-to-be-used-deprecated" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-enforce-ssh-expiration.yml b/data/deprecations/14-8-enforce-ssh-expiration.yml index 2f8362001df..5887e749d2c 100644 --- a/data/deprecations/14-8-enforce-ssh-expiration.yml +++ b/data/deprecations/14-8-enforce-ssh-expiration.yml @@ -9,5 +9,6 @@ The feature to disable enforcement of SSH expiration is unusual from a security perspective. We have become concerned that this unusual feature could create unexpected behavior for users. Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature. + stage: manage issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351963" # (optional) This is a link to the deprecation issue in GitLab documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-ssh-keys-to-be-used-deprecated" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-graphql-ids.yml b/data/deprecations/14-8-graphql-ids.yml index 67ff418c51a..cd830a313b1 100644 --- a/data/deprecations/14-8-graphql-ids.yml +++ b/data/deprecations/14-8-graphql-ids.yml @@ -58,7 +58,7 @@ to one of the other two forms (using the correct appropriate type in the signature, or using an inline argument expression). # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + stage: ecosystem 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] issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/257883' documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-grpc-proxy.yml b/data/deprecations/14-8-grpc-proxy.yml index 1ec505fd216..9d161dbc8f9 100644 --- a/data/deprecations/14-8-grpc-proxy.yml +++ b/data/deprecations/14-8-grpc-proxy.yml @@ -18,7 +18,7 @@ increase throughput and reduce Go garbage collection latency. For more information, see the [relevant epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463). # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth + stage: platform 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] issue_url: # (optional) This is a link to the deprecation issue in GitLab documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-protect-cns-chs.yml b/data/deprecations/14-8-protect-cns-chs.yml index 8ea76d1b371..6fb67e98b2c 100644 --- a/data/deprecations/14-8-protect-cns-chs.yml +++ b/data/deprecations/14-8-protect-cns-chs.yml @@ -6,7 +6,7 @@ breaking_change: true reporter: sam.white body: | # Do not modify this line, instead modify the lines below. - All functionality related to GitLab's Container Network Security and Container Host Security categories is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies into GitLab, add the desired Helm charts into your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through the GitLab [Secure CI/CD Tunnel](https://docs.gitlab.com/ee/user/clusters/agent/repository.html#run-kubectl-commands-using-the-cicd-tunnel). + All functionality related to GitLab's Container Network Security and Container Host Security categories is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies into GitLab, add the desired Helm charts into your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through GitLab [CI/CD](https://docs.gitlab.com/ee/user/clusters/agent/ci_cd_workflow.html). As part of this change, the following specific capabilities within GitLab are now deprecated, and are scheduled for removal in GitLab 15.0: 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 0300641e540..99af852c13e 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 @@ -27,7 +27,7 @@ existing runners. stage: Verify tiers: [Core, Premium, Ultimate] - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347211 - documentation_url: https://docs.gitlab.com/ee/api/runners.html + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351109 + documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#cirunner 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/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 8f706840f0d..174e51f5f5d 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 @@ -15,4 +15,4 @@ stage: Verify tiers: [Core, Premium, Ultimate] issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351109 - documentation_url: https://docs.gitlab.com/ee/api/runners.html + documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#queryrunners diff --git a/data/deprecations/14-8-sast-analyzer-removals.yml b/data/deprecations/14-8-sast-analyzer-removals.yml index 6bbeee0cd6b..cf9549f7315 100644 --- a/data/deprecations/14-8-sast-analyzer-removals.yml +++ b/data/deprecations/14-8-sast-analyzer-removals.yml @@ -1,8 +1,8 @@ - name: "SAST analyzer consolidation and CI/CD template changes" announcement_milestone: "14.8" announcement_date: "2022-02-22" - removal_milestone: "15.0" - removal_date: "2022-05-22" + removal_milestone: "15.2" + removal_date: "2022-07-22" breaking_change: true reporter: connorgilbert body: | # Do not modify this line, instead modify the lines below. @@ -11,12 +11,15 @@ We are reducing the number of analyzers used in GitLab SAST as part of our long-term strategy to deliver a better and more consistent user experience. Streamlining the set of analyzers will also enable faster [iteration](https://about.gitlab.com/handbook/values/#iteration), better [results](https://about.gitlab.com/handbook/values/#results), and greater [efficiency](https://about.gitlab.com/handbook/values/#results) (including a reduction in CI runner usage in most cases). - In GitLab 15.0, GitLab SAST will no longer use the following analyzers: + In GitLab 15.2, GitLab SAST will no longer use the following analyzers: - [ESLint](https://gitlab.com/gitlab-org/security-products/analyzers/eslint) (JavaScript, TypeScript, React) - [Gosec](https://gitlab.com/gitlab-org/security-products/analyzers/gosec) (Go) - [Bandit](https://gitlab.com/gitlab-org/security-products/analyzers/bandit) (Python) + NOTE: + This change was originally planned for GitLab 15.0 and has been postponed. + These analyzers will be removed from the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml) and replaced with the [Semgrep-based analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/semgrep). They will no longer receive routine updates, except for security issues. We will not delete container images previously published for these analyzers; any such change would be announced as a [deprecation, removal, or breaking change announcement](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes). @@ -25,7 +28,7 @@ This change will make it simpler to scan Java code; compilation will no longer be required. This change will be reflected in the automatic language detection portion of the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml). - If you applied customizations to any of the affected analyzers, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352554#breaking-change). + If you applied customizations to any of the affected analyzers or if you currently disable the Semgrep analyzer in your pipelines, you must take action as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352554#breaking-change). # The following items are not published on the docs page, but may be used in the future. stage: Secure tiers: [Free, Silver, Gold, Core, Premium, Ultimate] diff --git a/data/deprecations/14-9-deprecate-composer-download-permissions.yml b/data/deprecations/14-9-deprecate-composer-download-permissions.yml index 79cb2a81c53..e44f1c55167 100644 --- a/data/deprecations/14-9-deprecate-composer-download-permissions.yml +++ b/data/deprecations/14-9-deprecate-composer-download-permissions.yml @@ -1,11 +1,12 @@ - name: "Permissions change for downloading Composer dependencies" announcement_milestone: "14.9" announcement_date: "2022-03-22" - removal_milestone: "15.0" - removal_date: "2022-05-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. The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies. Downloading Composer dependencies without authentication is deprecated in GitLab 14.9, and will be removed in GitLab 15.0. Starting with GitLab 15.0, you must authenticate to download Composer dependencies. + stage: package 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 740b3ca2e0d..366f0e83470 100644 --- a/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml +++ b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml @@ -14,3 +14,4 @@ - [Container Registry cleanup policy](https://docs.gitlab.com/ee/api/graphql/reference/#containerexpirationpolicy) - [Dependency Proxy time-to-live policy](https://docs.gitlab.com/ee/api/graphql/reference/#dependencyproxyimagettlgrouppolicy) - [Enabling the Dependency Proxy for your group](https://docs.gitlab.com/ee/api/graphql/reference/#dependencyproxysetting) + stage: package diff --git a/data/deprecations/14-9-deprecate-testcoveragesetting.yml b/data/deprecations/14-9-deprecate-testcoveragesetting.yml index 9015172eeb9..e6dfb22562b 100644 --- a/data/deprecations/14-9-deprecate-testcoveragesetting.yml +++ b/data/deprecations/14-9-deprecate-testcoveragesetting.yml @@ -7,8 +7,9 @@ reporter: jreporter # GitLab username of the person reporting the deprecation body: | # Do not modify this line, instead modify the lines below. To simplify setting a test coverage pattern, in GitLab 15.0 the - [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-using-project-settings-deprecated) + [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-using-project-settings-removed) is being removed. Instead, using the project’s `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set testing coverage results in merge requests. + stage: verify diff --git a/data/deprecations/templates/14-9-deprecation-htpassword-authentication-container-registry.yml b/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml index 14c6b235a1a..5d940b5e14d 100644 --- a/data/deprecations/templates/14-9-deprecation-htpassword-authentication-container-registry.yml +++ b/data/deprecations/14-9-deprecation-htpassword-authentication-container-registry.yml @@ -9,3 +9,4 @@ The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`. Since it isn't used in the context of GitLab (the product), `htpasswd` authentication will be deprecated in GitLab 14.9 and removed in GitLab 15.0. + stage: package diff --git a/data/deprecations/15-0-JTW_v2_update.yml b/data/deprecations/15-0-JTW_v2_update.yml deleted file mode 100644 index 39880d7fbe0..00000000000 --- a/data/deprecations/15-0-JTW_v2_update.yml +++ /dev/null @@ -1,28 +0,0 @@ -# This is a template for a feature deprecation -# A deprecation typically occurs when a feature or capability is planned to be removed in a future release. -# Deprecations should be announced at least two releases prior to removal. Any breaking changes should only be done in major releases. -# -# Below is an example of what a single entry should look like, it's required attributes, -# and what types we expect those attribute values to be. -# -# For more information please refer to the handbook documentation here: -# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations -# -# Please delete this line and above before submitting your merge request. - -- name: "Changes to the `CI_JOB_JWT`" # 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: dhershkovitch # GitLab username of the person reporting the deprecation - body: | # Do not modify this line, instead modify the lines below. - The `CI_JOB_JWT` will be updated to support a wider variety of cloud providers. It will be changed to match [`CI_JOB_JWT_V2`](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html), but this change may not be backwards compatible for all users, including Hashicorp Vault users. To maintain the current behavior, users can switch to using `CI_JOB_JWT_V1`, or update their configuration in GitLab 15.0 to use the improved `CI_JOB_JWT`. -# The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth - 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] - issue_url: # (optional) This is a link to the deprecation issue in GitLab - 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-0-ci-cd-settings-update-mutation-renamed.yml b/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml new file mode 100644 index 00000000000..7f426190963 --- /dev/null +++ b/data/deprecations/15-0-ci-cd-settings-update-mutation-renamed.yml @@ -0,0 +1,19 @@ +- name: "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 + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/361801 + body: | + The `CiCdSettingsUpdate` mutation was renamed to `ProjectCiCdSettingsUpdate` in GitLab 15.0. + The `CiCdSettingsUpdate` mutation will be removed in GitLab 16.0. + Any user scripts that use the `CiCdSettingsUpdate` mutation must be updated to use `ProjectCiCdSettingsUpdate` + instead. + + tiers: [Core, Premium, Ultimate] + documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#mutationprojectcicdsettingsupdate + image_url: + video_url: diff --git a/data/deprecations/15-0-deprecate-postgresql-12.yml b/data/deprecations/15-0-deprecate-postgresql-12.yml new file mode 100644 index 00000000000..bebfba64405 --- /dev/null +++ b/data/deprecations/15-0-deprecate-postgresql-12.yml @@ -0,0 +1,19 @@ +- name: "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. + Support for PostgreSQL 12 is scheduled for removal in GitLab 16.0. + In GitLab 16.0, PostgreSQL 13 becomes the minimum required PostgreSQL version. + + PostgreSQL 12 will be supported for the full GitLab 15 release cycle. + PostgreSQL 13 will also be supported for instances that want to upgrade prior to GitLab 16.0. + + Upgrading to PostgreSQL 13 is not yet supported for GitLab instances with Geo enabled. Geo support for PostgreSQL 13 will be announced in a minor release version of GitLab 15, after the process is fully supported and validated. For more information, read the Geo related verifications on the [support epic for PostgreSQL 13](https://gitlab.com/groups/gitlab-org/-/epics/3832). + stage: Enablement + tiers: [Free, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/349185 + documentation_url: https://docs.gitlab.com/omnibus/development/managing-postgresql-versions.html diff --git a/data/deprecations/15-0-oauth-noexpiry.yml b/data/deprecations/15-0-oauth-noexpiry.yml index 154630c9f16..9f2521998aa 100644 --- a/data/deprecations/15-0-oauth-noexpiry.yml +++ b/data/deprecations/15-0-oauth-noexpiry.yml @@ -16,7 +16,8 @@ 1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don’t expire. # The following items are not published on the docs page, but may be used in the future. - stage: # Manage + reporter: hsutor + stage: manage 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] issue_url: # https://gitlab.com/gitlab-org/gitlab/-/issues/21745 documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-0-oauth.yml b/data/deprecations/15-0-oauth.yml index 98c7c974808..7e1c3ff51cd 100644 --- a/data/deprecations/15-0-oauth.yml +++ b/data/deprecations/15-0-oauth.yml @@ -7,7 +7,8 @@ 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). # The following items are not published on the docs page, but may be used in the future. - stage: # Manage + reporter: hsutor + stage: manage 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] issue_url: # https://gitlab.com/gitlab-org/gitlab/-/issues/344609 documentation_url: # (optional) This is a link to the current documentation page diff --git a/data/deprecations/15-0-runner-status-legacy-mode.yml b/data/deprecations/15-0-runner-status-legacy-mode.yml new file mode 100644 index 00000000000..ee7ac1af820 --- /dev/null +++ b/data/deprecations/15-0-runner-status-legacy-mode.yml @@ -0,0 +1,18 @@ +- name: "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. + The `legacyMode` argument to the `status` field in `RunnerType` will be rendered non-functional in the 16.0 release + as part of the deprecations details in the [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351109). + + In GitLab 16.0 and later, the `status` field will act as if `legacyMode` is null. The `legacyMode` argument will + be present during the 16.x cycle to avoid breaking the API signature, and will be removed altogether in the + 17.0 release. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/360545 + documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#cirunnerstatus diff --git a/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml new file mode 100644 index 00000000000..271e11f0d7f --- /dev/null +++ b/data/deprecations/15-2-deprecation-vulnerability-report-state-sort.yml @@ -0,0 +1,19 @@ +- name: "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.2" # (required) The milestone when this feature is planned to be removed + removal_date: "2022-07-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 + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/360516 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The ability to sort the Vulnerability Report by the `State` column was disabled and put behind a feature flag in GitLab 14.10 due to a refactor + of the underlying data model. The feature flag has remained off by default as further refactoring will be required to ensure sorting + by this value remains performant. Due to very low usage of the `State` column for sorting, the feature flag will instead be removed in + GitLab 15.2 to simplify the codebase and prevent any unwanted performance degradation. +# The following items are not published on the docs page, but may be used in the future. + tiers: Ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: # (optional) This is a link to the current documentation page + 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/distribution_deprecations_14-4.yml b/data/deprecations/distribution_deprecations_14-4.yml index b8c4e0d817c..5b7163d5b4d 100644 --- a/data/deprecations/distribution_deprecations_14-4.yml +++ b/data/deprecations/distribution_deprecations_14-4.yml @@ -2,5 +2,6 @@ announcement_milestone: "14.9" # The milestone when this feature was first announced as deprecated. announcement_date: "2021-10-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 09a53404798..46eb152d86a 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -36,15 +36,22 @@ For deprecation reviewers (Technical Writers only): https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc --> +{::options parse_block_html="true" /} + View deprecations by the product versions in which they were announced. Each deprecation has a **planned removal milestone** and indicates whether it is a breaking change. Most of the deprecations are **planned for removal in 15.0**, and many of them are **breaking changes**. +<div class="js-deprecation-filters"></div> <% if milestones.any? -%> <%- milestones.each do |milestone| %> +<div class="announcement-milestone"> + ## <%= milestone %> <%- entries.select{|d| d["announcement_milestone"] == milestone}.each do |deprecation| %> +<div class="deprecation removal-<%= deprecation["removal_milestone"].gsub('.', '') %><% if deprecation["breaking_change"] -%> breaking-change<% end %>"> + ### <%= deprecation["name"]%> <% if deprecation["breaking_change"] -%> @@ -57,9 +64,11 @@ changes to your code, settings, or workflow. <%= deprecation["body"] -%><% else %> <%= deprecation["body"] -%><% end %><%- if deprecation["removal_milestone"] -%> -**Planned removal milestone: <%= deprecation["removal_milestone"]%> (<%= deprecation["removal_date"]%>)** +**Planned removal milestone: <span class="removal-milestone"><%= deprecation["removal_milestone"]%></span> (<%= deprecation["removal_date"]%>)** +</div> <%- end -%> <%- end -%> +</div> <%- end -%> <%- else -%> diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml index 06e53084ed2..190235b0e3c 100644 --- a/data/deprecations/templates/example.yml +++ b/data/deprecations/templates/example.yml @@ -10,14 +10,16 @@ # # Please delete this line and above before submitting your merge request. -- name: "Feature name" # The name of the feature to be deprecated - announcement_milestone: "XX.YY" # The milestone when this feature was first announced as deprecated. - announcement_date: "YYYY-MM-DD" # 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" # The milestone when this feature is planned to be removed - removal_date: # 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: exampleuser # GitLab username of the person reporting the deprecation - body: | # Do not modify this line, instead modify the lines below. +- name: "Feature name" # (required) The name of the feature to be deprecated + 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 + 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. @@ -26,9 +28,7 @@ END OF BODY COMMENT --> # The following items are not published on the docs page, but may be used in the future. - stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth 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] - issue_url: # (optional) This is a link to the deprecation issue in GitLab 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 |