Creation of release with non-existent TAG leaves draft release when TAG creation is not allowed

[ricco1310cgi]

Expected Behavior

When creating a release in a repository the user is not permitted to create new TAGs in the workflow should optionally, as set by user parameter, remove the draft release as it is not allowed to publish said release.

Current Behavior

When creating a release in a repository the user is not permitted to create new TAGs in the workflow will create a new release as draft but not be able to finalize it. Resulting is an orphaned draft release which cannot be published nor is shown in the releases overview.

Possible Solution

the workflow should optionally, as set by user parameter, remove the draft release as it is not allowed to publish said release.

Steps to Reproduce

1. Create a ruleset which disallows creation of new TAGs
2. Create a workflow to publish a release
3. Step will fail without clear error message
4. A release will have been created in a draft state
5. Remove ruleset which disallows creation of new TAGs
6. Remove draft release
7. Rerun workflow
8. Release is now successfully published