Hardy Hobeck

I think this issue will be solved in the upcoming release v6.x. Please try [6.0.0-beta.1](https://github.com/GitTools/GitVersion/releases/tag/6.0.0-beta.1) preview release.

I think this issue is related to https://github.com/GitTools/GitVersion/issues/3097. I saw the following comment from orionstudt: > AFAIK this is expected behavior. If your release has multiple features you don't increment...

I think this is not a bug and the actual behavior is intentional.

Like you sayed the documentation says clearly to use a dedicated version numer for branches e.g. release/1.2.3. Thus this issue is not a bug.

This what you want is already possible in GitVersion with the usage of mainline mode:  This feature was introduced with issue https://github.com/GitTools/GitVersion/issues/1221. This might be also interesting https://github.com/GitTools/GitVersion/issues/2955

Actually if you specify some date in the future the behaviour of GitVersion should be throwing an exception because it is equivalent to the case you have an empty repository....

> From my perspective, section [Incrementing per commit](https://gitversion.net/docs/more-info/incrementing-per-commit) and its linked [blog post](https://www.xavierdecoster.com/post/2013/04/29/semantic-versioning-auto-incremented-nuget-package-versions.html) are the most valuable info for people looking for automated continuous building (whatever it's continuous integration/delivery/deployment). That's...

If I take your first scenario and execute the following integration test on the main branch then the behavior of GitVersion is like I would expecting it. Why would you...

The behavior in your second scenario is also correct. Please see the following integration test: ```csharp [Test] public void Scenario2() { var configuration = GitFlowConfigurationBuilder.New .WithVersioningMode(VersioningMode.ContinuousDeployment) .WithNextVersion("0.2.1") .WithBranch("main", builder =>...

Thank you very much providing the integration test because it gives me the possibility to dig into the issue very easily and I think I have found the problem. Actually...