The version 2.9.4 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 commitizen.
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 Notesv2.9.4
2.9.4 (2017-01-06)
Bug Fixes
commit: fix multiline commits with newlines (1d3139f0, closes #373)
Commits
The new version differs by 30 commits .
1d3139ffix(commit): fix multiline commits with newlines
a97e3f8ci(coverage): remove already tested branches not showing up in coverage
dd9298fchore(package): update find-node-modules to version 1.0.4 (#384)
0ac499cMerge branch 'master' of github.com:commitizen/cz-cli
e02c705Allow using ES6 modules with default export (#328)
89b9a03chore(package): update babel-core to version 6.18.2 (#379)
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.9.4 of commitizen just got published.
The version 2.9.4 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 commitizen. 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.9.42.9.4 (2017-01-06)
Bug Fixes
Commits
The new version differs by 30 commits .
1d3139ffix(commit): fix multiline commits with newlinesa97e3f8ci(coverage): remove already tested branches not showing up in coveragedd9298fchore(package): update find-node-modules to version 1.0.4 (#384)0ac499cMerge branch 'master' of github.com:commitizen/cz-clie02c705Allow using ES6 modules with default export (#328)89b9a03chore(package): update babel-core to version 6.18.2 (#379)2eb14c2ci(appveyor): retry failed npm installs2a09176ci(appveyor): bypass npm cacheafb47f7chore(package): update inquirer to version 1.2.3 (#385)3b9f0a6Update shelljs to version 0.7.5 🚀 (#372)7d7b2e3chore(package): update lodash to version 4.17.2 (#389)6deeb1dchore(package): update ghooks to version 1.3.2 (#277)c9d6c11chore(package): update babel-preset-stage-2 to version 6.18.0 (#371)0b9e519chore(package): update babel-preset-es2015 to version 6.18.0 (#370)3aae4f6chore(package): update babel-cli to version 6.18.0 (#369)There are 30 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: