Seems to be broken with newest semantic release version

[sonicoder86]

I try to use the package with semantic-release version 15.13.24
I get this output:

> CI=true semantic-release

[2:53:20 PM] [semantic-release]    Running semantic-release version 15.13.24
[2:53:21 PM] [semantic-release]    Loaded plugin "verifyConditions" from "@semantic-release/npm"
[2:53:21 PM] [semantic-release]    Loaded plugin "verifyConditions" from "@semantic-release/github"
[2:53:21 PM] [semantic-release]    Loaded plugin "analyzeCommits" from "@bubltechnology/customizable-commit-analyzer"
[2:53:21 PM] [semantic-release]    Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[2:53:21 PM] [semantic-release]    Loaded plugin "prepare" from "@semantic-release/npm"
[2:53:21 PM] [semantic-release]    Loaded plugin "publish" from "@semantic-release/npm"
[2:53:21 PM] [semantic-release]    Loaded plugin "publish" from "@semantic-release/github"
[2:53:21 PM] [semantic-release]    Loaded plugin "success" from "@semantic-release/github"
[2:53:21 PM] [semantic-release]    Loaded plugin "fail" from "@semantic-release/github"
[2:53:21 PM] [semantic-release]    Run automated release from branch master
[2:53:22 PM] [semantic-release]    Allowed to push to the Git repository
[2:53:22 PM] [semantic-release]    Start step "verifyConditions" of plugin "@semantic-release/npm"
[2:53:22 PM] [semantic-release] [@semantic-release/npm]    Verify authentication for registry https://registry.npmjs.org/
[2:53:23 PM] [semantic-release]    Completed step "verifyConditions" of plugin "@semantic-release/npm"
[2:53:23 PM] [semantic-release]    Start step "verifyConditions" of plugin "@semantic-release/github"
[2:53:23 PM] [semantic-release] [@semantic-release/github]    Verify GitHub authentication
[2:53:23 PM] [semantic-release]    Completed step "verifyConditions" of plugin "@semantic-release/github"
[2:53:23 PM] [semantic-release]    No git tag version found
[2:53:23 PM] [semantic-release]    No previous release found, retrieving all commits
[2:53:23 PM] [semantic-release]    Found 2 commits since last release
[2:53:23 PM] [semantic-release]    Start step "analyzeCommits" of plugin "@bubltechnology/customizable-commit-analyzer"
[2:53:24 PM] [semantic-release]    Failed step "analyzeCommits" of plugin "@bubltechnology/customizable-commit-analyzer"
[2:53:24 PM] [semantic-release]    An error occurred while running semantic-release: { TypeError: cb is not a function
at module.exports (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/@bubltechnology/customizable-commit-analyzer/index.js:16:3)
at validator (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at pReduce (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/semantic-release/lib/plugins/pipeline.js:37:40)
at next (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/p-reduce/index.js:17:9)
at process._tickCallback (internal/process/next_tick.js:68:7) pluginName: '@bubltechnology/customizable-commit-analyzer' }
{ TypeError: cb is not a function
at module.exports (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/@bubltechnology/customizable-commit-analyzer/index.js:16:3)
at validator (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at pReduce (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/semantic-release/lib/plugins/pipeline.js:37:40)
at next (/home/rof/src/github.com/emartech/typescript-package-example/node_modules/p-reduce/index.js:17:9)
at process._tickCallback (internal/process/next_tick.js:68:7) pluginName: '@bubltechnology/customizable-commit-analyzer' }npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @emartech/typescript-package-example@ release: `CI=true semantic-release`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @emartech/typescript-package-example@ release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rof/.npm/_logs/2019-08-30T14_53_24_056Z-debug.log