This introduced this:

We need to ensure that we only escape HTML outside of `!

Describe the bug

The release notes for the prerelease say "push to master" when make release notes. This is probably unnecessary or should reflect the branch name I'm pushing to (eg next/alpha/beta) depending on my configuration.

To Reproduce

Make a next branch and push directly to it

Expected behavior

Prerelease notes don't say "push to master" but rather the name of

In new version of the conventional-changelog there is a different approach to passing a preset option, preset option has to be now a {name: string} instead of string.

I have created PR #166 with updated library reference and appropriate change in code to accomodate that without introducing a breaking change.

Callable functions are not secure by default.

Check that each function has the appropriate security checks

It would be great if you can filter the commits by the milestone they've got in their pull request.

e.g. gitreleases.dev/gh/rokka-io/rokka-go/latest/rokka_linux_{version}.zip would be automatically resolved to gitreleases.dev/gh/rokka-io/rokka-go/latest/rokka_linux_3.0.0.zip because 3.0.0 is the latest release.

I'll need to think about how the placeholder should be named actually, because it probably makes sense to use url safe characters only.

Golangflow only supports Github auth via the Goth Handler. It would be nice to support Twitter & Github auth.

A query parameter and set of regex should be added to select release assets targeted to a given architecture. Currently just assumes the user wants amd64/x86_64.

i was trying to use the change log assertion for a project. 🌞

The issue i encountered is that the changelog assertion without the 'version' or 'tag' just assert that the file exists. ( we might think about to improve it better).

Another issue that i found also is that the version assertion is hardcode to ruby version.rb https://github.com/cornelius/yes_ship_it/blob/master/ass