lerna-changelog always combines Unreleased with the previous release.

[devbucket]

I noticed that lerna-changelog always combines the latest release with the Unreleased code together to Unreleased. So the previous version disappears from the generated changelog. Is this a known issue? Is there a way to change this?

[Turbo87]

hmm, not sure what you mean. the workflow is usually to run lerna-changelog before bumping the version number. haven't had any issues like what you described yet when doing it that way.

[devbucket]

Ok even if we create the changelog before the version bump, it does it. So before the new changelog was created, it was looking like this:

And after the new changelog has been created, it looks like this:

[devbucket]

Anything new here? Since this issue still exists and happens every single time

[Turbo87]

All I can say is that it works fine on all of my repos and without reproduction instructions I have no clue what might be going wrong for you 😅

[runspired]

@Turbo87 I think this has been happening to us in ember-data too