CHANGELOGS not generated correctly when using "--conventional-graduate"

Expected Behavior

When versioning and publishing a prerelease version we do not want to generate the CHANGELOGS. This is done successfully with the “–no-changelog” for DTA environments.

But when we do “–conventional-graduate” for the production release to remove the “preid”, we want to generate a CHANGELOG for the production version. This is what we expect in the CHANGELOG for production.

## [0.0.7](git-tags) (2019-09-02)

### Bug Fixes

- commit 1
- commit 2

Current Behavior

This is what we are currently seeing in the CHANGELOG for production.

## [0.0.7](git-tags) (2019-09-02)

**Note:** Version bump only for package @package

Possible Solution

It probably has something to do with the git-tags for the prerelease versions that are already “released” with their changes. That is why the production publish does not see the changes anymore.

Steps to Reproduce (for bugs)

For prerelease:

1. lerna version --conventional-prerelease --no-changelog
2. lerna publish

Then for production:

1. lerna version --conventional-graduate
2. lerna publish

lerna.json

{
  "packages": ["packages/*"],
  "version": "independent",
  "command": {
    "publish": {
      "conventionalCommits": true,
      "ignoreChanges": ["**/*.md"],
      "yes": true
    },
    "version": {
      "conventionalCommits": true,
      "ignoreChanges": ["**/*.md"]
    }
  },
}

Context

Your Environment

Executable	Version
lerna --version	3.16.4
npm --version	10
node --version	6

[kelvincy]

Hey @thuringia, I tried with the commit messages fix and feat. Both of them will not generate CHANGELOGs when performing lerna version --conventional-graduate on production.

We have found a fix for this. Not sure if this is a preferred way, but it is currently working for us:

Prereleases:

1. lerna version --conventional-prerelease --preid dev --no-changelog
2. git tag -d $(git describe --abbrev=0) (This will remove the git tags from the commit so that lerna does not think it is released already)
3. git push
4. lerna publish from-package

Production:

1. lerna version --conventional-graduate
2. lerna publish from-git

[morewry]

I found that for 4.0.0, --no-git-tag-version skips all git interactions. No tag, no commit, no push. (--no-push appears superfluous and --push doesn’t change anything about the behavior.)

Using it prevents use of lerna publish from-git with the message:

lerna notice from-git No tagged release found

One has to add steps to make a commit and then lerna publish from-package or it fails with the message:

lerna ERR! EUNCOMMIT Working tree has uncommitted changes, please commit or remove the following changes before continuing:

(This is in the above build script, but now it’s in plain text.)