Calling getNextSemanticVersion() influences getHighestSemanticVersion()

[sschuberth]

When calling getNextSemanticVersion() before getHighestSemanticVersion() (on the same GitChangelogApi instance), that influences the result of getHighestSemanticVersion().

In my test case, calling getHighestSemanticVersion() alone would result in "1.0.1", but if getNextSemanticVersion() is called before (which yields "1.1.0"), then getHighestSemanticVersion() suddenly returns "0.0.0".

Is this intended?

[tomasbjerre]

Sounds really strange, will have a look later.

[sschuberth]

I believe this happens because of

git-changelog-lib/src/main/java/se/bjurr/gitchangelog/api/GitChangelogApi.java

Line 192 in d33434c

this.withFromRevision(tag.get());

which alters the state of the current GitChangelogApi.

[tomasbjerre]

I had a look, don't have time to work on it now but yes you are right. I'm putting it on my TODO.

[tomasbjerre]

Releasing a fix for this in 1.173.1. Open issue again if not working.