Can you use PR title when determining version like in V5?

[n-rowe]

We have a CD pipeline for pull requests that will run tests and deploy to a staging environment, upon completion we merge to the main branch for deployment to production environments.

We recently upgraded from GitVersion v5 to v6 and we used to use the Mainline mode.

Is there a way to correctly determine the version whilst taking into account the PR title?
e.g., a PR of feat!: add something new is a breaking change so should increment the semver major version.

This isn't exclusive to major versions either, it seems to just not increment the version at all. I'm assuming this is caused by commit-message-incrementing: MergeMessageOnly. We have this set because of the squash merges we perform, if we didn't have it set the versions would be completely incorrect.

This is the config we use right now:

major-version-bump-message: "^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\\([\\w\\s-]*\\))?(!:|:.*\\n\\n((.+\\n)+\\n)?BREAKING CHANGE:\\s.+)"
minor-version-bump-message: "^(feat)(\\([\\w\\s-]*\\))?:"
patch-version-bump-message: "^(build|chore|ci|docs|fix|perf|refactor|revert|style|test)(\\([\\w\\s-]*\\))?:"
strategies:
  - ConfiguredNextVersion
  - Mainline
branches:
  feature:
    label: feature
  pull-request:
    label: beta{Number}
mode: ContinuousDelivery
commit-message-incrementing: MergeMessageOnly