semantic-release: commits with `fix` or `feat` not triggering new release

Current behavior

I have some commits contains fix() and feat() but still not triggered a new release, the log:

Expected behavior

should trigger a new release

Environment

> semantic-release-test-repo@1.0.0 semantic-release /home/travis/build/neekey/semantic-release-test-repo
> semantic-release
[Semantic release]: Running semantic-release version 15.1.5
[Semantic release]: Load plugin verifyConditions from @semantic-release/npm
[Semantic release]: Load plugin verifyConditions from @semantic-release/github
[Semantic release]: Load plugin analyzeCommits from @semantic-release/commit-analyzer
[Semantic release]: Load plugin generateNotes from @semantic-release/release-notes-generator
[Semantic release]: Load plugin prepare from @semantic-release/npm
[Semantic release]: Load plugin prepare from @semantic-release/git
[Semantic release]: Load plugin publish from @semantic-release/npm
[Semantic release]: Load plugin publish from @semantic-release/github
[Semantic release]: Load plugin success from @semantic-release/github
[Semantic release]: Load plugin fail from @semantic-release/github
[Semantic release]: Run automated release from branch master
[Semantic release]: Call plugin verify-conditions
[Semantic release]: Verify authentication for registry https://registry.npmjs.org/
[Semantic release]: Wrote NPM_TOKEN to .npmrc.
[Semantic release]: Verify GitHub authentication
[Semantic release]: Found git tag v1.0.0 associated with version 1.0.0
[Semantic release]: Found 5 commits since last release
[Semantic release]: Call plugin analyze-commits
[Semantic release]: Analyzing commit: Merge pull request #3 from neekey/release
fix(test): fix test 
feat(text): feat test
perf(pencil): remove graphiteWidth option
[Semantic release]: The commit should not trigger a release
[Semantic release]: Analyzing commit: update dummyjs2
[Semantic release]: The commit should not trigger a release
[Semantic release]: Analyzing commit: Merge pull request #2 from neekey/release
Release new version
[Semantic release]: The commit should not trigger a release
[Semantic release]: Analyzing commit: Merge pull request #1 from neekeyni/master
feat(test): test feature
[Semantic release]: The commit should not trigger a release
[Semantic release]: Analyzing commit: test feature
[Semantic release]: The commit should not trigger a release
[Semantic release]: Analysis of 5 commits complete: no release
[Semantic release]: There are no relevant changes, so no new version is released.

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 1
  • Comments: 17 (4 by maintainers)

Most upvoted comments

That PR was closed without being merged

Looking at the commit on your master branch the 1.0.0 release none of that have a valid angular format:

  • Merge pull request #3 from neekey/release
  • update dummyjs2
  • Merge pull request #2 from neekey/release
  • Merge pull request #1 from neekeyni/master
  • test feature

None of your commits since the 1.0.0 release contain fix() or feat() in their subject.

If you want semantic-release to analyze those commit you have to format them according to Angular convention.

If you look at the convention you will see that fix(), feat(), etc… have to be in the subject not the body.

Feel free to comment further or re-open if you disagree.

@pvdlg having this same issue when using GitHub’s squash and merge. The default format is:

PR title (#3)

* feat: Adds something

Extended description

* refactor: Refactors something

Extended description

Do semantic release works with squash and merge commits? Or should everything be rebased?

Ah, i understand now! must include the (). I was sure I was missing something, thank you!