Add latest changes from gitlab-org/gitlab@master

doc/administration/raketasks/_index.md

@@ -15,6 +15,8 @@ title: Rake tasks
 GitLab provides [Rake](https://ruby.github.io/rake/) tasks to assist you with common administration and operational
 processes.
 
+All Rake tasks must be run on a Rails node unless the documentation for a task specifically states otherwise.
+
 You can perform GitLab Rake tasks by using:
 
 - `gitlab-rake <raketask>` for [Linux package](https://docs.gitlab.com/omnibus/) and [GitLab Helm chart](https://docs.gitlab.com/charts/troubleshooting/kubernetes_cheat_sheet.html#gitlab-specific-kubernetes-information) installations.

doc/api/jobs.md

@@ -16,12 +16,6 @@ Use this API to interact with [CI/CD jobs](../ci/jobs/_index.md).
 
 ## List project jobs
 
-{{< history >}}
-
-- Support for keyset pagination [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/362172) in GitLab 15.9.
-
-{{< /history >}}
-
 Get a list of jobs in a project. Jobs are sorted in descending order of their IDs.
 
 By default, this request returns 20 results at a time because the API results [are paginated](rest/_index.md#pagination)

doc/api/pipeline_schedules.md

@@ -120,12 +120,6 @@ curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/a
 
 ## Get all pipelines triggered by a pipeline schedule
 
-{{< history >}}
-
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368566) in GitLab 15.3.
-
-{{< /history >}}
-
 Get all pipelines triggered by a pipeline schedule in a project.
 
 ```plaintext

doc/api/pipelines.md

@@ -18,7 +18,6 @@ Use this API to interact with [CI/CD pipelines](../ci/pipelines/_index.md).
 
 {{< history >}}
 
-- `iid` in response [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/342223) in GitLab 14.6.
 - `name` in response [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115310) in GitLab 15.11 [with a flag](../administration/feature_flags/_index.md) named `pipeline_name_in_api`. Disabled by default.
 - `name` in request [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115310) in 15.11 [with a flag](../administration/feature_flags/_index.md) named `pipeline_name_search`. Disabled by default.
 - `name` in response [generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/398131) in GitLab 16.3. Feature flag `pipeline_name_in_api` removed.
@@ -98,7 +97,6 @@ Example of response
 
 {{< history >}}
 
-- `iid` in response [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/342223) in GitLab 14.6.
 - `name` in response [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115310) in GitLab 15.11 [with a flag](../administration/feature_flags/_index.md) named `pipeline_name_in_api`. Disabled by default.
 - `name` in response [generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/398131) in GitLab 16.3. Feature flag `pipeline_name_in_api` removed.
 

doc/ci/pipelines/instance_runner_compute_minutes.md

@@ -73,12 +73,6 @@ In some cases, the quota limit is replaced by one of the following labels:
 
 ### View usage for a group
 
-{{< history >}}
-
-- Displaying instance runners duration per project [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/355666) in GitLab 15.0.
-
-{{< /history >}}
-
 Prerequisites:
 
 - You must have the Owner role for the group.
@@ -96,12 +90,6 @@ subgroups, sorted in descending order of compute usage.
 
 ### View usage for a personal namespace
 
-{{< history >}}
-
-- Displaying instance runners duration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/345795) in GitLab 15.0.
-
-{{< /history >}}
-
 You can view the compute usage for your personal namespace:
 
 1. On the left sidebar, select your avatar.

doc/ci/pipelines/merge_request_pipelines.md

@@ -136,12 +136,6 @@ To use the UI to run a pipeline in the parent project for a merge request from a
 
 ### Prevent pipelines from fork projects
 
-{{< history >}}
-
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/325189) in GitLab 15.3.
-
-{{< /history >}}
-
 To prevent users from running new pipelines for fork projects in the parent project
 use [the projects API](../../api/projects.md#edit-a-project) to disable the `ci_allow_fork_pipelines_to_run_in_parent_project`
 setting.

doc/ci/pipelines/merged_results_pipelines.md

@@ -12,12 +12,6 @@ title: Merged results pipelines
 
 {{< /details >}}
 
-{{< history >}}
-
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/91849) in GitLab 15.1, merged results pipelines also run on [Draft merge requests](../../user/project/merge_requests/drafts.md).
-
-{{< /history >}}
-
 A merged results pipeline runs on the result of the source and target branches merged together.
 It is a type of [merge request pipeline](merge_request_pipelines.md).
 

doc/ci/pipelines/settings.md

@@ -89,12 +89,6 @@ running job can be canceled before it completes. After a job with
 
 ## Prevent outdated deployment jobs
 
-{{< history >}}
-
-- Also preventing outdated manual or retried deployment jobs from running [added](https://gitlab.com/gitlab-org/gitlab/-/issues/363328) in GitLab 15.5.
-
-{{< /history >}}
-
 Your project may have multiple concurrent deployment jobs that are
 scheduled to run in the same time frame.
 

doc/ci/testing/code_coverage/_index.md

@@ -186,13 +186,6 @@ For language-specific configuration details see:
 
 ### Coverage reports from child pipelines
 
-{{< history >}}
-
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/363301) in GitLab 15.1 [with a flag](../../../administration/feature_flags/_index.md) named `ci_child_pipeline_coverage_reports`. Disabled by default.
-- [Enabled on GitLab.com and GitLab Self-Managed](https://gitlab.com/gitlab-org/gitlab/-/issues/363557) in GitLab 15.2. Feature flag `ci_child_pipeline_coverage_reports` removed.
-
-{{< /history >}}
-
 Coverage reports from child pipelines appear in merge request diff annotations but not in the merge request widget.
 This happens because parent pipelines cannot access coverage report artifacts generated by child pipelines.
 

doc/user/project/integrations/pipeline_status_emails.md

@@ -15,6 +15,8 @@ title: Pipeline status emails
 You can send notifications about pipeline status changes in a group or
 project to a list of email addresses.
 
+Pipeline notifications triggered by blocked users are not delivered.
+
 ## Enable pipeline status email notifications
 
 To enable pipeline status emails:
@@ -27,6 +29,3 @@ To enable pipeline status emails:
    **Notify only broken pipelines**.
 1. Select the branches to send notifications for.
 1. Select **Save changes**.
-
-In [GitLab 15.1](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89546)
-and later, pipeline notifications triggered by blocked users are not delivered.