Jean-Philippe Lévesque

>Also, provide a mechanism to be able to override the default font provided by the libraries. This is a important requirement for projects.

Just to be clear, I'm not reporting this as a regression of any kind. Just as a bug. 😊

> Why do you think `no-bump-message` should take precedence? Mainly intuition to be honest. I just thought that would be the behavior. ## Reasoning What is expected when enabling `commit-message-incrementing`?...

I'm enforcing the usage of [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). Knowing that, the version is driven by the conventional commit message **type** (fix, feat, chore, docs, (...), and the presence of `!` or...

> Have you read the [section on conventional commits in the documentation](https://gitversion.net/docs/reference/version-increments#conventional-commit-messages)? Yes! That's what I used to create my config.

@asbjornu I've created this draft PR https://github.com/GitTools/GitVersion/pull/3202 to start the conversation. I'm assuming the target branch is incorrect if this changed is aimed toward v6?

Thanks! 🚀

> Do you feel like this is ready for review now, @jeanplevesque? Yep! 😀

I think I'm having this problem too but with `IObservable`. 

Any update on this? We have the same use-case: migrating from UWP to WinUI.