Floris Lambrechts

> it would be good if the bump2version command would fail if the value in new-version does not match according to parse, instead of silently incorrectly replacing stuff. This is...

Bump2version can definitely be used for calver schemes. You have to *tell it* the current year and month though. There is support for using `now` and `utcnow` but that's only...

This configuration supports the `twisted` scheme. ```[bumpversion] current_version = 20.3.0 parse = (?P\d\d)\.(?P\d\d?)\.(?P\d+)((?P.+)(?P\d+))? serialize = {year}.{month}.{minor} {year}.{month}.{minor}{modifier}{micro} [bumpversion:part:modifier] optional_value = release values = beta rc release [bumpversion:file:version.txt] ``` Allowing command...

Thanks for the feedback, that's really useful. I'll spin off two issues for improving the documentation. Three in fact, because the `invoke` integration is really useful too. Out of curiosity,...

Hi, you're not the first one bugged by this. bump2version actually rewrites the full configuration file. Which we might stop doing altogether. Here's the meta-issue about it: #185.

So [6.2.0-0-ccs, 6.2.1-0-ccs) Means compatibility starts with version `6.2.0-0` and ends when `6.2.0` becomes `6.2.1` or higher. I don't think you can express such a thing in `bump2version` directly. You're...

I agree, the use of `in` is incorrect. Not sure if we can use `== lookbehind[0].lstrip()` because that would mean that extra first-line *leading* characters (and last-line *trailing* characters) are...

I don't think bump2version can be used in the way you describe. I think most people consider it good practice to do the version bump in a separate commit. Git...

No, I don't think that's possible. Do you have an example of this workflow? It sounds like you have multiple commits in the repository with a non-development version string?

Thanks, So the use case is: * Have version string `0.0.7` in `master` while 0.0.7 is in development. * Tag it as `v0.0.7` when it's ready. * Immediately bump to...