The current semver inc logic tries to encode the scope of the change by incrementing n times for each semver level branch in the PR. I find that very useful especially for gauging risk app deployments. But for libraries, versions kind of double as a bit of branding. So it might be nice to have a vanity mode that has the minimum necessary semver change. E.g. if there's any minors, increment minor once, and do not increment patches.
It is basically just reversing the current loop. But special care needs to be taken to ensure pre-release inc's aren't erased by a latter semver level inc.
The current semver inc logic tries to encode the scope of the change by incrementing n times for each semver level branch in the PR. I find that very useful especially for gauging risk app deployments. But for libraries, versions kind of double as a bit of branding. So it might be nice to have a vanity mode that has the minimum necessary semver change. E.g. if there's any minors, increment minor once, and do not increment patches.
It is basically just reversing the current loop. But special care needs to be taken to ensure pre-release inc's aren't erased by a latter semver level inc.