Release tag version format

[herchu]

This is more of a question than an issue. In my project I am tagging releases in a format like 2018-01-01_1.2.3_456 (a date, followed by a version 1.2.3, followed by another release number 456).

I love how auto-changelog lists the merge requests, but they all fall into "unreleased" category since it appears it is not using any of our tags as a version number. (Only a couple of very old tags from our repo appear listed, which are indeed in format 1.2.3).

Is there any way to specify the release tag format?

If not, a hint to where to do changes in the code would be also appreciated (I'll be happy to fork and work on the changes to contribute back with the feature).

[herchu]

Nevermind... I found our issue; most tags were being filtered out as not semver.valid().

Since our project uses non-semver tags, and we still find the tool really useful, I forked and added an option to disable validation via semver. The tool is the same; just filtering out "invalid" tags is disabled in that mode.

Please consider accepting pull request #70 . Closing this issue. Thanks!