Add latest changes from gitlab-org/gitlab@14-7-stable-eev14.7.0-rc42

111 files changed, 1011 insertions, 71 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 a1261154e8c..7e2d8338dfd 100644
--- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml
+++ b/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.
 
diff --git a/data/deprecations/14-3-deprecation-release-cli.yml b/data/deprecations/14-2-deprecation-release-cli.yml
index d04e97df380..809d8eb1e8b 100644
--- a/data/deprecations/14-3-deprecation-release-cli.yml
+++ b/data/deprecations/14-2-deprecation-release-cli.yml
@@ -1,8 +1,9 @@
-- name: "Release CLI be distributed as a generic package" # The name of the feature to be deprecated
+- name: "Release CLI distributed as a generic package" # The name of the feature to be deprecated
   announcement_milestone: "14.2" # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated
   removal_milestone: "14.6" # The milestone when this feature is planned to be removed
   removal_date: "2021-12-22" # the date of the milestone release when this feature is planned to be removed
+  breaking_change: false
   body: | # Do not modify this line, instead modify the lines below.
     The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as a [generic package](https://gitlab.com/gitlab-org/release-cli/-/packages) starting in GitLab 14.2. We will continue to deploy it as a binary to S3 until GitLab 14.5 and stop distributing it in S3 in GitLab 14.6.
   stage: # (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-2-deprecation-task-runner.yml b/data/deprecations/14-2-deprecation-task-runner.yml
index 9f4d81ddd3a..8162b5c4d4e 100644
--- a/data/deprecations/14-2-deprecation-task-runner.yml
+++ b/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).
 
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 e460abcb077..29e55337261 100644
--- a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml
+++ b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml
@@ -3,12 +3,13 @@
   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
-   supported using a single PostgreSQL adapter, whereas the new format is changing to support multiple databases. The `main:` database needs to be defined as a first configuration item.
-   
-   This deprecation mainly impacts users compiling GitLab from source because Omnibus will handle this configuration automatically.
+    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
+    supported using a single PostgreSQL adapter, whereas the new format is changing to support multiple databases. The `main:` database needs to be defined as a first configuration item.
+
+    This deprecation mainly impacts users compiling GitLab from source because Omnibus will handle this configuration automatically.
   stage: Enablement
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/338182
diff --git a/data/deprecations/deprecation_omniauth-kerberos_gem.yml b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml
index 903d64db717..17c6cbc8e7a 100644
--- a/data/deprecations/deprecation_omniauth-kerberos_gem.yml
+++ b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml
@@ -1,7 +1,9 @@
 - 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"
 
diff --git a/data/deprecations/14-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml
index defa4576cde..72281be5e97 100644
--- a/data/deprecations/14-3-repository-push-audit-events.yml
+++ b/data/deprecations/14-3-repository-push-audit-events.yml
@@ -1,7 +1,9 @@
 - 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
diff --git a/data/deprecations/serverless.yml b/data/deprecations/14-3-serverless.yml
index 3d280ff2f62..aac3cc9cd6a 100644
--- a/data/deprecations/serverless.yml
+++ b/data/deprecations/14-3-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/"
-
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 e93fa25facb..60664f785b2 100644
--- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml
+++ b/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
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 29b8fe0e70c..b33f2cc88f1 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
@@ -3,10 +3,10 @@
   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.
 
   stage: Verify
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/345347
-
diff --git a/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
index 5da61172410..6fb97cbc7f4 100644
--- a/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
+++ b/data/deprecations/14-5-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.
diff --git a/data/deprecations/14-5-deprecate-opensuse-15-2.yml b/data/deprecations/14-5-deprecate-opensuse-15-2.yml
index 7b776293dbb..f95a80e6eac 100644
--- a/data/deprecations/14-5-deprecate-opensuse-15-2.yml
+++ b/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).
 
diff --git a/data/deprecations/15-0-deprecate-sles-12sp2.yml b/data/deprecations/14-5-deprecate-sles-12sp2.yml
index a466d8b4100..61e989defd3 100644
--- a/data/deprecations/15-0-deprecate-sles-12sp2.yml
+++ b/data/deprecations/14-5-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.
diff --git a/data/deprecations/15-0-deprecation-versions-packagetype.yml b/data/deprecations/14-5-deprecation-versions-packagetype.yml
index e409e9be072..78db5c0d414 100644
--- a/data/deprecations/15-0-deprecation-versions-packagetype.yml
+++ b/data/deprecations/14-5-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).
 
@@ -10,4 +11,3 @@
   stage: package
   tiers: Free
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/327453
-
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 5706e826a9d..2c16aca5df6 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
@@ -3,9 +3,10 @@
   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.
-    
+
     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
   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]
diff --git a/data/deprecations/disable_strict_host_key_checking.yml b/data/deprecations/14-5-disable_strict_host_key_checking.yml
index e7e5eb1fa9f..a3a6a3bf223 100644
--- a/data/deprecations/disable_strict_host_key_checking.yml
+++ b/data/deprecations/14-5-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.
 
diff --git a/data/deprecations/14-5-geo-deprecate-promote-db.yml b/data/deprecations/14-5-geo-deprecate-promote-db.yml
index ba2aa7dc032..113ddc53165 100644
--- a/data/deprecations/14-5-geo-deprecate-promote-db.yml
+++ b/data/deprecations/14-5-geo-deprecate-promote-db.yml
@@ -1,19 +1,9 @@
-# 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"
diff --git a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml
index 29301ed3c47..591ca6f6a87 100644
--- a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml
+++ b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml
@@ -1,19 +1,9 @@
-# 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"
diff --git a/data/deprecations/14-3-package-container-registry-api-group-update.yml b/data/deprecations/14-5-package-container-registry-api-group-update.yml
index de5d184888a..951de288d90 100644
--- a/data/deprecations/14-3-package-container-registry-api-group-update.yml
+++ b/data/deprecations/14-5-package-container-registry-api-group-update.yml
@@ -1,7 +1,9 @@
 - 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
diff --git a/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml
index b7e317d148e..1e6a4e7d378 100644
--- a/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml
+++ b/data/deprecations/14-5-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.
 
diff --git a/data/deprecations/15-0-remove-package-pipelines-api.yml b/data/deprecations/14-5-remove-package-pipelines-api.yml
index d26e291bb97..46ef1213da8 100644
--- a/data/deprecations/15-0-remove-package-pipelines-api.yml
+++ b/data/deprecations/14-5-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.
 
diff --git a/data/deprecations/15-0-remove-pipelines-from-version-field.yml b/data/deprecations/14-5-remove-pipelines-from-version-field.yml
index 88eafedf36b..917442219e5 100644
--- a/data/deprecations/15-0-remove-pipelines-from-version-field.yml
+++ b/data/deprecations/14-5-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:
 
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 5cf7b107354..dd2e6e7a6fb 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,7 +1,9 @@
 - 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"
diff --git a/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml b/data/deprecations/14-5-runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
index c4c5f6258b4..d957b79e450 100644
--- a/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
+++ b/data/deprecations/14-5-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`.
 
diff --git a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml
new file mode 100644
index 00000000000..42de723ee99
--- /dev/null
+++ b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml
@@ -0,0 +1,26 @@
+- name: "Enforced validation of security report schemas" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [Security report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported in GitLab 15.0.
+
+    Security tools that [integrate with GitLab by outputting security reports](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as pipeline job artifacts are affected. You must ensure that all output reports adhere to the correct
+    schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
+    against the declared schema version will not be processed, and vulnerability
+    findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will display a
+    [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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: [Core, 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]
+  issue_url: https://gitlab.com/groups/gitlab-org/-/epics/6968 # (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-container-scanning-schemas-below-14.yml b/data/deprecations/14-6-container-scanning-schemas-below-14.yml
new file mode 100644
index 00000000000..b79418d5765
--- /dev/null
+++ b/data/deprecations/14-6-container-scanning-schemas-below-14.yml
@@ -0,0 +1,23 @@
+- name: "Container scanning schemas below 14.0.0" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [Container scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported in GitLab 15.0.
+
+    Third-party tools that [integrate with GitLab by outputting a container scanning security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate against the declared schema version will not be processed, and vulnerability findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will display a
+    [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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-coverage-fuzzing-schemas-below-14.yml b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml
new file mode 100644
index 00000000000..13babcc26ba
--- /dev/null
+++ b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml
@@ -0,0 +1,26 @@
+- name: "Coverage guided fuzzing schemas below 14.0.0" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [Coverage guided fuzzing report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    below version 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported in GitLab 15.0.
+
+    Third-party tools that [integrate with GitLab by outputting a coverage guided fuzzing security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
+    schema with a minimum version of 14.0.0. Any reports with a lower version or that fail to validate
+    against the declared schema version will not be processed, and vulnerability
+    findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will display a
+    [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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-dast-schemas-below-14.yml b/data/deprecations/14-6-dast-schemas-below-14.yml
new file mode 100644
index 00000000000..afd27a1fa7a
--- /dev/null
+++ b/data/deprecations/14-6-dast-schemas-below-14.yml
@@ -0,0 +1,26 @@
+- name: "DAST schemas below 14.0.0" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [DAST report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
+
+    Third-party tools that [integrate with GitLab by outputting a DAST security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
+    schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
+    against the declared schema version will not be processed, and vulnerability
+    findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will cause a
+    [warning to be displayed](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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-dependency-scanning-schemas-below-14.yml b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml
new file mode 100644
index 00000000000..226cffc3afc
--- /dev/null
+++ b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml
@@ -0,0 +1,26 @@
+- name: "Dependency scanning schemas below 14.0.0" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [Dependency scanning report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
+
+    Third-party tools that [integrate with GitLab by outputting a Dependency scanning security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
+    schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
+    against the declared schema version will not be processed, and vulnerability
+    findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will cause a
+    [warning to be displayed](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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-deprecate-types.yml b/data/deprecations/14-6-deprecate-types.yml
index 5cbc07efa89..3e04ad1d6fe 100644
--- a/data/deprecations/14-6-deprecate-types.yml
+++ b/data/deprecations/14-6-deprecate-types.yml
@@ -3,8 +3,9 @@
   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 `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]
diff --git a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml
index d75b668f111..55c74ddfabd 100644
--- a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml
+++ b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml
@@ -2,10 +2,11 @@
   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. 
+    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. 
+    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]
@@ -13,4 +14,4 @@
   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
+  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml
index 23e59da21e4..8cf0ddc49f4 100644
--- a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml
+++ b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml
@@ -2,8 +2,9 @@
   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. 
+    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.
@@ -13,4 +14,4 @@
   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
+  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/job_char_limit.yml b/data/deprecations/14-6-job_char_limit.yml
index 706e3a078eb..6570b1b8e81 100644
--- a/data/deprecations/job_char_limit.yml
+++ b/data/deprecations/14-6-job_char_limit.yml
@@ -1,19 +1,9 @@
-# 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"
diff --git a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml
index b06bb4d16dc..b9140a84cdd 100644
--- a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml
+++ b/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.
 
diff --git a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml
index f2b22b047af..bdf7a64700b 100644
--- a/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml
+++ b/data/deprecations/14-6-remove-api-fuzzing-ci-configuration-create-mutation.yml
@@ -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"
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
index 5f7db1ac0e5..5654d3227eb 100644
--- a/data/deprecations/14-6-runner-api-status-renames-not_connected.yml
+++ b/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.
diff --git a/data/deprecations/runner_api_new_stale_status_breaking_change.yml b/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml
index bb3098ff517..3cf6ed69354 100644
--- a/data/deprecations/runner_api_new_stale_status_breaking_change.yml
+++ b/data/deprecations/14-6-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.
 
diff --git a/data/deprecations/14-6-sast-schemas-below-14.yml b/data/deprecations/14-6-sast-schemas-below-14.yml
new file mode 100644
index 00000000000..02e112ec4b8
--- /dev/null
+++ b/data/deprecations/14-6-sast-schemas-below-14.yml
@@ -0,0 +1,26 @@
+- name: "SAST schemas below 14.0.0" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [SAST report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
+
+    Third-party tools that [integrate with GitLab by outputting a SAST security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
+    schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
+    against the declared schema version will not be processed, and vulnerability
+    findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will display a
+    [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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-secret-detection-schemas-below-14.yml b/data/deprecations/14-6-secret-detection-schemas-below-14.yml
new file mode 100644
index 00000000000..d366e08a8c0
--- /dev/null
+++ b/data/deprecations/14-6-secret-detection-schemas-below-14.yml
@@ -0,0 +1,26 @@
+- name: "Secret detection schemas below 14.0.0" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    [Secret detection report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/releases)
+    versions earlier than 14.0.0 will no longer be supported in GitLab 15.0. Reports that do not pass validation
+    against the schema version declared in the report will also no longer be supported as of GitLab 15.0.
+
+    Third-party tools that [integrate with GitLab by outputting a Secret detection security report](https://docs.gitlab.com/ee/development/integrations/secure.html#report)
+    as a pipeline job artifact are affected. You must ensure that all output reports adhere to the correct
+    schema with a minimum version of 14.0.0. Reports with a lower version or that fail to validate
+    against the declared schema version will not be processed, and vulnerability
+    findings will not display in MRs, pipelines, or Vulnerability Reports.
+
+    To help with the transition, from GitLab 14.10, non-compliant reports will display a
+    [warning](https://gitlab.com/gitlab-org/gitlab/-/issues/335789#note_672853791)
+    in the Vulnerability Report.
+# 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-7-deprecate-artifacts-keyword.yml b/data/deprecations/14-7-deprecate-artifacts-keyword.yml
new file mode 100644
index 00000000000..cbd1a6d41e5
--- /dev/null
+++ b/data/deprecations/14-7-deprecate-artifacts-keyword.yml
@@ -0,0 +1,16 @@
+- name: "Removal of `artifacts:report:cobertura` keyword"
+  announcement_milestone: "14.7"
+  announcement_date: "2022-01-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: false
+  body: |
+     Currently, test coverage visualizations in GitLab only support Cobertura reports. Starting 15.0, the
+     `artifacts:report:cobertura` keyword will be replaced by
+     [`artifacts:reports:coverage_report`](https://gitlab.com/gitlab-org/gitlab/-/issues/344533). Cobertura will be the
+     only supported report file in 15.0, but this is the first step towards GitLab supporting other report types.
+
+# The following items are not published on the docs page, but may be used in the future.
+  stage: Verify
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/348980
+  documentation_url: https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportscobertura
diff --git a/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml
new file mode 100644
index 00000000000..cf986341884
--- /dev/null
+++ b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml
@@ -0,0 +1,12 @@
+- name: "Godep support in License Compliance" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed.
+  body: | # Do not modify this line, instead modify the lines below.
+    The Godep dependency manager for Golang was deprecated in 2020 by Go and
+    has been replaced with Go modules.
+    To reduce our maintenance cost we are deprecating License Compliance for Godep projects as of 14.7
+    and will remove it in GitLab 15.0
+  documentation_url: "https://docs.gitlab.com/ee/user/compliance/license_compliance/#supported-languages-and-package-managers"
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/327057"
diff --git a/data/deprecations/14-7-deprecate-merged_by-api-field.yml b/data/deprecations/14-7-deprecate-merged_by-api-field.yml
new file mode 100644
index 00000000000..31b2d9c9244
--- /dev/null
+++ b/data/deprecations/14-7-deprecate-merged_by-api-field.yml
@@ -0,0 +1,27 @@
+# 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: "merged_by API field" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "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: false # If this deprecation is a breaking change, set this value to true
+  body: | # Do not modify this line, instead modify the lines below.
+    The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-requests) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `merge_user` field (already present in GraphQL) which more correctly identifies who merged a merge request when performing actions (merge when pipeline succeeds, add to merge train) other than a simple merge.
+# 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: # (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/350534 # (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-7-deprecate-static-site-editor.yml b/data/deprecations/14-7-deprecate-static-site-editor.yml
new file mode 100644
index 00000000000..d8acfbf8ab3
--- /dev/null
+++ b/data/deprecations/14-7-deprecate-static-site-editor.yml
@@ -0,0 +1,14 @@
+- name: "Removal of Static Site Editor" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed.
+  body: | # Do not modify this line, instead modify the lines below.
+    The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver smiliar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the Web IDE. 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]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347137 # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/user/project/static_site_editor/ # (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-7-pseudonymizer.yml b/data/deprecations/14-7-pseudonymizer.yml
new file mode 100644
index 00000000000..bd8cb215496
--- /dev/null
+++ b/data/deprecations/14-7-pseudonymizer.yml
@@ -0,0 +1,12 @@
+- name: "Pseudonymizer" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed.
+  body: | # Do not modify this line, instead modify the lines below.
+    The Pseudonymizer feature is generally unused,
+    can cause production issues with large databases,
+    and can interfere with object storage development.
+    It is now considered deprecated, and will be removed in GitLab 15.0.
+  documentation_url: "https://docs.gitlab.com/ee/administration/pseudonymizer.html"
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/219952"
diff --git a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml
new file mode 100644
index 00000000000..34c262b1539
--- /dev/null
+++ b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml
@@ -0,0 +1,30 @@
+- name: "Sidekiq metrics and health checks configuration"
+  announcement_milestone: "14.7"
+  announcement_date: "2021-01-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
+  body: | # Do not modify this line, instead modify the lines below.
+    Exporting Sidekiq metrics and health checks using a single process and port is deprecated.
+    Support will be removed in 15.0.
+
+    We have updated Sidekiq to export [metrics and health checks from two separate processes](https://gitlab.com/groups/gitlab-org/-/epics/6409)
+    to improve stability and availability and prevent data loss in edge cases.
+    As those are two separate servers, a configuration change will be required in 15.0
+    to explicitly set separate ports for metrics and health-checks.
+    The newly introduced settings for `sidekiq['health_checks_*']`
+    should always be set in `gitlab.rb`.
+    For more information, check the documentation for [configuring Sidekiq](https://docs.gitlab.com/ee/administration/sidekiq.html).
+
+    These changes also require updates in either Prometheus to scrape the new endpoint or k8s health-checks to target the new
+    health-check port to work properly, otherwise either metrics or health-checks will disappear.
+
+    For the deprecation period those settings are optional
+    and GitLab will default the Sidekiq health-checks port to the same port as `sidekiq_exporter`
+    and only run one server (not changing the current behaviour).
+    Only if they are both set and a different port is provided, a separate metrics server will spin up
+    to serve the Sidekiq metrics, similar to the way Sidekiq will behave in 15.0.
+  stage: Enablement
+  tiers: [Free, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347509
+  documentation_url: https://docs.gitlab.com/ee/administration/sidekiq.html
diff --git a/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml b/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml
new file mode 100644
index 00000000000..cda67e53b8e
--- /dev/null
+++ b/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml
@@ -0,0 +1,15 @@
+- name: "`fixup!` commit messages setting draft status of associated Merge Request" # 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-06-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 use of `fixup!` as a commit message to trigger draft status
+    of the associated Merge Request is generally unused, and can cause
+    confusion with other uses of the term. "Draft" is the preferred
+    and supported trigger for triggering draft status from commit
+    messages, as part of our streamlining of the feature.
+    Support for `fixup!` is now considered deprecated, and will be
+    removed in GitLab 15.0.
+  documentation_url: "https://docs.gitlab.com/ee/user/project/merge_requests/drafts.html#mark-merge-requests-as-drafts"
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/342937"
diff --git a/data/deprecations/15-0-deprecate-monitor-logging.yml b/data/deprecations/15-0-deprecate-monitor-logging.yml
new file mode 100644
index 00000000000..facb66e4ee8
--- /dev/null
+++ b/data/deprecations/15-0-deprecate-monitor-logging.yml
@@ -0,0 +1,16 @@
+- name: "Logging in GitLab" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true # If this deprecation is a breaking change, set this value to true
+  body: | # Do not modify this line, instead modify the lines below.
+    The logging features in GitLab allow users to install the ELK stack (Elasticsearch, Logstash, and Kibana) to aggregate and manage application logs. Users can search for relevant logs in GitLab. However, since deprecating certificate-based integration with Kubernetes clusters and GitLab Managed Apps, we don't have a recommended solution for logging within GitLab. For more information, you can follow the issue for [integrating Opstrace with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976).
+# The following items are not published on the docs page, but may be used in the future.
+  stage: Monitor # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: [Free] # (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/346485 # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/operations/#aggregate-and-store-logs-deprecated # (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-deprecate-monitor-metrics.yml b/data/deprecations/15-0-deprecate-monitor-metrics.yml
new file mode 100644
index 00000000000..0a28785105f
--- /dev/null
+++ b/data/deprecations/15-0-deprecate-monitor-metrics.yml
@@ -0,0 +1,17 @@
+- name: "Monitor performance metrics through Prometheus" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true # If this deprecation is a breaking change, set this value to true
+  body: | # Do not modify this line, instead modify the lines below.
+     By displaying data stored in a Prometheus instance, GitLab allows users to view performance metrics. GitLab also displays visualizations of these metrics in dashboards. The user can connect to a previously-configured external Prometheus instance, or set up Prometheus as a GitLab Managed App.
+     However, since certificate-based integration with Kubernetes clusters is deprecated in GitLab, the metrics functionality in GitLab that relies on Prometheus is also deprecated. This includes the metrics visualizations in dashboards. GitLab is working to develop a single user experience based on [Opstrace](https://about.gitlab.com/press/releases/2021-12-14-gitlab-acquires-opstrace-to-expand-its-devops-platform-with-open-source-observability-solution.html). An [issue exists](https://gitlab.com/groups/gitlab-org/-/epics/6976) for you to follow work on the Opstrace integration.
+# The following items are not published on the docs page, but may be used in the future.
+  stage: Monitor # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: [Free] # (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/346541 # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/operations/metrics/dashboards/ # (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-deprecate-monitor-tracing.yml b/data/deprecations/15-0-deprecate-monitor-tracing.yml
new file mode 100644
index 00000000000..126ada081f4
--- /dev/null
+++ b/data/deprecations/15-0-deprecate-monitor-tracing.yml
@@ -0,0 +1,16 @@
+- name: "Tracing in GitLab" # The name of the feature to be deprecated
+  announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-01-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true # If this deprecation is a breaking change, set this value to true
+  body: | # Do not modify this line, instead modify the lines below.
+    Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distributed tracing system. GitLab users can navigate to their Jaeger instance to gain insight into the performance of a deployed application, tracking each function or microservice that handles a given request. Tracing in GitLab is deprecated in GitLab 14.7, and scheduled for removal in 15.0. To track work on a possible replacement, see the issue for [Opstrace integration with GitLab](https://gitlab.com/groups/gitlab-org/-/epics/6976).
+# The following items are not published on the docs page, but may be used in the future.
+  stage: Monitor # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: [Free] # (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/346540 # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/operations/tracing.html#tracing # (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/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb
index b0068c32ad9..70169ef5c5c 100644
--- a/data/deprecations/templates/_deprecation_template.md.erb
+++ b/data/deprecations/templates/_deprecation_template.md.erb
@@ -4,7 +4,7 @@ group: none
 info: "See the Technical Writers assigned to Development Guidelines: https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments-to-development-guidelines"
 ---
 
-# Deprecated feature removal schedule
+# Deprecations by milestone
 
 DISCLAIMER:
 This page contains information related to upcoming products, features, and functionality.
@@ -38,13 +38,19 @@ For deprecation reviewers (Technical Writers only):
 <% if milestones.any? -%>
   <%- milestones.each do |milestone| %>
 ## <%= milestone %>
-    <%- deprecations.select{|d| d["removal_milestone"] == milestone}.each do |deprecation| %>
+    <%- entries.select{|d| d["announcement_milestone"] == milestone}.each do |deprecation| %>
 ### <%= deprecation["name"]%>
+<% if deprecation["breaking_change"] -%>
 
-<%= deprecation["body"] -%>
+WARNING:
+This feature will be changed or removed in <%= deprecation["removal_milestone"]%>
+as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
+Before updating GitLab, review the details carefully to determine if you need to make any
+changes to your code, settings, or workflow.
 
-Announced: <%= deprecation["announcement_date"]%>
-Planned removal: <%= deprecation["removal_date"]%>
+<%= deprecation["body"] -%><% else %>
+<%= deprecation["body"] -%><% end %>
+**Planned removal milestone: <%= deprecation["removal_milestone"]%> (<%= deprecation["removal_date"]%>)**
     <%- end -%>
   <%- end -%>
 <%- else -%>
diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml
index 07e65af8277..3097db557b8 100644
--- a/data/deprecations/templates/example.yml
+++ b/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
 
diff --git a/data/removals/14_0/14_0-ds-deprecations.yml b/data/removals/14_0/14_0-ds-deprecations.yml
new file mode 100644
index 00000000000..c9eefe65c91
--- /dev/null
+++ b/data/removals/14_0/14_0-ds-deprecations.yml
@@ -0,0 +1,10 @@
+- name: "Deprecations for Dependency Scanning"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: nicoleschwartz
+  body: |
+    As mentioned in [13.9](https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#deprecations-for-dependency-scanning) and [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/) several removals for Dependency Scanning take effect.
+
+    Previously, to exclude a DS analyzer, you needed to remove it from the default list of analyzers, and use that to set the `DS_DEFAULT_ANALYZERS` variable in your project’s CI template. We determined it should be easier to avoid running a particular analyzer without losing the benefit of newly added analyzers. As a result, we ask you to migrate from `DS_DEFAULT_ANALYZERS` to `DS_EXCLUDED_ANALYZERS` when it is available. Read about it in [issue #287691](https://gitlab.com/gitlab-org/gitlab/-/issues/287691).
+
+    Previously, to prevent the Gemnasium analyzers to fetch the advisory database at runtime, you needed to set the `GEMNASIUM_DB_UPDATE` variable. However, this is not documented properly, and its naming is inconsistent with the equivalent `BUNDLER_AUDIT_UPDATE_DISABLED` variable. As a result, we ask you to migrate from `GEMNASIUM_DB_UPDATE` to `GEMNASIUM_UPDATE_DISABLED` when it is available. Read about it in [issue #215483](https://gitlab.com/gitlab-org/gitlab/-/issues/215483).
diff --git a/data/removals/14_0/14_0-lc-deprecations.yml b/data/removals/14_0/14_0-lc-deprecations.yml
new file mode 100644
index 00000000000..8f59fdbb557
--- /dev/null
+++ b/data/removals/14_0/14_0-lc-deprecations.yml
@@ -0,0 +1,6 @@
+- name: "Removals for License Compliance"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: nicoleschwartz
+  body: |
+    In 13.0, we deprecated the License-Management CI template and renamed it License-Scanning. We have been providing backward compatibility by warning users of the old template to switch. Now in 14.0, we are completely removing the License-Management CI template. Read about it in [issue #216261](https://gitlab.com/gitlab-org/gitlab/-/issues/216261) or [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/).
diff --git a/data/removals/14_0/change_default_branch_name_to_main.yml b/data/removals/14_0/change_default_branch_name_to_main.yml
new file mode 100644
index 00000000000..d2c0128daa5
--- /dev/null
+++ b/data/removals/14_0/change_default_branch_name_to_main.yml
@@ -0,0 +1,10 @@
+- name: "Default branch name for new repositories now `main`"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: sarahwaldner
+  body: |
+    Every Git repository has an initial branch, which is named `master` by default. It's the first branch to be created automatically when you create a new repository. Future [Git versions](https://lore.kernel.org/git/pull.656.v4.git.1593009996.gitgitgadget@gmail.com/) will change the default branch name in Git from `master` to `main`. In coordination with the Git project and the broader community, [GitLab has changed the default branch name](https://gitlab.com/gitlab-org/gitlab/-/issues/223789) for new projects on both our SaaS (GitLab.com) and self-managed offerings starting with GitLab 14.0. This will not affect existing projects.
+
+    GitLab has already introduced changes that allow you to change the default branch name both at the [instance level](https://docs.gitlab.com/ee/user/project/repository/branches/default.html#instance-level-custom-initial-branch-name) (for self-managed users) and at the [group level](https://docs.gitlab.com/ee/user/group/#use-a-custom-name-for-the-initial-branch) (for both SaaS and self-managed users). We encourage you to make use of these features to set default branch names on new projects.
+
+    For more information, check out our [blog post](https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/).
diff --git a/data/removals/14_0/create-code-review-draft-wip.yml b/data/removals/14_0/create-code-review-draft-wip.yml
new file mode 100644
index 00000000000..addd6c400a6
--- /dev/null
+++ b/data/removals/14_0/create-code-review-draft-wip.yml
@@ -0,0 +1,6 @@
+- name: "WIP merge requests renamed 'draft merge requests'"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: phikai
+  body: |
+    The WIP (work in progress) status for merge requests signaled to reviewers that the merge request in question wasn't ready to merge. We've renamed the WIP feature to **Draft**, a more inclusive and self-explanatory term. **Draft** clearly communicates the merge request in question isn't ready for review, and makes no assumptions about the progress being made toward it. **Draft** also reduces the cognitive load for new users, non-English speakers, and anyone unfamiliar with the WIP acronym.
diff --git a/data/removals/14_0/create-code-review-w-parameter-removal.yml b/data/removals/14_0/create-code-review-w-parameter-removal.yml
new file mode 100644
index 00000000000..471df85b540
--- /dev/null
+++ b/data/removals/14_0/create-code-review-w-parameter-removal.yml
@@ -0,0 +1,6 @@
+- name: "Remove `?w=1` URL parameter to ignore whitespace changes"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: phikai
+  body: |
+    To create a consistent experience for users based on their preferences, support for toggling whitespace changes via URL parameter has been removed in GitLab 14.0.
diff --git a/data/removals/14_0/deprecate_ci_project_config_path_variable.yml b/data/removals/14_0/deprecate_ci_project_config_path_variable.yml
new file mode 100644
index 00000000000..c262a641bd1
--- /dev/null
+++ b/data/removals/14_0/deprecate_ci_project_config_path_variable.yml
@@ -0,0 +1,6 @@
+- name: "`CI_PROJECT_CONFIG_PATH` removed in GitLab 14.0"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: stkerr
+  body: |
+    GitLab 14.0 removes the `CI_PROJECT_CONFIG_PATH` pre-defined project variable in favor of `CI_CONFIG_PATH`, which is functionally the same. If you are using `CI_PROJECT_CONFIG_PATH` in your pipeline configurations, update them to use `CI_CONFIG_PATH` instead.
diff --git a/data/removals/14_0/deprecation_bump_terraform_template_version.yml b/data/removals/14_0/deprecation_bump_terraform_template_version.yml
new file mode 100644
index 00000000000..a2e4bad9913
--- /dev/null
+++ b/data/removals/14_0/deprecation_bump_terraform_template_version.yml
@@ -0,0 +1,18 @@
+- name: "New Terraform template version"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0" # example
+  issue_url: ""
+  reporter: nagyv-gitlab
+  body: |
+    As we continuously [develop GitLab's Terraform integrations](https://gitlab.com/gitlab-org/gitlab/-/issues/325312), to minimize customer disruption, we maintain two GitLab CI/CD templates for Terraform:
+
+    - The ["latest version" template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.latest.gitlab-ci.yml), which is updated frequently between minor releases of GitLab (such as 13.10, 13.11, etc).
+    - The ["major version" template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml), which is updated only at major releases (such as 13.0, 14.0, etc).
+
+    At every major release of GitLab, the "latest version" template becomes the "major version" template, inheriting the "latest template" setup.
+    As we have added many new features to the Terraform integration, the new setup for the "major version" template can be considered a breaking change.
+
+    The latest template supports the [Terraform Merge Request widget](https://docs.gitlab.com/ee/user/infrastructure/mr_integration.html) and
+    doesn't need additional setup to work with the [GitLab managed Terraform state](https://docs.gitlab.com/ee/user/infrastructure/terraform_state.html).
+
+    To check the new changes, see the [new "major version" template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml).
diff --git a/data/removals/14_0/deprecation_manage_access_14_0.yml b/data/removals/14_0/deprecation_manage_access_14_0.yml
new file mode 100644
index 00000000000..bc82067821f
--- /dev/null
+++ b/data/removals/14_0/deprecation_manage_access_14_0.yml
@@ -0,0 +1,17 @@
+- name: Limit projects returned in `GET /groups/:id/`
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: ogolowisnki
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/257829
+  body: |
+    To improve performance, we are limiting the number of projects returned from the `GET /groups/:id/` API call to 100. A complete list of projects can still be retrieved with the `GET /groups/:id/projects` API call.
+
+- name: "GitLab OAuth implicit grant deprecation"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: ogolowinski
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/288516'
+  body: |
+    GitLab is deprecating the [OAuth 2 implicit grant flow](https://docs.gitlab.com/ee/api/oauth2.html#implicit-grant-flow) as it has been removed for [OAuth 2.1](https://oauth.net/2.1/).
+
+    Beginning in 14.0, new applications can't be created with the OAuth 2 implicit grant flow. Existing OAuth implicit grant flows are no longer supported in 14.4. Migrate your existing applications to other supported [OAuth2 flows](https://docs.gitlab.com/ee/api/oauth2.html#supported-oauth2-flows) before release 14.4.
diff --git a/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml b/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml
new file mode 100644
index 00000000000..97adc4bb050
--- /dev/null
+++ b/data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml
@@ -0,0 +1,6 @@
+- name: "Update CI/CD templates to stop using hardcoded `master`"
+  reporter: dhershkovitch
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  body: |
+    Our CI/CD templates have been updated to no longer use hard-coded references to a `master` branch. In 14.0, they all use a variable that points to your project's configured default branch instead. If your CI/CD pipeline relies on our built-in templates, verify that this change works with your current configuration. For example, if you have a `master` branch and a different default branch, the updates to the templates may cause changes to your pipeline behavior. For more information, [read the issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324131).
diff --git a/data/removals/14_0/deuley_servicetemplates_removal.yml b/data/removals/14_0/deuley_servicetemplates_removal.yml
new file mode 100644
index 00000000000..94816bbee4a
--- /dev/null
+++ b/data/removals/14_0/deuley_servicetemplates_removal.yml
@@ -0,0 +1,8 @@
+- name: "Service Templates removed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deuley
+  body: |
+    Service Templates are [removed in GitLab 14.0](https://gitlab.com/groups/gitlab-org/-/epics/5672). They were used to apply identical settings to a large number of projects, but they only did so at the time of project creation.
+
+    While they solved part of the problem, _updating_ those values later proved to be a major pain point. [Project Integration Management](https://docs.gitlab.com/ee/user/admin_area/settings/project_integration_management.html) solves this problem by enabling you to create settings at the Group or Instance level, and projects within that namespace inheriting those settings.
diff --git a/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml b/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml
new file mode 100644
index 00000000000..066022dae87
--- /dev/null
+++ b/data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml
@@ -0,0 +1,7 @@
+- name: "Removal of release description in the Tags API"
+  reporter: kbychu
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/300887'
+  body: |
+    GitLab 14.0 removes support for the release description in the Tags API. You can no longer add a release description when [creating a new tag](https://docs.gitlab.com/ee/api/tags.html#create-a-new-tag). You also can no longer [create](https://docs.gitlab.com/ee/api/tags.html#create-a-new-release) or [update](https://docs.gitlab.com/ee/api/tags.html#update-a-release) a release through the Tags API. Please migrate to use the [Releases API](https://docs.gitlab.com/ee/api/releases/#create-a-release) instead.
diff --git a/data/removals/14_0/release_deprecation_auto-deploy-image.yml b/data/removals/14_0/release_deprecation_auto-deploy-image.yml
new file mode 100644
index 00000000000..7a8f0e598c4
--- /dev/null
+++ b/data/removals/14_0/release_deprecation_auto-deploy-image.yml
@@ -0,0 +1,9 @@
+- name: "Update Auto Deploy template version"
+  reporter: kbychu
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/300862'
+  body: |
+    In GitLab 14.0, we will update the [Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/stages.html#auto-deploy) CI template to the latest version. This includes new features, bug fixes, and performance improvements with a dependency on the v2 [auto-deploy-image](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image). Auto Deploy CI tempalte v1 will is deprecated going forward.
+
+    Since the v1 and v2 versions are not backward-compatible, your project might encounter an unexpected failure if you already have a deployed application. Follow the [upgrade guide](https://docs.gitlab.com/ee/topics/autodevops/upgrading_auto_deploy_dependencies.html#upgrade-guide) to upgrade your environments. You can also start using the latest template today by following the [early adoption guide](https://docs.gitlab.com/ee/topics/autodevops/upgrading_auto_deploy_dependencies.html#early-adopters).
diff --git a/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml b/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml
new file mode 100644
index 00000000000..694c168fb93
--- /dev/null
+++ b/data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml
@@ -0,0 +1,7 @@
+- name: "Remove disk source configuration for GitLab Pages"
+  reporter: kbychu
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5993'
+  body: |
+    GitLab Pages [API-based configuration](https://docs.gitlab.com/ee/administration/pages/#gitlab-api-based-configuration) has been available since GitLab 13.0. It replaces the unsupported `disk` source configuration removed in GitLab 14.0, which can no longer be chosen. You should stop using `disk` source configuration, and move to `gitlab` for an API-based configuration. To migrate away from the 'disk' source configuration, set `gitlab_pages['domain_config_source'] = "gitlab"` in your `/etc/gitlab/gitlab.rb` file. We recommend you migrate before updating to GitLab 14.0, to identify and troubleshoot any potential problems before upgrading.
diff --git a/data/removals/14_0/release_legacy_feature_flags_deprecation.yml b/data/removals/14_0/release_legacy_feature_flags_deprecation.yml
new file mode 100644
index 00000000000..aa62be7eb1d
--- /dev/null
+++ b/data/removals/14_0/release_legacy_feature_flags_deprecation.yml
@@ -0,0 +1,7 @@
+- name: "Legacy feature flags removed"
+  reporter: kbychu
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/254324'
+  body: |
+    Legacy feature flags became read-only in GitLab 13.4. GitLab 14.0 removes support for legacy feature flags, so you must migrate them to the [new version](https://docs.gitlab.com/ee/operations/feature_flags.html). You can do this by first taking a note (screenshot) of the legacy flag, then deleting the flag through the API or UI (you don't need to alter the code), and finally create a new Feature Flag with the same name as the legacy flag you deleted. Also, make sure the strategies and environments match the deleted flag. We created a [video tutorial](https://www.youtube.com/watch?v=CAJY2IGep7Y) to help with this migration.
diff --git a/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml b/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml
new file mode 100644
index 00000000000..48e79230297
--- /dev/null
+++ b/data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml
@@ -0,0 +1,7 @@
+- name: "Remove redundant timestamp field from DORA metrics API payload"
+  reporter: kbychu
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/325931'
+  body: |
+    The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora4_project_analytics.html#list-project-deployment-frequencies) endpoint has been deprecated in favor of the [DORA 4 API](https://docs.gitlab.com/ee/api/dora/metrics.html), which consolidates all the metrics under one API with the specific metric as a required field. As a result, the timestamp field, which doesn't allow adding future extensions and causes performance issues, will be removed. With the old API, an example response would be `{ "2021-03-01": 3, "date": "2021-03-01", "value": 3 }`. The first key/value (`"2021-03-01": 3`) will be removed and replaced by the last two (`"date": "2021-03-01", "value": 3`).
diff --git a/data/removals/14_0/removal-geo-fdw-settings.yml b/data/removals/14_0/removal-geo-fdw-settings.yml
new file mode 100644
index 00000000000..c2066269cb8
--- /dev/null
+++ b/data/removals/14_0/removal-geo-fdw-settings.yml
@@ -0,0 +1,11 @@
+- name: "Geo Foreign Data Wrapper settings removed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: fzimmer
+  body: |
+    As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/#geo-foreign-data-wrapper-settings-deprecated), the following configuration settings in `/etc/gitlab/gitlab.rb` have been removed in 14.0:
+
+    - `geo_secondary['db_fdw']`
+    - `geo_postgresql['fdw_external_user']`
+    - `geo_postgresql['fdw_external_password']`
+    - `gitlab-_rails['geo_migrated_local_files_clean_up_worker_cron']`
diff --git a/data/removals/14_0/removal-graphql-fields.yml b/data/removals/14_0/removal-graphql-fields.yml
new file mode 100644
index 00000000000..24d2bb4a4eb
--- /dev/null
+++ b/data/removals/14_0/removal-graphql-fields.yml
@@ -0,0 +1,13 @@
+- name: "Deprecated GraphQL fields have been removed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: gweaver
+  body: |
+    In accordance with our [GraphQL deprecation and removal process](https://docs.gitlab.com/ee/api/graphql/#deprecation-process), the following fields that were deprecated prior to 13.7 are [fully removed in 14.0](https://gitlab.com/gitlab-org/gitlab/-/issues/267966):
+
+    - `Mutations::Todos::MarkAllDone`, `Mutations::Todos::RestoreMany` - `:updated_ids`
+    - `Mutations::DastScannerProfiles::Create`, `Types::DastScannerProfileType` - `:global_id`
+    - `Types::SnippetType` - `:blob`
+    - `EE::Types::GroupType`, `EE::Types::QueryType` - `:vulnerabilities_count_by_day_and_severity`
+    - `DeprecatedMutations (concern**)` - `AddAwardEmoji`, `RemoveAwardEmoji`, `ToggleAwardEmoji`
+    - `EE::Types::DeprecatedMutations (concern***)` - `Mutations::Pipelines::RunDastScan`, `Mutations::Vulnerabilities::Dismiss`, `Mutations::Vulnerabilities::RevertToDetected`
diff --git a/data/removals/14_0/removal-legacy-storage.yml b/data/removals/14_0/removal-legacy-storage.yml
new file mode 100644
index 00000000000..677ec7b8512
--- /dev/null
+++ b/data/removals/14_0/removal-legacy-storage.yml
@@ -0,0 +1,6 @@
+- name: "Legacy storage removed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: fzimmer
+  body: |
+    As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/#planned-removal-of-legacy-storage-in-14.0), [legacy storage](https://docs.gitlab.com/ee/administration/repository_storage_types.html#legacy-storage) has been removed in GitLab 14.0.
diff --git a/data/removals/14_0/removal-protect-features.yml b/data/removals/14_0/removal-protect-features.yml
new file mode 100644
index 00000000000..8e50925f6db
--- /dev/null
+++ b/data/removals/14_0/removal-protect-features.yml
@@ -0,0 +1,13 @@
+- name: Container Scanning Engine Clair
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: sam.white
+  body: |
+    Clair, the default container scanning engine, was deprecated in GitLab 13.9 and is removed from GitLab 14.0 and replaced by Trivy. We advise customers who are customizing variables for their container scanning job to [follow these instructions](https://docs.gitlab.com/ee/user/application_security/container_scanning/#change-scanners) to ensure that their container scanning jobs continue to work.
+
+- name: Web Application Firewall (WAF)
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: sam.white
+  body: |
+    The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed from GitLab 14.0. The WAF had limitations inherent in the architectural design that made it difficult to meet the requirements traditionally expected of a WAF. By removing the WAF, GitLab is able to focus on improving other areas in the product where more value can be provided to users. Users who currently rely on the WAF can continue to use the free and open source [ModSecurity](https://github.com/SpiderLabs/ModSecurity) project, which is independent from GitLab. Additional details are available in the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271276).
diff --git a/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml b/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml
new file mode 100644
index 00000000000..442c0e97cde
--- /dev/null
+++ b/data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml
@@ -0,0 +1,10 @@
+- name: Sidekiq queue selector options no longer accept the 'experimental' prefix
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: smcgivern
+  body: |
+    GitLab supports a [queue selector](https://docs.gitlab.com/ee/administration/operations/extra_sidekiq_processes.html#queue-selector) to run only a subset of background jobs for a given process. When it was introduced, this option had an 'experimental' prefix (`experimental_queue_selector` in Omnibus, `experimentalQueueSelector` in Helm charts).
+
+    As announced in the [13.6 release post](https://about.gitlab.com/releases/2020/11/22/gitlab-13-6-released/#sidekiq-cluster-queue-selector-configuration-option-has-been-renamed), the 'experimental' prefix is no longer supported. Instead, `queue_selector` for Omnibus and `queueSelector` in Helm charts should be used.
+
+
diff --git a/data/removals/14_0/removal-unicorn.yml b/data/removals/14_0/removal-unicorn.yml
new file mode 100644
index 00000000000..af0bed0f3ec
--- /dev/null
+++ b/data/removals/14_0/removal-unicorn.yml
@@ -0,0 +1,6 @@
+- name: "Unicorn removed in favor of Puma for GitLab self-managed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: fzimmer
+  body: |
+    [Support for Unicorn](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6078) has been removed in GitLab 14.0 in favor of Puma. [Puma has a multi-threaded architecture](https://docs.gitlab.com/ee/administration/operations/puma.html) which uses less memory than a multi-process application server like Unicorn. On GitLab.com, we saw a 40% reduction in memory consumption by using Puma.
diff --git a/data/removals/14_0/removal_ci_project_config_path.yml b/data/removals/14_0/removal_ci_project_config_path.yml
new file mode 100644
index 00000000000..8e90c83c7c4
--- /dev/null
+++ b/data/removals/14_0/removal_ci_project_config_path.yml
@@ -0,0 +1,11 @@
+- name: "`CI_PROJECT_CONFIG_PATH` variable has been removed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: stkerr
+  body: |
+    The `CI_PROJECT_CONFIG_PATH` [predefined project variable](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html)
+    has been removed in favor of `CI_CONFIG_PATH`, which is functionally the same.
+
+    If you are using `CI_PROJECT_CONFIG_PATH` in your pipeline configurations,
+    please update them to use `CI_CONFIG_PATH` instead.
+
diff --git a/data/removals/14_0/removal_enablement_helm2.yml b/data/removals/14_0/removal_enablement_helm2.yml
new file mode 100644
index 00000000000..323b22fd3b4
--- /dev/null
+++ b/data/removals/14_0/removal_enablement_helm2.yml
@@ -0,0 +1,8 @@
+- name: "Helm v2 support"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: joshlambert
+  body: |
+    Helm v2 was [officially deprecated](https://helm.sh/blog/helm-v2-deprecation-timeline/) in November of 2020, with the `stable` repository being [de-listed from the Helm Hub](https://about.gitlab.com/blog/2020/11/09/ensure-auto-devops-work-after-helm-stable-repo/) shortly thereafter. With the release of GitLab 14.0, which will include the 5.0 release of the [GitLab Helm chart](https://docs.gitlab.com/charts/), Helm v2 will no longer be supported.
+
+    Users of the chart should [upgrade to Helm v3](https://helm.sh/docs/topics/v2_v3_migration/) to deploy GitLab 14.0 and later.
diff --git a/data/removals/14_0/removal_enablement_opensuse_15_1.yml b/data/removals/14_0/removal_enablement_opensuse_15_1.yml
new file mode 100644
index 00000000000..cff442d7b92
--- /dev/null
+++ b/data/removals/14_0/removal_enablement_opensuse_15_1.yml
@@ -0,0 +1,6 @@
+- name: "OpenSUSE Leap 15.1"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: dorrino
+  body: |
+    Support for [OpenSUSE Leap 15.1 is being deprecated](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/5135). Support for 15.1 will be dropped in 14.0. We are now providing support for openSUSE Leap 15.2 packages.
diff --git a/data/removals/14_0/removal_enablement_pg11.yml b/data/removals/14_0/removal_enablement_pg11.yml
new file mode 100644
index 00000000000..c7b9f8b528b
--- /dev/null
+++ b/data/removals/14_0/removal_enablement_pg11.yml
@@ -0,0 +1,10 @@
+- name: "PostgreSQL 11 support"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: joshlambert
+  body: |
+    PostgreSQL 12 will be the minimum required version in GitLab 14.0. It offers [significant improvements](https://www.postgresql.org/about/news/postgresql-12-released-1976/) to indexing, partitioning, and general performance benefits.
+
+    Starting in GitLab 13.7, all new installations default to version 12. From GitLab 13.8, single-node instances are automatically upgraded as well. If you aren't ready to upgrade, you can [opt out of automatic upgrades](https://docs.gitlab.com/omnibus/settings/database.html#opt-out-of-automatic-postgresql-upgrades).
+
+
diff --git a/data/removals/14_0/removal_enablement_ubuntu_16.yml b/data/removals/14_0/removal_enablement_ubuntu_16.yml
new file mode 100644
index 00000000000..65457db8c68
--- /dev/null
+++ b/data/removals/14_0/removal_enablement_ubuntu_16.yml
@@ -0,0 +1,11 @@
+- name: "Ubuntu 16.04 support"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: joshlambert
+  body: |
+    Ubuntu 16.04 [reached end-of-life in April 2021](https://ubuntu.com/about/release-cycle), and no longer receives maintenance updates. We strongly recommend users to upgrade to a newer release, such as 20.04.
+
+    GitLab 13.12 will be the last release with Ubuntu 16.04 support.
+
+
+
diff --git a/data/removals/14_0/removal_repost_static_analysis_notices.yml b/data/removals/14_0/removal_repost_static_analysis_notices.yml
new file mode 100644
index 00000000000..1105f21e3fd
--- /dev/null
+++ b/data/removals/14_0/removal_repost_static_analysis_notices.yml
@@ -0,0 +1,39 @@
+- name: "Migrate from `SAST_DEFAULT_ANALYZERS` to `SAST_EXCLUDED_ANALYZERS`"
+  reporter: tmccaslin
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/229974'
+  body: |
+    Until GitLab 13.9, if you wanted to avoid running one particular GitLab SAST analyzer, you needed to remove it from the [long string of analyzers in the `SAST.gitlab-ci.yml` file](https://gitlab.com/gitlab-org/gitlab/-/blob/390afc431e7ce1ac253b35beb39f19e49c746bff/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L12) and use that to set the [`SAST_DEFAULT_ANALYZERS`](https://docs.gitlab.com/ee/user/application_security/sast/#docker-images) variable in your project's CI file. If you did this, it would exclude you from future new analyzers because this string hard codes the list of analyzers to execute. We avoid this problem by inverting this variable's logic to exclude, rather than choose default analyzers.
+    Beginning with 13.9, [we migrated](https://gitlab.com/gitlab-org/gitlab/-/blob/14fed7a33bfdbd4663d8928e46002a5ef3e3282c/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml#L13) to `SAST_EXCLUDED_ANALYZERS` in our `SAST.gitlab-ci.yml` file. We encourage anyone who uses a [customized SAST configuration](https://docs.gitlab.com/ee/user/application_security/sast/#customizing-the-sast-settings) in their project CI file to migrate to this new variable. If you have not overridden `SAST_DEFAULT_ANALYZERS`, no action is needed. The CI/CD variable `SAST_DEFAULT_ANALYZERS` has been removed in GitLab 14.0, which released on June 22, 2021.
+
+- name: "Remove `secret_detection_default_branch` job"
+  reporter: tmccaslin
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/297269'
+  body: |
+    To ensure Secret Detection was scanning both default branches and feature branches, we introduced two separate secret detection CI jobs (`secret_detection_default_branch` and `secret_detection`) in our managed [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Secret-Detection.gitlab-ci.yml) template. These two CI jobs created confusion and complexity in the CI rules logic. This deprecation moves the `rule` logic into the `script` section, which then determines how the `secret_detection` job is run (historic, on a branch, commits, etc).
+    If you override or maintain custom versions of `SAST.gitlab-ci.yml` or `Secret-Detection.gitlab-ci.yml`, you must update your CI templates. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/secret_detection/#custom-settings-example) to future-proof your CI templates. GitLab 14.0 no longer supports the old `secret_detection_default_branch` job.
+
+- name: "Remove SAST analyzer `SAST_GOSEC_CONFIG` variable in favor of
+    custom rulesets"
+  reporter: tmccaslin
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/301215'
+  body: |
+    With the release of [SAST Custom Rulesets](https://docs.gitlab.com/ee/user/application_security/sast/#customize-rulesets) in GitLab 13.5 we allow greater flexibility in configuration options for our Go analyzer (GoSec). As a result we no longer plan to support our less flexible [`SAST_GOSEC_CONFIG`](https://docs.gitlab.com/ee/user/application_security/sast/#analyzer-settings) analyzer setting. This variable was deprecated in GitLab 13.10.
+    GitLab 14.0 removes the old `SAST_GOSEC_CONFIG variable`. If you use or override `SAST_GOSEC_CONFIG` in your CI file, update your SAST CI configuration or pin to an older version of the GoSec analyzer. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/sast/#overriding-sast-jobs) to future-proof your CI templates.
+
+- name: "Removed Global `SAST_ANALYZER_IMAGE_TAG` in SAST CI template"
+  reporter: tmccaslin
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/301216'
+  body: |
+    With the maturity of GitLab Secure scanning tools, we've needed to add more granularity to our release process. Previously, GitLab shared a major version number for [all analyzers and tools](https://docs.gitlab.com/ee/user/application_security/sast/#supported-languages-and-frameworks). This requires all tools to share a major version, and prevents the use of [semantic version numbering](https://semver.org/). In GitLab 14.0, SAST removes the `SAST_ANALYZER_IMAGE_TAG` global variable in our [managed `SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST.gitlab-ci.yml) CI template, in favor of the analyzer job variable setting the `major.minor` tag in the SAST vendored template.
+
+    Each analyzer job now has a scoped `SAST_ANALYZER_IMAGE_TAG` variable, which will be actively managed by GitLab and set to the `major` tag for the respective analyzer. To pin to a specific version, [change the variable value to the specific version tag](https://docs.gitlab.com/ee/user/application_security/sast/#pinning-to-minor-image-version).
+    If you override or maintain custom versions of `SAST.gitlab-ci.yml`, update your CI templates to stop referencing the global `SAST_ANALYZER_IMAGE_TAG`, and move it to a scoped analyzer job tag. We strongly encourage [inheriting and overriding our managed CI templates](https://docs.gitlab.com/ee/user/application_security/sast/#overriding-sast-jobs) to future-proof your CI templates. This change allows you to more granularly control future analyzer updates with a pinned `major.minor` version.
+    This deprecation and removal changes our [previously announced plan](https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#pin-static-analysis-analyzers-and-tools-to-minor-versions) to pin the Static Analysis tools.
diff --git a/data/removals/14_0/removal_runner_25555.yml b/data/removals/14_0/removal_runner_25555.yml
new file mode 100644
index 00000000000..f317eaab846
--- /dev/null
+++ b/data/removals/14_0/removal_runner_25555.yml
@@ -0,0 +1,7 @@
+- name: "Remove off peak time mode configuration for Docker Machine autoscaling"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/5069), we introduced new timing options for the GitLab Docker Machine executor. In GitLab Runner 14.0, we have removed the old configuration option, [off peak time mode](https://docs.gitlab.com/runner/configuration/autoscale.html#off-peak-time-mode-configuration-deprecated).
+
diff --git a/data/removals/14_0/removal_runner_26036.yml b/data/removals/14_0/removal_runner_26036.yml
new file mode 100644
index 00000000000..564143fda82
--- /dev/null
+++ b/data/removals/14_0/removal_runner_26036.yml
@@ -0,0 +1,6 @@
+- name: "Remove Ubuntu 19.10 (Eoan Ermine) package"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitLab Runner 14.0, Ubuntu 19.10 (Eoan Ermine) is no longer available from our package distribution. Refer to [issue #26036](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26036) for details.
diff --git a/data/removals/14_0/removal_runner_26419.yml b/data/removals/14_0/removal_runner_26419.yml
new file mode 100644
index 00000000000..8b0f3846c7a
--- /dev/null
+++ b/data/removals/14_0/removal_runner_26419.yml
@@ -0,0 +1,6 @@
+- name: "Make `pwsh` the default shell for newly-registered Windows Runners"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor. In 14.0, PowerShell Core, `pwsh` is now the default shell for newly-registered Windows runners. Windows `CMD` will still be available as a shell option for Windows runners. Refer to [issue #26419](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26419) for details.
diff --git a/data/removals/14_0/removal_runner_4845.yml b/data/removals/14_0/removal_runner_4845.yml
new file mode 100644
index 00000000000..92e4e0172f2
--- /dev/null
+++ b/data/removals/14_0/removal_runner_4845.yml
@@ -0,0 +1,6 @@
+- name: "GitLab Runner installation to ignore the `skel` directory"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In GitLab Runner 14.0, the installation process will ignore the `skel` directory by default when creating the user home directory. Refer to [issue #4845](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4845) for details.
diff --git a/data/removals/14_0/removal_runner_6413.yml b/data/removals/14_0/removal_runner_6413.yml
new file mode 100644
index 00000000000..f08b1091cca
--- /dev/null
+++ b/data/removals/14_0/removal_runner_6413.yml
@@ -0,0 +1,6 @@
+- name: "Remove `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL` feature flag"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitlab-131-and-later), [issue #3376](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3376), we introduced `sigterm` and then `sigkill` to a process in the Shell executor. We also introduced a new feature flag, `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL`, so you can use the previous process termination sequence. In GitLab Runner 14.0, [issue #6413](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6413), the feature flag has been removed.
diff --git a/data/removals/14_0/removals-14-testing-team.yml b/data/removals/14_0/removals-14-testing-team.yml
new file mode 100644
index 00000000000..d76de564cdd
--- /dev/null
+++ b/data/removals/14_0/removals-14-testing-team.yml
@@ -0,0 +1,26 @@
+- name: "Default Browser Performance testing job renamed in GitLab 14.0"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: jheimbuck_gl
+  body: |
+    Browser Performance Testing has run in a job named `performance` by default. With the introduction of [Load Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/load_performance_testing.html) in GitLab 13.2, this naming could be confusing. To make it clear which job is running [Browser Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html), the default job name is changed from `performance` to `browser_performance` in the template in GitLab 14.0.
+
+    Relevant Issue: [Rename default Browser Performance Testing job](https://gitlab.com/gitlab-org/gitlab/-/issues/225914)
+- name: "Code Quality RuboCop support changed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: jheimbuck_gl
+  body: |
+    By default, the Code Quality feature has not provided support for Ruby 2.6+ if you're using the Code Quality template. To better support the latest versions of Ruby, the default RuboCop version is updated to add support for Ruby 2.4 through 3.0. As a result, support for Ruby 2.1, 2.2, and 2.3 is removed. You can re-enable support for older versions by [customizing your configuration](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#rubocop-errors).
+
+    Relevant Issue: [Default `codeclimate-rubocop` engine does not support Ruby 2.6+](https://gitlab.com/gitlab-org/ci-cd/codequality/-/issues/28)
+- name: "Ruby version changed in `Ruby.gitlab-ci.yml`"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: jheimbuck_gl
+  body: |
+    By default, the `Ruby.gitlab-ci.yml` file has included Ruby 2.5.
+
+    To better support the latest versions of Ruby, the template is changed to use `ruby:latest`, which is currently 3.0. To better understand the changes in Ruby 3.0, please reference the [Ruby-lang.org release announcement](https://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released/).
+
+    Relevant Issue: [Updates Ruby version 2.5 to 3.0](https://gitlab.com/gitlab-org/gitlab/-/issues/329160)
diff --git a/data/removals/14_0/removals_runner_26651.yml b/data/removals/14_0/removals_runner_26651.yml
new file mode 100644
index 00000000000..a22f8dfc9ac
--- /dev/null
+++ b/data/removals/14_0/removals_runner_26651.yml
@@ -0,0 +1,6 @@
+- name: "Remove `/usr/lib/gitlab-runner` symlink from package"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab-runner` to `/usr/bin/gitlab-runner`. In 14.0, the symlink has been removed and the runner is now installed in `/usr/bin/gitlab-runner`. Refer to [issue #26651](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26651) for details.
diff --git a/data/removals/14_0/removals_runner_26679.yml b/data/removals/14_0/removals_runner_26679.yml
new file mode 100644
index 00000000000..816bd8f37d5
--- /dev/null
+++ b/data/removals/14_0/removals_runner_26679.yml
@@ -0,0 +1,6 @@
+- name: "Remove `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag. Refer to issue [#26679](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26679) for details.
diff --git a/data/removals/14_0/removals_runner_26900.yml b/data/removals/14_0/removals_runner_26900.yml
new file mode 100644
index 00000000000..bdba368eee8
--- /dev/null
+++ b/data/removals/14_0/removals_runner_26900.yml
@@ -0,0 +1,6 @@
+- name: "Remove success and failure for finished build metric conversion"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In GitLab Runner 13.5, we introduced `failed` and `success` states for a job. To support Prometheus rules, we chose to convert `success/failure` to `finished` for the metric. In 14.0, the conversion has now been removed. Refer to [issue #26900](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26900) for details.
diff --git a/data/removals/14_0/removals_runner_27175.yml b/data/removals/14_0/removals_runner_27175.yml
new file mode 100644
index 00000000000..33629084073
--- /dev/null
+++ b/data/removals/14_0/removals_runner_27175.yml
@@ -0,0 +1,6 @@
+- name: "Remove `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag. Refer to [issue #27175](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27175) for details.
diff --git a/data/removals/14_0/removals_runner_27218.yml b/data/removals/14_0/removals_runner_27218.yml
new file mode 100644
index 00000000000..fb1e27c3f91
--- /dev/null
+++ b/data/removals/14_0/removals_runner_27218.yml
@@ -0,0 +1,6 @@
+- name: "GitLab Runner helper image in GitLab.com Container Registry"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image) from the GitLab Container Registry instead of Docker Hub. Refer to [issue #27218](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27218) for details.
diff --git a/data/removals/14_0/removals_runner_27551.yml b/data/removals/14_0/removals_runner_27551.yml
new file mode 100644
index 00000000000..6f4ee52749c
--- /dev/null
+++ b/data/removals/14_0/removals_runner_27551.yml
@@ -0,0 +1,6 @@
+- name: "Remove support for Windows Server 1903 image"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In 14.0, we have removed Windows Server 1903. Microsoft ended support for this version on 2020-08-12. Refer to [issue #27551](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27551) for details.
diff --git a/data/removals/14_0/removals_runner_27899.yml b/data/removals/14_0/removals_runner_27899.yml
new file mode 100644
index 00000000000..226520abda4
--- /dev/null
+++ b/data/removals/14_0/removals_runner_27899.yml
@@ -0,0 +1,6 @@
+- name: "Remove support for Windows Server 1909 image"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: deastman
+  body: |
+    In 14.0, we have removed Windows Server 1909. Microsoft ended support for this version on 2021-05-11. Refer to [issue #27899](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27899) for details.
diff --git a/data/removals/14_0/remove-sql-elector.yml b/data/removals/14_0/remove-sql-elector.yml
new file mode 100644
index 00000000000..d35fac0786c
--- /dev/null
+++ b/data/removals/14_0/remove-sql-elector.yml
@@ -0,0 +1,9 @@
+- name: "Gitaly Cluster SQL primary elector has been removed"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: mjwood
+  body: |
+    Now that Praefect supports a [primary election strategy](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#repository-specific-primary-nodes) for each repository, we have removed the `sql` election strategy.
+    The `per_repository` election strategy is the new default, which is automatically used if no election strategy was specified.
+
+    If you had configured the `sql` election strategy, you must follow the [migration instructions](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#migrate-to-repository-specific-primary-gitaly-nodes) before upgrading to 14.0.
diff --git a/data/removals/14_0/remove_dast_env_variables.yml b/data/removals/14_0/remove_dast_env_variables.yml
new file mode 100644
index 00000000000..f2bbe748af5
--- /dev/null
+++ b/data/removals/14_0/remove_dast_env_variables.yml
@@ -0,0 +1,15 @@
+- name: "DAST environment variable renaming and removal"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: derekferguson
+  body: |
+    GitLab 13.8 renamed multiple environment variables to support their broader usage in different workflows. In GitLab 14.0, the old variables have been permanently removed and will no longer work. Any configurations using these variables must be updated to the new variable names. Any scans using these variables in GitLab 14.0 and later will fail to be configured correctly. These variables are:
+
+    - `DAST_AUTH_EXCLUDE_URLS` becomes `DAST_EXCLUDE_URLS`.
+    - `AUTH_EXCLUDE_URLS` becomes `DAST_EXCLUDE_URLS`.
+    - `AUTH_USERNAME` becomes `DAST_USERNAME`.
+    - `AUTH_PASSWORD` becomes `DAST_PASSWORD`.
+    - `AUTH_USERNAME_FIELD` becomes `DAST_USERNAME_FIELD`.
+    - `AUTH_PASSWORD_FIELD` becomes `DAST_PASSWORD_FIELD`.
+    - `DAST_ZAP_USE_AJAX_SPIDER` will now be `DAST_USE_AJAX_SPIDER`.
+    - `DAST_FULL_SCAN_DOMAIN_VALIDATION_REQUIRED` will be removed, since the feature is being removed.
diff --git a/data/removals/14_0/remove_dast_legacy_domain_validation.yml b/data/removals/14_0/remove_dast_legacy_domain_validation.yml
new file mode 100644
index 00000000000..61fb9002880
--- /dev/null
+++ b/data/removals/14_0/remove_dast_legacy_domain_validation.yml
@@ -0,0 +1,8 @@
+- name: "Remove legacy DAST domain validation"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: derekferguson
+  body: |
+    The legacy method of DAST Domain Validation for CI/CD scans was deprecated in GitLab 13.8, and is removed in GitLab 14.0. This method of domain validation only disallows scans if the `DAST_FULL_SCAN_DOMAIN_VALIDATION_REQUIRED` environment variable is set to `true` in the `gitlab-ci.yml` file, and a `Gitlab-DAST-Permission` header on the site is not set to `allow`. This two-step method required users to opt in to using the variable before they could opt out from using the header.
+
+    For more information, see the [removal issue](https://gitlab.com/gitlab-org/gitlab/-/issues/293595).
diff --git a/data/removals/14_0/remove_dast_legacy_report_fields.yml b/data/removals/14_0/remove_dast_legacy_report_fields.yml
new file mode 100644
index 00000000000..ec98b173a24
--- /dev/null
+++ b/data/removals/14_0/remove_dast_legacy_report_fields.yml
@@ -0,0 +1,8 @@
+- name: "Removal of legacy fields from DAST report"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: derekferguson
+  body: |
+    As a part of the migration to a common report format for all of the Secure scanners in GitLab, DAST is making changes to the DAST JSON report. Certain legacy fields were deprecated in 13.8 and have been completely removed in 14.0. These fields are `@generated`, `@version`, `site`, and `spider`. This should not affect any normal DAST operation, but does affect users who consume the JSON report in an automated way and use these fields. Anyone affected by these changes, and needs these fields for business reasons, is encouraged to open a new GitLab issue and explain the need.
+
+    For more information, see [the removal issue](https://gitlab.com/gitlab-org/gitlab/-/issues/33915).
diff --git a/data/removals/14_0/remove_dast_spider_host_reset.yml b/data/removals/14_0/remove_dast_spider_host_reset.yml
new file mode 100644
index 00000000000..de334618b88
--- /dev/null
+++ b/data/removals/14_0/remove_dast_spider_host_reset.yml
@@ -0,0 +1,6 @@
+- name: "Default DAST spider begins crawling at target URL"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: derekferguson
+  body: |
+    In GitLab 14.0, DAST has removed the current method of resetting the scan to the hostname when starting to spider. Prior to GitLab 14.0, the spider would not begin at the specified target path for the URL but would instead reset the URL to begin crawling at the host root. GitLab 14.0 changes the default for the new variable `DAST_SPIDER_START_AT_HOST` to `false` to better support users' intention of beginning spidering and scanning at the specified target URL, rather than the host root URL. This change has an added benefit: scans can take less time, if the specified path does not contain links to the entire site. This enables easier scanning of smaller sections of an application, rather than crawling the entire app during every scan.
diff --git a/data/removals/14_0/remove_dast_template_stages.yml b/data/removals/14_0/remove_dast_template_stages.yml
new file mode 100644
index 00000000000..0f72091735d
--- /dev/null
+++ b/data/removals/14_0/remove_dast_template_stages.yml
@@ -0,0 +1,6 @@
+- name: "Remove DAST default template stages"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: derekferguson
+  body: |
+    In GitLab 14.0, we've removed the stages defined in the current `DAST.gitlab-ci.yml` template to avoid the situation where the template overrides manual changes made by DAST users. We're making this change in response to customer issues where the stages in the template cause problems when used with customized DAST configurations. Because of this removal, `gitlab-ci.yml` configurations that do not specify a `dast` stage must be updated to include this stage.
diff --git a/data/removals/14_0/remove_optimize_api.yml b/data/removals/14_0/remove_optimize_api.yml
new file mode 100644
index 00000000000..5df120858c6
--- /dev/null
+++ b/data/removals/14_0/remove_optimize_api.yml
@@ -0,0 +1,6 @@
+- name: "Segments removed from DevOps Adoption API"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: ljlane
+  body: |
+    The first release of the DevOps Adoption report had a concept of **Segments**. Segments were [quickly removed from the report](https://gitlab.com/groups/gitlab-org/-/epics/5251) because they introduced an additional layer of complexity on top of **Groups** and **Projects**. Subsequent iterations of the DevOps Adoption report focus on comparing adoption across groups rather than segments. GitLab 14.0 removes all references to **Segments** [from the GraphQL API](https://gitlab.com/gitlab-org/gitlab/-/issues/324414) and replaces them with **Enabled groups**.
diff --git a/data/removals/14_0/remove_terraform_template.yml b/data/removals/14_0/remove_terraform_template.yml
new file mode 100644
index 00000000000..bc3b529f630
--- /dev/null
+++ b/data/removals/14_0/remove_terraform_template.yml
@@ -0,0 +1,9 @@
+- name: "Breaking changes to Terraform CI template"
+  reporter: nagyv-gitlab
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/328500'
+  body: |
+    GitLab 14.0 renews the Terraform CI template to the latest version. The new template is set up for the GitLab Managed Terraform state, with a dependency on the GitLab `terraform-images` image, to provide a good user experience around GitLab's Infrastructure-as-Code features.
+
+    The current stable and latest templates are not compatible, and the current latest template becomes the stable template beginning with GitLab 14.0, your Terraform pipeline might encounter an unexpected failure if you run a custom `init` job.
diff --git a/data/removals/14_0/verify-ci-removal-parametertrace.yml b/data/removals/14_0/verify-ci-removal-parametertrace.yml
new file mode 100644
index 00000000000..c37497c1a35
--- /dev/null
+++ b/data/removals/14_0/verify-ci-removal-parametertrace.yml
@@ -0,0 +1,8 @@
+- name: "Removal of deprecated `trace` parameter from `jobs` API endpoint"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: jreporter
+  body: |
+   GitLab Runner was updated in GitLab 13.4 to internally stop passing the `trace` parameter to the `/api/jobs/:id` endpoint. GitLab 14.0 deprecates the `trace` parameter entirely for all other requests of this endpoint. Make sure your [GitLab Runner version matches your GitLab version](https://docs.gitlab.com/runner/#gitlab-runner-versions) to ensure consistent behavior.
+
+
diff --git a/data/removals/14_0/verify-ci-removalpipelineservice.yml b/data/removals/14_0/verify-ci-removalpipelineservice.yml
new file mode 100644
index 00000000000..f3583bd0498
--- /dev/null
+++ b/data/removals/14_0/verify-ci-removalpipelineservice.yml
@@ -0,0 +1,6 @@
+- name: "External Pipeline Validation Service Code Changes"
+  removal_date: "2021-06-22"
+  removal_milestone: "14.0"
+  reporter: jreporter
+  body: |
+    For self-managed instances using the experimental [external pipeline validation service](https://docs.gitlab.com/ee/administration/external_pipeline_validation.html), the range of error codes GitLab accepts will be reduced. Currently, pipelines are invalidated when the validation service returns a response code from `400` to `499`. In GitLab 14.0 and later, pipelines will be invalidated for the `406: Not Accepted` response code only.
diff --git a/data/removals/14_1/removal-memory-prometheus-options-source.yml b/data/removals/14_1/removal-memory-prometheus-options-source.yml
new file mode 100644
index 00000000000..afef081c348
--- /dev/null
+++ b/data/removals/14_1/removal-memory-prometheus-options-source.yml
@@ -0,0 +1,8 @@
+- name: "Remove support for `prometheus.listen_address` and `prometheus.enable`"
+  removal_date: July 22, 2021
+  removal_milestone: "14.1"
+  reporter: fzimmer
+  body: |
+    The support for `prometheus.listen_address` and `prometheus.enable` has been removed from `gitlab.yml`. Use `prometheus.enabled` and `prometheus.server_address` to set up Prometheus server that GitLab instance connects to. Refer to [our documentation](https://docs.gitlab.com/ee/install/installation.html#prometheus-server-setup) for details.
+
+    This only affects new installations from source where users might use the old configurations.
diff --git a/data/removals/14_1/removal-outdated-browser-support.yml b/data/removals/14_1/removal-outdated-browser-support.yml
new file mode 100644
index 00000000000..1019b8fe2f3
--- /dev/null
+++ b/data/removals/14_1/removal-outdated-browser-support.yml
@@ -0,0 +1,20 @@
+- name: "Remove support for older browsers"
+  removal_date: July 22, 2021
+  removal_milestone: "14.1"
+  reporter: leipert
+  body: |
+    In GitLab 14.1, we are cleaning up and [removing old code](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63994) that was specific for browsers that we no longer support. This has no impact on users when one of our [supported web browsers](https://docs.gitlab.com/ee/install/requirements.html#supported-web-browsers) is used.
+
+    Most notably, support for the following browsers has been removed:
+
+    - Apple Safari 13 and older.
+    - Mozilla Firefox 68.
+    - Pre-Chromium Microsoft Edge.
+
+    The minimum supported browser versions are:
+
+    - Apple Safari 13.1.
+    - Mozilla Firefox 78.
+    - Google Chrome 84.
+    - Chromium 84.
+    - Microsoft Edge 84.
diff --git a/data/removals/14_2/removal-verify-build-log.yml b/data/removals/14_2/removal-verify-build-log.yml
new file mode 100644
index 00000000000..6b4e37c7c6e
--- /dev/null
+++ b/data/removals/14_2/removal-verify-build-log.yml
@@ -0,0 +1,7 @@
+- name: "Max job log file size of 100 MB"
+  removal_date: August 22, 2021 # day the removal was released
+  removal_milestone: "14.2"
+  reporter: jreporter # GitLab username of the person reporting the removal
+  body: |
+    GitLab values efficiency for all users in our wider community of contributors, so we're always working hard to make sure the application performs at a high level with a lovable UX.
+      In GitLab 14.2, we have introduced a [job log file size limit](https://docs.gitlab.com/ee/administration/instance_limits.html#maximum-file-size-for-job-logs), set to 100 megabytes by default. Administrators of self-managed GitLab instances can customize this to any value. All jobs that exceed this limit are dropped and marked as failed, helping prevent performance impacts or over-use of resources. This ensures that everyone using GitLab has the best possible experience.
diff --git a/data/removals/14_3/removal-limit-tags-to-50.yml b/data/removals/14_3/removal-limit-tags-to-50.yml
new file mode 100644
index 00000000000..db624656e6e
--- /dev/null
+++ b/data/removals/14_3/removal-limit-tags-to-50.yml
@@ -0,0 +1,6 @@
+- name: "Introduced limit of 50 tags for jobs"
+  removal_date: September 22nd, 2021 
+  removal_milestone: "14.3"
+  reporter: jreporter 
+  body: |
+    GitLab values efficiency and is prioritizing reliability for [GitLab.com in FY22](https://about.gitlab.com/direction/#gitlab-hosted-first). In 14.3, GitLab CI/CD jobs must have less than 50 [tags](https://docs.gitlab.com/ee/ci/yaml/index.html#tags). If a pipeline contains a job with 50 or more tags, you will receive an error and the pipeline will not be created.
diff --git a/data/removals/14_3/removal-verify-pe-pipelinefindername.yml b/data/removals/14_3/removal-verify-pe-pipelinefindername.yml
new file mode 100644
index 00000000000..979317f99df
--- /dev/null
+++ b/data/removals/14_3/removal-verify-pe-pipelinefindername.yml
@@ -0,0 +1,6 @@
+- name: "List project pipelines API endpoint removes `name` support in 14.3"
+  removal_date: September 22, 2021 # day the removal was released
+  removal_milestone: "14.3"
+  reporter: jreporter # GitLab username of the person reporting the removal
+  body: |
+    In GitLab 14.3, we will remove the ability to filter by `name` in the [list project pipelines API endpoint](https://docs.gitlab.com/ee/api/pipelines.html#list-project-pipelines) to improve performance. If you currently use this parameter with this endpoint, you must switch to `username`.
diff --git a/data/removals/14_3/removal_legacy_storage_setting.yml b/data/removals/14_3/removal_legacy_storage_setting.yml
new file mode 100644
index 00000000000..b1f98e47554
--- /dev/null
+++ b/data/removals/14_3/removal_legacy_storage_setting.yml
@@ -0,0 +1,8 @@
+- name: Use of legacy storage setting
+  removal_date: September 22nd, 2021 # day the removal was released
+  removal_milestone: "14.3"
+  reporter: dorrino # GitLab username of the person reporting the removal
+  body: |  # example (supports markdown)
+    The support for [`gitlab_pages['use_legacy_storage']` setting](https://docs.gitlab.com/ee/administration/pages/index.html#domain-source-configuration-before-140) in Omnibus installations has been removed.
+    
+    In 14.0 we removed [`domain_config_source`](https://docs.gitlab.com/ee/administration/pages/index.html#domain-source-configuration-before-140) which had been previously deprecated, and allowed users to specify disk storage. In 14.0 we added `use_legacy_storage` as a **temporary** flag to unblock upgrades, and allow us to debug issues with our users and it was deprecated and communicated for removal in 14.3.
diff --git a/data/removals/templates/_removal_template.md.erb b/data/removals/templates/_removal_template.md.erb
new file mode 100644
index 00000000000..e227c6aa6e6
--- /dev/null
+++ b/data/removals/templates/_removal_template.md.erb
@@ -0,0 +1,46 @@
+---
+stage: none
+group: none
+info: "See the Technical Writers assigned to Development Guidelines: https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments-to-development-guidelines"
+---
+
+# Removals by milestone
+
+<!-- vale off -->
+
+<!--
+DO NOT EDIT THIS PAGE DIRECTLY
+
+This page is automatically generated from the YAML files in `/data/removals` by the rake task
+located at `lib/tasks/gitlab/docs/compile_removals.rake`.
+
+For removal authors (usually Product Managers and Engineering Managers):
+
+- To add a removal, use the example.yml file in `/data/removals/templates` as a template.
+- For more information about authoring removals, check the the removal item guidance:
+  https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-removal-entry
+
+For removal reviewers (Technical Writers only):
+
+- To update the removal doc, run: `bin/rake gitlab:docs:compile_removals`
+- To verify the removals doc is up to date, run: `bin/rake gitlab:docs:check_removals`
+- For more information about updating the removal doc, see the removal doc update guidance:
+  https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-removals-doc
+-->
+<% if milestones.any? -%>
+  <%- milestones.each do |milestone| %>
+## <%= milestone %>
+    <%- entries.select{|entry| entry["removal_milestone"] == milestone}.each do |removal| %>
+### <%= removal["name"]%>
+<% if removal["breaking_change"] -%>
+WARNING:
+This feature was changed or removed in <%= removal["removal_milestone"]%>
+as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
+Before updating GitLab, review the details carefully to determine if you need to make any
+changes to your code, settings, or workflow.
+
+<%= removal["body"] -%><% else %>
+<%= removal["body"] -%><% end %><%- end -%><%- end -%>
+<%- else -%>
+Features scheduled for removal will be listed here, sorted by GitLab milestone.
+<% end -%>
diff --git a/data/removals/templates/example.yml b/data/removals/templates/example.yml
new file mode 100644
index 00000000000..78cbec2be28
--- /dev/null
+++ b/data/removals/templates/example.yml
@@ -0,0 +1,32 @@
+# This is a template for a feature removal
+# Generally, a feature or configuration should be removed in a major release.
+# It should be announced at least 2 releases prior to being removed.
+#
+# Below is an example of a removal.
+#
+# For more information please refer to the handbook documentation here:
+# https://about.gitlab.com/handbook/marketing/blog/release-posts/#removals
+#
+# Please delete this line and above before submitting your merge request.
+
+- name: "Announcement headline" # The headline announcing the removal. i.e. "`CI_PROJECT_CONFIG_PATH` removed in Gitlab 14.0"
+  announcement_milestone: "XX.YY" # The milestone when this feature was deprecated.
+  announcement_date: "YYYY-MM-DD" # The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post.
+  removal_milestone: "XX.YY" # The milestone when this feature is being removed.
+  removal_date: "YYYY-MM-DD" # This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed.
+  breaking_change: false # Change to true if this removal is a breaking change.
+  body: | # 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.
+
+    When ready, assign to your tech writer for review. When ready, they will run `bin/rake gitlab:docs:compile_removals` to update the removals doc, then merge.
+
+    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
diff --git a/data/whats_new/202010230001_13_05.yml b/data/whats_new/202010230001_13_05.yml
index d7dc43d0294..9166d148b37 100644
--- a/data/whats_new/202010230001_13_05.yml
+++ b/data/whats_new/202010230001_13_05.yml
@@ -5,7 +5,7 @@
 
     Despite this popularity, teams have struggled with the limitation that wikis were only available at the project level. Teams working on multiple projects needed to create separate wikis for each repository, leading to a fragmented experience.
 
-    In Gitlab 13.5, we are so excited to bring you group wikis! With [680 upvotes](https://gitlab.com/gitlab-org/gitlab/-/issues/13195) this was the most upvoted feature in the entire GitLab backlog. While highly requested, making a large project-only feature like wikis available at the group level has been a non-trivial operation.
+    In GitLab 13.5, we are so excited to bring you group wikis! With [680 upvotes](https://gitlab.com/gitlab-org/gitlab/-/issues/13195) this was the most upvoted feature in the entire GitLab backlog. While highly requested, making a large project-only feature like wikis available at the group level has been a non-trivial operation.
 
     We know a lot of folks have been looking forward to this feature and shared their input pre-release. We hope all of you will continue to weigh in now that group wikis are available and we’ve opened up a [dedicated issue](https://gitlab.com/gitlab-org/gitlab/-/issues/267593) for your feedback.
   stage: Create
diff --git a/data/whats_new/2021102000001_14_04.yml b/data/whats_new/2021102000001_14_04.yml
index 6157b243cbc..146544f6f6b 100644
--- a/data/whats_new/2021102000001_14_04.yml
+++ b/data/whats_new/2021102000001_14_04.yml
@@ -48,7 +48,7 @@
   release: 14.4
 - title: Integrated error tracking inside GitLab without a Sentry instance
   body: |
-     Prior to GitLab 14.4, you could integrate with Sentry Error Tracking by supplying an endpoint for a Sentry backend (either self-deployed or in their cloud service). With Gitlab 14.4, you now have access to a Sentry-compatible backend built into your GitLab instance. This allows you to quickly instrument your apps so your errors show up directly in GitLab without the need for a separate Sentry instance.
+     Prior to GitLab 14.4, you could integrate with Sentry Error Tracking by supplying an endpoint for a Sentry backend (either self-deployed or in their cloud service). With GitLab 14.4, you now have access to a Sentry-compatible backend built into your GitLab instance. This allows you to quickly instrument your apps so your errors show up directly in GitLab without the need for a separate Sentry instance.
   stage: Manage
   self-managed: true
   gitlab-com: true
diff --git a/data/whats_new/2021111800001_14_05.yml b/data/whats_new/2021111800001_14_05.yml
index 63b87c21ee0..c38d4cfa9fa 100644
--- a/data/whats_new/2021111800001_14_05.yml
+++ b/data/whats_new/2021111800001_14_05.yml
@@ -1,6 +1,6 @@
 - title: Introducing Infrastructure as Code (IaC) security scanning
   body: |
-    With Gitlab 14.5 we're introducing security scanning for Infrastructure as Code (IaC) configuration files. Like all our SAST scanners, we've chosen to make this capability available for all customers for free to encourage secure coding practices with the rise of IaC. The initial version of this IaC security scanner supports configuration files for Terraform, Ansible, AWS CloudFormation, and Kubernetes and is based on the open-source [Keeping Infrastructure as Code Secure (KICS) project](https://kics.io/). This new IaC scanning capability joins our [existing Kubernetes manifest SAST scanner](https://docs.gitlab.com/ee/user/application_security/sast/#enabling-kubesec-analyzer).
+    With GitLab 14.5 we're introducing security scanning for Infrastructure as Code (IaC) configuration files. Like all our SAST scanners, we've chosen to make this capability available for all customers for free to encourage secure coding practices with the rise of IaC. The initial version of this IaC security scanner supports configuration files for Terraform, Ansible, AWS CloudFormation, and Kubernetes and is based on the open-source [Keeping Infrastructure as Code Secure (KICS) project](https://kics.io/). This new IaC scanning capability joins our [existing Kubernetes manifest SAST scanner](https://docs.gitlab.com/ee/user/application_security/sast/#enabling-kubesec-analyzer).
   stage: Secure
   self-managed: true
   gitlab-com: true