Using rcs and minor releases causes incorrect version bumps

[chris-ware]

In the use case I have, I have version 2.6 of my app. We released 3 release candidates, and have now done a minor release. So the following tags were generated:

• 2.7.0-rc.1
• 2.7.0-rc.2
• 2.7.0-rc.3
• 2.7.0

Now I'm trying to prepare the release candidate for 2.8 and instead of tagging it as 2.8.0-rc.1, it's tagging it as 2.7.0-rc.4, even though 2.7.0 has been fully released and tagged.

I've been able to get around it by deleting the tags for the RC's on my local instance and running the --rc command again, but it seems odd that the detection on the latest version doesn't do it based on the latest tag, but rather the latest tag of that type.