We use
assembly-versioning-format: '{major}.{minor}.{WeightedPreReleaseNumber}'
in combination with
mode: ContinuousDeployment
to have an increasing build number. Everything works in a normal development workflow (PRs, direct commits etc increase the version from e.g. 1.1.1 to 1.1.2). However, as soon as we want to release a new version, we push a tag with the new version (say 2.0-beta). In this case, WeightedPreReleaseNumber is null (or empty) for some reason which leads to the invalid build number 2.0. (notice the missing last bit of the version). I would have expected this to be 2.0.0 (or more generally: 2.0.x where x is the weight corresponding to the beta tag).

Full GitVersion file:
https://github.com/JabRef/jabref/blob/master/GitVersion.yml/GitVersion.yml