conventional commits/changelog adds all previous commits to release

Current Behavior

With a lerna setup with version: independent and conventionalCommits: true for the publish command in lerna.json: when publishing a new release with lerna publish lerna takes all previous commits into account and adds all commits again into CHANGELOG.md for this release and also raises the version respecting all previous commits.

Expected Behavior

After publishing a release with lerna publish only commits are respected which came after the previous release.

Steps to Reproduce

1. Add a feature commit feat: add a new feature
2. lerna publish // will raise minor version 1.0.0 -> 1.1.0
3. Add a fix commit fix: fix a bug
4. lerna publish // will raise minor version again 1.1.0 -> 1.2.0 but should only raise patch to 1.1.1

Also in the CHANGELOG.md for the second release both commits will be listed but only the latest one should be listed.

See this demo repo: https://github.com/rumtraubenuss/monorepo/blob/master/packages/foo/CHANGELOG.md

Environment

{
  "lerna": "3.0.0-rc.0",
  "packages": ["ui-lib/*"],
  "version": "independent",
  "npmClient": "yarn",
  "useWorkspaces": true,
  "commands": {
    "publish": {
      "allowBranch": "master",
      "conventionalCommits": true
    }
  }
}

Executable	Version
lerna --version	3.0.0-rc.0 and 2.11.0
npm --version	5.6.0
yarn --version	1.7.0
node --version	8.11.1

OS	Version
macOS	10.13.6

[rumtraubenuss]

The issue is triggered by a format setting in my global git config ~/.gitconfig:

[format]
	pretty = %Cblue%h%Creset %Cgreen[%cr]%Creset (%an) %s

Removing this and everything works as expected.

@evocateur Do you think that this is still related to lerna itself or rather to a dependency package like conventional-changelog-core?

[lock[bot]]

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.