Error 403 while creating release if creation of tags are protected

Summary

The release-cli is failing to create a release if it doesn't has access to create tags, even if the tag already exists.

Steps to reproduce

  1. Create a tag, e.g, v.5.1.0
  2. Go to the settings page and protect the creation of tags, like shown in the image below: image
  3. Try to create a release with this version. A 403 error will be shown
$ release-cli ... create --tag-name v.5.1.0 ...
> INFO[0000] Creating Release... tag-name=v.5.1.0 version=0.6.0
FATA[0001] failed to create release: API Error Response status_code: 403 message: Access Denied  cli=release-cli version=0.6.0

What is the expected correct behavior?

If the tag already exists the error should not be shown.

Edited by Jaime Martinez