version inference strategy based on commit messages

[haikalrios]

Does Nebula work with a version inference strategy based on commit messages (Conventional Commits )? For instance, if the commits made after the last version tag begin with "BREAKING CHANGE:", does it increment the major version, If not, does it evaluate if the commit message starts with "feat" to increment the minor version, If not, does it evaluate if the commit message starts with "fix" to increment the patch version, Otherwise, does not it increment nothing

[DanielThomas]

It doesn't, but optional support for conventional commits is an interesting idea. We're already walking the commits to find the nearest tag.

We don't have enough utility for that to implement it ourselves, because the majority of our use of this is pre-release version semantics. Our release versions internally are almost all continuously incremented and do not carry semantic meaning, but we'd certainly consider a well tested PR if someone was inclined.