Semantic-Release 不会创建具有 BREAKING CHANGE 的版本

Question

当我创建这样的提交时，git commit -m'BREAKING CHANGE: foo bar' 并向上推送 semantic-release 告诉我，

[@semantic-release/commit-analyzer] › ℹ  Analyzing commit: BREAKING CHANGE: Changes from slice_into_subrepo
[@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[@semantic-release/commit-analyzer] › ℹ  Analysis of 1 commits complete: no release

为什么 BREAKING CHANGE 没有创建版本，它是 documented to do that here,

BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reasons.

Answer 1

这是一个非常糟糕的错误。原因是reported in GitHub issue #108,

Please see the Angular Commit Message Conventions. BREAKING CHANGE: must be in the footer of the commit. You wrote it in the subject.

这可能会造成混淆，因为主页上的示例显示，

perf(pencil): remove graphiteWidth option

BREAKING CHANGE: The graphiteWidth option has been removed.
The default graphite width of 10mm is always used for performance reasons.

这不是两个示例，而是一个。这就是在页脚中添加“BREAKING CHANGE:”的样子。

这也是touched on on the documentation for @semantic-release/commit-analyzer,

Note: Your commits must be formatted exactly as specified by the chosen convention. For example the Angular Commit Message Conventions require the BREAKING CHANGE keyword to be followed by a colon (:) and to be in the footer of the commit message.

有关详细信息，请参阅 "Angular Commit Message Format"

上的上游文档

Semantic-Release 不会创建具有 BREAKING CHANGE 的版本

Semantic-Release doesn't create release with BREAKING CHANGE

javascript

node.js

semantic-release