diff options
Diffstat (limited to 'data')
31 files changed, 155 insertions, 15 deletions
diff --git a/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml b/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml index 01ca5839281..c4c5f6258b4 100644 --- a/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml +++ b/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml @@ -1,11 +1,12 @@ -- name: "`AuthenticationType` for `[runners.cache.s3]` must be explicitly assigned" +- name: "Must explicitly assign `AuthenticationType` for `[runners.cache.s3]`" 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 body: | # Do not modify this line, instead modify the lines below. In GitLab 15.0 and later, to access the AWS S3 cache, you must specify the `AuthenticationType` for [`[runners.cache.s3]`](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscaches3-section). The `AuthenticationType` must be `IAM` or `credentials`. - Prior to 14.5, if you did not define the `AuthenticationType`, GitLab Runner chose a type for you. + Prior to 14.5, if you did not define the `AuthenticationType`, GitLab Runner chose a type for you. stage: Verify tiers: [Core, Premium, Ultimate] issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28171 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 6884f6e3f69..a1261154e8c 100644 --- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml +++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml @@ -2,6 +2,7 @@ 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.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. 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 in GitLab 15.0. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information. @@ -19,4 +20,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 - the date of the milestone release when this feature is planned to be removed diff --git a/data/deprecations/14-2-deprecation-task-runner.yml b/data/deprecations/14-2-deprecation-task-runner.yml index 52fd1f0f288..9f4d81ddd3a 100644 --- a/data/deprecations/14-2-deprecation-task-runner.yml +++ b/data/deprecations/14-2-deprecation-task-runner.yml @@ -2,6 +2,7 @@ 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 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). @@ -13,4 +14,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: "2021-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 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 f3f6553729e..e460abcb077 100644 --- a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml +++ b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml @@ -2,6 +2,7 @@ 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 body: | The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html) configuration located in `database.yml` is changing and the legacy format is deprecated. The legacy format diff --git a/data/deprecations/14-3-deprecation-release-cli.yml b/data/deprecations/14-3-deprecation-release-cli.yml index 4273d00fc73..d04e97df380 100644 --- a/data/deprecations/14-3-deprecation-release-cli.yml +++ b/data/deprecations/14-3-deprecation-release-cli.yml @@ -2,6 +2,7 @@ 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 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. stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth @@ -10,4 +11,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: "2021-12-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 diff --git a/data/deprecations/14-3-package-container-registry-api-group-update.yml b/data/deprecations/14-3-package-container-registry-api-group-update.yml index 3021e283846..de5d184888a 100644 --- a/data/deprecations/14-3-package-container-registry-api-group-update.yml +++ b/data/deprecations/14-3-package-container-registry-api-group-update.yml @@ -1,6 +1,7 @@ - name: "Update to the Container Registry group-level API" announcement_milestone: "14.5" # 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" # 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. 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-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml index 4bca8751db4..defa4576cde 100644 --- a/data/deprecations/14-3-repository-push-audit-events.yml +++ b/data/deprecations/14-3-repository-push-audit-events.yml @@ -1,6 +1,7 @@ - name: "Audit events for repository push events" announcement_milestone: "14.3" # 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" # 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. Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#repository-push) are now deprecated and will be removed in GitLab 15.0. 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 86e7718b9e1..e93fa25facb 100644 --- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml +++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml @@ -2,6 +2,7 @@ announcement_milestone: "14.5" announcement_date: "2021-11-15" removal_milestone: "15.0" + removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed body: | [We are deprecating the certificate-based integration with Kubernetes](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/). The timeline of removal of the integration from the product is not yet planned and we will communicate @@ -16,4 +17,3 @@ tiers: [Free, Silver, Gold, 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' - removal_date: # (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-5-deprecate-convert-instance-runner-to-project.yml b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml index c5f9e244af0..29b8fe0e70c 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 @@ -2,6 +2,7 @@ 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 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. diff --git a/data/deprecations/14-5-deprecate-opensuse-15-2.yml b/data/deprecations/14-5-deprecate-opensuse-15-2.yml index b887f92e6a3..7b776293dbb 100644 --- a/data/deprecations/14-5-deprecate-opensuse-15-2.yml +++ b/data/deprecations/14-5-deprecate-opensuse-15-2.yml @@ -2,6 +2,7 @@ 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 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-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml index 2961fab7487..5706e826a9d 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 @@ -2,8 +2,9 @@ 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 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. + 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. If you monitor Value Stream Analytics metrics and rely on the date filter, to avoid losing data, you must save the data prior to this change. stage: manage # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth 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 8c7cde8a121..5cf7b107354 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,15 +1,15 @@ - name: "REST API Runner will not contain `paused`" announcement_milestone: "14.5" # 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" # 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. - Runner REST API will not return `paused` as a status in GitLab 15.0. + The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 15.0. - Paused runners' status will only relate to runner contact status, such as: - `online`, `offline`, or `not_connected`. Status `paused` will not appear when the runner is - not active. + A runner's status will only relate to runner contact status, such as: + `online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear. When checking if a runner is `paused`, API users are advised to check the boolean attribute - `active` to be `false` instead. + `active` to be `false` instead. When checking if a runner is `active`, check if `active` is `true`. stage: Verify tiers: [Core, Premium, Ultimate] issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648 diff --git a/data/deprecations/14-6-deprecate-types.yml b/data/deprecations/14-6-deprecate-types.yml new file mode 100644 index 00000000000..5cbc07efa89 --- /dev/null +++ b/data/deprecations/14-6-deprecate-types.yml @@ -0,0 +1,14 @@ +- name: "Remove `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 + 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 + 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/14-6-deprecation-license-compliance-api-terms.yml b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml new file mode 100644 index 00000000000..d75b668f111 --- /dev/null +++ b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml @@ -0,0 +1,16 @@ +- name: "Deprecate 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 + body: | # Do not modify this line, instead modify the lines below. + We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0. + + If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release. +# 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: https://gitlab.com/gitlab-org/gitlab/-/issues/335707 # (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 + 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 new file mode 100644 index 00000000000..23e59da21e4 --- /dev/null +++ b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml @@ -0,0 +1,16 @@ +- name: "Deprecation of 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 + body: | # Do not modify this line, instead modify the lines below. + As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium. + + If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you will need to clean up (remove the reference) in 15.0. If you have customized your pipeline's Dependency Scanning configuration, for example to edit the `bundler-audit-dependency_scanning` job, you will want to switch to gemnasium-dependency_scanning before removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference bundler-audit, or customized your template specifically for bundler-audit, you will not need to take action. +# 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: https://gitlab.com/gitlab-org/gitlab/-/issues/289832 # (optional) This is a link to the deprecation issue in GitLab + 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-pipeline-fields-package-deprecation.yml b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml new file mode 100644 index 00000000000..b06bb4d16dc --- /dev/null +++ b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml @@ -0,0 +1,12 @@ +- name: "Deprecate `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 + 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-remove-api-fuzzing-ci-configuration-create-mutation.yml b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml new file mode 100644 index 00000000000..f2b22b047af --- /dev/null +++ b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml @@ -0,0 +1,13 @@ +- name: "apiFuzzingCiConfigurationCreate GraphQL mutation" + announcement_milestone: "14.6" + announcement_date: "2021-12-22" + removal_milestone: "15.0" + body: | + The API Fuzzing configuration snippet is now being generated client-side and does not require an + API request anymore. We are therefore deprecating the `apiFuzzingCiConfigurationCreate` mutation + which isn't being used in GitLab anymore. + stage: Secure + tiers: Ultimate + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/333233 + documentation_url: https://docs.gitlab.com/ee/user/application_security/api_fuzzing/#web-api-fuzzing-configuration-form + removal_date: "2022-05-22" 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 new file mode 100644 index 00000000000..5f7db1ac0e5 --- /dev/null +++ b/data/deprecations/14-6-runner-api-status-renames-not_connected.yml @@ -0,0 +1,14 @@ +- name: "Deprecation of 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" + 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/15-0-deprecate-sles-12sp2.yml b/data/deprecations/15-0-deprecate-sles-12sp2.yml index fd5057bb8d3..a466d8b4100 100644 --- a/data/deprecations/15-0-deprecate-sles-12sp2.yml +++ b/data/deprecations/15-0-deprecate-sles-12sp2.yml @@ -2,5 +2,6 @@ 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 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/15-0-deprecation-versions-packagetype.yml b/data/deprecations/15-0-deprecation-versions-packagetype.yml index 4e1501b48ba..e409e9be072 100644 --- a/data/deprecations/15-0-deprecation-versions-packagetype.yml +++ b/data/deprecations/15-0-deprecation-versions-packagetype.yml @@ -2,6 +2,7 @@ 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 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/15-0-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml index 292dc4a14c0..b7e317d148e 100644 --- a/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml +++ b/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml @@ -2,6 +2,7 @@ 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 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/15-0-remove-package-pipelines-api.yml b/data/deprecations/15-0-remove-package-pipelines-api.yml index ba69ed75e0f..d26e291bb97 100644 --- a/data/deprecations/15-0-remove-package-pipelines-api.yml +++ b/data/deprecations/15-0-remove-package-pipelines-api.yml @@ -2,6 +2,7 @@ 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 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/15-0-remove-pipelines-from-version-field.yml b/data/deprecations/15-0-remove-pipelines-from-version-field.yml index 6f4f8db55cd..88eafedf36b 100644 --- a/data/deprecations/15-0-remove-pipelines-from-version-field.yml +++ b/data/deprecations/15-0-remove-pipelines-from-version-field.yml @@ -2,6 +2,7 @@ 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 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/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml index eba37d1eb8f..5da61172410 100644 --- a/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml +++ b/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml @@ -1,7 +1,8 @@ -- name: "defaultMergeCommitMessageWithDescription GraphQL API field will be removed in GitLab 15.0" # The name of the feature to be deprecated +- name: "Removal of `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 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. @@ -11,4 +12,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: # (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/deprecation_omniauth-kerberos_gem.yml b/data/deprecations/deprecation_omniauth-kerberos_gem.yml index 8adbeb19416..903d64db717 100644 --- a/data/deprecations/deprecation_omniauth-kerberos_gem.yml +++ b/data/deprecations/deprecation_omniauth-kerberos_gem.yml @@ -1,6 +1,7 @@ - name: "OmniAuth Kerberos gem" announcement_milestone: "14.3" removal_milestone: "15.0" + removal_date: "2022-05-22" 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/disable_strict_host_key_checking.yml b/data/deprecations/disable_strict_host_key_checking.yml index 62011795bb9..e7e5eb1fa9f 100644 --- a/data/deprecations/disable_strict_host_key_checking.yml +++ b/data/deprecations/disable_strict_host_key_checking.yml @@ -2,6 +2,7 @@ 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" 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/job_char_limit.yml b/data/deprecations/job_char_limit.yml new file mode 100644 index 00000000000..706e3a078eb --- /dev/null +++ b/data/deprecations/job_char_limit.yml @@ -0,0 +1,26 @@ +# 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: "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 + 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 + 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 + 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" diff --git a/data/deprecations/runner_api_new_stale_status_breaking_change.yml b/data/deprecations/runner_api_new_stale_status_breaking_change.yml new file mode 100644 index 00000000000..bb3098ff517 --- /dev/null +++ b/data/deprecations/runner_api_new_stale_status_breaking_change.yml @@ -0,0 +1,13 @@ +- 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" + 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/serverless.yml b/data/deprecations/serverless.yml index 1b99ece154f..3d280ff2f62 100644 --- a/data/deprecations/serverless.yml +++ b/data/deprecations/serverless.yml @@ -2,6 +2,7 @@ announcement_milestone: "14.3" announcement_date: "2021-09-22" removal_milestone: "15.0" + removal_date: "2022-05-22" body: | [GitLab Serverless](https://docs.gitlab.com/ee/user/project/clusters/serverless/) is a feature set to support Knative-based serverless development with automatic deployments and monitoring. diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index 80b860b367f..b0068c32ad9 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -44,6 +44,7 @@ For deprecation reviewers (Technical Writers only): <%= deprecation["body"] -%> Announced: <%= deprecation["announcement_date"]%> +Planned removal: <%= deprecation["removal_date"]%> <%- end -%> <%- end -%> <%- else -%> diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml index 0aaa68e4bd8..07e65af8277 100644 --- a/data/deprecations/templates/example.yml +++ b/data/deprecations/templates/example.yml @@ -14,6 +14,7 @@ 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: "YYYY-MM-DD" # 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. <!-- START OF BODY COMMENT @@ -29,4 +30,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: # (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 |