In addition to #193, another major bug appeared in release, which is, from my perspective, completely blocking the workflow, and making release unusable:
When using release on a new repository for the first time, it won't respect any existing releases that might've been created in the list of GitHub releases already. For example, in the screenshot below, I ran release patch -P to create version 1.1.1 in this repository, which, as you can see on the link, already has a bunch of existing releases that were created on different devices a longer time ago.
What release created, unfortunately, is a new release that said "Initial release", which makes no sense.
In addition to #193, another major bug appeared in
release, which is, from my perspective, completely blocking the workflow, and makingreleaseunusable:When using
releaseon a new repository for the first time, it won't respect any existing releases that might've been created in the list of GitHub releases already. For example, in the screenshot below, I ranrelease patch -Pto create version1.1.1in this repository, which, as you can see on the link, already has a bunch of existing releases that were created on different devices a longer time ago.What
releasecreated, unfortunately, is a new release that said "Initial release", which makes no sense.