Can't release because commit does not validate with commitlint

Using,

    "@commitlint/cli": "^5.0.0",
    "@commitlint/config-angular": "^5.0.0",

with standard version, fails with:

husky > npm run -s commitmsg (node v8.4.0)

⧗   input: chore(release): 1.0.0
✖   subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
✖   type must be one of [build, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]
✖   found 2 problems, 0 warnings

husky > commit-msg hook failed (add --no-verify to bypass)

Command failed: git commit CHANGELOG.md package.json package-lock.json -m "chore(release): 1.0.0"
husky > npm run -s precommit (node v8.4.0)

Running tasks for *.js [started]
Running tasks for *.js [skipped]
→ No staged files match *.js
husky > npm run -s commitmsg (node v8.4.0)

⧗   input: chore(release): 1.0.0
✖   subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
✖   type must be one of [build, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]
✖   found 2 problems, 0 warnings

Perhaps the type and message need to be adjusted?

//cc @marionebl @bcoe

[marionebl]

This is caused by commitlint switching to the new Angular (vs. Angular.js) commit conventions with version 5.0.0.

I think we should update standard-version to match the latest conventions.

You can fall back to @commitlint/config-angular@4 until that lands.

[bcoe]

@satazor see conversation here, @marionebl has done a great job of outlining some of the work that we’d need to take on to simplify the commit conventions.