Closed
Description
Description
In our company, we make a release candidate and if it works, perform the full release. Currently, this logic is not compatible with cz bump because it always requires to have commits. Here is an example of the log:
The release candidate bump:
$ cz bump -pr rc
bump: version 0.6.0 → 0.6.1rc0
tag to create: v0.6.1rc0
increment detected: PATCH
[detached HEAD de92ff6] bump: version 0.6.0 → 0.6.1rc0
1 file changed, 11 insertions(+)
Attempting to do a real release on the commit tagged as 0.6.1rc0:
$ cz bump
bump: version 0.6.1rc0 → 0.6.1
tag to create: v0.6.1
No commits found
and exits with the exit code 3.
Possible Solution
Sometimes a release candidate is good. Let us just allow updating the changelog and tag that commit.
Additional context
We are using changelog_merge_prerelease = True so I would expect a changelog entry with the same info as in 0.6.1rc0 to be created, committed and tagged.
We have also tried to ignore the error and force proceed with
cz bump -nr 3
as indicated in the Documentation, but that gave the same result.
Additional context
No response