diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-17 03:08:44 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-17 03:08:44 +0300 |
commit | 73c608b8c9e79319096fdbeb990dd5cb9ebf2b36 (patch) | |
tree | 50555f33cc354b8b4ea0da8123302626249a6934 /data | |
parent | 7cd99add2fedcf0a9f10e57c5fc213d5e51b6f61 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data')
-rw-r--r-- | data/deprecations/15-8-raise-permissions-settings-package-stage.yml | 26 |
1 files changed, 16 insertions, 10 deletions
diff --git a/data/deprecations/15-8-raise-permissions-settings-package-stage.yml b/data/deprecations/15-8-raise-permissions-settings-package-stage.yml index 66abbd1316d..72b53ee8c9b 100644 --- a/data/deprecations/15-8-raise-permissions-settings-package-stage.yml +++ b/data/deprecations/15-8-raise-permissions-settings-package-stage.yml @@ -1,11 +1,17 @@ -- title: "Owner permissions are required to update Package settings" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. - announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "16.0" # (required) The milestone when this feature is planned to be removed - breaking_change: true # (required) If this deprecation is a breaking change, set this value to true - reporter: trizzi # (required) GitLab username of the person reporting the deprecation - stage: Package # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/370471 # (required) Link to the deprecation issue in GitLab - body: | # (required) Do not modify this line, instead modify the lines below. - You must have Owner permissions to use the GitLab UI to update the `Packages and registries` settings for your groups. This includes [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), and [enabling lifecycle rules for the Dependency Proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/reduce_dependency_proxy_storage.html). Currently, you can use the GraphQL API with Owner or Maintainer permissions to update these settings. +- title: "Maintainer role providing the ability to change Package settings using GraphQL API" + announcement_milestone: "15.8" + removal_milestone: "16.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: - In GitLab 16.0 and later, you must have Owner permissions to use the GraphQL API to change the `Packages and registries` settings. + - [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. |