Add latest changes from gitlab-org/gitlab@master

5 files changed, 31 insertions, 14 deletions

diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index b661bcd6746..4c6af23849d 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -118,9 +118,6 @@ sequenceDiagram
     participant GitLab instance
     participant Version Application
     GitLab instance->>Version Application: Is there a version update?
-    loop Version Check
-        Version Application->>Version Application: Record version info
-    end
     Version Application->>GitLab instance: Response (PNG/SVG)
 ```
 
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index f5198c54136..6b14d394e3a 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -29313,6 +29313,17 @@ Represents the notifications widget.
 | <a id="workitemwidgetnotificationssubscribed"></a>`subscribed` | [`Boolean!`](#boolean) | Whether the current user is subscribed to notifications on the work item. |
 | <a id="workitemwidgetnotificationstype"></a>`type` | [`WorkItemWidgetType`](#workitemwidgettype) | Widget type. |
 
+### `WorkItemWidgetParticipants`
+
+Represents a participants widget.
+
+#### Fields
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="workitemwidgetparticipantsparticipants"></a>`participants` | [`UserCoreConnection`](#usercoreconnection) | Participants in the work item. (see [Connections](#connections)) |
+| <a id="workitemwidgetparticipantstype"></a>`type` | [`WorkItemWidgetType`](#workitemwidgettype) | Widget type. |
+
 ### `WorkItemWidgetProgress`
 
 Represents a progress widget.
@@ -32296,6 +32307,7 @@ Type of a work item widget.
 | <a id="workitemwidgettypemilestone"></a>`MILESTONE` | Milestone widget. |
 | <a id="workitemwidgettypenotes"></a>`NOTES` | Notes widget. |
 | <a id="workitemwidgettypenotifications"></a>`NOTIFICATIONS` | Notifications widget. |
+| <a id="workitemwidgettypeparticipants"></a>`PARTICIPANTS` | Participants widget. |
 | <a id="workitemwidgettypeprogress"></a>`PROGRESS` | Progress widget. |
 | <a id="workitemwidgettyperequirement_legacy"></a>`REQUIREMENT_LEGACY` | Requirement Legacy widget. |
 | <a id="workitemwidgettyperolledup_dates"></a>`ROLLEDUP_DATES` | Rolledup Dates widget. |
@@ -33983,6 +33995,7 @@ Implementations:
 - [`WorkItemWidgetMilestone`](#workitemwidgetmilestone)
 - [`WorkItemWidgetNotes`](#workitemwidgetnotes)
 - [`WorkItemWidgetNotifications`](#workitemwidgetnotifications)
+- [`WorkItemWidgetParticipants`](#workitemwidgetparticipants)
 - [`WorkItemWidgetProgress`](#workitemwidgetprogress)
 - [`WorkItemWidgetRequirementLegacy`](#workitemwidgetrequirementlegacy)
 - [`WorkItemWidgetRolledupDates`](#workitemwidgetrolledupdates)
diff --git a/doc/development/pipelines/internals.md b/doc/development/pipelines/internals.md
index 16d0bfdfa30..020962e8425 100644
--- a/doc/development/pipelines/internals.md
+++ b/doc/development/pipelines/internals.md
@@ -46,7 +46,6 @@ Here's a list of where we're using this right now, and should try to move away
 from using `$FORCE_GITLAB_CI`.
 
 - [JiHu validation pipeline](https://about.gitlab.com/handbook/ceo/chief-of-staff-team/jihu-support/jihu-validation-pipelines.html)
-- [Gitaly downstream GitLab pipeline](https://gitlab.com/gitlab-org/gitaly/-/issues/4615)
 
 See the next section for how we can enable pipelines without using
 `$FORCE_GITLAB_CI`.
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index bad3a2b09e7..982c00d264e 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -79,13 +79,22 @@ available, though the exact requirements [depend on the number of users](../admi
 We highly recommend using at least the minimum PostgreSQL versions (as specified in
 the following table) as these were used for development and testing:
 
-| GitLab version | Minimum PostgreSQL version |
-|----------------|----------------------------|
-| 13.0           | 11                         |
-| 14.0           | 12.7                       |
-| 15.0           | 12.10                      |
-| 16.0           | 13.6                       |
-| 17.0 (planned) | 14.8                       |
+| GitLab version | Minimum PostgreSQL version<sup>1</sup> | Maximum PostgreSQL version<sup>2</sup> |
+|----------------|----------------------------------------|----------------------------------------|
+| 13.0           | 11                                     | <sup>2</sup>                                       |
+| 14.0           | 12.7                                   | <sup>2</sup>                                       |
+| 15.0           | 12.10                                  | 13.x (14.x<sup>3</sup>)                |
+| 16.0           | 13.6                                   | 15.x<sup>4</sup>                       |
+| 17.0 (planned) | 14.9                                   | 15.x<sup>4</sup>                       |
+
+1. PostgreSQL minor release upgrades (for example 14.8 to 14.9) [include only bug and security fixes](https://www.postgresql.org/support/versioning/).
+   Patch levels in this table are not prescriptive. Always deploy the most recent patch level
+   to avoid [known bugs in PostgreSQL that might be triggered by GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/364763).
+1. If you want to run a later major release of PostgreSQL than the specified minimum
+   [check if a more recent version shipped with Linux package (Omnibus) GitLab](http://gitlab-org.gitlab.io/omnibus-gitlab/licenses.html).
+   `postgresql-new` is a later version that's definitely supported.
+1. PostgreSQL 14.x [tested against GitLab 15.11 only](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/114624).
+1. [Tested against GitLab 16.1 and later](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119344).
 
 You must also ensure the following extensions are loaded into every
 GitLab database. [Read more about this requirement, and troubleshooting](postgresql_extensions.md).
@@ -135,7 +144,7 @@ exclusive use of GitLab. Do not make direct changes to the database, schemas, us
 properties except when following procedures in the GitLab documentation or following the directions
 of GitLab Support or other GitLab engineers.
 
-- The main GitLab application currently uses three schemas:
+- The main GitLab application uses three schemas:
 
   - The default `public` schema
   - `gitlab_partitions_static` (automatically created)
@@ -253,7 +262,7 @@ The requirements for Redis are as follows:
 
 ## Sidekiq
 
-Sidekiq processes the background jobs with a multithreaded process.
+Sidekiq processes the background jobs with a multi-threaded process.
 This process starts with the entire Rails stack (200 MB+) but it can grow over time due to memory leaks.
 On a very active server (10,000 billable users) the Sidekiq process can use 1 GB+ of memory.
 
diff --git a/doc/user/analytics/analytics_dashboards.md b/doc/user/analytics/analytics_dashboards.md
index e647dcf170a..585512698f3 100644
--- a/doc/user/analytics/analytics_dashboards.md
+++ b/doc/user/analytics/analytics_dashboards.md
@@ -43,7 +43,6 @@ For more information about the development of product analytics, see the [group
 
 - Comment on issue [391970](https://gitlab.com/gitlab-org/gitlab/-/issues/391970).
 - Create an issue with the `group::product analytics` label.
-- [Schedule a call](https://calendly.com/jheimbuck/30-minute-call) with the team.
 
 ### Value Stream Management