Closed jmalloc closed 2 years ago
This can be accomplished under GitHub actions using the official create-release
action. We just need to figure out how best to set the prerelease
option based on semver's notion of pre-release (0 major version, or explicit pre-release tag).
That create-release
action may not actually be appropriate. We wan't to use the markdown from the changelog, not the commit message.
That is, unless we change the tagging process somehow to support the markdown headers, which are treated as comments by git tag
.
Done
The release should be updated to include the changelog entries relevant to that tag.
Perhaps the implementation of this could take inspiration from this project.
Travis CI can also deploy to GitHub releases, but I'm not sure if there's any way to set the description of the release itself.