oo6 / mix-bump Goto Github PK

For example, If I'm on 1.2.7, bumping minor should make the version 1.3.0. Current behavior sets the mix version at 1.3.7.

• When bumping a major version, minor should be set to 0, and patch should be set to 0
• When bumping a minor version, patch should be set to 0
• When bumping a patch version, other values should not be affected (current behavior)

I should be able to throw a quick PR on this sometime tomorrow night. Seems like it'd just be hard-coding 0 on lines 17 and 25 of mix-bump.ex, and tossing an underscore in front of unused arguments.

Hello,

Would it be possible to add commit and tag feature similar to npm version patch -m "Bump version patch"? It would be a great feature so that I don't have to manually tag or make the commit message each time.

So I've been using this for a bit, and kind of manually creating releases in github after tagging.

At least for github/github enterprise, this could be automated. We could generate releases from the command line by using -a for annotated tags, over the default simple tags.

def tag(version, message) do
  Command.execute("git tag -a #{version} -m #{message}")
end

This would change the nature of tags for users of mix bump. Not sure if it does any harm, but maybe not everyone wants annotated tags.