Closed mctwynne closed 5 years ago
We should probably use the regular version-comparison.
@reinout Any rough idea of what the timeline looks like for this one? It seems like a pretty critical issue, no?
Not that critical. Most people only use "fullrelease", not bumpversion. And it only goes wrong on .9
or .19
, so all the software that's at 0.1
works just fine :-)
But I'll fix it, probably today. I want to fix #301, so that's always a good time to clear out some other bugs.
The fix itself was small, but getting it to work reliably took quite some doing :-) I'm waiting for @mauritsvanrees' review and then I'll release a new version.
@mctwynne: I've released the fix in 6.15.4 Thanks for reporting the issue and figuring out where the problem was!
When running
bumpversion --feature --no-input
with a current version of1.9.1.dev0
I expected to have a successful bump to1.10.0
, however I received the following message instead:This appears to be due to the fact that
bumpversion.BumpVersion._grab_version
compares versions that are represented as strings.A little pdb shows the crux of the problem: