Research: Permissions for Releases
if given permission, developers will still be able to modify releases via the API.
GitHub has a different permissions system. I don't think that a :developer is always the same as GitHub write access, but it's probably the closest. In this case write users may:
Create and edit releases Publish packages They may not
Push to protected branches I believe that "edit release" includes "delete release" permission (it is not clear to me from the GitHub docs).
GitHub editing releases
I couldn't find a lot of information on Bitbucket releases. It appears they are using git tags and then managing releases with the rest of the Atlassian suite. It was difficult to find much information.
This video is interesting (28:45)
In summary, I think we can go with developer permissions for release (& dependent objects like links) for: create, update, delete.