Add latest changes from gitlab-org/gitlab@master

7 files changed, 27 insertions, 29 deletions

diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index 20479a7dd8a..b661bcd6746 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -100,15 +100,6 @@ for all authenticated users, and on the Admin Area pages. The statuses are:
 
 ![Orange version check example](../settings/img/update-available.png)
 
-GitLab Inc. collects your instance's version and hostname (through the HTTP
-referer) as part of the version check. No other information is collected.
-
-This information is used, among other things, to identify to which versions
-patches must be backported, making sure active GitLab instances remain
-secure.
-
-If you disable version check, this information isn't collected.
-
 ### Enable or disable version check
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index a9df0da4596..20cf9ceb7c8 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -394,7 +394,7 @@ Returns [`Group`](#group).
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
-| <a id="querygroupfullpath"></a>`fullPath` | [`ID!`](#id) | Full path of the project, group, or namespace. For example, `gitlab-org/gitlab-foss`. |
+| <a id="querygroupfullpath"></a>`fullPath` | [`ID!`](#id) | Full path of the group. For example, `gitlab-org/gitlab-foss`. |
 
 ### `Query.groups`
 
@@ -633,7 +633,7 @@ Returns [`Namespace`](#namespace).
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
-| <a id="querynamespacefullpath"></a>`fullPath` | [`ID!`](#id) | Full path of the project, group, or namespace. For example, `gitlab-org/gitlab-foss`. |
+| <a id="querynamespacefullpath"></a>`fullPath` | [`ID!`](#id) | Full path of the namespace. For example, `gitlab-org/gitlab-foss`. |
 
 ### `Query.note`
 
@@ -689,7 +689,7 @@ Returns [`Project`](#project).
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
-| <a id="queryprojectfullpath"></a>`fullPath` | [`ID!`](#id) | Full path of the project, group, or namespace. For example, `gitlab-org/gitlab-foss`. |
+| <a id="queryprojectfullpath"></a>`fullPath` | [`ID!`](#id) | Full path of the project. For example, `gitlab-org/gitlab-foss`. |
 
 ### `Query.projects`
 
diff --git a/doc/api/search.md b/doc/api/search.md
index f452d7f0398..68b845227db 100644
--- a/doc/api/search.md
+++ b/doc/api/search.md
@@ -384,7 +384,7 @@ NOTE:
 This scope is available only if [Elasticsearch](../integration/advanced_search/elasticsearch.md) is enabled.
 
 ```shell
-curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/6/search?scope=notes&search=maxime"
+curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/search?scope=notes&search=maxime"
 ```
 
 Example response:
@@ -775,7 +775,7 @@ NOTE:
 This scope is available only if [Elasticsearch](../integration/advanced_search/elasticsearch.md) is enabled.
 
 ```shell
-curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/6/search?scope=notes&search=maxime"
+curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/groups/6/search?scope=notes&search=maxime"
 ```
 
 Example response:
@@ -1023,8 +1023,6 @@ Example response:
 
 > Moved to GitLab Premium in 13.9.
 
-This scope is available only if [Elasticsearch](../integration/advanced_search/elasticsearch.md) is enabled.
-
 ```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/6/search?scope=notes&search=maxime"
 ```
@@ -1060,8 +1058,6 @@ Example response:
 
 > Moved to GitLab Premium in 13.9.
 
-This scope is available only if [Elasticsearch](../integration/advanced_search/elasticsearch.md) is enabled.
-
 Filters are available for this scope:
 
 - filename
@@ -1144,8 +1140,6 @@ Example response:
 
 > Moved to GitLab Premium in 13.9.
 
-This scope is available only if [Elasticsearch](../integration/advanced_search/elasticsearch.md) is enabled.
-
 Filters are available for this scope:
 
 - Filename
diff --git a/doc/architecture/blueprints/cells/impacted_features/personal-namespaces.md b/doc/architecture/blueprints/cells/impacted_features/personal-namespaces.md
index 757f83c32d3..d80f5c44b98 100644
--- a/doc/architecture/blueprints/cells/impacted_features/personal-namespaces.md
+++ b/doc/architecture/blueprints/cells/impacted_features/personal-namespaces.md
@@ -138,6 +138,6 @@ Cons:
 
 ## 4. Evaluation
 
-The most straightforward solution requiring the least engineering effort is to create [one personal Namespace in each Organization](#33-one-personal-namespace-in-each-organization).
-We recognize that this solution is not ideal for users working across multiple Organizations, but find this acceptable due to our expectation that most users will mainly work in one Organization.
-At a later point, this concept will be reviewed and possibly replaced with a better solution.
+We will begin by [making the personal namespace optional for Organizations](https://gitlab.com/groups/gitlab-org/-/epics/12179). The goal of this iteration is to disable personal namespaces for any Organization other than the default Organization, so that customers who do not want to use personal namespaces can already move to Organizations. The first phase will only change the Ruby on Rails model relationships in preparation for further changes at the user-facing level.
+
+We need to [split the concept of a User Profile and a personal namespace](https://gitlab.com/gitlab-org/gitlab/-/issues/432654) now that a User is cluster-wide and a User's personal namespace must be Cell-local. It is likely we will [discontinue personal namespaces](#34-discontinue-personal-namespaces) in favor of Groups.
diff --git a/doc/user/analytics/value_streams_dashboard.md b/doc/user/analytics/value_streams_dashboard.md
index a50eab42a2d..ee669df9059 100644
--- a/doc/user/analytics/value_streams_dashboard.md
+++ b/doc/user/analytics/value_streams_dashboard.md
@@ -16,7 +16,7 @@ For more information, see also the [Value Stream Management category direction p
 The Value Streams Dashboard is a customizable dashboard you can use to identify trends, patterns, and opportunities for digital transformation improvements.
 The centralized UI in Value Streams Dashboard acts as the single source of truth (SSOT), where all stakeholders can access and view the same set of metrics that are relevant to the organization.
 
-The Value Streams Dashboard includes the following metrics:
+The Value Streams Dashboard includes two panels (DevSecOps metrics comparison and DORA Performers score) that visualize the following metrics:
 
 - [DORA metrics](dora_metrics.md)
 - [Value Stream Analytics (VSA) - flow metrics](../group/value_stream_analytics/index.md)
@@ -29,9 +29,11 @@ With the Value Streams Dashboard, you can:
 - Understand security exposure.
 - Drill down into individual projects or metrics to take actions for improvement.
 
-The Value Streams Dashboard has a default configuration, but you can also [customize the dashboard panels](#customize-the-dashboard-panels).
+## Value Streams Dashboard panels
 
-## DevSecOps metrics comparison panel
+The Value Streams Dashboard panels has a default configuration, but you can also [customize the dashboard panels](#customize-the-dashboard-panels).
+
+### DevSecOps metrics comparison panel
 
 The DevSecOps metrics comparison displays DORA4, vulnerability, and flow metrics for a group or project in the
 month-to-date, last month, the month before, and the past 180 days.
@@ -46,7 +48,7 @@ that are the largest value contributors, overperforming, or underperforming.
 You can also drill down the metrics for further analysis.
 When you hover over a metric, a tooltip displays an explanation of the metric and a link to the related documentation page.
 
-## DORA Performers score panel
+### DORA Performers score panel
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/386843) in GitLab 16.2 [with a flag](../../administration/feature_flags.md) named `dora_performers_score_panel`. Disabled by default.
 
@@ -73,7 +75,7 @@ For example, if a project has a high score for Deployment Frequency (Velocity),
 
 These scoring are based on Google's classifications in the [DORA 2022 Accelerate State of DevOps Report](https://cloud.google.com/blog/products/devops-sre/dora-2022-accelerate-state-of-devops-report-now-out).
 
-### Filter by project topics
+#### Filter the DORA Performers score by project topics
 
 When used in combination with a [YAML configuration](#using-yaml-configuration), you can filter the projects shown based on their assigned [topics](../project/settings/project_features_permissions.md#project-topics).
 
@@ -221,9 +223,19 @@ panels:
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
 For an overview of editing label filters in the configuration file, see [GitLab Value Streams Dashboard - Label filters demo](https://www.youtube.com/watch?v=4qDAHCxCfik).
 
+### Filter the DevSecOps metrics comparison panel by labels
+
 Label filters are appended as query parameters to the URL of the drill-down report of each eligible metric and automatically applied.
 If the comparison panel from the configuration file is enabled with `filter_labels`, the drill-down links inherit the labels from the panel filter.
 
+```yaml
+  - data:
+      namespace: group/another-project
+      filter_labels:
+        - in_development
+        - in_review
+```
+
 ## Dashboard metrics and drill-down reports
 
 | Metric | Description | Drill-down report | Documentation page | ID |
diff --git a/doc/user/packages/composer_repository/index.md b/doc/user/packages/composer_repository/index.md
index db3d31d3c18..c116a43293b 100644
--- a/doc/user/packages/composer_repository/index.md
+++ b/doc/user/packages/composer_repository/index.md
@@ -128,6 +128,7 @@ Install a package from the package registry so you can use it as a dependency.
 Prerequisites:
 
 - A package in the package registry.
+- The package registry is enabled in the project responsible for publishing the package.
 - The group ID, which is on the group's home page.
 - One of the following token types:
   - A [personal access token](../../../user/profile/personal_access_tokens.md)
diff --git a/doc/user/project/settings/project_features_permissions.md b/doc/user/project/settings/project_features_permissions.md
index 27c0668079c..c1fe9045ea5 100644
--- a/doc/user/project/settings/project_features_permissions.md
+++ b/doc/user/project/settings/project_features_permissions.md
@@ -173,7 +173,7 @@ To subscribe to a topic:
 
 - From the **Explore topics** page:
 
-  1. On the left sidebar, expand the top-most chevron ({**chevron-down**}).
+  1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
   1. Select **Explore**.
   1. Select **Topics**.
   1. Select the topic you want to subscribe to.