not fully conventional commit compliant

[segator]

if you commit feat!: foo bar is not trying to bump a major unless
you define explicitly major-keywords: feat!

it is fine to set it but I would expect the GH action is fully compliant with https://www.conventionalcommits.org/en/v1.0.0/

[virgofx]

Hey @segator Yeah you're absolutely right - we took a more flexible approach initially rather than going full conventional commits spec.

I think your suggestion makes perfect sense. We could add something like use_conventional_commits_for_version_bumps (or maybe conventional_commits_compliance to keep it shorter?) and when that's enabled, leverage a proper conventional commits package for parsing.

Then we'd fall back to the existing major/minor/patch regex logic when it's disabled, so we don't break anyone's current setup.
That way people get the best of both worlds - full spec compliance if they want it, or the current flexible approach if they prefer that. Should be pretty straightforward to implement too.

[segator]

sounds good to me! TY