Make the bump version rules configurable

[jsurkont]

Is your feature request related to a problem? Please describe.

The new bump flag is great! However, since 4eef684 the default behavior for zero-based releases is problematic, i.e. features always bump the minor version, while breaking changes bump the major version, including from 0 to 1. I think this is an undesired behavior for projects following the bump rules described in next_version.

Describe the solution you'd like

I think it should be possible to opt out from the default behavior. That is, the hardcoded values in

git-cliff/git-cliff-core/src/release.rs

Lines 117 to 118 in 4eef684

	.with_features_always_increment_minor(true)
	.with_breaking_always_increment_major(true)

should take values form the configuration instead.

Describe alternatives you've considered

I couldn't think of any alternative (other than forking the project).

Additional context

If you would be interested, I could write a PR for it.

[ribeaud]

Any news or opinion on that one? We would be interested as well...

[orhun]

Hello! I think it would be nice to have this, @jsurkont are you still interested in creating a PR?

[jsurkont]

Hello @orhun! Yes, I still am. I'll create a PR soon.