SetNextMutualDependenciesReleaseWorker always updates minor version number

[andreaswolf]

As the title says, even when performing a patchlevel (or major) release, the minor version number is always updated.

For a release of 0.4.1, this will lead to the dependencies being set to ^0.5 and the branch alias 0.5-dev, which is not always desirable, as long as you're not working on the next incompatible release.

For a release of 1.0, this will lead to the dependencies being set to ^1.1 and the branch alias 1.1-dev, which might also be wrong if you're creating a release branch for the 1.x series and want to continue developing 2.0 on main.

IMO it would be best to somehow be able to specify if and how the version should be raised (e.g. with a parameter with values "major"/"minor"/"unchanged").

[kayw-geek]

This seems like can be resole your issue.

[andreaswolf]

Unfortunately not, because raising the minor version is hardcoded in VersionUtils.