Update validate-commit-msg to the latest version 🚀

[greenkeeper]

Version 2.13.1 of validate-commit-msg just got published.

Dependency	validate-commit-msg
Current Version	2.12.3
Type	devDependency

The version 2.13.1 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of validate-commit-msg.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Release Notes

v2.13.1

<a name"2.13.1">

2.13.1 (2017-07-23)

Bug Fixes

• CLI: correctly exit with 1 when validation fails (888617bf)

Commits

The new version differs by 3 commits.

• 888617b fix(CLI): correctly exit with 1 when validation fails
• 6d23bbc feat(release): manually release a minor version
• 7484c7f chore: Update package URLs to new org

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[coveralls]

Coverage remained the same at 80.435% when pulling e953a5b on greenkeeper/validate-commit-msg-2.13.1 into ea5d67e on master.

[greenkeeper]

Version 2.14.0 just got published.

Update to this version instead 🚀

Release Notes

v2.14.0

<a name"2.14.0">

2.14.0 (2017-07-29)

Features

• autoFix: fix the commit message case instead of ignoring case (2e048fb5)

Commits

The new version differs by 1 commits.

• 2e048fb feat(autoFix): fix the commit message case instead of ignoring case

See the full diff