My many year peeve is github adding "Source code (zip)" to the files in a release. It is the repository state at the tag, and needs some processing (think similar to generating configure etc), hence being a hindrance for someone looking for the source code to use. I do provide a useful source code file, but can't override github being unhelpful.

Do you plan on creating „real“ Github Actions actions to integrate with releases? All examples mentioned here use the github-script action, which, to me, feels like a workaround. Or some form of direct integration into Github Actions, e.g. configure a workflow as „pre-release“ and the tags and release notes are created automatically?

Given the currently documented automation features, I don’t see how this provides a tangible improvement to our team setups compared to current solutions like auto or semantic-release.