Replies: 1 comment 1 reply
-
One could argue that a however significant increase in performance is a feature to the benefit of the user. Therefore I tend towards |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The conventional commits spec states that only
feat
,fix
,BREAKING CHANGE
and!
correspond to semver changes (as it's implemented in this great tool).Additional types like
perf
(code change that improves performance) are allowed, but do not bump versions.From my POV a performance improvement (an actual code change) is something that I maybe want to release sooner than the next feature or bugfix, but I wouldn't be able get a new automated version for it.
How do you guys handle that in your projects? Forget about the existence of
perf
and stick tofeat
/fix
etc.? Manually intervene and declare a new version?Thanks in advance for your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions