Add latest changes from gitlab-org/gitlab@14-5-stable-eev14.5.0-rc42

21 files changed, 243 insertions, 11 deletions

diff --git a/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml b/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
new file mode 100644
index 00000000000..01ca5839281
--- /dev/null
+++ b/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml
@@ -0,0 +1,12 @@
+- name: "`AuthenticationType` for `[runners.cache.s3]` must be explicitly assigned"
+  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
+  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. 
+  stage: Verify
+  tiers: [Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28171
+  documentation_url: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscaches3-section
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 f38742439aa..6884f6e3f69 100644
--- a/data/deprecations/14-0-nfs-fot-git-repository-storage.yml
+++ b/data/deprecations/14-0-nfs-fot-git-repository-storage.yml
@@ -1,7 +1,7 @@
 - name: "NFS for Git repository storage deprecated" # 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.2" # The milestone when this feature is planned to be removed
+  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.
     With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS in GitLab 15.0. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information.
 
@@ -19,4 +19,4 @@
   documentation_url: # (optional) This is a link to the current documentation page
   image_url: # (optional) This is a link to a thumbnail image depicting the feature
   video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  removal_date: "2022-06-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
+  removal_date: "2022-05-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-2-deprecation-task-runner.yml b/data/deprecations/14-2-deprecation-task-runner.yml
index 4d01a1969ad..52fd1f0f288 100644
--- a/data/deprecations/14-2-deprecation-task-runner.yml
+++ b/data/deprecations/14-2-deprecation-task-runner.yml
@@ -1,7 +1,7 @@
 - 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.4" # The milestone when this feature is planned to be removed
+  removal_milestone: "14.5" # The milestone when this feature is planned to be removed
   body: | # Do not modify this line, instead modify the lines below.
     The Task Runner pod is used to execute periodic housekeeping tasks within the GitLab application and is often confused with the GitLab Runner. Thus, [Task Runner will be renamed to Toolbox](https://gitlab.com/groups/gitlab-org/charts/-/epics/25).
 
@@ -13,4 +13,4 @@
   documentation_url: # (optional) This is a link to the current documentation page
   image_url: # (optional) This is a link to a thumbnail image depicting the feature
   video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  removal_date: "2021-10-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
+  removal_date: "2021-11-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-3-package-container-registry-api-group-update.yml b/data/deprecations/14-3-package-container-registry-api-group-update.yml
new file mode 100644
index 00000000000..3021e283846
--- /dev/null
+++ b/data/deprecations/14-3-package-container-registry-api-group-update.yml
@@ -0,0 +1,12 @@
+- name: "Update to the Container Registry group-level API"
+  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
+  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.
+  stage: Package
+  tiers: Free
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/336912
+  documentation_url: https://docs.gitlab.com/ee/api/container_registry.html#within-a-group
+  announcement_date: 2021-11-22
diff --git a/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml
new file mode 100644
index 00000000000..86e7718b9e1
--- /dev/null
+++ b/data/deprecations/14-5-certificate-based-integration-with-kubernetes.yml
@@ -0,0 +1,19 @@
+- name: "Certificate-based integration with Kubernetes"
+  announcement_milestone: "14.5"
+  announcement_date: "2021-11-15"
+  removal_milestone: "15.0"
+  body: |
+    [We are deprecating the certificate-based integration with Kubernetes](https://about.gitlab.com/blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/).
+    The timeline of removal of the integration from the product is not yet planned and we will communicate
+    more details as they emerge. 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. We will provide migration plans in a future iteration. See [the list of features affected by this deprecation](https://docs.gitlab.com/ee/user/infrastructure/clusters/#deprecated-features).
+    For updates and details, follow this [epic](https://gitlab.com/groups/gitlab-org/configure/-/epics/8).
+
+    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.
+  stage: Configure
+  tiers: [Free, Silver, Gold, Core, Premium, Ultimate]
+  issue_url: 'https://gitlab.com/groups/gitlab-org/configure/-/epics/8'
+  documentation_url: 'https://docs.gitlab.com/ee/user/infrastructure/clusters/#certificate-based-kubernetes-integration-deprecated'
+  removal_date: # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml
new file mode 100644
index 00000000000..c5f9e244af0
--- /dev/null
+++ b/data/deprecations/14-5-deprecate-convert-instance-runner-to-project.yml
@@ -0,0 +1,11 @@
+- name: "Converting an instance (shared) runner to a project (specific) runner is 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
+  body: | # Do not modify this line, instead modify the lines below.
+    In GitLab 15.0, we will remove the feature that enables you to convert an instance (shared) runner to a project (specific) runner. Users who need to add a runner to only a particular project can register a runner to the project directly.
+
+  stage: Verify
+  tiers: [Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/345347
+
diff --git a/data/deprecations/14-5-deprecate-opensuse-15-2.yml b/data/deprecations/14-5-deprecate-opensuse-15-2.yml
new file mode 100644
index 00000000000..b887f92e6a3
--- /dev/null
+++ b/data/deprecations/14-5-deprecate-opensuse-15-2.yml
@@ -0,0 +1,9 @@
+- 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
+  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.
+  issue_url: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6427
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
new file mode 100644
index 00000000000..2961fab7487
--- /dev/null
+++ b/data/deprecations/14-5-deprecation-vsa-announce-deprecation-of-vsa-filtering-calculation.yml
@@ -0,0 +1,13 @@
+- 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
+  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
diff --git a/data/deprecations/14-5-geo-deprecate-promote-db.yml b/data/deprecations/14-5-geo-deprecate-promote-db.yml
new file mode 100644
index 00000000000..ba2aa7dc032
--- /dev/null
+++ b/data/deprecations/14-5-geo-deprecate-promote-db.yml
@@ -0,0 +1,25 @@
+# This is a template for a feature deprecation
+# A deprecation typically occurs when a feature or capability is planned to be removed in a future release.
+# Deprecations should be announced at least two releases prior to removal.  Any breaking changes should only be done in major releases.
+#
+# Below is an example of what a single entry should look like, it's required attributes,
+# and what types we expect those attribute values to be.
+#
+# For more information please refer to the handbook documentation here:
+# {{LINK TBD}}
+#
+# Please delete this line and above before submitting your merge request.
+
+- name: "Removal of `promote-db` command from `gitlab-ctl`" # The name of the feature to be deprecated
+  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  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
+  removal_date: "2022-05-22"
diff --git a/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml
new file mode 100644
index 00000000000..29301ed3c47
--- /dev/null
+++ b/data/deprecations/14-5-geo-deprecate-promote-to-primary-node.yml
@@ -0,0 +1,25 @@
+# This is a template for a feature deprecation
+# A deprecation typically occurs when a feature or capability is planned to be removed in a future release.
+# Deprecations should be announced at least two releases prior to removal.  Any breaking changes should only be done in major releases.
+#
+# Below is an example of what a single entry should look like, it's required attributes,
+# and what types we expect those attribute values to be.
+#
+# For more information please refer to the handbook documentation here:
+# {{LINK TBD}}
+#
+# Please delete this line and above before submitting your merge request.
+
+- name: "Removal of `promote-to-primary-node` command from `gitlab-ctl`" # The name of the feature to be deprecated
+  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  announcement_date: "2021-11-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+  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
+  removal_date: "2022-05-22"
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
new file mode 100644
index 00000000000..8c7cde8a121
--- /dev/null
+++ b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml
@@ -0,0 +1,17 @@
+- name: "REST API Runner will not contain `paused`"
+  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
+  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
+  body: | # Do not modify this line, instead modify the lines below.
+    Runner REST API will not return `paused` as a status in GitLab 15.0.
+
+    Paused runners' status will only relate to runner contact status, such as:
+    `online`, `offline`, or `not_connected`. Status `paused` will not appear when the runner is
+    not active.
+
+    When checking if a runner is `paused`, API users are advised to check the boolean attribute
+    `active` to be `false` instead.
+  stage: Verify
+  tiers: [Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648
+  documentation_url: https://docs.gitlab.com/ee/api/runners.html
+  announcement_date: "2021-11-22"
diff --git a/data/deprecations/15-0-deprecate-sles-12sp2.yml b/data/deprecations/15-0-deprecate-sles-12sp2.yml
new file mode 100644
index 00000000000..fd5057bb8d3
--- /dev/null
+++ b/data/deprecations/15-0-deprecate-sles-12sp2.yml
@@ -0,0 +1,6 @@
+- name: "Deprecate 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
+  body: | # Do not modify this line, instead modify the lines below.
+    Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly.
diff --git a/data/deprecations/15-0-deprecation-versions-packagetype.yml b/data/deprecations/15-0-deprecation-versions-packagetype.yml
new file mode 100644
index 00000000000..4e1501b48ba
--- /dev/null
+++ b/data/deprecations/15-0-deprecation-versions-packagetype.yml
@@ -0,0 +1,12 @@
+- name: "Deprecate `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
+  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`.
+  stage: package
+  tiers: Free
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/327453
+
diff --git a/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml b/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml
new file mode 100644
index 00000000000..292dc4a14c0
--- /dev/null
+++ b/data/deprecations/15-0-remove-dependency-proxy-permissions-flag.yml
@@ -0,0 +1,11 @@
+- name: "Remove the `: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
+  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.
+  stage: package
+  tiers: Free
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/276777
diff --git a/data/deprecations/15-0-remove-package-pipelines-api.yml b/data/deprecations/15-0-remove-package-pipelines-api.yml
new file mode 100644
index 00000000000..ba69ed75e0f
--- /dev/null
+++ b/data/deprecations/15-0-remove-package-pipelines-api.yml
@@ -0,0 +1,11 @@
+- 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
+  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.
+  stage: package
+  tiers: Free
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/289956
diff --git a/data/deprecations/15-0-remove-pipelines-from-version-field.yml b/data/deprecations/15-0-remove-pipelines-from-version-field.yml
new file mode 100644
index 00000000000..6f4f8db55cd
--- /dev/null
+++ b/data/deprecations/15-0-remove-pipelines-from-version-field.yml
@@ -0,0 +1,14 @@
+- name: "Remove the `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
+  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.
+    - The `pipelines` field of a specific `version`. This returns only the pipelines associated with that single package version.
+
+    To mitigate possible performance problems, we will remove the `versions` field's `pipelines` field in milestone 15.0. Although you will no longer be able to get all pipelines for all versions of a package, you can still get the pipelines of a single version through the remaining `pipelines` field for that version.
+  stage: package
+  tiers: Free
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/342882
diff --git a/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml b/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
new file mode 100644
index 00000000000..eba37d1eb8f
--- /dev/null
+++ b/data/deprecations/deprecate-defaultMergeCommitMessageWithDescription-graphql.yml
@@ -0,0 +1,14 @@
+- name: "defaultMergeCommitMessageWithDescription GraphQL API field will be removed in GitLab 15.0" # 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
+  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
+  removal_date: # (optional - may be required in the future) YYYY-MM-DD format. This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed
diff --git a/data/deprecations/disable_strict_host_key_checking.yml b/data/deprecations/disable_strict_host_key_checking.yml
new file mode 100644
index 00000000000..62011795bb9
--- /dev/null
+++ b/data/deprecations/disable_strict_host_key_checking.yml
@@ -0,0 +1,12 @@
+- name: "Known host required for GitLab Runner SSH executor"
+  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
+  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.
+  stage: Verify
+  tiers: [Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192
+  documentation_url: https://docs.gitlab.com/runner/executors/ssh.html#security
diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb
index a037151c6ac..80b860b367f 100644
--- a/data/deprecations/templates/_deprecation_template.md.erb
+++ b/data/deprecations/templates/_deprecation_template.md.erb
@@ -17,13 +17,23 @@ sole discretion of GitLab Inc.
 <!-- vale off -->
 
 <!--
+DO NOT EDIT THIS PAGE DIRECTLY
+
 This page is automatically generated from the YAML files in `/data/deprecations` by the rake task
 located at `lib/tasks/gitlab/docs/compile_deprecations.rake`.
 
-Do not edit this page directly.
+For deprecation authors (usually Product Managers and Engineering Managers):
+
+- To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template.
+- For more information about authoring deprecations, check the the deprecation item guidance:
+  https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-deprecation-entry
+
+For deprecation reviewers (Technical Writers only):
 
-To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template,
-then run `bin/rake gitlab:docs:compile_deprecations`.
+- To update the deprecation doc, run: `bin/rake gitlab:docs:compile_deprecations`
+- To verify the deprecations doc is up to date, run: `bin/rake gitlab:docs:check_deprecations`
+- For more information about updating the deprecation doc, see the deprecation doc update guidance:
+  https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc
 -->
 <% if milestones.any? -%>
   <%- milestones.each do |milestone| %>
diff --git a/data/deprecations/templates/example.yml b/data/deprecations/templates/example.yml
index a11a6800a74..0aaa68e4bd8 100644
--- a/data/deprecations/templates/example.yml
+++ b/data/deprecations/templates/example.yml
@@ -6,7 +6,7 @@
 # and what types we expect those attribute values to be.
 #
 # For more information please refer to the handbook documentation here:
-# {{LINK TBD}}
+# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations
 #
 # Please delete this line and above before submitting your merge request.
 
@@ -19,11 +19,10 @@
 
     This area supports markdown.  Delete this entire comment and replace it with your markdown content.
 
-    Make sure to run `bin/rake gitlab:docs:compile_deprecations` locally before committing and pushing your changes.
-
-    When ready, assign to your tech writer to review and merge.
+    When ready, assign to your tech writer for review. When ready, they will run `bin/rake gitlab:docs:compile_deprecations` to update the deprecations doc, then merge.
 
     END OF BODY COMMENT -->
+# The following items are not published on the docs page, but may be used in the future.
   stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
   tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently.  e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
   issue_url: # (optional) This is a link to the deprecation issue in GitLab
diff --git a/data/deprecations/vsa_warning.png b/data/deprecations/vsa_warning.png
new file mode 100644
index 00000000000..7ee6c1e2343
--- /dev/null
+++ b/data/deprecations/vsa_warning.png