Users allowed to create protected tags cannot unprotect tags
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Users in the Allowed to create or delete list for protected tags are not able to delete protected tags with Developer permissions, although Maintainer permissions work.
Is Maintainer access required for deleting protected tags and the document should be updated to reflect this, or should an account in the list be able to delete a protected tag even with Developer permissions?
Steps to reproduce
- Create a protected tag in a repository with at least one Developer and one Maintainer.
- Attempt to delete the protected tag with the Developer account, it fails.
- Attempt to delete the protected tag with the Maintainer account, it succeeds.
Example Project
Project contains customer details. Adding in an internal comment below.
What is the current bug behavior?
A Developer cannot remove a protected account even if they are in the list.
What is the expected correct behavior?
The users added to the list should be able to remove tags.
Relevant logs and/or screenshots
See internal comment below.
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)
Possible fixes
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.