Morl99
commented
2 years ago If you are willing to switch to conventional commits, take a look at my approach to releasing: https://github.com/dbsystel/trivy-vulnerability-explorer/blob/main/.github/workflows/publish.yml
It doesn't take much to setup and works well. In your case, the publish step itself wouldn't be necessary, but you would end the workflow after creating the release and uploading the assets to it.
To better track progress and also when do I need to update my sources, it would be nice to have tagged releases in GitHub. Even tagged pre-releases would help. I'm not asking for a binary release, just a tag with the source as a tar ball under the release section. There are probably more advantages to that.