New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"feat:" commits causing PATCH instead of MINOR #454
Comments
Hey @JVMartin – as of 7.0.0 this is expected behavior for module versions < 1.0.0. You can follow the related changeset (and conversation) here: #347 If you don't mind, I'm going to close this as it is expected behavior. If you need to break out of this behavior for a release, consider using the |
Hey @jbottigliero , thanks for the details! IMO, the behavior of We run So it seems like our only options for pre-1.0.0, is to have every release be a PATCH, or every release be a MINOR, which is not great. If the functionality for pre-1.0.0 were exactly the same as for post-1.0.0, then both automated and non-automated workflows would be supported completely. Everyone could do a Thoughts? |
Also, regarding #347... The title of the PR is That is, in fact, exactly what we need it to do! Currently this is broken, because feat bumps PATCH rather than MINOR, when it is supposed to bump MINOR, and #347 agrees that it's supposed to bump MINOR... |
You know what, I think I misunderstood. 😞 We can still get a MINOR to happen in < 1.0.0 by doing a So actually, we're all set. Thanks much! 😄 |
conventional-changelog/conventional-changelog#452 (comment) explains the reasoning for the behavior. The intent is to work well with npm by allowing caret semver ranges to install all non-breaking updates. |
We are using version
7.0.0
.Expected behavior:
feat:
commit messages should result in a MINOR bump.Actual behavior:
feat:
commit messages result in a PATCH bump.Details:
We have our pipeline set up to release on every commit to master, notice how both
fix
andfeat
result in patches:Here is the output from
standard-version
on afeat:
release:Here is the resulting commit:
The text was updated successfully, but these errors were encountered: