conventional-changelog-cli always generates an empty changelog

[jeroenptrs]

trafficstars

I'm following the Angular commit spec, and using all variations of npx conventional-changelog -p angular -i CHANGELOG.md -s -r 0 (with and without flags) always generates empty commits.

I've tried numerous things, programmatically via conventional-changelog, generated via the cli or standard-version... always the same thing:

<a name="1.0.0"></a>
# 1.0.0 (2018-09-26)

Obviously i'm missing something, I just don't know what and the documentation isn't providing me with answers.

[plondon]

What is your git log?

[huangxiaoleng]

Have you tried this?

Bump version in package.json

https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-cli#recommended-workflow

[tommoor]

I have a similar issue, I suspect it's because we need to tag the release before running conventional-changelog due to the way our CI is setup (it's actually the tagging that triggers CI in the first place).

So our flow is:

• Tag a new build
• CI runs and passes
• Assets are build and deployed
• We run conventional-changelog to try and generate release notes that are then provided to an API request to update a database record.

I thought that providing releaseCount=2 would get around the issue, but that's not the case, our command looks like:

conventional-changelog -p angular -t desktop@ -k desktop/package.json --verbose --releaseCount=2

But with, or without the releaseCount the changelog produced is empty. Is this a bug? It seems like the "recommended workflow" might actually be the only workflow.

[zodiac1214]

i am still having this issue that is 3 year old...any update or wayts to debug this?

[kilofox]

It always generate an empty release in a PHP repository: # [](http://xxx.com/product/compare/v1.3.0...v) (2022-01-26) How to fix that, please?

[foogunlana]

For me I had this problem but resolved it when I found this line in the docs: The above generates a changelog based on commits since the last semver tag that matches the pattern of "Feature", "Fix", "Performance Improvement" or "Breaking Changes".

I had to create a feat(...): ... before and then the changelog would start from there.

Also, dropping the preset. I was using --preset angular. Removing that worked

[juanjoDiaz]

4 years later and hitting this. Any solution?

[haexyh]

5 years later also having this issue, but I found out if I give the option from=<GitSha> it works