Add latest changes from gitlab-org/gitlab@master

10 files changed, 87 insertions, 27 deletions

diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index 560f1a4c60a..18e44336223 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -22944,6 +22944,7 @@ Represents vulnerability letter grades with associated projects.
 | <a id="workitemauthor"></a>`author` **{warning-solid}** | [`UserCore`](#usercore) | **Introduced** in 15.9. This feature is an Experiment. It can be changed or removed at any time. User that created the work item. |
 | <a id="workitemclosedat"></a>`closedAt` | [`Time`](#time) | Timestamp of when the work item was closed. |
 | <a id="workitemconfidential"></a>`confidential` | [`Boolean!`](#boolean) | Indicates the work item is confidential. |
+| <a id="workitemcreatenoteemail"></a>`createNoteEmail` | [`String`](#string) | User specific email address for the work item. |
 | <a id="workitemcreatedat"></a>`createdAt` | [`Time!`](#time) | Timestamp of when the work item was created. |
 | <a id="workitemdescription"></a>`description` | [`String`](#string) | Description of the work item. |
 | <a id="workitemdescriptionhtml"></a>`descriptionHtml` | [`String`](#string) | GitLab Flavored Markdown rendering of `description`. |
@@ -22961,6 +22962,20 @@ Represents vulnerability letter grades with associated projects.
 | <a id="workitemwidgets"></a>`widgets` | [`[WorkItemWidget!]`](#workitemwidget) | Collection of widgets that belong to the work item. |
 | <a id="workitemworkitemtype"></a>`workItemType` | [`WorkItemType!`](#workitemtype) | Type assigned to the work item. |
 
+#### Fields with arguments
+
+##### `WorkItem.reference`
+
+Internal reference of the work item. Returned in shortened format by default.
+
+Returns [`String!`](#string).
+
+###### Arguments
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="workitemreferencefull"></a>`full` | [`Boolean`](#boolean) | Boolean option specifying whether the reference should be returned in full. |
+
 ### `WorkItemPermissions`
 
 Check permissions for the current user on a work item.
diff --git a/doc/api/rest/deprecations.md b/doc/api/rest/deprecations.md
index bf248487cf6..295f869720c 100644
--- a/doc/api/rest/deprecations.md
+++ b/doc/api/rest/deprecations.md
@@ -49,6 +49,18 @@ API users are encouraged to switch to the new diffs endpoint instead.
 
 The `changes from a single merge request` endpoint will be removed in v5 of the GitLab REST API.
 
+## Managed Licenses API endpoint
+
+Breaking change. [Related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/397067).
+
+The endpoint to get
+[all managed licenses for a given project](../managed_licenses.md)
+has been deprecated in favor the
+[License Approval policy](../../user/compliance/license_approval_policies.md) feature.
+Users who wish to continue to enforce approvals based on detected licenses are encouraged to create a new [License Approval policy](../../user/compliance/license_approval_policies.md) instead.
+
+The `managed licenses` endpoint will be removed in v5 of the GitLab REST API.
+
 ## Approvers and Approver Group fields in Merge Request Approval API
 
 Breaking change. [Related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/353097).
diff --git a/doc/api/vulnerability_exports.md b/doc/api/vulnerability_exports.md
index 28053eb20b6..c72e4a36929 100644
--- a/doc/api/vulnerability_exports.md
+++ b/doc/api/vulnerability_exports.md
@@ -8,11 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/197494) in GitLab 12.10. [Updated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/30397) in GitLab 13.0.
 
-WARNING:
-This API is in an [Experiment](../policy/alpha-beta-support.md#experiment) and considered unstable.
-The response payload may be subject to change or breakage
-across GitLab releases.
-
 Every API call to vulnerability exports must be [authenticated](rest/index.md#authentication).
 
 ## Create a project-level vulnerability export
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md
index d9f231be8bd..b335ff6e6a9 100644
--- a/doc/update/deprecations.md
+++ b/doc/update/deprecations.md
@@ -639,6 +639,27 @@ We will stop publishing runner images based on the following, end-of-life Alpine
 - Alpine 3.14 (end-of-life on 2023-05-23)
 
 </div>
+
+<div class="deprecation breaking-change" data-milestone="16.1">
+
+### License Compliance CI Template
+
+<div class="deprecation-notes">
+- Announced in: GitLab <span class="milestone">15.9</span>
+- [Breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/)
+</div>
+
+**Update:** We previously announced we would remove the existing License Compliance CI template in GitLab 16.0. However, due to performance issues with the [license scanning of CycloneDX files](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/) we will do this change in 16.1 instead.
+
+The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/license_compliance/) CI template is now deprecated and is scheduled for removal in the GitLab 16.1 release. Users who wish to continue using GitLab for License Compliance should remove the License Compliance template from their CI pipeline and add the [Dependency Scanning template](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuration). The Dependency Scanning template is now capable of gathering the required license information so it is no longer necessary to run a separate License Compliance job. The License Compliance CI template should not be removed prior to verifying that the `license_scanning_sbom_scanner` and `package_metadata_synchronization` flags are enabled for the instance and that the instance has been upgraded to a version that supports [the new method of license scanning](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/).
+
+| CI Pipeline Includes | GitLab <= 15.8 | 15.9 <= GitLab < 16.1 | GitLab >= 16.1 |
+| ------------- | ------------- | ------------- | ------------- |
+| Both DS and LS templates | License data from LS job is used | License data from LS job is used | License data from DS job is used |
+| DS template is included but LS template is not | No license data | License data from DS job is used | License data from DS job is used |
+| LS template is included but DS template is not | License data from LS job is used | License data from LS job is used | No license data |
+
+</div>
 </div>
 
 <div class="milestone-wrapper" data-milestone="16.0">
@@ -1318,25 +1339,6 @@ Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are
 
 <div class="deprecation breaking-change" data-milestone="16.0">
 
-### License Compliance CI Template
-
-<div class="deprecation-notes">
-- Announced in: GitLab <span class="milestone">15.9</span>
-- [Breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/)
-</div>
-
-The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/license_compliance/) CI template is now deprecated and is scheduled for removal in the GitLab 16.0 release. Users who wish to continue using GitLab for License Compliance should remove the License Compliance template from their CI pipeline and add the [Dependency Scanning template](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuration). The Dependency Scanning template is now capable of gathering the required license information so it is no longer necessary to run a separate License Compliance job. The License Compliance CI template should not be removed prior to verifying that the `license_scanning_sbom_scanner` and `package_metadata_synchronization` flags are enabled for the instance and that the instance has been upgraded to a version that supports [the new method of license scanning](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/).
-
-| CI Pipeline Includes | GitLab <= 15.8 | 15.9 <= GitLab < 16.0 | GitLab >= 16.0 |
-| ------------- | ------------- | ------------- | ------------- |
-| Both DS and LS templates | License data from LS job is used | License data from LS job is used | License data from DS job is used |
-| DS template is included but LS template is not | No license data | License data from DS job is used | License data from DS job is used |
-| LS template is included but DS template is not | License data from LS job is used | License data from LS job is used | No license data |
-
-</div>
-
-<div class="deprecation breaking-change" data-milestone="16.0">
-
 ### License-Check and the Policies tab on the License Compliance page
 
 <div class="deprecation-notes">
@@ -1955,7 +1957,11 @@ You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status o
 - [Breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/)
 </div>
 
-Using third-party container registries is deprecated in GitLab 15.8 and the end of support is scheduled for GitLab 16.0. Supporting both GitLab's Container Registry and third-party container registries is challenging for maintenance, code quality, and backward compatibility. This hinders our ability to stay [efficient](https://about.gitlab.com/handbook/values/#efficiency).
+Using third-party container registries with GitLab as an auth endpoint is deprecated in GitLab 15.8 and the [end of support](https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology) is scheduled for GitLab 16.0. This impacts self-managed customers that have connected their external registry to the GitLab user interface to find, view, and delete container images.
+
+Supporting both GitLab's Container Registry as well as third-party container registries is challenging for maintenance, code quality, and backward compatibility. This hinders our ability to stay [efficient](https://about.gitlab.com/handbook/values/#efficiency). As a result we will not support this functionality moving forward.
+
+This change will not impact your ability to pull and push container images to external registries using pipelines.
 
 Since we released the new [GitLab Container Registry](https://gitlab.com/groups/gitlab-org/-/epics/5523) version for GitLab.com, we've started to implement additional features that are not available in third-party container registries. These new features have allowed us to achieve significant performance improvements, such as [cleanup policies](https://gitlab.com/groups/gitlab-org/-/epics/8379). We are focusing on delivering [new features](https://gitlab.com/groups/gitlab-org/-/epics/5136), most of which will require functionalities only available on the GitLab Container Registry. This deprecation allows us to reduce fragmentation and user frustration in the long term by focusing on delivering a more robust integrated registry experience and feature set.
 
diff --git a/doc/update/index.md b/doc/update/index.md
index ed9d73ba56b..9990a2e8ffe 100644
--- a/doc/update/index.md
+++ b/doc/update/index.md
@@ -151,7 +151,7 @@ Read how to [upgrade without downtime](zero_downtime.md).
 ## Upgrading to a new major version
 
 Upgrading the *major* version requires more attention.
-Backward-incompatible changes and migrations are reserved for major versions.
+Backward-incompatible changes are reserved for major versions.
 Follow the directions carefully as we
 cannot guarantee that upgrading between major versions is seamless.
 
diff --git a/doc/update/removals.md b/doc/update/removals.md
index 3e72b2a7a5e..2085ce94748 100644
--- a/doc/update/removals.md
+++ b/doc/update/removals.md
@@ -78,6 +78,14 @@ The `CiCdSettingsUpdate` mutation will be removed in GitLab 16.0.
 Any user scripts that use the `CiCdSettingsUpdate` mutation must be updated to use `ProjectCiCdSettingsUpdate`
 instead.
 
+### Conan project-level search returns only project-specific results"
+
+WARNING:
+This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
+Review the details carefully before upgrading.
+
+The [GitLab Conan repository](https://docs.gitlab.com/ee/user/packages/conan_repository/) supports the `conan search` command, but when searching a project-level endpoint, instance-level Conan packages could have been returned. This unintended functionality is removed in GitLab 16.0. The search endpoint for the project level now only returns packages from the target project.
+
 ### Container Registry pull-through cache is removed
 
 WARNING:
diff --git a/doc/user/compliance/license_compliance/index.md b/doc/user/compliance/license_compliance/index.md
index 95347929d01..b7a68317fba 100644
--- a/doc/user/compliance/license_compliance/index.md
+++ b/doc/user/compliance/license_compliance/index.md
@@ -11,7 +11,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387561) in GitLab 15.9.
 
 WARNING:
-This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387561) in GitLab 15.9. You should instead migrate to use [License approval policies](../license_approval_policies.md) and the [new method of license scanning](../license_scanning_of_cyclonedx_files/index.md) prior to GitLab 16.0.
+This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387561) in GitLab 15.9. You should instead migrate to use [License approval policies](../license_approval_policies.md) and the [new method of license scanning](../license_scanning_of_cyclonedx_files/index.md) prior to GitLab 16.1.
 
 If you're using [GitLab CI/CD](../../../ci/index.md), you can use License Compliance to search your
 project's dependencies for their licenses. You can then decide whether to allow or deny the use of
diff --git a/doc/user/group/iterations/index.md b/doc/user/group/iterations/index.md
index 72d3bf65447..9b246e6ad47 100644
--- a/doc/user/group/iterations/index.md
+++ b/doc/user/group/iterations/index.md
@@ -62,6 +62,8 @@ To create an iteration cadence:
    - From the **Upcoming iterations** dropdown list, select how many upcoming iterations should be
      created and maintained by GitLab.
    - Optional. To move incomplete issues to the next iteration, select **Roll over issues**.
+     At the end of the current iteration, all open issues are added to the next iteration.
+     Issues are moved at midnight in the instance time zone (UTC by default). Administrators can change the instance time zone.
 1. Select **Create cadence**. The cadence list page opens.
 
 If you want to manually manage the created cadence, read [Manual Iteration Management](#manual-iteration-management).
diff --git a/doc/user/okrs.md b/doc/user/okrs.md
index 450827619fd..675d2d7ad5f 100644
--- a/doc/user/okrs.md
+++ b/doc/user/okrs.md
@@ -292,3 +292,14 @@ To add an existing key result to an objective:
 
    To add multiple objectives, repeat this step.
 1. Select **Add key result**.
+
+### Reorder objective and key result children
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/385887) in GitLab 16.0.
+
+Prerequisites:
+
+- You must have at least the Reporter role for the project.
+
+By default, child OKRs are ordered by creation date.
+To reorder them, drag them around.
diff --git a/doc/user/tasks.md b/doc/user/tasks.md
index c0c0946dd8c..fc232ee298e 100644
--- a/doc/user/tasks.md
+++ b/doc/user/tasks.md
@@ -158,6 +158,17 @@ To delete a task:
 1. In the task window, in the options menu (**{ellipsis_v}**), select **Delete task**.
 1. Select **OK**.
 
+## Reorder tasks
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/385887) in GitLab 16.0.
+
+Prerequisites:
+
+- You must have at least the Reporter role for the project.
+
+By default, tasks are ordered by creation date.
+To reorder them, drag them around.
+
 ## Assign users to a task
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/334810) in GitLab 15.4.