Update package breaking changes

data/deprecations/14-5-remove-package-pipelines-api.yml

 - title: "Package pipelines in API payload is paginated"  # The name of the feature to be deprecated
   announcement_milestone: "14.5"  # The milestone when this feature was first announced as deprecated.
-  removal_milestone: "16.0"  # The milestone when this feature is planned to be removed
+  removal_milestone: "17.0"  # The milestone when this feature is planned to be removed
   breaking_change: true
   body: |  # Do not modify this line, instead modify the lines below.
     A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines.
 
-    In milestone 16.0, we will remove the `pipelines` attribute from the API response.
+    In milestone 17.0, we will remove the `pipelines` attribute from the API response.
   stage: package
   tiers: Free
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/289956

data/deprecations/15-8-raise-permissions-settings-package-stage.yml

 - title: "Maintainer role providing the ability to change Package settings using GraphQL API"
   announcement_milestone: "15.8"
-  removal_milestone: "16.0"
+  removal_milestone: "17.0"
   breaking_change: true
   reporter: trizzi
   stage: Package
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/370471
   body: |
     The ability for users with the Maintainer role to change the **Packages and registries** settings for a group using
-    the GraphQL API is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. These settings include:
+    the GraphQL API is deprecated in GitLab 15.8 and will be removed in GitLab 17.0. These settings include:
 
     - [Allowing or preventing duplicate package uploads](https://docs.gitlab.com/ee/user/packages/maven_repository/#do-not-allow-duplicate-maven-packages).
     - [Package request forwarding](https://docs.gitlab.com/ee/user/packages/maven_repository/#request-forwarding-to-maven-central).
     - [Enabling lifecycle rules for the Dependency Proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/reduce_dependency_proxy_storage.html).
 
-    In GitLab 16.0 and later, you must have Owner role for a group to change the **Packages and registries**
+    In GitLab 17.0 and later, you must have the Owner role for a group to change the **Packages and registries**
     settings for the group using either the GitLab UI or GraphQL API.

doc/update/deprecations.md

@@ -315,6 +315,44 @@ Due to low customer usage, Load Performance Testing is deprecated and will be re
 
 <div class="deprecation breaking-change" data-milestone="17.0">
 
+### Maintainer role providing the ability to change Package settings using GraphQL API
+
+<div class="deprecation-notes">
+- Announced in: GitLab <span class="milestone">15.8</span>
+- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
+- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/370471).
+</div>
+
+The ability for users with the Maintainer role to change the **Packages and registries** settings for a group using
+the GraphQL API is deprecated in GitLab 15.8 and will be removed in GitLab 17.0. These settings include:
+
+- [Allowing or preventing duplicate package uploads](https://docs.gitlab.com/ee/user/packages/maven_repository/#do-not-allow-duplicate-maven-packages).
+- [Package request forwarding](https://docs.gitlab.com/ee/user/packages/maven_repository/#request-forwarding-to-maven-central).
+- [Enabling lifecycle rules for the Dependency Proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/reduce_dependency_proxy_storage.html).
+
+In GitLab 17.0 and later, you must have the Owner role for a group to change the **Packages and registries**
+settings for the group using either the GitLab UI or GraphQL API.
+
+</div>
+
+<div class="deprecation breaking-change" data-milestone="17.0">
+
+### Package pipelines in API payload is paginated
+
+<div class="deprecation-notes">
+- Announced in: GitLab <span class="milestone">14.5</span>
+- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
+- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/289956).
+</div>
+
+A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines.
+
+In milestone 17.0, we will remove the `pipelines` attribute from the API response.
+
+</div>
+
+<div class="deprecation breaking-change" data-milestone="17.0">
+
 ### PipelineSecurityReportFinding projectFingerprint GraphQL field
 
 <div class="deprecation-notes">
@@ -1570,28 +1608,6 @@ With external authorization enabled, personal access tokens (PATs) and deploy to
 
 <div class="deprecation breaking-change" data-milestone="16.0">
 
-### Maintainer role providing the ability to change Package settings using GraphQL API
-
-<div class="deprecation-notes">
-- Announced in: GitLab <span class="milestone">15.8</span>
-- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
-- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/370471).
-</div>
-
-The ability for users with the Maintainer role to change the **Packages and registries** settings for a group using
-the GraphQL API is deprecated in GitLab 15.8 and will be removed in GitLab 16.0. These settings include:
-
-- [Allowing or preventing duplicate package uploads](https://docs.gitlab.com/ee/user/packages/maven_repository/#do-not-allow-duplicate-maven-packages).
-- [Package request forwarding](https://docs.gitlab.com/ee/user/packages/maven_repository/#request-forwarding-to-maven-central).
-- [Enabling lifecycle rules for the Dependency Proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/reduce_dependency_proxy_storage.html).
-
-In GitLab 16.0 and later, you must have Owner role for a group to change the **Packages and registries**
-settings for the group using either the GitLab UI or GraphQL API.
-
-</div>
-
-<div class="deprecation breaking-change" data-milestone="16.0">
-
 ### Major bundled Helm Chart updates for the GitLab Helm Chart
 
 <div class="deprecation-notes">
@@ -1725,22 +1741,6 @@ The option to delete groups and projects immediately by default was deprecated t
 
 <div class="deprecation breaking-change" data-milestone="16.0">
 
-### Package pipelines in API payload is paginated
-
-<div class="deprecation-notes">
-- Announced in: GitLab <span class="milestone">14.5</span>
-- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
-- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/289956).
-</div>
-
-A request to the API for `/api/v4/projects/:id/packages` returns a paginated result of packages. Each package lists all of its pipelines in this response. This is a performance concern, as it's possible for a package to have hundreds or thousands of associated pipelines.
-
-In milestone 16.0, we will remove the `pipelines` attribute from the API response.
-
-</div>
-
-<div class="deprecation breaking-change" data-milestone="16.0">
-
 ### PipelineSecurityReportFinding name GraphQL field
 
 <div class="deprecation-notes">