Hardy Hobeck

I think conventionalcommits.org has problems with it's certficate: 

The artefacts tests are failing... Maybe because of my changes!? Probably we need to change the assertion condition.

@asbjornu @arturcic Please proceed and merge this pull request to main.

Hi Miguel. I have tried to reproduce this issue in azure devops without success. The following integration test proofs your scenario and has been executed with the code base of...

May I ask you to explain your scenario based on an integration test? If you take the following example what is your expectation? ```csharp [Test] public void Just_A_Test() { var...

> May I ask you to explain your scenario based on an integration test? If you take the following example what is your expectation? > > ```cs > [Test] >...

I have taken a look into it. In your scenario the version increment strategy is set to `Increment.None` for `release` branches. That means if you not providing the version number...

May I ask you to provide an integration test please (or at least steps to reproduce)? I have no clue what you are expecting and I have no idea if...

Okay no problem. Because of missing steps to reproduce I'm going to close this issue.

This issue is probably related to #3438. 1. What I'm suprised with is that you are expecting that after tagging a pre-release version the minor, major or patch number should...