Feature request: Bump semver

[alvagante]

@carlossg huge thanks for the tool and the help, publishing to the Forge now is a pleasure and is forcing me to be more disciplined.

A small nice feature would be to bump semver aware versions: major, minor, patch. Or maybe is already possible but I don't know how to do it.

cu al

[carlossg]

you mean bumping the x and y in x.y.z ? When I want to do that, I just go in and change the file before calling the rake tasks

[alvagante]

Yes I meant that. The manual approach is ok, anyway. Just out of curiosity, the bump increments always the last digit (z)?

[carlossg]

yes, only bumps the z, the idea is that it runs automatically, so you don't want to increase the x or y so often

[adamjk-dev]

Seems like this still might be convenient for some people/workflows. If you bump the major/minor version manually and run this rake task, then you would get two version bumps for one, right?

Or, it might be nice to not bump the patch version if the major or minor version was changed somehow... just thinking out loud.

[carlossg]

If you bump major or minor, e.g. 1.0.0 and then run rake module:release blacksmith will release 1.0.0, push it and increase the version to 1.0.1, which is what I would expect

[adamjk-dev]

Oh, you mean cycling the release forward for development purposes, that is. So, release 1.0.0 and start development on 1.0.1. Does this work just as well for local development? Meaning, if the module is not being pushed to the forge.

[carlossg]

Yes, there is rake module:bump and module:bump_commit IIRC, just run rake -T to see other options

[adamjk-dev]

Okay, yeah I did inspect those. So, perhaps I was thinking about it from the other end (running this rake task on each check-in to increase the version for release). But, really, we should set the release version manually, and this gem serves to increment the patch version for development that will continue.

[carlossg]

Implemented in #16