Providing a revision from one tag to another does result in a wrong version bump #3
Description
next-version --rev v1.3.0..v1.4.0
If a feat or fix is present between the two version tags, the suggested version will be v1.5.0 or v.1.4.1 respectively. This is due to the fact that the tool does not know that the newest version from the viewpoint of the v1.3.0 tag is actually v.1.3.0 and not v1.4.0. The tool will always resolve against the biggest semver version, thus returning a wrong version here.
The output is expected. However, I am not sure if this should be the intended behaviour. The revision can be used to debug versions if wanted as there isn't normally another use-case for determining the version of older commits that already have been surpassed. This would require to determine the version that is the nearest to the first part of the revision.