Support custom "getNextVersion" in configuration proposal for ship.js

readme.md

Is your feature request related to a problem? Please describe. Currently, It seems that ship.js support only conventional commits to get Next version.

• https://github.com/algolia/shipjs/blob/5c5cca180a37a163bef53df28d222c923eab87c2/packages/shipjs-lib/src/lib/util/getNextVersion.js

I want to custom the logic of getNextVersion. For example, I want to implement label based version management:

Calculate Next version from labels If these includes only Version: patch, next version is patch If these includes Version: patch and Version: minor, next version is minor If any one is Version: major label, next version is major

• https://gist.github.com/azu/e39fcc506eff4242beb27b84cac17b82

Describe the solution you'd like

Add new lifecyle hook like updateVersion before shouldPrepare

module.exports = {
    updateVersion: async ({revisionRange,
                     currentVersion,
                     dir}) => {
       // user defined logic
       const nextVersion = await calculateNextVersion();
       return { nextVersion } 
    }
};

• https://community.algolia.com/shipjs/reference/all-config.html

Describe alternatives you've considered

• Add { versionStrategy: "conventional-commits" | customFunction }
  • it looks like mergeStrategy

Additional context

Customization for updateVersion logic may be used for independent mode.