You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to create a changelog for just one specific release version (e.g. v12.2.0).
If I use --starting-version v12.2.0, it creates a changelog of v12.2.0, v12.2.1, etc (as expected). So I added --tag-pattern as well to restrict the tags to just the specific version:
$ auto-changelog --starting-version v12.2.0 --tag-pattern v12.2.0 --commit-limit false
However that creates a changelog that includes every commit in the history, not just those for v12.2.0. Is this a bug, or am I using --tag-pattern in an unexpected way?
Any other way to get just a changelog of one specific release version?
The text was updated successfully, but these errors were encountered:
Perhaps an --ending-version option is what is needed here, if this isn't the intended use of --tag-pattern or there's some technical limitation with --tag-pattern supporting a full tag version
The problem here is that --tag-pattern is applied before the tags are "enriched" with the diff, which uses the previous tag to store a diff string used later. --starting-version is applied afterwards, so previous versions can be removed without losing the diff data of the remaining tags. Great job with the PR – I'll merge it soon.
I'm trying to create a changelog for just one specific release version (e.g. v12.2.0).
If I use --starting-version v12.2.0, it creates a changelog of v12.2.0, v12.2.1, etc (as expected). So I added --tag-pattern as well to restrict the tags to just the specific version:
$ auto-changelog --starting-version v12.2.0 --tag-pattern v12.2.0 --commit-limit false
However that creates a changelog that includes every commit in the history, not just those for v12.2.0. Is this a bug, or am I using --tag-pattern in an unexpected way?
Any other way to get just a changelog of one specific release version?
The text was updated successfully, but these errors were encountered: