Creating a change log for a semantically released package

Question

Here is the package I'm working on now.

This is the first time I'm trying to align a regular change log and use semantic versioning . The release of itself works fine, I have CIV testing on travis, creating and publishing a package before npm, creating a new version and git tag. There is also a version of the GitHub package that, in a sense, replaces a separate change file.

What I'm trying to achieve is to automatically generate ChangeLog based on the latest release changes. As far as I understand, it conventional-changelogcan help with this, but whenever I run:

$ conventional-changelog -p eslint-plugin-protractor -i CHANGELOG.md -w -r 0

I get all changes grouped under the version 0.0.0-semantically-released, which is a stub versionplaced in package.jsonto avoid warnings in time npm install.

What am I doing wrong and how can I generate logs for each semantic version?

Answer 1

It works fine for me when I run the following command in the project folder:

conventional-changelog -p eslint-plugin-protractor -i CHANGELOG.md -s -r 0

I added the contents of the generated CHANGELOG.md to the text.

Perhaps an error occurred conventional-changelogwhile opening this problem?