Closed mauritsvanrees closed 5 years ago
I just realized this is the more general version of issue #310. That one was about bumpversion which does the same.
So.... sounds like you smell a solution right around the corner? :-)
I think we have covered all cases. Closing.
When your
CHANGES.rst
does not have an(unreleased)
version, but has for example1.2.3 (2000-01-01)
as most recent header, thenpre/fullrelease
will find this and happily update it to next version number you are releasing, say1.2.4 (2019-02-15)
.This can happen when your package is supposed to use
towncrier
butzestreleaser.towncrier
is not installed. See this comment inplone.restapi
.zest.releaser
can probably check if(unreleased)
is missing and then either don't touch this file, or give a warning and ask for permission to continue.