As discussed, it makes the bump-version action bump the minor version number, while the patch version number is set to 0.
This is the behavior we want to achieve on every "standard" release (where new features will be provided). For hotfix releases the process is still manual, but they should not definitely bump the snapshot version.
Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
What this PR changes/adds
As discussed, it makes the
bump-versionaction bump the minor version number, while the patch version number is set to 0. This is the behavior we want to achieve on every "standard" release (where new features will be provided). For hotfix releases the process is still manual, but they should not definitely bump the snapshot version.Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
_Please be sure to take a look at the contributing guidelines and our etiquette for pull requests._