Pete Cook

Merge commits and commits that fix an issue are grouped into separate lists (`merges` and `fixes`) which is why they don’t appear in `commits`. I guess in your case you...

@IllusionVK Any thoughts on the comments here?

Can we rename the template to just `conventional` (I'm a sucker for brevity) and then I’ll get this published.

This looks interesting but couldn’t the same be achieved with the existing `--tag-pattern` option and capture groups?

I think this would lose a lot of potentially useful information from the changelog, based on the fact that the filtering is happening _after_ the `diff` for each release is...

@ljharb This takes me back to [a conversation we had over two years ago](https://github.com/cookpete/auto-changelog/issues/132). Time flies eh?

v2 is much smarter about how it gathers the differences between two versions (see https://github.com/CookPete/auto-changelog/pull/144), and is useful for a bunch of use cases (namely https://github.com/cookpete/auto-changelog/issues/136 and https://github.com/cookpete/auto-changelog/issues/142). The downside...

>The problem with using --starting-version is that it has to be updated/maintained so it does not fit easily into an automated build-deploy process I'm not sure I follow – you...

Would it make more sense to hide the prereleases altogether once the official version is out, and just show all changes under the main release? It seems redundant to list...

Fair point. In which case, is there an issue where any new changes between the most recent pre-release and the new release (if any) would get lost in the rolled...