Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42

author: GitLab Bot <gitlab-bot@gitlab.com> 2022-03-18 23:02:30 +0300
committer: GitLab Bot <gitlab-bot@gitlab.com> 2022-03-18 23:02:30 +0300
commit: 41fe97390ceddf945f3d967b8fdb3de4c66b7dea (patch)
tree: 9c8d89a8624828992f06d892cd2f43818ff5dcc8 /data/deprecations
parent: 0804d2dc31052fb45a1efecedc8e06ce9bc32862 (diff)
80 files changed, 578 insertions, 504 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 fd5db7f8835..9e02524b022 100644
--- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml
+++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml
@@ -1,10 +1,10 @@
-- name: "NFS for Git repository storage" # The name of the feature to be deprecated
-  announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated
-  removal_milestone: "15.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
+- name: "NFS for Git repository storage"  # The name of the feature to be deprecated
+  announcement_milestone: "14.0"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-06-22"  # The date of the milestone release when this feature was first announced as deprecated
+  removal_milestone: "15.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.
+  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.
 
     Gitaly Cluster offers tremendous benefits for our customers such as:
@@ -15,9 +15,9 @@
 
     We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/index.html#migrate-to-gitaly-cluster).
 
-  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
+  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-2-deprecation-release-cli.yml b/data/deprecations/14-2-deprecation-release-cli.yml
index 809d8eb1e8b..fe53dea309a 100644
--- a/data/deprecations/14-2-deprecation-release-cli.yml
+++ b/data/deprecations/14-2-deprecation-release-cli.yml
@@ -1,14 +1,14 @@
-- 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
+- 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.
+  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
-  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
+  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-2-deprecation-task-runner.yml b/data/deprecations/14-2-deprecation-task-runner.yml
index 8162b5c4d4e..1b72330c5bd 100644
--- a/data/deprecations/14-2-deprecation-task-runner.yml
+++ b/data/deprecations/14-2-deprecation-task-runner.yml
@@ -1,17 +1,17 @@
-- name: "Rename Task Runner pod to Toolbox" # The name of the feature to be deprecated
-  announcement_milestone: "14.2" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-08-22" # The date of the milestone release when this feature was first announced as deprecated
-  removal_milestone: "14.5" # The milestone when this feature is planned to be removed
-  removal_date: "2021-11-22" # the date of the milestone release when this feature is planned to be removed
+- name: "Rename Task Runner pod to Toolbox"  # The name of the feature to be deprecated
+  announcement_milestone: "14.2"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-08-22"  # The date of the milestone release when this feature was first announced as deprecated
+  removal_milestone: "14.5"  # The milestone when this feature is planned to be removed
+  removal_date: "2021-11-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: false
-  body: | # Do not modify this line, instead modify the lines below.
+  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).
 
     This will result in the rename of the sub-chart: `gitlab/task-runner` to `gitlab/toolbox`. Resulting pods will be named along the lines of `{{ .Release.Name }}-toolbox`, which will often be `gitlab-toolbox`. They will be locatable with the label `app=toolbox`.
 
-  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
+  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-3-database-deprecate-legacy-database-conf.yml b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml
index 29e55337261..3644b681da0 100644
--- a/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml
+++ b/data/deprecations/14-3-database-deprecate-legacy-database-conf.yml
@@ -2,7 +2,7 @@
   announcement_milestone: "14.3"
   announcement_date: "2021-09-22"
   removal_milestone: "15.0"
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
   body: |
     The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
diff --git a/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml
index 17c6cbc8e7a..ba7c07eaf83 100644
--- a/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml
+++ b/data/deprecations/14-3-deprecation_omniauth-kerberos_gem.yml
@@ -4,7 +4,7 @@
   removal_milestone: "15.0"
   removal_date: "2022-05-22"
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  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.
 
     This gem has not been maintained and has very little usage. We therefore plan to remove support for this authentication method and recommend using the Kerberos [SPNEGO](https://en.wikipedia.org/wiki/SPNEGO) integration instead. You can follow the [upgrade instructions](https://docs.gitlab.com/ee/integration/kerberos.html#upgrading-from-password-based-to-ticket-based-kerberos-sign-ins) to upgrade from the `omniauth-kerberos` integration to the supported one.
@@ -14,4 +14,3 @@
   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
-
diff --git a/data/deprecations/14-3-repository-push-audit-events.yml b/data/deprecations/14-3-repository-push-audit-events.yml
index 97a7a01b593..587dc98d03c 100644
--- a/data/deprecations/14-3-repository-push-audit-events.yml
+++ b/data/deprecations/14-3-repository-push-audit-events.yml
@@ -1,10 +1,10 @@
 - 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
+  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.
+  body: |  # Do not modify this line, instead modify the lines below.
     Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#repository-push-deprecated) are now deprecated and will be removed in GitLab 15.0.
 
     These events have always been disabled by default and had to be manually enabled with a
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 698d8b0dc69..5cf9354cd05 100644
--- a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml
+++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml
@@ -2,22 +2,25 @@
   announcement_milestone: "14.5"
   announcement_date: "2021-11-15"
   removal_milestone: "15.6"
-  removal_date: "2022-11-22" # the date of the milestone release when this feature is planned to be removed
+  removal_date: "2022-11-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 planned to happen in two steps, starting with milestone 15.0 and finishing in GitLab version 15.6.
+    [The certificate-based integration with Kubernetes will be deprecated and removed](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/).
 
-    In 15.0, we plan to introduce a feature flag that will allow GitLab Self-Managed customers to keep the certificate-based integration enabled, it will be disabled by default. We plan to remove this feature flag together with the underlying code in GitLab version 15.6.
-    The certificate-based integration will continue to receive security and
-    critical fixes, and features built on the integration will continue to work with supported Kubernetes
-    versions until the final removal in 15.6.
+    If you are a self-managed customer, in GitLab 15.0, a feature flag will be introduced so you can keep
+    certificate-based integration enabled. The flag will be disabled by default.
+    The flag and the related code will be removed in GitLab 15.6.
 
-    For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend the use of the
-    [Kubernetes Agent](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab. 
-    We provide [migration plans](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html) in the documentation. 
+    Until the final removal in 15.6, features built on the integration will continue to work, and
+    GitLab will continue to fix security and critical issues.
 
-    For updates and details around this deprecation, follow this [epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8).
+    If you use GitLab.com, certificate-based integrations will cease functioning in 15.0.
+
+    For a more robust, secure, forthcoming, and reliable integration with Kubernetes, we recommend you use the
+    [agent for Kubernetes](https://docs.gitlab.com/ee/user/clusters/agent/) to connect Kubernetes clusters with GitLab.
+    See the documentation for [how to migrate](https://docs.gitlab.com/ee/user/infrastructure/clusters/migrate_to_gitlab_agent.html).
+
+    For updates and details about this deprecation, follow [this epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8).
   stage: Configure
   tiers: [Free, Silver, Gold, Core, Premium, Ultimate]
   issue_url: 'https://gitlab.com/groups/gitlab-org/configure/-/epics/8'
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 9cf806da021..9b45454fef8 100644
--- a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml
+++ b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml
@@ -1,10 +1,10 @@
 - name: "Converting an instance (shared) runner to a project (specific) runner"
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  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.
+  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
diff --git a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
index af172f47ed1..2dfc20ae14e 100644
--- a/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
+++ b/data/deprecations/14-5-deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
@@ -1,15 +1,15 @@
-- name: "`defaultMergeCommitMessageWithDescription` GraphQL API field" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+- name: "`defaultMergeCommitMessageWithDescription` GraphQL API field"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprecated and will be removed in GitLab 15.0. For projects with a commit message template set, it will ignore the template.
 # The following items are not published on the docs page, but may be used in the future.
-  stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  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
+  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-5-deprecate-opensuse-15-2.yml b/data/deprecations/14-5-deprecate-opensuse-15-2.yml
index f95a80e6eac..877fcf7e3a6 100644
--- a/data/deprecations/14-5-deprecate-opensuse-15-2.yml
+++ b/data/deprecations/14-5-deprecate-opensuse-15-2.yml
@@ -1,10 +1,10 @@
-- name: "openSUSE Leap 15.2 packages" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "14.8" # The milestone when this feature is planned to be removed
-  removal_date: "2022-02-22" # the date of the milestone release when this feature is planned to be removed
+- name: "openSUSE Leap 15.2 packages"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "14.8"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-02-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: false
-  body: | # Do not modify this line, instead modify the lines below.
+  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).
 
     Starting in 14.5 we are providing packages for openSUSE Leap 15.3, and will stop providing packages for openSUSE Leap 15.2 in the 14.8 milestone.
diff --git a/data/deprecations/14-5-deprecate-sles-12sp2.yml b/data/deprecations/14-5-deprecate-sles-12sp2.yml
index 9c6d1f6da52..69f8eb73bfd 100644
--- a/data/deprecations/14-5-deprecate-sles-12sp2.yml
+++ b/data/deprecations/14-5-deprecate-sles-12sp2.yml
@@ -1,8 +1,8 @@
-- name: "Support for SLES 12 SP2" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+- name: "Support for SLES 12 SP2"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  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.
+  body: |  # Do not modify this line, instead modify the lines below.
     Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly.
diff --git a/data/deprecations/14-5-deprecation-versions-packagetype.yml b/data/deprecations/14-5-deprecation-versions-packagetype.yml
index 92188b1b21d..da6e705b94f 100644
--- a/data/deprecations/14-5-deprecation-versions-packagetype.yml
+++ b/data/deprecations/14-5-deprecation-versions-packagetype.yml
@@ -1,10 +1,10 @@
 - name: "`Versions` on base `PackageType`"
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  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).
 
     In milestone 15.0, we will completely remove `Version` from `PackageType`.
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 2c16aca5df6..0ba7b828f8d 100644
--- a/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml
+++ b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml
@@ -1,15 +1,15 @@
-- name: "Value Stream Analytics filtering calculation change" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+- name: "Value Stream Analytics filtering calculation change"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  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]
-  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/343210' # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: "https://docs.gitlab.com/ee/user/analytics/value_stream_analytics.html#filter-value-stream-analytics-data" # (optional) This is a link to the current documentation page
-  image_url: "vsa_warning.png" # (optional) This is a link to a thumbnail image depicting the feature
+  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]
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/343210'  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: "https://docs.gitlab.com/ee/user/analytics/value_stream_analytics.html#filter-value-stream-analytics-data"  # (optional) This is a link to the current documentation page
+  image_url: "vsa_warning.png"  # (optional) This is a link to a thumbnail image depicting the feature
diff --git a/data/deprecations/14-5-disable_strict_host_key_checking.yml b/data/deprecations/14-5-disable_strict_host_key_checking.yml
index a3a6a3bf223..b2091578ff4 100644
--- a/data/deprecations/14-5-disable_strict_host_key_checking.yml
+++ b/data/deprecations/14-5-disable_strict_host_key_checking.yml
@@ -1,10 +1,10 @@
 - name: "Known host required for GitLab Runner SSH executor"
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
+  removal_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.
+  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.
 
     In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner 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 81a2d10e35b..0dbd785c1a0 100644
--- a/data/deprecations/14-5-geo-deprecate-promote-db.yml
+++ b/data/deprecations/14-5-geo-deprecate-promote-db.yml
@@ -1,14 +1,14 @@
-- name: "`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
+- name: "`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.
+  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"
   tiers: [Premium, Ultimate]
   issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/345207"
-  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
+  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-5-geo-deprecate-promote-to-primary-node.yml b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml
index bbecfcd65ec..69034bcd33d 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,14 +1,14 @@
-- name: "`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
+- name: "`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.
+  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"
   tiers: [Premium, Ultimate]
   issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/345207"
-  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
+  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-5-package-container-registry-api-group-update.yml b/data/deprecations/14-5-package-container-registry-api-group-update.yml
index 951de288d90..67e3557cae3 100644
--- a/data/deprecations/14-5-package-container-registry-api-group-update.yml
+++ b/data/deprecations/14-5-package-container-registry-api-group-update.yml
@@ -1,10 +1,10 @@
 - name: "Update to the Container Registry group-level API"
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  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.
+  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).
 
     The `GET /groups/:id/registry/repositories` endpoint will remain, but won't return any info about tags. To get the info about tags, you can use the existing `GET /registry/repositories/:id` endpoint, which will continue to support the `tags` and `tag_count` options as it does today. The latter must be called once per image repository.
diff --git a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml
index 098be766942..2229637f527 100644
--- a/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml
+++ b/data/deprecations/14-5-remove-dependency-proxy-permissions-flag.yml
@@ -1,10 +1,10 @@
-- name: "`dependency_proxy_for_private_groups` feature flag" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+- name: "`dependency_proxy_for_private_groups` feature flag"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  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.
 
     In milestone 15.0, we will remove the feature flag entirely. Moving forward, you must authenticate when using the Dependency Proxy.
diff --git a/data/deprecations/14-5-remove-package-pipelines-api.yml b/data/deprecations/14-5-remove-package-pipelines-api.yml
index 46ef1213da8..392636f90a0 100644
--- a/data/deprecations/14-5-remove-package-pipelines-api.yml
+++ b/data/deprecations/14-5-remove-package-pipelines-api.yml
@@ -1,10 +1,10 @@
-- name: "Package pipelines in API payload is paginated" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+- name: "Package pipelines in API payload is paginated"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines.
 
     In milestone 15.0, we will remove the `pipelines` attribute from the API response.
diff --git a/data/deprecations/14-5-remove-pipelines-from-version-field.yml b/data/deprecations/14-5-remove-pipelines-from-version-field.yml
index fc8ec519fa7..98174daa26c 100644
--- a/data/deprecations/14-5-remove-pipelines-from-version-field.yml
+++ b/data/deprecations/14-5-remove-pipelines-from-version-field.yml
@@ -1,10 +1,10 @@
-- name: "`pipelines` field from the `version` field" # The name of the feature to be deprecated
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed
+- name: "`pipelines` field from the `version` field"  # The name of the feature to be deprecated
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  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:
 
     - The `versions` field's `pipelines` field. This returns all the pipelines associated with all the package's versions, which can pull an unbounded number of objects in memory and create performance concerns.
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 c3fbe553706..46f1ef89b53 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,10 +1,10 @@
 - name: "REST and GraphQL API Runner status will not return `paused`"
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  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.
+  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.
 
     A runner's status will only relate to runner contact status, such as:
diff --git a/data/deprecations/14-5-runner-s3-authenticationtype-nonexplicit-config-deprecation.yml b/data/deprecations/14-5-runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
index d957b79e450..7026438f649 100644
--- a/data/deprecations/14-5-runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
+++ b/data/deprecations/14-5-runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
@@ -1,10 +1,10 @@
 - name: "Must explicitly assign `AuthenticationType` for `[runners.cache.s3]`"
-  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  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.
+  body: |  # Do not modify this line, instead modify the lines below.
     In GitLab 15.0 and later, to access the AWS S3 cache, you must specify the `AuthenticationType` for [`[runners.cache.s3]`](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscaches3-section). The `AuthenticationType` must be `IAM` or `credentials`.
 
     Prior to 14.5, if you did not define the `AuthenticationType`, GitLab Runner chose a type for you.
diff --git a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml
index 42de723ee99..b80fd45239e 100644
--- a/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml
+++ b/data/deprecations/14-6-Enforce-validation-of-security-schemas.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -18,9 +18,9 @@
     [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
+  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
index b79418d5765..9427c9f0e88 100644
--- a/data/deprecations/14-6-container-scanning-schemas-below-14.yml
+++ b/data/deprecations/14-6-container-scanning-schemas-below-14.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -15,9 +15,9 @@
     [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
+  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
index 13babcc26ba..78d076294ed 100644
--- a/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml
+++ b/data/deprecations/14-6-coverage-fuzzing-schemas-below-14.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -18,9 +18,9 @@
     [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
+  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
index afd27a1fa7a..305cf9469f9 100644
--- a/data/deprecations/14-6-dast-schemas-below-14.yml
+++ b/data/deprecations/14-6-dast-schemas-below-14.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -18,9 +18,9 @@
     [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
+  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
index 226cffc3afc..f04130bc68f 100644
--- a/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml
+++ b/data/deprecations/14-6-dependency-scanning-schemas-below-14.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -18,9 +18,9 @@
     [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
+  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 f8886eeef37..3db9f574d38 100644
--- a/data/deprecations/14-6-deprecate-types.yml
+++ b/data/deprecations/14-6-deprecate-types.yml
@@ -1,15 +1,15 @@
-- name: "`type` and `types` keyword in CI/CD configuration" # The name of the feature to be deprecated
-  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+- name: "`type` and `types` keyword in CI/CD configuration"  # The name of the feature to be deprecated
+  announcement_milestone: "14.6"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-12-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior.
 # The following items are not published on the docs page, but may be used in the future.
-  stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: # (optional) This is a link to the current documentation page
-  image_url: # (optional) This is a link to a thumbnail image depicting the feature
-  video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  stage:  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers:  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url:  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url:  # (optional) This is a link to the current documentation page
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
diff --git a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml
index e09205f2d9b..344d1a04a4b 100644
--- a/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml
+++ b/data/deprecations/14-6-deprecation-license-compliance-api-terms.yml
@@ -1,17 +1,17 @@
-- name: "Legacy approval status names from License Compliance API" # The name of the feature to be deprecated
-  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+- name: "Legacy approval status names from License Compliance API"  # The name of the feature to be deprecated
+  announcement_milestone: "14.6"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-12-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     We deprecated legacy names for approval status of license policy (blacklisted, approved) in the `managed_licenses` API but they are still used in our API queries and responses. They will be removed in 15.0.
 
     If you are using our License Compliance API you should stop using the `approved` and `blacklisted` query parameters, they are now `allowed` and `denied`. In 15.0 the responses will also stop using `approved` and `blacklisted` so you need to adjust any of your custom tools to use the old and new values so they do not break with the 15.0 release.
 # The following items are not published on the docs page, but may be used in the future.
-  stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/335707 # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: # (optional) This is a link to the current documentation page
-  image_url: # (optional) This is a link to a thumbnail image depicting the feature
-  video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
+  stage: secure  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: ultimate  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/335707  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url:  # (optional) This is a link to the current documentation page
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  removal_date: "2022-05-22"  # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml
index 4f4a2ad8a7d..72039930348 100644
--- a/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml
+++ b/data/deprecations/14-6-deprecation-secure-dependency-scanning-bundler-audit.yml
@@ -1,17 +1,17 @@
-- name: "bundler-audit Dependency Scanning tool" # The name of the feature to be deprecated
-  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+- name: "bundler-audit Dependency Scanning tool"  # The name of the feature to be deprecated
+  announcement_milestone: "14.6"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-12-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     As of 14.6 bundler-audit is being deprecated from Dependency Scanning. It will continue to be in our CI/CD template while deprecated. We are removing bundler-audit from Dependency Scanning on May 22, 2022 in 15.0. After this removal Ruby scanning functionality will not be affected as it is still being covered by Gemnasium.
 
     If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you will need to clean up (remove the reference) in 15.0. If you have customized your pipeline's Dependency Scanning configuration, for example to edit the `bundler-audit-dependency_scanning` job, you will want to switch to gemnasium-dependency_scanning before removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference bundler-audit, or customized your template specifically for bundler-audit, you will not need to take action.
 # The following items are not published on the docs page, but may be used in the future.
-  stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/289832 # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.html # (optional) This is a link to the current documentation page
-  image_url: # (optional) This is a link to a thumbnail image depicting the feature
-  video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
+  stage: secure  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: ultimate  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/289832  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.html  # (optional) This is a link to the current documentation page
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  removal_date: "2022-05-22"  # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-6-job_char_limit.yml b/data/deprecations/14-6-job_char_limit.yml
index 6570b1b8e81..ee3efafe9f6 100644
--- a/data/deprecations/14-6-job_char_limit.yml
+++ b/data/deprecations/14-6-job_char_limit.yml
@@ -1,15 +1,15 @@
-- 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
+- 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.
+  body: |  # Do not modify this line, instead modify the lines below.
     In GitLab 15.0 we are going to limit the number of characters in CI/CD job names to 255. Any pipeline with job names that exceed the 255 character limit will stop working after the 15.0 release.
 # The following items are not published on the docs page, but may be used in the future.
-  stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/342800 # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: # (optional) This is a link to the current documentation page
-  image_url: # (optional) This is a link to a thumbnail image depicting the feature
-  video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  stage:  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers:  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/342800  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url:  # (optional) This is a link to the current documentation page
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
diff --git a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml
index 897886d2d0b..14892d2bbae 100644
--- a/data/deprecations/14-6-pipeline-fields-package-deprecation.yml
+++ b/data/deprecations/14-6-pipeline-fields-package-deprecation.yml
@@ -1,10 +1,10 @@
 - name: "`pipelines` fields in the Package GraphQL types"
-  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
+  announcement_milestone: "14.6"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-12-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # the date of the milestone release when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `pipelines` fields in all Package-related GraphQL types. As of GitLab 14.6, the `pipelines` field is deprecated in [`Package`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#package) and [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype) due to scalability and performance concerns.
 
     In milestone 15.0, we will completely remove `pipelines` from `Package` and `PackageDetailsType`. You can follow and contribute to work on a replacement in the epic [GitLab-#7214](https://gitlab.com/groups/gitlab-org/-/epics/7214).
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 a535cfbf7a7..a2aba7cadbe 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
@@ -1,9 +1,9 @@
 - name: "Runner status `not_connected` API value"
-  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
+  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.
+  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/14-6-runner_api_new_stale_status_breaking_change.yml b/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml
index 3cf6ed69354..0f21318d329 100644
--- a/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml
+++ b/data/deprecations/14-6-runner_api_new_stale_status_breaking_change.yml
@@ -1,10 +1,10 @@
 - name: "API: `stale` status returned instead of `offline` or `not_connected`"
-  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.6"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-12-22"
-  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
+  removal_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.
+  body: |  # Do not modify this line, instead modify the lines below.
     A breaking change will occur for the Runner [API](https://docs.gitlab.com/ee/api/runners.html#runners-api) endpoints in 15.0.
 
     Instead of the GitLab Runner API endpoints returning `offline` and `not_connected` for runners that have not contacted the GitLab instance in the past three months, the API endpoints will return the `stale` value, which was introduced in 14.6.
diff --git a/data/deprecations/14-6-sast-schemas-below-14.yml b/data/deprecations/14-6-sast-schemas-below-14.yml
index 02e112ec4b8..635eaa3624b 100644
--- a/data/deprecations/14-6-sast-schemas-below-14.yml
+++ b/data/deprecations/14-6-sast-schemas-below-14.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -18,9 +18,9 @@
     [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
+  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
index d366e08a8c0..16af233df44 100644
--- a/data/deprecations/14-6-secret-detection-schemas-below-14.yml
+++ b/data/deprecations/14-6-secret-detection-schemas-below-14.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
@@ -18,9 +18,9 @@
     [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
+  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-godep-support-in-license-compliance.yml b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml
index cf986341884..9d0e2aa91dc 100644
--- a/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml
+++ b/data/deprecations/14-7-deprecate-godep-support-in-license-compliance.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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
diff --git a/data/deprecations/14-7-deprecate-merged_by-api-field.yml b/data/deprecations/14-7-deprecate-merged_by-api-field.yml
index e2ecef1aa6a..0a84b118981 100644
--- a/data/deprecations/14-7-deprecate-merged_by-api-field.yml
+++ b/data/deprecations/14-7-deprecate-merged_by-api-field.yml
@@ -10,18 +10,18 @@
 #
 # 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: true # If this deprecation is a breaking change, set this value to true
-  body: | # Do not modify this line, instead modify the lines below.
+- 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: true  # If this deprecation is a breaking change, set this value to true
+  body: |  # Do not modify this line, instead modify the lines below.
     The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-requests) 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
+  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
index e522699e823..18f2ec26645 100644
--- a/data/deprecations/14-7-deprecate-static-site-editor.yml
+++ b/data/deprecations/14-7-deprecate-static-site-editor.yml
@@ -1,14 +1,14 @@
-- name: "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.
+- name: "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
+  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
index bd8cb215496..f278cd506e2 100644
--- a/data/deprecations/14-7-pseudonymizer.yml
+++ b/data/deprecations/14-7-pseudonymizer.yml
@@ -1,9 +1,9 @@
-- 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.
+- 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.
diff --git a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml
index 34c262b1539..1faec65e9ef 100644
--- a/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml
+++ b/data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml
@@ -4,7 +4,7 @@
   removal_milestone: "15.0"
   removal_date: "2022-05-22"
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  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.
 
diff --git a/data/deprecations/14-8-Elasticsearch-6-8.yml b/data/deprecations/14-8-Elasticsearch-6-8.yml
index 20f32966f24..28a25803d41 100644
--- a/data/deprecations/14-8-Elasticsearch-6-8.yml
+++ b/data/deprecations/14-8-Elasticsearch-6-8.yml
@@ -2,17 +2,16 @@
   announcement_milestone: "14.8"
   announcement_date: "2022-02-22"
   removal_milestone: "15.0"
-  removal_date: "2022-05-22" 
-  breaking_change: true 
-  body: | 
+  removal_date: "2022-05-22"
+  breaking_change: true
+  body: |
         Elasticsearch 6.8 is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0.
         Customers using Elasticsearch 6.8 need to upgrade their Elasticsearch version to 7.x prior to upgrading to GitLab 15.0.
         We recommend using the latest version of Elasticsearch 7 to benefit from all Elasticsearch improvements.
 
         Elasticsearch 6.8 is also incompatible with Amazon OpenSearch, which we [plan to support in GitLab 15.0](https://gitlab.com/gitlab-org/gitlab/-/issues/327560).
 
-  stage: Enablement 
-  tiers: [Premium, Ultimate] 
+  stage: Enablement
+  tiers: [Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350275
   documentation_url: https://docs.gitlab.com/ee/integration/elasticsearch.html#version-requirements
-
diff --git a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml
index 73ba7d8011a..104dbc5f72d 100644
--- a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml
+++ b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml
@@ -5,7 +5,7 @@
   removal_date: "2022-05-22"
   breaking_change: true
   reporter: sam.white
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The [required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers.
 
     This change to move the feature to GitLab's Ultimate tier is intended to help our features better align with our [pricing philosophy](https://about.gitlab.com/company/pricing/#three-tiers) as we see demand for this feature originating primarily from executives.
diff --git a/data/deprecations/14-8-compliance-status-check-api-field.yml b/data/deprecations/14-8-compliance-status-check-api-field.yml
index f32a8379481..5ad653c8fce 100644
--- a/data/deprecations/14-8-compliance-status-check-api-field.yml
+++ b/data/deprecations/14-8-compliance-status-check-api-field.yml
@@ -5,7 +5,7 @@
   removal_date: "2022-05-22"
   breaking_change: true
   reporter: sam.white
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The [external status check API](https://docs.gitlab.com/ee/api/status_checks.html) was originally implemented to
     support pass-by-default requests to mark a status check as passing. Pass-by-default requests are now deprecated.
     Specifically, the following are deprecated:
diff --git a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml
index ea75e70afe3..0638f86968a 100644
--- a/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml
+++ b/data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml
@@ -2,7 +2,7 @@
   announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   breaking_change: true  # If this deprecation is a breaking change, set this value to true
   reporter: matt_wilson  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
diff --git a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml
index a5e5ce6e9ea..3713ae532b3 100644
--- a/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml
+++ b/data/deprecations/14-8-deprecation-secure-dependency-scanning-retire-js.yml
@@ -1,17 +1,17 @@
-- name: "Retire-JS Dependency Scanning tool" # The name of the feature to be deprecated
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+- name: "Retire-JS Dependency Scanning tool"  # The name of the feature to be deprecated
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     As of 14.8 the retire.js job is being deprecated from Dependency Scanning. It will continue to be included in our CI/CD template while deprecated. We are removing retire.js from Dependency Scanning on May 22, 2022 in GitLab 15.0. JavaScript scanning functionality will not be affected as it is still being covered by Gemnasium.
 
     If you have explicitly excluded retire.js 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 related to the `retire-js-dependency_scanning` job you will want to switch to gemnasium-dependency_scanning before the removal in 15.0, to prevent your pipeline from failing. If you have not used the DS_EXCLUDED_ANALYZERS to reference retire.js, or customized your template specifically for retire.js, you will not need to take action.
 # The following items are not published on the docs page, but may be used in the future.
-  stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350510 # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.html # (optional) This is a link to the current documentation page
-  image_url: # (optional) This is a link to a thumbnail image depicting the feature
-  video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
+  stage: secure  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: ultimate  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/350510  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/analyzers.html  # (optional) This is a link to the current documentation page
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  removal_date: "2022-05-22"  # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-8-enforce-pat-expiration.yml b/data/deprecations/14-8-enforce-pat-expiration.yml
index 6c6fdf31fe6..bb5155984ef 100644
--- a/data/deprecations/14-8-enforce-pat-expiration.yml
+++ b/data/deprecations/14-8-enforce-pat-expiration.yml
@@ -1,13 +1,13 @@
-- name: "Optional enforcement of PAT expiration" # The name of the feature to be deprecated
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  breaking_change: true # If this deprecation is a breaking change, set this value to true
-  reporter: djensen # GitLab username of the person reporting the deprecation
-  body: | # Do not modify this line, instead modify the lines below.
+- name: "Optional enforcement of PAT expiration"  # The name of the feature to be deprecated
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  reporter: djensen  # GitLab username of the person reporting the deprecation
+  body: |  # Do not modify this line, instead modify the lines below.
     The feature to disable enforcement of PAT expiration is unusual from a security perspective.
     We have become concerned that this unusual feature could create unexpected behavior for users.
     Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature.
-  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351962" # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-personal-access-tokens-to-be-used-deprecated" # (optional) This is a link to the current documentation page
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351962"  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-personal-access-tokens-to-be-used-deprecated"  # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/14-8-enforce-ssh-expiration.yml b/data/deprecations/14-8-enforce-ssh-expiration.yml
index 815d592a2a9..2f8362001df 100644
--- a/data/deprecations/14-8-enforce-ssh-expiration.yml
+++ b/data/deprecations/14-8-enforce-ssh-expiration.yml
@@ -1,13 +1,13 @@
-- name: "Optional enforcement of SSH expiration" # The name of the feature to be deprecated
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  breaking_change: true # If this deprecation is a breaking change, set this value to true
-  reporter: djensen # GitLab username of the person reporting the deprecation
-  body: | # Do not modify this line, instead modify the lines below.
+- name: "Optional enforcement of SSH expiration"  # The name of the feature to be deprecated
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  reporter: djensen  # GitLab username of the person reporting the deprecation
+  body: |  # Do not modify this line, instead modify the lines below.
     The feature to disable enforcement of SSH expiration is unusual from a security perspective.
     We have become concerned that this unusual feature could create unexpected behavior for users.
     Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature.
-  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351963" # (optional) This is a link to the deprecation issue in GitLab
-  documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-ssh-keys-to-be-used-deprecated" # (optional) This is a link to the current documentation page
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351963"  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-ssh-keys-to-be-used-deprecated"  # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml
index 137ae01f63b..d38e579e3e6 100644
--- a/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml
+++ b/data/deprecations/14-8-geo-deprecate-db-rake-tasks.yml
@@ -2,7 +2,7 @@
   announcement_milestone: "14.8"
   announcement_date: "2022-02-22"
   removal_milestone: "15.0"
-  removal_date:  "2022-05-22"
+  removal_date: "2022-05-22"
   breaking_change: false
   reporter: nhxnguyen
   body: |
@@ -28,7 +28,7 @@
     - `geo:db:test:purge` -> `db:test:purge:geo`
   stage: "Enablement"
   tiers: ["Premium", "Ultimate"]
-  issue_url:  "https://gitlab.com/gitlab-org/gitlab/-/issues/351945"
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351945"
   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-8-geo-deprecate-replication-detail-routes.yml b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml
index 94a026edd81..c28dc849f72 100644
--- a/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml
+++ b/data/deprecations/14-8-geo-deprecate-replication-detail-routes.yml
@@ -10,6 +10,6 @@
   stage: "Enablement"
   tiers: ["Premium", "Ultimate"]
   issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351345"
-  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
+  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-8-gitaly-remove-per-repository-election.yml b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml
index 334da51c4a0..7edaff9821f 100644
--- a/data/deprecations/14-8-gitaly-remove-per-repository-election.yml
+++ b/data/deprecations/14-8-gitaly-remove-per-repository-election.yml
@@ -2,7 +2,7 @@
   announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "14.9"  # The milestone when this feature is planned to be removed
-  removal_date:  "2022-03-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_date: "2022-03-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   breaking_change: false  # If this deprecation is a breaking change, set this value to true
   reporter: mjwood  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
@@ -13,7 +13,7 @@
 # The following items are not published on the docs page, but may be used in the future.
   stage:  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
   tiers:  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/352612" # (optional) This is a link to the deprecation issue in GitLab
+  issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/352612"  # (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-8-graphql-ids.yml b/data/deprecations/14-8-graphql-ids.yml
index dd73f310335..67ff418c51a 100644
--- a/data/deprecations/14-8-graphql-ids.yml
+++ b/data/deprecations/14-8-graphql-ids.yml
@@ -2,7 +2,7 @@
   announcement_milestone: "14.8"
   announcement_date: "2022-02-22"
   removal_milestone: "15.0"
-  removal_date:  "2022-04-22"
+  removal_date: "2022-04-22"
   breaking_change: true
   reporter: alexkalderimis
   body: |  # Do not modify this line, instead modify the lines below.
@@ -52,7 +52,7 @@
       }
     }
     ```
-    
+
     This query works now, and will continue to work after GitLab 15.0.
     You should convert any queries in the first form (using `ID` as a named type in the signature)
     to one of the other two forms (using the correct appropriate type in the signature, or using
@@ -60,7 +60,7 @@
 # The following items are not published on the docs page, but may be used in the future.
   stage:  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
   tiers:  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url:  'https://gitlab.com/gitlab-org/gitlab/-/issues/257883'
+  issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/257883'
   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-8-grpc-proxy.yml b/data/deprecations/14-8-grpc-proxy.yml
index 353c0abc901..1ec505fd216 100644
--- a/data/deprecations/14-8-grpc-proxy.yml
+++ b/data/deprecations/14-8-grpc-proxy.yml
@@ -2,7 +2,7 @@
   announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
-  removal_date: 2022-05-22 # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   breaking_change: true  # If this deprecation is a breaking change, set this value to true
   reporter: jacobvosmaer-gitlab  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
diff --git a/data/deprecations/14-8-iteration-started-field.yml b/data/deprecations/14-8-iteration-started-field.yml
index 590c9800db6..e323b93752b 100644
--- a/data/deprecations/14-8-iteration-started-field.yml
+++ b/data/deprecations/14-8-iteration-started-field.yml
@@ -1,15 +1,15 @@
-- name: "`started` iterations API field" # The name of the feature to be deprecated
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  breaking_change: true # If this deprecation is a breaking change, set this value to true
-  body: | # Do not modify this line, instead modify the lines below.
+- name: "`started` iterations API field"  # The name of the feature to be deprecated
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  body: |  # Do not modify this line, instead modify the lines below.
     The `started` field in the [iterations API](https://docs.gitlab.com/ee/api/iterations.html#list-project-iterations) is being deprecated and will be removed in GitLab 15.0. This field is being replaced with the `current` field (already available) which aligns with the naming for other time-based entities, such as milestones.
 # The following items are not published on the docs page, but may be used in the future.
   stage: plan
-  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]
+  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/334018
-  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
+  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-8-nfs_support.yml b/data/deprecations/14-8-nfs_support.yml
index 832b309e979..534975b0642 100644
--- a/data/deprecations/14-8-nfs_support.yml
+++ b/data/deprecations/14-8-nfs_support.yml
@@ -20,7 +20,7 @@
     - [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/#distributed-reads)
 
 # The following items are not published on the docs page, but may be used in the future.
-  stage: Gitaly # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  stage: Gitaly  # (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
diff --git a/data/deprecations/14-8-protect-cns-chs.yml b/data/deprecations/14-8-protect-cns-chs.yml
index b3a4cc8c1e8..8ea76d1b371 100644
--- a/data/deprecations/14-8-protect-cns-chs.yml
+++ b/data/deprecations/14-8-protect-cns-chs.yml
@@ -5,7 +5,7 @@
   removal_date: "2022-05-22"
   breaking_change: true
   reporter: sam.white
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     All functionality related to GitLab's Container Network Security and Container Host Security categories is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies into GitLab, add the desired Helm charts into your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through the GitLab [Secure CI/CD Tunnel](https://docs.gitlab.com/ee/user/clusters/agent/repository.html#run-kubectl-commands-using-the-cicd-tunnel).
 
     As part of this change, the following specific capabilities within GitLab are now deprecated, and are scheduled for removal in GitLab 15.0:
diff --git a/data/deprecations/14-8-protect-vulnerability-check.yml b/data/deprecations/14-8-protect-vulnerability-check.yml
index 0f8fb44081a..ddb296886b2 100644
--- a/data/deprecations/14-8-protect-vulnerability-check.yml
+++ b/data/deprecations/14-8-protect-vulnerability-check.yml
@@ -5,7 +5,7 @@
   removal_date: "2022-05-22"
   breaking_change: true
   reporter: sam.white
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The vulnerability check feature is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. We encourage you to migrate to the new security approvals feature instead. You can do so by navigating to **Security & Compliance > Policies** and creating a new Scan Result Policy.
 
     The new security approvals feature is similar to vulnerability check. For example, both can require approvals for MRs that contain security vulnerabilities. However, security approvals improve the previous experience in several ways:
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
index cda67e53b8e..f738b71f1b7 100644
--- 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
@@ -1,9 +1,9 @@
-- 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.
+- 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
diff --git a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml
index b93b25c00d0..4029443cc76 100644
--- a/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml
+++ b/data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml
@@ -2,15 +2,15 @@
   announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
-  removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  breaking_change: true # If this deprecation is a breaking change, set this value to true
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
   reporter: sarahwaldner  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
     The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 15.0. Upon its removal, push rules will supersede CODEOWNERS. The CODEOWNERS feature will no longer be available for access control.
 # 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
+  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/262019 # (optional) This is a link to the deprecation issue in GitLab
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/262019   # (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-8-request-profiling.yml b/data/deprecations/14-8-request-profiling.yml
index 8b549a6002f..82d2aadd149 100644
--- a/data/deprecations/14-8-request-profiling.yml
+++ b/data/deprecations/14-8-request-profiling.yml
@@ -1,11 +1,11 @@
 - name: "Request profiling"
   announcement_milestone: "14.8"
   announcement_date: "2021-02-22"
-  removal_milestone: "15.0" 
+  removal_milestone: "15.0"
   removal_date: "2022-05-22"
   breaking_change: true
   reporter: iroussos
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     [Request profiling](https://docs.gitlab.com/ee/administration/monitoring/performance/request_profiling.html) is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0.
 
     We're working on [consolidating our profiling tools](https://gitlab.com/groups/gitlab-org/-/epics/7327) and making them more easily accessible.
diff --git a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml
index 63178061aae..0300641e540 100644
--- a/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml
+++ b/data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml
@@ -29,5 +29,5 @@
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347211
   documentation_url: https://docs.gitlab.com/ee/api/runners.html
-  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
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
diff --git a/data/deprecations/14-8-runner-api-project_type-breaking-change.yml b/data/deprecations/14-8-runner-api-project_type-breaking-change.yml
index 67cd854aa89..d965d830c58 100644
--- a/data/deprecations/14-8-runner-api-project_type-breaking-change.yml
+++ b/data/deprecations/14-8-runner-api-project_type-breaking-change.yml
@@ -11,5 +11,5 @@
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351466
   documentation_url: https://docs.gitlab.com/ee/api/runners.html
-  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
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
diff --git a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml
index 51472b3cd28..8f706840f0d 100644
--- a/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml
+++ b/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml
@@ -1,10 +1,10 @@
 - name: "REST API Runner will not accept `status` filter values of `active` or `paused`"
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2022-02-22"
   removal_milestone: "16.0"
   removal_date: "2023-04-22"
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The GitLab Runner REST endpoints will stop accepting `paused` or `active` as a status value in GitLab 16.0.
 
     A runner's status will only relate to runner contact status, such as: `online`, `offline`.
diff --git a/data/deprecations/14-8-sast-secret-analyzer-image.yml b/data/deprecations/14-8-sast-secret-analyzer-image.yml
index b1cb5c82764..cc7e559722d 100644
--- a/data/deprecations/14-8-sast-secret-analyzer-image.yml
+++ b/data/deprecations/14-8-sast-secret-analyzer-image.yml
@@ -12,7 +12,7 @@
     Starting in GitLab 14.8, new versions of GitLab Secure and Protect analyzers are published to a new registry location under `registry.gitlab.com/security-products`.
 
     We will update the default value of [GitLab-managed CI/CD templates](https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/gitlab/ci/templates/Security) to reflect this change:
-      
+
     - For all analyzers except Container Scanning, we will update the variable `SECURE_ANALYZERS_PREFIX` to the new image registry location.
     - For Container Scanning, the default image address is already updated. There is no `SECURE_ANALYZERS_PREFIX` variable for Container Scanning.
 
diff --git a/data/deprecations/data/deprecations/14-9-secure-and-protect-analyzer-bump.yml.yml b/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml
index 8f1d030f47c..b8eedeeaadb 100644
--- a/data/deprecations/data/deprecations/14-9-secure-and-protect-analyzer-bump.yml.yml
+++ b/data/deprecations/14-8-secure-and-protect-analyzer-bump.yml
@@ -1,8 +1,8 @@
 - name: "Secure and Protect analyzer major version update"  # The name of the feature to be deprecated
   announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
   announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.00"  # The milestone when this feature is planned to be removed
-  removal_date:  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   breaking_change: true  # If this deprecation is a breaking change, set this value to true
   reporter: NicoleSchwartz  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
@@ -20,9 +20,10 @@
     - Coverage-guided fuzz testing: version 2
     - Dependency Scanning: version 2
     - Dynamic Application Security Testing (DAST): version 2
+    - Infrastructure as Code (IaC) Scanning: version 1
     - License Scanning: version 3
     - Secret Detection: version 3
-    - Static Application Security Testing (SAST): version 2, except security-code-scan which is version 3
+    - Static Application Security Testing (SAST): version 2 of [all analyzers](https://docs.gitlab.com/ee/user/application_security/sast/#supported-languages-and-frameworks), except `gosec` which is currently at version 3
       - `bandit`: version 2
       - `brakeman`: version 2
       - `eslint`: version 2
@@ -33,12 +34,12 @@
       - `nodejs-scan`: version 2
       - `phpcs-security-audit`: version 2
       - `pmd-apex`: version 2
-      - `security-code-scan`: version 3
+      - `security-code-scan`: version 2
       - `semgrep`: version 2
       - `sobelow`: version 2
       - `spotbugs`: version 2
 # The following items are not published on the docs page, but may be used in the future.
-  stage: secure, protect # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: Free, Silver, Gold, 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/gitlab-org/gitlab/-/issues/350936 # (optional) This is a link to the deprecation issue in GitLab
+  stage: secure, protect  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: Free, Silver, Gold, 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/gitlab-org/gitlab/-/issues/350936  # (optional) This is a link to the deprecation issue in GitLab
   documentation_url:  # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/14-8-secure-ca-python-deprecation.yml b/data/deprecations/14-8-secure-ca-python-deprecation.yml
index c4b5c2e36b7..c97271e4db2 100644
--- a/data/deprecations/14-8-secure-ca-python-deprecation.yml
+++ b/data/deprecations/14-8-secure-ca-python-deprecation.yml
@@ -1,10 +1,10 @@
-- name: "Dependency Scanning Python 3.9 and 3.6 image deprecation" # The name of the feature to be deprecated
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: 2021-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.
+- name: "Dependency Scanning Python 3.9 and 3.6 image deprecation"  # The name of the feature to be deprecated
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2021-05-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  body: |  # Do not modify this line, instead modify the lines below.
     For those using Dependency Scanning for Python projects, we are deprecating the default `gemnasium-python:2` image which uses Python 3.6 as well as the custom `gemnasium-python:2-python-3.9` image which uses Python 3.9. The new default image as of GitLab 15.0 will be for Python 3.9 as it is a [supported version](https://endoflife.date/python) and 3.6 [is no longer supported](https://endoflife.date/python).
 
     For users using Python 3.9 or 3.9-compatible projects, you should not need to take action and dependency scanning should begin to work in GitLab 15.0. If you wish to test the new container now please run a test pipeline in your project with this container (which will be removed in 15.0). Use the Python 3.9 image:
@@ -17,7 +17,7 @@
 
     For users using Python 3.6, as of GitLab 15.0 you will no longer be able to use the default template for dependency scanning. You will need to switch to use the deprecated `gemnasium-python:2` analyzer image. If you are impacted by this please comment in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351503) so we can extend the removal if needed.
 
-    For users using the 3.9 special exception image, you must instead use the default value and no longer override your container. To verify if you are using the 3.9 special exception image, check your `.gitlab-ci.yml` file for the following reference: 
+    For users using the 3.9 special exception image, you must instead use the default value and no longer override your container. To verify if you are using the 3.9 special exception image, check your `.gitlab-ci.yml` file for the following reference:
 
     ```yaml
     gemnasium-python-dependency_scanning:
@@ -25,9 +25,9 @@
         name: registry.gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python:2-python-3.9
     ```
 # The following items are not published on the docs page, but may be used in the future.
-  stage: secure # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
-  tiers: ultimate # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/334060 # (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
+  stage: secure  # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
+  tiers: ultimate  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/334060  # (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-9-deprecate-composer-download-permissions.yml b/data/deprecations/14-9-deprecate-composer-download-permissions.yml
new file mode 100644
index 00000000000..79cb2a81c53
--- /dev/null
+++ b/data/deprecations/14-9-deprecate-composer-download-permissions.yml
@@ -0,0 +1,11 @@
+- name: "Permissions change for downloading Composer dependencies"
+  announcement_milestone: "14.9"
+  announcement_date: "2022-03-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
+  reporter: trizzi
+  body: |  # Do not modify this line, instead modify the lines below.
+    The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies.
+
+    Downloading Composer dependencies without authentication is deprecated in GitLab 14.9, and will be removed in GitLab 15.0. Starting with GitLab 15.0, you must authenticate to download Composer dependencies.
diff --git a/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml
new file mode 100644
index 00000000000..740b3ca2e0d
--- /dev/null
+++ b/data/deprecations/14-9-deprecate-permissions-change-package-settings.yml
@@ -0,0 +1,16 @@
+- name: "GraphQL permissions change for Package settings"
+  announcement_milestone: "14.9"
+  announcement_date: "2022-03-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
+  reporter: trizzi
+  body: |  # Do not modify this line, instead modify the lines below.
+    The GitLab Package stage offers a Package Registry, Container Registry, and Dependency Proxy to help you manage all of your dependencies using GitLab. Each of these product categories has a variety of settings that can be adjusted using the API.
+
+    The permissions model for GraphQL is being updated. After 15.0, users with the Guest, Reporter, and Developer role can no longer update these settings:
+
+    - [Package Registry settings](https://docs.gitlab.com/ee/api/graphql/reference/#packagesettings)
+    - [Container Registry cleanup policy](https://docs.gitlab.com/ee/api/graphql/reference/#containerexpirationpolicy)
+    - [Dependency Proxy time-to-live policy](https://docs.gitlab.com/ee/api/graphql/reference/#dependencyproxyimagettlgrouppolicy)
+    - [Enabling the Dependency Proxy for your group](https://docs.gitlab.com/ee/api/graphql/reference/#dependencyproxysetting)
diff --git a/data/deprecations/14-9-deprecate-testcoveragesetting.yml b/data/deprecations/14-9-deprecate-testcoveragesetting.yml
index 19bc6004b02..9015172eeb9 100644
--- a/data/deprecations/14-9-deprecate-testcoveragesetting.yml
+++ b/data/deprecations/14-9-deprecate-testcoveragesetting.yml
@@ -7,7 +7,7 @@
   reporter: jreporter  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
       To simplify setting a test coverage pattern, in GitLab 15.0 the
-      [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-deprecated)
+      [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-using-project-settings-deprecated)
       is being removed.
 
       Instead, using the project’s `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set
diff --git a/data/deprecations/14-9-pages-daemon.yml b/data/deprecations/14-9-pages-daemon.yml
new file mode 100644
index 00000000000..a8fb5924ac6
--- /dev/null
+++ b/data/deprecations/14-9-pages-daemon.yml
@@ -0,0 +1,16 @@
+- name: "GitLab Pages running as daemon"  # The name of the feature to be deprecated
+  announcement_milestone: "14.9"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-03-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: false  # If this deprecation is a breaking change, set this value to true
+  reporter: cbalane  # GitLab username of the person reporting the deprecation
+  body: |  # Do not modify this line, instead modify the lines below.
+    In 15.0, support for daemon mode for GitLab Pages will be removed.
+  # 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-9-system_monitoring.yml b/data/deprecations/14-9-system_monitoring.yml
new file mode 100644
index 00000000000..6c8dc61db4d
--- /dev/null
+++ b/data/deprecations/14-9-system_monitoring.yml
@@ -0,0 +1,14 @@
+- name: "GitLab self-monitoring"  # The name of the feature to be deprecated
+  announcement_milestone: "14.9"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-03-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  reporter: abellucci  # GitLab username of the person reporting the deprecation
+  body: |  # Do not modify this line, instead modify the lines below.
+    GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 15.0.
+# 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: [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/gitlab-org/gitlab/-/issues/348909  # (optional) This is a link to the deprecation issue in GitLab
+  documentation_url: https://docs.gitlab.com/ee/administration/monitoring/gitlab_self_monitoring_project/  # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/JTW_v2_update.yml b/data/deprecations/15-0-JTW_v2_update.yml
index 53aa9ca2c19..39880d7fbe0 100644
--- a/data/deprecations/JTW_v2_update.yml
+++ b/data/deprecations/15-0-JTW_v2_update.yml
@@ -14,7 +14,7 @@
   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:  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
   breaking_change: true  # If this deprecation is a breaking change, set this value to true
   reporter: dhershkovitch  # GitLab username of the person reporting the deprecation
   body: |  # Do not modify this line, instead modify the lines below.
diff --git a/data/deprecations/15-0-deprecate-monitor-logging.yml b/data/deprecations/15-0-deprecate-monitor-logging.yml
index facb66e4ee8..8dbae6f5c4c 100644
--- a/data/deprecations/15-0-deprecate-monitor-logging.yml
+++ b/data/deprecations/15-0-deprecate-monitor-logging.yml
@@ -1,16 +1,15 @@
-- 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.
+- 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
-
+  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
index 0a28785105f..f5fa63b9c40 100644
--- a/data/deprecations/15-0-deprecate-monitor-metrics.yml
+++ b/data/deprecations/15-0-deprecate-monitor-metrics.yml
@@ -1,17 +1,16 @@
-- 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.
+- 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
-
+  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
index 448404a5c70..3c1eef177ff 100644
--- a/data/deprecations/15-0-deprecate-monitor-tracing.yml
+++ b/data/deprecations/15-0-deprecate-monitor-tracing.yml
@@ -1,15 +1,15 @@
-- 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.
+- 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
+  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/15-0-instance-statistics-graphql-node-removal.yml b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml
index c617a6cc478..113ccdc66ea 100644
--- a/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml
+++ b/data/deprecations/15-0-instance-statistics-graphql-node-removal.yml
@@ -4,7 +4,7 @@
   removal_milestone: "15.0"
   removal_date: "2022-05-22"
   breaking_change: true
-  body: | # Do not modify this line, instead modify the lines below.
+  body: |  # Do not modify this line, instead modify the lines below.
     The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTrendsMeasurements` in 13.10 and the old field name has been marked as deprecated. To fix the existing GraphQL queries, replace `instanceStatisticsMeasurements` with `usageTrendsMeasurements`.
 # The following items are not published on the docs page, but may be used in the future.
   stage: Manage
diff --git a/data/deprecations/15-0-oauth-noexpiry.yml b/data/deprecations/15-0-oauth-noexpiry.yml
index 2e1e4a35f7b..154630c9f16 100644
--- a/data/deprecations/15-0-oauth-noexpiry.yml
+++ b/data/deprecations/15-0-oauth-noexpiry.yml
@@ -1,10 +1,10 @@
-- name: "OAuth tokens without expiration" # The name of the feature to be deprecated
-  announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: 2022-05-22 # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  breaking_change: true # If this deprecation is a breaking change, set this value to true
-  body: | # Do not modify this line, instead modify the lines below.
+- name: "OAuth tokens without expiration"  # The name of the feature to be deprecated
+  announcement_milestone: "14.8"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2022-02-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  body: |  # Do not modify this line, instead modify the lines below.
     By default, all new applications expire access tokens after 2 hours. In GitLab 14.2 and earlier, OAuth access tokens
     had no expiration. In GitLab 15.0, an expiry will be automatically generated for any existing token that does not
     already have one.
@@ -16,9 +16,9 @@
     1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don’t expire.
 
 # The following items are not published on the docs page, but may be used in the future.
-  stage: # Manage
-  tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: # https://gitlab.com/gitlab-org/gitlab/-/issues/21745
-  documentation_url: # (optional) This is a link to the current documentation page
-  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
+  stage:  # Manage
+  tiers:  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url:  # https://gitlab.com/gitlab-org/gitlab/-/issues/21745
+  documentation_url:  # (optional) This is a link to the current documentation page
+  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-oauth.yml b/data/deprecations/15-0-oauth.yml
index 5ca30d9f330..98c7c974808 100644
--- a/data/deprecations/15-0-oauth.yml
+++ b/data/deprecations/15-0-oauth.yml
@@ -1,15 +1,15 @@
-- name: "OAuth implicit grant" # The name of the feature to be deprecated
-  announcement_milestone: "14.0" # The milestone when this feature was first announced as deprecated.
-  announcement_date: "2021-06-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
-  removal_date: 2022-05-22 # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
-  breaking_change: yes # If this deprecation is a breaking change, set this value to true
-  body: | # Do not modify this line, instead modify the lines below.
+- name: "OAuth implicit grant"  # The name of the feature to be deprecated
+  announcement_milestone: "14.0"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-06-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0"  # The milestone when this feature is planned to be removed
+  removal_date: "2022-05-22"  # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  breaking_change: true  # If this deprecation is a breaking change, set this value to true
+  body: |  # Do not modify this line, instead modify the lines below.
     The OAuth implicit grant authorization flow will be removed in our next major release, GitLab 15.0. Any applications that use OAuth implicit grant should switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html).
 # The following items are not published on the docs page, but may be used in the future.
-  stage: # Manage
-  tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
-  issue_url: # https://gitlab.com/gitlab-org/gitlab/-/issues/344609
-  documentation_url: # (optional) This is a link to the current documentation page
-  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
+  stage:  # Manage
+  tiers:  # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url:  # https://gitlab.com/gitlab-org/gitlab/-/issues/344609
+  documentation_url:  # (optional) This is a link to the current documentation page
+  image_url:  # (optional) This is a link to a thumbnail image depicting the feature
+  video_url:  # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
diff --git a/data/deprecations/distribution_deprecations_14-4.yml b/data/deprecations/distribution_deprecations_14-4.yml
new file mode 100644
index 00000000000..b8c4e0d817c
--- /dev/null
+++ b/data/deprecations/distribution_deprecations_14-4.yml
@@ -0,0 +1,6 @@
+- name: "Move `custom_hooks_dir` setting from GitLab Shell to Gitaly"  # The name of the feature to be deprecated
+  announcement_milestone: "14.9"  # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-10-22"
+  removal_milestone: "15.0"  # the milestone when this feature is planned to be removed
+  body: |  # Do not modify this line, instead modify the lines below.
+    The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks.html#create-a-global-server-hook-for-all-repositories) setting is now configured in Gitaly, and will be removed from GitLab Shell in GitLab 15.0.
diff --git a/data/deprecations/templates/14-9-deprecation-htpassword-authentication-container-registry.yml b/data/deprecations/templates/14-9-deprecation-htpassword-authentication-container-registry.yml
new file mode 100644
index 00000000000..14c6b235a1a
--- /dev/null
+++ b/data/deprecations/templates/14-9-deprecation-htpassword-authentication-container-registry.yml
@@ -0,0 +1,11 @@
+- name: "htpasswd Authentication for the Container Registry"
+  announcement_milestone: "14.9"
+  announcement_date: "2022-03-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
+  reporter: trizzi
+  body: |  # Do not modify this line, instead modify the lines below.
+    The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`.
+
+    Since it isn't used in the context of GitLab (the product), `htpasswd` authentication will be deprecated in GitLab 14.9 and removed in GitLab 15.0.
author	GitLab Bot <gitlab-bot@gitlab.com>	2022-03-18 23:02:30 +0300
committer	GitLab Bot <gitlab-bot@gitlab.com>	2022-03-18 23:02:30 +0300
commit	41fe97390ceddf945f3d967b8fdb3de4c66b7dea (patch)
tree	9c8d89a8624828992f06d892cd2f43818ff5dcc8 /data/deprecations
parent	0804d2dc31052fb45a1efecedc8e06ce9bc32862 (diff)