conventional-recommended-bump does not increment versions in a conventional way.
mchambaud opened this issue · comments
Latest version 0.3.0 should have been 1.0.0
According to SEMVER
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
This impacted our ability to ship code for a day while investigating our broken CI which allowed installing minor version of conventional-recommended-bump.
@stevemao After one year, it would be great to go to version one, don't you think?
I agree with @mchambaud on this one, I found it strange that this really useful tool did not respect the semver convention to determine version to update.
It should increase MAJOR on a Breaking Change and not increase PATCH on something secondary like chore commit.
@lucmerceron I DID follow semver very carefully. See the above link