Add latest changes from gitlab-org/gitlab@master

doc/development/documentation/styleguide/_index.md

@@ -214,6 +214,21 @@ Instead, focus on facts and achievable goals. Be specific. For example:
 - You can use this feature to save time when you create a project. The API creates the file and you
   do not need to manually intervene.
 
+### Self-referential writing
+
+Avoid writing about the document itself. For example, do not use:
+
+- This page shows...
+- This guide explains...
+
+These phrases slow the user down. Instead, get right to the point. For example, instead of:
+
+- This page explains different types of pipelines.
+
+Use:
+
+- GitLab has different types of pipelines to help address your development needs.
+
 ### Capitalization
 
 As a company, we tend toward lowercase.

doc/user/application_security/policies/pipeline_execution_policies.md

@@ -339,7 +339,7 @@ Result: The pipeline contains the following stages: `[build, test, policy-stage,
 
 Special cases:
 
-- If the `.gitlab-ci.yml` specified the stages as `[build, deploy, test]`, the pipeline would fail because the constraints cannot be satisfied. In order to fix the failure, the project configuration must be adjusted to align the stages with the policies.
+- If the `.gitlab-ci.yml` specified the stages as `[build, deploy, test]`, the pipeline would fail with the error `Cyclic dependencies detected when enforcing policies` because the constraints cannot be satisfied. In order to fix the failure, the project configuration must be adjusted to align the stages with the policies.
 - If the `.gitlab-ci.yml` specified stages as `[build]`, the resulting pipeline has the following stages: `[build, policy-stage]`.
 
 ##### Example 2

doc/user/markdown.md

@@ -33,6 +33,7 @@ You can use GitLab Flavored Markdown in:
 - Snippets (the snippet must be named with a `.md` extension)
 - Wiki pages
 - Markdown documents inside repositories
+- Releases
 
 You can also use other rich text files in GitLab. You might have to install a dependency
 to do so. For more information, see the [`gitlab-markup` gem project](https://gitlab.com/gitlab-org/gitlab-markup).

doc/user/project/issues/crosslinking_issues.md

@@ -77,10 +77,11 @@ collaborators know that there are opened issues regarding the same topic.
 You do that as explained above, when [mentioning an issue from a commit message](#from-commit-messages).
 
 When mentioning issue `#111` in issue `#222`, issue `#111` also displays a notification
-in its tracker. That is, you only need to mention the relationship once for it to
+in its **Activity** feed. That is, you only need to mention the relationship once for it to
 display in both issues. The same is valid when mentioning issues in [merge requests](#from-merge-requests).
 
-![issue mentioned in issue](img/mention_in_issue_v9_3.png)
+When the activity feed for an issue is filtered to **Show history only** or **Show all activity**,
+crosslinks are shown as `(Username) mentioned in issue #(number) (time ago)`.
 
 ## From merge requests
 
@@ -92,7 +93,8 @@ When you mention an issue in a merge request description, it
 you can also [set an issue to close automatically](managing_issues.md#closing-issues-automatically)
 as soon as the merge request is merged.
 
-![issue mentioned in MR](img/mention_in_merge_request_v9_3.png)
+When the activity feed for an issue is filtered to **Show history only** or **Show all activity**,
+crosslinks are shown as `(Username) mentioned in merge request !(number) (time ago)`.
 
 ## From branch names
 

doc/user/project/issues/multiple_assignees_for_issues.md

@@ -25,5 +25,3 @@ would as single assignees), simplifying communication and ownership.
 
 After an assignee completes their work, they remove themselves as an assignee, making
 it clear that their task is complete.
-
-![multiple assignees for issues](img/multiple_assignees_for_issues_v9_4.png)

doc/user/project/merge_requests/duo_in_merge_requests.md

@@ -21,8 +21,8 @@ GitLab Duo is designed to provide contextually relevant information during the l
 
 {{< details >}}
 
-- Status: Beta
-- LLM: Vertex AI Codey [`text-bison`](https://console.cloud.google.com/vertex-ai/publishers/google/model-garden/text-bison)
+- Status: Experiment
+- LLM: Anthropic [Claude 3.5 Sonnet](https://console.cloud.google.com/vertex-ai/publishers/anthropic/model-garden/claude-3-5-sonnet)
 
 {{< /details >}}
 
@@ -106,7 +106,7 @@ Interactions with GitLab Duo can help to improve the suggestions and feedback as
 {{< details >}}
 
 - Status: Experiment
-- LLM: Vertex AI Codey [`text-bison`](https://console.cloud.google.com/vertex-ai/publishers/google/model-garden/text-bison)
+- LLM: Anthropic [Claude 3.5 Sonnet](https://console.cloud.google.com/vertex-ai/publishers/anthropic/model-garden/claude-3-5-sonnet)
 
 {{< /details >}}
 

doc/user/project/service_desk/using_service_desk.md

@@ -28,16 +28,15 @@ The email address is available at the top of the issue list.
 
 To create a Service Desk issue, an end user does not need to know anything about
 the GitLab instance. They just send an email to the address they are given, and
-receive an email back confirming receipt:
+receive an email back from GitLab Support Bot, confirming receipt:
 
-![Service Desk enabled](img/service_desk_confirmation_email_v9_1.png)
+> Thank you for your support request! We are tracking your request as ticket `#%{issue_iid}`,
+> and will respond as soon as we can.
 
-This also gives the end user an option to unsubscribe.
+This email also gives the end user an option to unsubscribe.
 
 If they don't choose to unsubscribe, then any new comments added to the issue
-are sent as emails:
-
-![Service Desk reply email](img/service_desk_reply_v9_1.png)
+are sent as emails.
 
 Any responses they send by email are displayed in the issue itself.
 
@@ -77,8 +76,6 @@ Messages from the end user are shown as coming from the special
 [Support Bot user](../../../subscriptions/self_managed/_index.md#billable-users).
 You can read and write comments as you usually do in GitLab:
 
-![Service Desk issue thread](img/service_desk_thread_v9_1.png)
-
 - The project's visibility (private, internal, public) does not affect Service Desk.
 - The path to the project, including its group or namespace, is shown in emails.
 

qa/gdk/Dockerfile.gdk

@@ -1,4 +1,4 @@
-ARG GDK_SHA=af3f6a68f68ead604bbda99726049b777f1beb6b
+ARG GDK_SHA=1305f9ba528237f69f39bf507149d66325ed783d
 # Use tag prefix when running on 'stable' branch to make sure 'protected' image is used which is not deleted by registry cleanup
 ARG GDK_BASE_TAG_PREFIX