Squash merges and version not bumped

[adamralph]

Squash merges and version not bumped

[adamralph]

Hey @ben-foster-cko, thank for asking these questions.

The main thing to bear in mind is that MinVer performs no logic at all based on branch names. In fact, there is nothing in MinVer which even attempts to read which branches the current commit is contained in. The version is purely based on the last tag found in the history and the height of the current commit from that tag. There's more on this in the README.

• When branching off feature branches the version remains the same as develop. Am I right in thinking that the only way to deploy feature artefacts would be to tag them explicitly?

Feature branches will indeed be versioned in the same way as develop, only the height will change as the current commit gets further away from the last tag. If you want a specific version to be built from your feature branch then yes, you can tag the commit. Or you can add some special logic yourself based on the name of the current branch using a similar technique to those described in the README for performing custom logic.

• When squash merging a feature branch back into develop it didn't bump the version of develop (it remained as 0.1.0)

Correct, for the reasons described above.

• When merging develop into master and tagging, then switching back to develop, it didn't bump the version - I would expect this to be the same as master (0.1.1) - perhaps due to using annotated tags?

Correct, for the reasons described above. Annotated tags should be fine, although I don't think I've tested them explicitly. I should probably add something into the tests to make sure they are handled correctly.

---

In short, don't expect MinVer to work the same way as GitVersion. When I started prototyping, I did attempt to introduce logic around branching, but it very quickly turned into a can of worms. MinVer is purely tag-based versioning, and branches are irrelevant.