Add latest changes from gitlab-org/gitlab@16-3-stable-eev16.3.0-rc42

32 files changed, 180 insertions, 32 deletions

diff --git a/data/deprecations/  16_3_runner-terminationgracepriodseconds.yml b/data/deprecations/  16_3_runner-terminationgracepriodseconds.yml
new file mode 100644
index 00000000000..032032b2196
--- /dev/null
+++ b/data/deprecations/  16_3_runner-terminationgracepriodseconds.yml
@@ -0,0 +1,22 @@
+- title: "Deprecate `terminationGracePeriodSeconds` in the GitLab Runner Kubernetes executor" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters."
+  removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed
+  announcement_milestone: "16.3" # (required) The milestone when this feature was first announced as deprecated.
+  breaking_change: false # (required) Change to false if this is not a breaking change.
+  reporter: deastman # (required) GitLab username of the person reporting the change
+  stage: stage # (required) String value of the stage that the feature was created in. e.g., Growth
+  issue_url: "https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28165"  # (required) Link to the deprecation issue in GitLab
+  body: | # (required) Do not modify this line, instead modify the lines below.
+    The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes.html#other-configtoml-settings).
+
+#
+# OPTIONAL END OF SUPPORT FIELDS
+#
+# If an End of Support period applies, the announcement should be shared with GitLab Support
+# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
+#
+  end_of_support_milestone: 17.0 # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  #
+  # OTHER OPTIONAL FIELDS
+  #
+  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]
+  documentation_url: "https://docs.gitlab.com/runner/executors/kubernetes.html" # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/15-11-legacy-shell-escaping-quoting.yml b/data/deprecations/15-11-legacy-shell-escaping-quoting.yml
index 340be971e2c..cac8b17ac9a 100644
--- a/data/deprecations/15-11-legacy-shell-escaping-quoting.yml
+++ b/data/deprecations/15-11-legacy-shell-escaping-quoting.yml
@@ -13,7 +13,7 @@
 # If an End of Support period applies, the announcement should be shared with GitLab Support
 # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
 #
-  end_of_support_milestone: 17.9  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   #
   # OTHER OPTIONAL FIELDS
   #
diff --git a/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml b/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml
index b93e2513c68..1bb7947739f 100644
--- a/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml
+++ b/data/deprecations/15-6-deprecate-config-fields-runner-helm-chart.yml
@@ -7,4 +7,4 @@
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/379064  # (required) Link to the deprecation issue in GitLab
   body: |  # (required) Do not modify this line, instead modify the lines below.
     From GitLab 13.6, users can [specify any runner configuration in the GitLab Runner Helm chart](https://docs.gitlab.com/runner/install/kubernetes.html). When we implemented this feature, we deprecated values in the GitLab Helm Chart configuration that were specific to GitLab Runner. These fields are deprecated and we plan to remove them in v1.0 of the GitLab Runner Helm chart.
-  end_of_support_milestone: "16.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
diff --git a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml
index 786132b19b5..81c56d914d2 100644
--- a/data/deprecations/15-6-deprecate-post-api-v4-runner.yml
+++ b/data/deprecations/15-6-deprecate-post-api-v4-runner.yml
@@ -23,6 +23,6 @@
     - `--maintenance-note`
 
     This change is a breaking change. You should [create a runner in the UI](../ci/runners/register_runner.md) to add configurations, and use the authentication token in the `gitlab-runner register` command instead.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   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]
   documentation_url: https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner  # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml b/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml
index a01c995ae4f..0882d8ac894 100644
--- a/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml
+++ b/data/deprecations/15-6-deprecate-runner-reg-token-helm.yml
@@ -14,4 +14,4 @@
     The work is planned in [this epic](https://gitlab.com/groups/gitlab-org/-/epics/7633).
 
     From GitLab 17.0 and later, the methods to register runners introduced by the new GitLab Runner token architecture will be the only supported methods.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
diff --git a/data/deprecations/15-6-deprecate-runner-register-command.yml b/data/deprecations/15-6-deprecate-runner-register-command.yml
index 81e0f46078f..6443580d8f8 100644
--- a/data/deprecations/15-6-deprecate-runner-register-command.yml
+++ b/data/deprecations/15-6-deprecate-runner-register-command.yml
@@ -21,4 +21,4 @@
     - `--maintenance-note`
 
     This change is a breaking change. You should [create a runner in the UI](../ci/runners/register_runner.md) to add configurations, and use the authentication token in the `gitlab-runner register` command instead.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
diff --git a/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml b/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml
index 61b117feb35..c4910f72887 100644
--- a/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml
+++ b/data/deprecations/15-6-deprecate-runner-register-token-k8s-operator.yml
@@ -17,7 +17,7 @@
     - `--tag-list`
 
     This change is a breaking change. You should use an [authentication token](../ci/runners/register_runner.md) in the `gitlab-runner register` command instead.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   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]
   documentation_url: https://docs.gitlab.com/runner/install/operator.html#install-the-kubernetes-operator  # (optional) This is a link to the current documentation page
   image_url:  # (optional) This is a link to a thumbnail image depicting the feature
diff --git a/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml b/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml
index 3a9690e0836..d617b5de531 100644
--- a/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml
+++ b/data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml
@@ -21,6 +21,6 @@
     This new architecture introduces a new method for registering runners and will eliminate the legacy
     [runner registration token](https://docs.gitlab.com/ee/security/token_overview.html#runner-registration-tokens).
     From GitLab 17.0 and later, the runner registration methods implemented by the new GitLab Runner token architecture will be the only supported methods.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   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]
   documentation_url: https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner  # (optional) This is a link to the current documentation page
diff --git a/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml b/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml
index 0b52fa4d72d..a8b425d2dc4 100644
--- a/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml
+++ b/data/deprecations/15-7-deprecate-gitlab-runner-exec-cmd.yml
@@ -7,7 +7,7 @@
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/385235  # (required) Link to the deprecation issue in GitLab
   body: |  # (required) Do not modify this line, instead modify the lines below.
     The [`gitlab-runner exec`](https://docs.gitlab.com/runner/commands/#gitlab-runner-exec) command is deprecated and will be fully removed from GitLab Runner in 16.0. The `gitlab-runner exec` feature was initially developed to provide the ability to validate a GitLab CI pipeline on a local system without needing to commit the updates to a GitLab instance. However, with the continued evolution of GitLab CI, replicating all GitLab CI features into `gitlab-runner exec` was no longer viable. Pipeline syntax and validation [simulation](https://docs.gitlab.com/ee/ci/pipeline_editor/#simulate-a-cicd-pipeline) are available in the GitLab pipeline editor.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
 
 
   # OTHER OPTIONAL FIELDS
diff --git a/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml b/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml
index 921bea87b38..64ec200f207 100644
--- a/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml
+++ b/data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml
@@ -8,7 +8,7 @@
   body: |  # (required) Do not modify this line, instead modify the lines below.
     The `gitlab.kas.metrics.port` has been deprecated in favor of the new `gitlab.kas.observability.port` configuration field for the [GitLab Helm Chart](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/2839).
     This port is used for much more than just metrics, which warranted this change to avoid confusion in configuration.
-  end_of_support_milestone: "16.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
 
 
   # OTHER OPTIONAL FIELDS
diff --git a/data/deprecations/15-7-deprecate-shimo-integration.yml b/data/deprecations/15-7-deprecate-shimo-integration.yml
index aa92bdf943a..f9437a9f44e 100644
--- a/data/deprecations/15-7-deprecate-shimo-integration.yml
+++ b/data/deprecations/15-7-deprecate-shimo-integration.yml
@@ -14,7 +14,7 @@
 # If an End of Support period applies, the announcement should be shared with GitLab Support
 # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
 #
-  end_of_support_milestone: "16.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   #
   # OTHER OPTIONAL FIELDS
   #
diff --git a/data/deprecations/15-7-deprecate-zentao-integration.yml b/data/deprecations/15-7-deprecate-zentao-integration.yml
index 332aaefdf04..72da0544ac3 100644
--- a/data/deprecations/15-7-deprecate-zentao-integration.yml
+++ b/data/deprecations/15-7-deprecate-zentao-integration.yml
@@ -14,7 +14,7 @@
 # If an End of Support period applies, the announcement should be shared with GitLab Support
 # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
 #
-  end_of_support_milestone: "16.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   #
   # OTHER OPTIONAL FIELDS
   #
diff --git a/data/deprecations/15-7-enable-period-in-terraform-state-name.yml b/data/deprecations/15-7-enable-period-in-terraform-state-name.yml
index f56505ed2bc..19c32b1c9ef 100644
--- a/data/deprecations/15-7-enable-period-in-terraform-state-name.yml
+++ b/data/deprecations/15-7-enable-period-in-terraform-state-name.yml
@@ -17,6 +17,6 @@
       1. Run your Terraform commands.
 
     To use the full state name, including the period, [migrate to the full state file](https://docs.gitlab.com/ee/user/infrastructure/iac/terraform_state.html#migrate-to-a-gitlab-managed-terraform-state).
-  end_of_support_milestone: 16.0
+  end_of_support_milestone:
   tiers: [Free, Silver, Gold, Core, Premium, Ultimate]
   documentation_url: 'https://docs.gitlab.com/ee/user/infrastructure/iac/troubleshooting.html#troubleshooting-terraform-state'
diff --git a/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml b/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml
index 0097f59d1f9..77982b66bc5 100644
--- a/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml
+++ b/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml
@@ -1,13 +1,13 @@
 - title: "Automatic backup upload using Openstack Swift and Rackspace APIs"  # (required) The name of the feature to be deprecated
   announcement_milestone: "15.8"  # (required) The milestone when this feature was first announced as deprecated.
   removal_milestone: "15.10"  # (required) The milestone when this feature is planned to be removed
-  end_of_support_milestone: "15.10"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   breaking_change: true  # (required) If this deprecation is a breaking change, set this value to true
   reporter: sranasinghe  # (required) GitLab username of the person reporting the deprecation
   stage: Enablement  # (required) String value of the stage that the feature was created in. e.g., Growth
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387976  # (required) Link to the deprecation issue in GitLab
   body: |  # (required) Do not modify this line, instead modify the lines below.
-    We are deprecating support for [uploading backups to remote storage](https://docs.gitlab.com/ee/raketasks/backup_gitlab.html#upload-backups-to-a-remote-cloud-storage) using Openstack Swift and Rackspace APIs. The support for these APIs depends on third-party libraries that are no longer actively maintained and have not been updated for  Ruby 3. GitLab is switching over to Ruby 3 prior to EOL of Ruby 2 in order to stay up to date on security patches.
+    We are deprecating support for [uploading backups to remote storage](https://docs.gitlab.com/ee/raketasks/backup_gitlab.html#upload-backups-to-a-remote-cloud-storage) using Openstack Swift and Rackspace APIs. The support for these APIs depends on third-party libraries that are no longer actively maintained and have not been updated for Ruby 3. GitLab is switching over to Ruby 3 prior to EOL of Ruby 2 in order to stay up to date on security patches.
 
     - If you're using OpenStack, you need to change you configuration to use the S3 API instead of Swift.
     - If you're using Rackspace storage, you need to switch to a different provider or manually upload the backup file after the backup task is complete.
diff --git a/data/deprecations/15-8-deprecate-slack-notifications-integration.yml b/data/deprecations/15-8-deprecate-slack-notifications-integration.yml
index 8ac12d64a77..33f9e6ce3a7 100644
--- a/data/deprecations/15-8-deprecate-slack-notifications-integration.yml
+++ b/data/deprecations/15-8-deprecate-slack-notifications-integration.yml
@@ -19,7 +19,7 @@
 # If an End of Support period applies, the announcement should be shared with GitLab Support
 # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
 #
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   #
   # OTHER OPTIONAL FIELDS
   #
diff --git a/data/deprecations/15-8-third-party-registries.yml b/data/deprecations/15-8-third-party-registries.yml
index 83380581505..c4eddf2e64f 100644
--- a/data/deprecations/15-8-third-party-registries.yml
+++ b/data/deprecations/15-8-third-party-registries.yml
@@ -21,4 +21,4 @@
 # If an End of Support period applies, the announcement should be shared with GitLab Support
 # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
 #
-  end_of_support_milestone: 16.0  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
diff --git a/data/deprecations/15-9-deprecate-ci-pre-clone-script.yml b/data/deprecations/15-9-deprecate-ci-pre-clone-script.yml
index bb1dcc9412a..0d0aa6f0f04 100644
--- a/data/deprecations/15-9-deprecate-ci-pre-clone-script.yml
+++ b/data/deprecations/15-9-deprecate-ci-pre-clone-script.yml
@@ -13,7 +13,7 @@
   # If an End of Support period applies, the announcement should be shared with GitLab Support
   # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
   #
-  end_of_support_milestone: 16.0  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   #
   # OTHER OPTIONAL FIELDS
   #
diff --git a/data/deprecations/15-9-insecure-ci-job-token.yml b/data/deprecations/15-9-insecure-ci-job-token.yml
index 5664ffee008..f807c337de8 100644
--- a/data/deprecations/15-9-insecure-ci-job-token.yml
+++ b/data/deprecations/15-9-insecure-ci-job-token.yml
@@ -18,6 +18,8 @@
     In 17.0, we plan to remove the **Limit** setting completely, and set the **Allow access** setting to enabled for all projects. This change ensures a higher level of security between projects. If you currently use the **Limit** setting, you should update your projects to use the **Allow access** setting instead. If other projects access your project with a job token, you must add them to the **Allow access** allowlist.
 
     To prepare for this change, users on GitLab.com or self-managed GitLab 15.9 or later can enable the **Allow access** setting now and add the other projects. It will not be possible to disable the setting in 17.0 or later.
+
+    In 16.3, the names of these settings were changed to clarify their meanings: the deprecated **Limit CI_JOB_TOKEN access** setting is now called **Limit access _from_ this project**, and the newer **Allow access to this project with a CI_JOB_TOKEN** setting is now called **Limit access _to_ this project**.
   #
   # OPTIONAL END OF SUPPORT FIELDS
   #
diff --git a/data/deprecations/16-0-deprecate-omnibus-grafana.yml b/data/deprecations/16-0-deprecate-omnibus-grafana.yml
index 93fd5c54071..61c04e9f042 100644
--- a/data/deprecations/16-0-deprecate-omnibus-grafana.yml
+++ b/data/deprecations/16-0-deprecate-omnibus-grafana.yml
@@ -18,6 +18,6 @@
 
     In GitLab versions 16.0 to 16.2, you can still [re-enable the bundled Grafana](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#temporary-workaround).
     However, enabling the bundled Grafana will no longer work from GitLab 16.3.
-  end_of_support_milestone: 16.3
+  end_of_support_milestone:
   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]
   documentation_url: https://docs.gitlab.com/omnibus/settings/grafana.html
diff --git a/data/deprecations/16-0-deprecate-postgresql-13.yml b/data/deprecations/16-0-deprecate-postgresql-13.yml
index 779a3074f39..828f9e64ab8 100644
--- a/data/deprecations/16-0-deprecate-postgresql-13.yml
+++ b/data/deprecations/16-0-deprecate-postgresql-13.yml
@@ -19,7 +19,7 @@
 # If an End of Support period applies, the announcement should be shared with GitLab Support
 # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
 #
-  end_of_support_milestone: 17.0
+  end_of_support_milestone:
   #
   # OTHER OPTIONAL FIELDS
   #
diff --git a/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml b/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml
index 6e892a02a9b..c4c2435ba6f 100644
--- a/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml
+++ b/data/deprecations/16-1-windows-cmd-runner-shell-executor.yml
@@ -9,5 +9,5 @@
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/414864 # (required) Link to the deprecation issue in GitLab
   body: |  # (required) Do not modify this line, instead modify the lines below.
     In GitLab 11.11 the Windows Batch executor, the CMD shell was deprecated in GitLab Runner in favor of PowerShell. Since then, the CMD shell has continued to be supported in GitLab Runner. However this has resulted in additional complexity for both the engineering team and customers using the Runner on Windows. We plan to fully remove support for Windows CMD from GitLab Runner in 17.0. Customers should plan to use PowerShell when using the runner on Windows with the shell executor. Customers can provide feedback or ask questions in the removal issue, [issue 29479](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29479).
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
   end_of_support_date: "2024-05-22" # (optional) The date of the milestone release when support for this feature will end.
diff --git a/data/deprecations/  16-2-cirunner_fields.yml b/data/deprecations/16-2-cirunner_fields.yml
index 1d43ed1b7c9..c39ef9e3205 100644
--- a/data/deprecations/  16-2-cirunner_fields.yml
+++ b/data/deprecations/16-2-cirunner_fields.yml
@@ -9,5 +9,5 @@
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/41518  # (required) Link to the deprecation issue in GitLab
   body: |  # (required) Do not modify this line, instead modify the lines below.
     These fields (`architectureName`, `ipAddress`, `platformName`, `revision`, `version`) are now deprecated from the [GraphQL `CiRunner`](https://docs.gitlab.com/ee/api/graphql/reference/#cirunner) type as they are duplicated with the introduction of runner managers grouped within a runner configuration.
-  end_of_support_milestone: "17.0"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
-  end_of_support_date: "2024-05-22"  # (optional) The date of the milestone release when support for this feature will end.
+  end_of_support_milestone:  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  end_of_support_date:  # (optional) The date of the milestone release when support for this feature will end.
diff --git a/data/deprecations/16-2-graphql-board-list-totalweight.yml b/data/deprecations/16-2-graphql-board-list-totalweight.yml
new file mode 100644
index 00000000000..0362c30246a
--- /dev/null
+++ b/data/deprecations/16-2-graphql-board-list-totalweight.yml
@@ -0,0 +1,11 @@
+- title: "GraphQL field `totalWeight` is deprecated"
+  announcement_milestone: "16.3"
+  removal_milestone: "17.0"
+  breaking_change: true
+  reporter: tmike
+  stage: Plan
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/416219
+  body: |  # (required) Do not modify this line, instead modify the lines below.
+    You can use GraphQL to query the total weight of issues in an issue board. However, the `totalWeight` field is limited to the maximum size 2147483647. As a result, `totalWeight` is deprecated and will be removed in GitLab 17.0.
+
+    Use `totalIssueWeight` instead, introduced in GitLab 16.2.
diff --git a/data/deprecations/16-3-deprecate-twitter-saas.yml b/data/deprecations/16-3-deprecate-twitter-saas.yml
new file mode 100644
index 00000000000..3c0150ec65c
--- /dev/null
+++ b/data/deprecations/16-3-deprecate-twitter-saas.yml
@@ -0,0 +1,10 @@
+- title: "Twitter OmniAuth login option is removed from GitLab.com"
+  removal_milestone: "16.3"
+  announcement_milestone: "16.3"
+  breaking_change: true
+  reporter: jessieay
+  stage: Manage
+  issue_url: https://gitlab.com/gitlab-com/Product/-/issues/11417
+  body: |  # (required) Do not modify this line, instead modify the lines below.
+    Twitter OAuth 1.0a OmniAuth is being deprecated and removed on GitLab.com in GitLab 16.3 due to low use, lack of gem support, and the lack of a functional sign-in option for this feature. If you sign into GitLab.com with Twitter, you can sign in with a password or another [supported OmniAuth provider](https://gitlab.com/users/sign_in).
+  documentation_url: https://docs.gitlab.com/ee/integration/twitter.html
diff --git a/data/deprecations/16-3-deprecate-twitter-sm.yml b/data/deprecations/16-3-deprecate-twitter-sm.yml
new file mode 100644
index 00000000000..562fce1ff1c
--- /dev/null
+++ b/data/deprecations/16-3-deprecate-twitter-sm.yml
@@ -0,0 +1,10 @@
+- title: "Twitter OmniAuth login option is deprecated from self-managed GitLab"
+  removal_milestone: "17.0"
+  announcement_milestone: "16.3"
+  breaking_change: true
+  reporter: jessieay
+  stage: Manage
+  issue_url: https://gitlab.com/gitlab-com/Product/-/issues/11417
+  body: |  # (required) Do not modify this line, instead modify the lines below.
+    Twitter OAuth 1.0a OmniAuth is deprecated and will be removed for self-managed GitLab instances in GitLab 17.0 due to low use and lack of gem support. Use [another supported OmniAuth provider](https://docs.gitlab.com/ee/integration/omniauth.html#supported-providers) instead.
+  documentation_url: https://docs.gitlab.com/ee/integration/twitter.html
diff --git a/data/deprecations/16-3-vulnerabilitytype-hassolutions.yml b/data/deprecations/16-3-vulnerabilitytype-hassolutions.yml
new file mode 100644
index 00000000000..b8acba158ae
--- /dev/null
+++ b/data/deprecations/16-3-vulnerabilitytype-hassolutions.yml
@@ -0,0 +1,11 @@
+- title: "Deprecate field `hasSolutions` from GraphQL VulnerabilityType"
+  removal_milestone: "17.0"
+  announcement_milestone: "16.3"
+  breaking_change: true
+  reporter: thiagocsf
+  stage: Govern
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/414895
+  body: |  # (required) Do not modify this line, instead modify the lines below.
+    The GraphQL field `Vulnerability.hasSolutions` is deprecated and will be removed in GitLab 17.0.
+    Use `Vulnerability.hasRemediations` instead.
+  documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#vulnerability
diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb
index 5261806f49a..2e0d2696f0f 100644
--- a/data/deprecations/templates/_deprecation_template.md.erb
+++ b/data/deprecations/templates/_deprecation_template.md.erb
@@ -56,13 +56,13 @@ For deprecation reviewers (Technical Writers only):
 ### <%= deprecation["title"] %>
 
 <div class="deprecation-notes">
-- Announced in: GitLab <span class="milestone"><%= deprecation["announcement_milestone"]%></span>
+- Announced in GitLab <span class="milestone"><%= deprecation["announcement_milestone"]%></span>
 <% if deprecation["end_of_support_milestone"] -%>
-- End of Support: GitLab <span class="milestone"><%= deprecation["end_of_support_milestone"]%></span>
+- End of Support in GitLab <span class="milestone"><%= deprecation["end_of_support_milestone"]%></span>
+<% end -%>
+<% if deprecation["removal_milestone"] -%>
+- Removal in GitLab <span class="milestone"><%= deprecation["removal_milestone"]%></span><% if deprecation["breaking_change"] -%> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change))<% end %>
 <% end -%>
-<% if deprecation["breaking_change"] -%>
-- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change).
-<%- end -%>
 <% if deprecation["issue_url"] -%>
 - To discuss this change or learn more, see the [deprecation issue](<%= deprecation["issue_url"]%>).
 <%- end -%>
diff --git a/data/whats_new/202204210001_14_10.yml b/data/whats_new/202204210001_14_10.yml
index c4028662f59..029dd19bcc7 100644
--- a/data/whats_new/202204210001_14_10.yml
+++ b/data/whats_new/202204210001_14_10.yml
@@ -5,7 +5,7 @@
   self-managed: true
   gitlab-com: true
   available_in: [Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/compliance/compliance_report/'
+  documentation_link: 'https://docs.gitlab.com/ee/user/compliance/compliance_center/'
   image_url: 'https://about.gitlab.com/images/14_10/manage_compliance_report_individual_violation.png'
   published_at: 2022-04-22
   release: 14.10
diff --git a/data/whats_new/202303220001_15_10.yml b/data/whats_new/202303220001_15_10.yml
index d2598fc8e2d..cefd469fe41 100644
--- a/data/whats_new/202303220001_15_10.yml
+++ b/data/whats_new/202303220001_15_10.yml
@@ -38,7 +38,7 @@
   self-managed: true
   gitlab-com: true
   available_in: [Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/compliance/compliance_report/#compliance-frameworks-report'
+  documentation_link: 'https://docs.gitlab.com/ee/user/compliance/compliance_center/#compliance-frameworks-report'
   image_url: 'https://about.gitlab.com/images/15_10/govern-compliance-framework-report.png'
   published_at: 2023-03-22
   release: 15.10
diff --git a/data/whats_new/202304220001_15_11.yml b/data/whats_new/202304220001_15_11.yml
index 38e5d8bef31..b9281c5a99e 100644
--- a/data/whats_new/202304220001_15_11.yml
+++ b/data/whats_new/202304220001_15_11.yml
@@ -22,7 +22,7 @@
   self-managed: true
   gitlab-com: true
   available_in: [Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/compliance/compliance_report/#compliance-frameworks-report'
+  documentation_link: 'https://docs.gitlab.com/ee/user/compliance/compliance_center/#compliance-frameworks-report'
   image_url: 'https://about.gitlab.com/images/15_11/govern-compliance-frameworks-report-management.png'
   published_at: 2023-04-22
   release: 15.11
diff --git a/data/whats_new/202306220001_16_1.yml b/data/whats_new/202306220001_16_1.yml
index cd14713143a..52a0b57d209 100644
--- a/data/whats_new/202306220001_16_1.yml
+++ b/data/whats_new/202306220001_16_1.yml
@@ -59,8 +59,8 @@
 
     [Learn more](https://about.gitlab.com/dedicated/) about GitLab Dedicated today.
   stage: Platforms
-  self-managed: true
-  gitlab-com: false
+  self-managed: false
+  gitlab-com: true
   available_in: [Ultimate]
   documentation_link: https://docs.gitlab.com/ee/subscriptions/gitlab_dedicated/
   image_url: https://about.gitlab.com/images/16_1/gitlab-dedicated.png
diff --git a/data/whats_new/202307220001_16_2.yml b/data/whats_new/202307220001_16_2.yml
new file mode 100644
index 00000000000..5d330c01642
--- /dev/null
+++ b/data/whats_new/202307220001_16_2.yml
@@ -0,0 +1,82 @@
+- name: All new rich text editor experience
+  description: |  # Do not modify this line, instead modify the lines below.
+    GitLab 16.2 features an all-new rich text editing experience! This new capability is available for everyone, as an alternative to the existing Markdown editing experience.
+
+    For many, using the plain text editor for comments or descriptions is a barrier to collaboration. Remembering the syntax for image references or working with long tables can be tedious even for those who are relatively experienced with the syntax. The rich text editor aims to break down these barriers by providing a "what you see is what you get" editing experience and an extensible foundation on which we can build custom editing interfaces for things like diagrams, content embeds, media management, and more.
+
+    The rich text editor is now available in all issues, epics and merge requests. We plan to make it available in more places across GitLab soon. You can follow our progress [here](https://gitlab.com/groups/gitlab-org/-/epics/10378).
+
+    We are proud of the new editing experience and can't wait to see what you think. Please try the new rich text editor and let us know about your experience in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/416293).
+  stage: plan
+  self-managed: true
+  gitlab-com: true
+  available_in: [Free, Premium, Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/rich_text_editor.html
+  image_url: https://about.gitlab.com/images/16_2/knowledge-rich-text-editor.gif
+  published_at: 2023-07-22
+  release: 16.2
+
+- name: Support for Keyless Signing with Cosign
+  description: |  # Do not modify this line, instead modify the lines below.
+    Properly storing, rotating, and managing signing keys can be difficult and typically requires the overhead of managing a separate Key Management System (KMS). GitLab now supports keyless signing through a native integration with the Sigstore Cosign tool which allows for easy, convenient, and secure signing within the GitLab CI/CD pipeline.  Signing is done using a very short-lived signing key. The key is generated through a token obtained from the GitLab server using the OIDC identity of the user who ran the pipeline. This token includes unique claims that certify the token was generated by a CI/CD pipeline.
+
+    To begin using keyless signing for your build artifacts, container images, and packages, users only need to add a few lines to their CI/CD file as [shown in our documentation](https://docs.gitlab.com/ee/ci/yaml/signing_examples.html).
+  stage: govern
+  self-managed: false
+  gitlab-com: true
+  available_in: [Free, Premium, Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/ci/yaml/signing_examples.html
+  image_url: https://about.gitlab.com/images/16_2/govern-keyless-signing.png
+  published_at: 2023-07-22
+  release: 16.2
+
+- name: Command palette
+  description: |  # Do not modify this line, instead modify the lines below.
+    If you're a power user, using the keyboard to navigate and take action can be frustrating. Now, a new command palette helps you use the keyboard to get more done.
+
+    To enable the command palette, open the left sidebar and click  **Search GitLab** (🔍) or use the <kbd>/</kbd> key.
+
+    Type one of the special characters:
+
+    * <kbd>></kbd> - Create a new object or find a menu item
+    * <kbd>@</kbd> - Search for a user
+    * <kbd>:</kbd> - Search for a project
+    * <kbd>/</kbd> - Search for project files in the default repository branch
+  stage: manage
+  self-managed: true
+  gitlab-com: true
+  available_in: [Free, Premium, Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/search/command_palette.html
+  image_url: https://img.youtube.com/vi/CXeHrMrJY6g/hqdefault.jpg
+  published_at: 2023-07-22
+  release: 16.2
+
+- name: New customization layer for the Value Streams Dashboard
+  description: |  # Do not modify this line, instead modify the lines below.
+    We added a new configuration file to the [Value Streams Dashboard](https://youtu.be/EA9Sbks27g4) for easier customization of the dashboard's data and appearance. In this file you can define various settings and parameters, such as title, description, and number of panels and filters. The file is schema-driven and managed with version control systems like Git. This enables tracking and maintaining a history of configuration changes, reverting to previous versions if necessary, and collaborating effectively with team members.
+
+    The new configuration also includes the option to filter the metrics by labels. You can adjust the [metrics comparison panel](https://about.gitlab.com/blog/2023/06/12/getting-started-with-value-streams-dashboard/) based on your areas of interest, filter out irrelevant information, and focus on the data that is most relevant to your analysis or decision-making process.
+  stage: plan
+  self-managed: true
+  gitlab-com: true
+  available_in: [Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/analytics/value_streams_dashboard.html
+  image_url: https://img.youtube.com/vi/4qDAHCxCfik/hqdefault.jpg
+  published_at: 2023-07-22
+  release: 16.2
+
+- name: Interactive diff suggestions in merge requests
+  description: |  # Do not modify this line, instead modify the lines below.
+    When you suggest changes in a merge request, you can now edit your suggestions more quickly. In a comment, switch to the rich text editor and use the UI to move up and down the lines of text. With this change, you can view your suggestions exactly as they will appear when the comment is posted.
+
+    The rich text editor is a new way of editing in GitLab. It's available in merge requests, but also available alongside the plain text editor in issues and epics.
+
+    We plan to have the rich text editor available in more areas of GitLab soon and we are actively working on that. You can follow our progress [here](https://gitlab.com/groups/gitlab-org/-/epics/10378).
+  stage: plan
+  self-managed: true
+  gitlab-com: true
+  available_in: [Free, Premium, Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/project/merge_requests/reviews/suggestions.html#using-the-rich-text-editor
+  image_url: https://about.gitlab.com/images/16_2/knowledge-suggest-changes.png
+  published_at: 2023-07-22
+  release: 16.2