Filip Noetzel
Filip Noetzel
Yes, that should be fixed already. Sorry for delaying the release. Could you upgrade to 0.5.3 and see if the bug still shows ? We could still use a bit...
@pombreda that is possible. Do you mean my workstation, appveyor or travis ?
@pombreda just checked, you should be able to do that in your fork (appveyor and travis build pull requests), should give you more flexibility.
Sounds like a reasonable request, will think about it the next time I'm sober (approx. Tuesday). Did you see the support for environment variables in template strings in the README?...
On second thought, this sounds reasonable (and was on my TODO list for some time, apparently). I experimented with the current feature set as well with two config files (one...
Ok, that error is definitely misleading, sorry about that, I'll fix it. However, you need to specify which part of the version to bump (in the standard configuration that's "major",...
Because I see `current_version = 0.5.2.beta` in your config: At the moment bumpversion doesn't support parts (that's what I call the individual digits that are combined to the version number)...
Also, `--config .bumpversion.cfg` is the default, so, unless you want to use another config file, it should be safe omit.
Yes, I usually just use `bumpversion patch` alone, everything else is in the config file. > OK, I tried bumpversion --new-version 0.5.2 patch but that changed the version number to...
You're right, thanks! I'll get to that.