Fix pipeline failures

- https://gitlab.com/gitlab-org/gitlab/-/jobs/2112193619#L51
- https://gitlab.com/gitlab-org/gitlab/-/jobs/2112193619#L55
- https://gitlab.com/gitlab-org/gitlab/-/jobs/2112193619#L59
- https://gitlab.com/gitlab-org/gitlab/-/jobs/2112193619#L63

doc/update/index.md

@@ -364,6 +364,15 @@ or [init scripts](upgrading_from_source.md#configure-sysv-init-script) by [follo
 
   For more information, refer to [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/331823).
 
+### 14.4.4
+
+- For [zero-downtime upgrades](zero_downtime.md) on a GitLab cluster with separate Web and API nodes, you need to enable the `paginated_tree_graphql_query` [feature flag](../api/feature_flags.md) _before_ upgrading GitLab Web nodes to 14.4.
+  This is because we [enabled `paginated_tree_graphql_query by default in 14.4](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70913/diffs), so if GitLab UI is on 14.4 and its API is on 14.3, the frontend will have this feature enabled but the backend will have it disabled. This will result in the following error:
+
+  ```shell
+  bundle.esm.js:63 Uncaught (in promise) Error: GraphQL error: Field 'paginatedTree' doesn't exist on type 'Repository' 
+  ```
+
 ### 14.4.0
 
 - Git 2.33.x and later is required. We recommend you use the

doc/update/zero_downtime.md

@@ -41,6 +41,8 @@ you check the release posts of any releases between your current and target
 version just in case they include any migrations that may require you to upgrade
 one release at a time. 
 
+We also recommend you verify the [version specific upgrading instructions](index.md#version-specific-upgrading-instructions) relevant to your [upgrade path](index.md#upgrade-paths).
+
 Some releases may also include so called "background migrations". These
 migrations are performed in the background by Sidekiq and are often used for
 migrating data. Background migrations are only added in the monthly releases.