Commit 8951c9b9 authored by Harsh Chouraria's avatar Harsh Chouraria Committed by Mike Jang

Correct role levels required for Release CRUD

Current permission docs are incorrect when it comes to deleting a
Release object in a project.

When originally added, the permission was only given to maintainers or
higher to be able to delete a Release:
Commit 8f1e96c8
from ~2018

This change corrects the permissions table and updates the API
documentation to mention the roles required when creating,
editing/updating, or deleting a Release.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/219392
parent 815a8dc5
......@@ -350,7 +350,7 @@ Example response:
## Create a release
Create a Release. You need push access to the repository to create a Release.
Create a release. Developer level access to the project is required to create a release.
```plaintext
POST /projects/:id/releases
......@@ -524,7 +524,7 @@ Example response:
## Update a release
Update a Release.
Update a release. Developer level access to the project is required to update a release.
```plaintext
PUT /projects/:id/releases/:tag_name
......@@ -631,7 +631,7 @@ Example response:
## Delete a Release
Delete a Release. Deleting a Release doesn't delete the associated tag.
Delete a release. Deleting a release doesn't delete the associated tag. Maintainer level access to the project is required to delete a release.
```plaintext
DELETE /projects/:id/releases/:tag_name
......
......@@ -104,7 +104,8 @@ The following table depicts the various user permission levels in a project.
| Publish [packages](packages/index.md) | | | ✓ | ✓ | ✓ |
| Create/edit/delete a Cleanup policy | | | ✓ | ✓ | ✓ |
| Upload [Design Management](project/issues/design_management.md) files | | | ✓ | ✓ | ✓ |
| Create/edit/delete [Releases](project/releases/index.md)| | | ✓ | ✓ | ✓ |
| Create/edit [releases](project/releases/index.md)| | | ✓ | ✓ | ✓ |
| Delete [releases](project/releases/index.md)| | | | ✓ | ✓ |
| Create new branches | | | ✓ | ✓ | ✓ |
| Push to non-protected branches | | | ✓ | ✓ | ✓ |
| Force push to non-protected branches | | | ✓ | ✓ | ✓ |
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment