You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will ensure that your version gets bumped according to the commits you've
created.
The current Conventional Commit configuration breaks the standard's rules. Where PATCH is supposed to be incremented by only fix or perf, the configuration increments PATCH when the commit Type is any Angular commit Type except feat and no breaking change is present.
Additionally, the following should be noted for consumers:
revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
WARN: this recommendation prevents commit message analyzers from determining the reverted commit's significance. Analyzers which also parse commit hashes in the message may be able to determine the reverted commit's significance. In contrast, the angular convention places the reverted commit's header in the header of the revert commit.
Some software used in tandem with GitVersion may use version-increment rules not present in a given commit convention preset (e.g. angular, conventionalcommits). @semantic-release/commit-analyzer v10.0.1, for example, will increment PATCH for any revert commits regardless of the (in)significance of the reverted changes. This semantic-release behavior can be counteracted by adding custom rules to @semantic-release/commit-analyzer's configuration. Rather than RegEx, commit-analyzer uses Micromatch's glob implementation.
The text was updated successfully, but these errors were encountered:
GitVersion/docs/input/docs/reference/version-increments.md
Lines 91 to 104 in 63f7d27
The current Conventional Commit configuration breaks the standard's rules. Where
PATCH
is supposed to be incremented by onlyfix
orperf
, the configuration incrementsPATCH
when the commit Type is any Angular commit Type exceptfeat
and no breaking change is present.Additionally, the following should be noted for consumers:
revert
-type commits do not explicitly increment the version as their significance differs on a case-by-case basis. The convention gives the following format recommendation:angular
convention places the reverted commit's header in the header of the revert commit.angular
,conventionalcommits
).@semantic-release/commit-analyzer
v10.0.1, for example, will incrementPATCH
for anyrevert
commits regardless of the (in)significance of the reverted changes. This semantic-release behavior can be counteracted by adding custom rules to@semantic-release/commit-analyzer
's configuration. Rather than RegEx, commit-analyzer uses Micromatch's glob implementation.The text was updated successfully, but these errors were encountered: