Should the release task honor autoBump?

[tacascer]

Thanks for maintaining this awesome plugin!

Currently, documentation states that the release task doesn't honor the autoBump setting.

Is it possible for the release task to honor the setting?

Use Case

We have a CI workflow that always run release version on a merge to main. We would like it to only create new releases if the commit was prefixed with one of the "major", "minor", "fix" messages.

[jmongard]

I think the release task always need to force a version change if there are no changes (similar to autoBump = true).
Otherwise, it would result in releasing the exact same version twice, and creating the same tag again is not possible.
If tagging is turned off, it would technically be possible to create identical release commit messages—but wouldn’t that just be confusing?

But I guess you would like a flag that stops the release task without any error if there are no changes?

[tacascer]

Yeah a flag that turns release into a no-op when it wouldn't increment the version would be nice.