We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Hello Tomas, it's really great tool, but using tag with long patch in version (like 1.2.333) works strange for me - it treats the version as 1.2.3.
I've investigate a little and find out regular expression here:
git-changelog-lib/src/main/java/se/bjurr/gitchangelog/internal/semantic/SemanticVersioning.java
Line 92 in a22a611
My assumption what is wrong:
Also I've tested it with older lib version npm i git-changelog-command-line@1.101.1 and get "long patch"
npm i git-changelog-command-line@1.101.1
I hope for a quick fix if my findings are correct
The text was updated successfully, but these errors were encountered:
fix: making semantic version match not greedy (refs #142)
14d0f08
Thanks for reporting! Should be fixed now. Open issue again if not working.
Sorry, something went wrong.
No branches or pull requests
Hello Tomas,
it's really great tool, but using tag with long patch in version (like 1.2.333) works strange for me - it treats the version as 1.2.3.
I've investigate a little and find out regular expression here:
git-changelog-lib/src/main/java/se/bjurr/gitchangelog/internal/semantic/SemanticVersioning.java
Line 92 in a22a611
My assumption what is wrong:
printf '1.2.33333' | grep -E '[0-9]+.[0-9]+.?[0-9]+?'
1.2.33333
printf '1.2.33333' | grep -E '[0-9]+.[0-9]+.?[0-9]+'
1.2.33333
Also I've tested it with older lib version
npm i git-changelog-command-line@1.101.1
and get "long patch"
I hope for a quick fix if my findings are correct
The text was updated successfully, but these errors were encountered: