Update deprecations yml files

data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml

@@ -3,6 +3,7 @@
   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 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`.
 

data/deprecations/14-0-nfs-fot-git-repository-storage.yml

@@ -2,7 +2,8 @@
   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
+  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     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.
 

data/deprecations/14-2-deprecation-task-runner.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated
   removal_milestone: "14.5" # The milestone when this feature is planned to be removed
   removal_date: "2021-11-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: false
   body: | # Do not modify this line, instead modify the lines below.
     The Task Runner pod is used to execute periodic housekeeping tasks within the GitLab application and is often confused with the GitLab Runner. Thus, [Task Runner will be renamed to Toolbox](https://gitlab.com/groups/gitlab-org/charts/-/epics/25).
 

data/deprecations/14-3-database-deprecate-legacy-database-conf.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-09-22"
   removal_milestone: "15.0"
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: |
    The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
    configuration located in `database.yml` is changing and the legacy format is deprecated. The legacy format

data/deprecations/14-3-deprecation-release-cli.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated
   removal_milestone: "14.6" # The milestone when this feature is planned to be removed
   removal_date: "2021-12-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: false
   body: | # Do not modify this line, instead modify the lines below.
     The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as a [generic package](https://gitlab.com/gitlab-org/release-cli/-/packages) starting in GitLab 14.2. We will continue to deploy it as a binary to S3 until GitLab 14.5 and stop distributing it in S3 in GitLab 14.6.
   stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth

data/deprecations/14-3-package-container-registry-api-group-update.yml

 - name: "Update to the Container Registry group-level API"
   announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"
   removal_milestone: "15.0" # the milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     In milestone 15.0, support for the `tags` and `tags_count` parameters will be removed from the Container Registry API that [gets registry repositories from a group](../api/container_registry.md#within-a-group).
 
@@ -10,4 +12,3 @@
   tiers: Free
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/336912
   documentation_url: https://docs.gitlab.com/ee/api/container_registry.html#within-a-group
-  announcement_date: 2021-11-22

data/deprecations/14-3-repository-push-audit-events.yml

 - name: "Audit events for repository push events"
   announcement_milestone: "14.3" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-09-22" # https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69024
   removal_milestone: "15.0" # the milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#repository-push) are now deprecated and will be removed in GitLab 15.0.
 
@@ -12,4 +14,3 @@
   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
-  announcement_date: "2021-09-22" # https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69024

data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml

@@ -3,6 +3,7 @@
   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
+  breaking_change: true
   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

data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml

@@ -3,6 +3,7 @@
   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.
 

data/deprecations/14-5-deprecate-opensuse-15-2.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "14.8" # The milestone when this feature is planned to be removed
   removal_date: "2022-02-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: false
   body: | # Do not modify this line, instead modify the lines below.
     Distribution support and security updates for openSUSE Leap 15.2 are [ending December 2021](https://en.opensuse.org/Lifetime#openSUSE_Leap).
 

data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     We are changing how the date filter works in Value Stream Analytics. Instead of filtering by the time that the issue or merge request was created, the date filter will filter by the end event time of the given stage. This will result in completely different figures after this change has rolled out.
     

data/deprecations/14-5-geo-deprecate-promote-db.yml

-# 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:
-# {{LINK TBD}}
-#
-# Please delete this line and above before submitting your merge request.
-
 - name: "Removal of `promote-db` command from `gitlab-ctl`" # The name of the feature to be deprecated
   announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-db` which is used to promote database nodes in multi-node Geo secondary sites. `gitlab-ctl promote-db` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures.
   stage: "Enablement"
@@ -22,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: "2022-05-22"

data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml

-# 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:
-# {{LINK TBD}}
-#
-# Please delete this line and above before submitting your merge request.
-
 - name: "Removal of `promote-to-primary-node` command from `gitlab-ctl`" # The name of the feature to be deprecated
   announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Geo secondary node to a primary during a failover. This command replaces `gitlab-ctl promote-to-primary-node` which was only usable for single-node Geo sites. `gitlab-ctl promote-to-primary-node` will continue to function as-is and be available until GitLab 15.0. We recommend that Geo customers begin testing the new `gitlab-ctl promote` command in their staging environments and incorporating the new command in their failover procedures.
   stage: "Enablement"
@@ -22,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: "2022-05-22"

data/deprecations/14-5-runner-api-status-does-contain-paused.yml

 - name: "REST API Runner will not contain `paused`"
   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.
     The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 15.0.
 
@@ -14,4 +16,3 @@
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648
   documentation_url: https://docs.gitlab.com/ee/api/runners.html
-  announcement_date: "2021-11-22"

data/deprecations/14-6-deprecate-types.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
    The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior.
 # The following items are not published on the docs page, but may be used in the future.

data/deprecations/14-6-deprecation-license-compliance-api-terms.yml

@@ -2,6 +2,7 @@
   announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     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. 
 

data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml

@@ -2,6 +2,7 @@
   announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     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. 
 

data/deprecations/14-6-pipeline-fields-package-deprecation.yml

@@ -3,6 +3,7 @@
   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.
 

data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml

@@ -2,6 +2,8 @@
   announcement_milestone: "14.6"
   announcement_date: "2021-12-22"
   removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
   body: |
     The API Fuzzing configuration snippet is now being generated client-side and does not require an
     API request anymore. We are therefore deprecating the `apiFuzzingCiConfigurationCreate` mutation
@@ -10,4 +12,3 @@
   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"

data/deprecations/14-6-runner-api-status-renames-not_connected.yml

@@ -2,6 +2,7 @@
   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.

data/deprecations/15-0-deprecate-sles-12sp2.yml

@@ -3,5 +3,6 @@
   announcement_date: "2021-11-22"
   removal_milestone: "15.0" # the milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly.

data/deprecations/15-0-deprecation-versions-packagetype.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype).
 

data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     We added a feature flag because [GitLab-#11582](https://gitlab.com/gitlab-org/gitlab/-/issues/11582) changed how public groups use the Dependency Proxy. Prior to this change, you could use the Dependency Proxy without authentication. The change requires authentication to use the Dependency Proxy.
 

data/deprecations/15-0-remove-package-pipelines-api.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     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.
 

data/deprecations/15-0-remove-pipelines-from-version-field.yml

@@ -2,7 +2,8 @@
   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_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     In GraphQL, there are two `pipelines` fields that you can use in a [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype) to get the pipelines for package versions:
 

data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0" # The milestone when this feature is planned to be removed
   removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprecated and will be removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template.
 # The following items are not published on the docs page, but may be used in the future.

data/deprecations/deprecation_omniauth-kerberos_gem.yml

 - name: "OmniAuth Kerberos gem"
   announcement_milestone: "14.3"
+  announcement_date: "2021-09-22"
   removal_milestone: "15.0"
   removal_date: "2022-05-22"
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     The `omniauth-kerberos` gem will be removed in our next major release, GitLab 15.0.
 
@@ -12,5 +14,4 @@
   tiers: [Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/337384
   documentation_url: https://docs.gitlab.com/ee/integration/kerberos.html#upgrading-from-password-based-to-ticket-based-kerberos-sign-ins
-  announcement_date: "2021-09-22"
 

data/deprecations/disable_strict_host_key_checking.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-11-22"
   removal_milestone: "15.0" # the milestone when this feature is planned to be removed
   removal_date: "2022-05-22"
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.
 

data/deprecations/job_char_limit.yml

-# 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
+  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed
+  breaking_change: true
   body: | # Do not modify this line, instead modify the lines below.
     In GitLab 15.0 we are going to limit the number of characters in CI/CD job names to 255. Any pipeline with job names that exceed the 255 character limit will stop working after the 15.0 release.
 # The following items are not published on the docs page, but may be used in the future.
@@ -23,4 +13,3 @@
   documentation_url: # (optional) This is a link to the current documentation page
   image_url: # (optional) This is a link to a thumbnail image depicting the feature
   video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  removal_date: "2022-05-22"

data/deprecations/runner_api_new_stale_status_breaking_change.yml

@@ -3,6 +3,7 @@
   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.
 

data/deprecations/serverless.yml

@@ -3,6 +3,7 @@
   announcement_date: "2021-09-22"
   removal_milestone: "15.0"
   removal_date: "2022-05-22"
+  breaking_change: true
   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.
 
@@ -11,4 +12,3 @@
   tiers: [Core, Premium, Ultimate]
   issue_url: "https://gitlab.com/groups/gitlab-org/configure/-/epics/6"
   documentation_url: "https://docs.gitlab.com/ee/user/project/clusters/serverless/"
-

data/deprecations/templates/example.yml

@@ -14,7 +14,8 @@
   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.
+  removal_date: # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: false # If this deprecation is a breaking change, set this value to true
   body: | # Do not modify this line, instead modify the lines below.
     <!-- START OF BODY COMMENT