Release tags cross wired

[alerque]

For one thing you seem to keep switching back and forth between v prefixes on tags and not. Personally I prefer with the v, but even I don't care that much which it is ... whatever you pick you should stick with it. The format changing makes downstream packaging for distros quite obnoxious as tooling for version checking and comparisons stops working automatically.

But the real issue is, the latest release is labeled as v2.3.1, but the tag is v2.3.0. The trouble is there was already a tag for 2.3.0 without the v prefix on another commit over a year ago.

[sergiocorreia]

That's one of the risks of manually typing it :(

What's the best way to fix it? Release a .2 that bumps the version and avoids the conflict?