The version 2.9.6 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.
afb47f7chore(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)
There are 116 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).
Coverage remained the same at 100.0% when pulling 9439867223c8bed0c6691cbd3e449ca25dd63392 on greenkeeper/commitizen-2.9.6 into 0dd75ddf48b1c7579e74c72514fdeb2768c2ab9a on master.
Coverage remained the same at 100.0% when pulling 9439867223c8bed0c6691cbd3e449ca25dd63392 on greenkeeper/commitizen-2.9.6 into 0dd75ddf48b1c7579e74c72514fdeb2768c2ab9a on master.
Coverage remained the same at 100.0% when pulling 9439867223c8bed0c6691cbd3e449ca25dd63392 on greenkeeper/commitizen-2.9.6 into 0dd75ddf48b1c7579e74c72514fdeb2768c2ab9a on master.
Version 2.9.6 of commitizen just got published.
The version 2.9.6 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.62.9.6 (2017-02-16)
Bug Fixes
Commits
The new version differs by 116 commits .
2a101b8
fix: bump vulnerable dependency (#421)
b17eecb
docs(readme): link to contributing (#419)
825485c
fix(commit): fix multiline commits with newlines (#413)
247d2c4
style: update spacing to follow eslint (#412)
1d3139f
fix(commit): fix multiline commits with newlines
a97e3f8
ci(coverage): remove already tested branches not showing up in coverage
dd9298f
chore(package): update find-node-modules to version 1.0.4 (#384)
0ac499c
Merge branch 'master' of github.com:commitizen/cz-cli
e02c705
Allow using ES6 modules with default export (#328)
89b9a03
chore(package): update babel-core to version 6.18.2 (#379)
2eb14c2
ci(appveyor): retry failed npm installs
2a09176
ci(appveyor): bypass npm cache
afb47f7
chore(package): update inquirer to version 1.2.3 (#385)
3b9f0a6
Update shelljs to version 0.7.5 🚀 (#372)
7d7b2e3
chore(package): update lodash to version 4.17.2 (#389)
There are 116 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: