Option to increment minor or major version instead of patch

[adamralph]

Option to increment minor or major version instead of patch

[enzian]

@adamralph maybe it was also a case of over engineering is underrated ;-) I patched it!

[enzian]

hey, need help on that?

[adamralph]

Hey @enzian, sure thing! I guess, from the user's perspective, this would result in a new property. Something like:

<MinVerAutoIncrement>major|minor|patch(default)</MinVerAutoIncrement>

I'm not wild about the name MinVerAutoIncrement. Any better idea? /cc @leastprivilege

[enzian]

I preliminarily introduced the --increment-segment option in the CLI, but I don't have a strong opinion about the naming either!

[adamralph]

@enzian thanks for the PR!

But also apologies, because I was not clear in my previous comment:

<MinVerAutoIncrement>major|minor|patch(default)</MinVerAutoIncrement>

I was using | to mean "or". That is, the default (implicit) value would be:

<MinVerAutoIncrement>patch</MinVerAutoIncrement>

And that could be changed to:

<MinVerAutoIncrement>minor</MinVerAutoIncrement>

or:

<MinVerAutoIncrement>major</MinVerAutoIncrement>

I can't think of a valid use case to auto-increment more than one part of the version.

[enzian]

@adamralph : I've seen (just once...) that a company did not release versions like 2.0.0. The first version they would release was 2.1.0 (for what reason is unclear to me...)! Should I switch to a single value?

[adamralph]

That sounds like a bizarre versioning scheme and not one I really want to encourage. 😉

I think, for now, let's stick to a single value for simplicity. We can always extend it to multiple values later, but I hope noone asks for that. 😉

[adamralph]

Released in 1.1.0-beta.1.

@leastprivilege would you like to give it a try? Just add a property:

<MinVerAutoIncrement>minor</MinVerAutoIncrement>

[leastprivilege]

sorry - swamped right now...

[adamralph]

@leastprivilege FYI I just pushed 1.1.0-rc.1.