The version 2.0.0 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 cz-conventional-changelog.
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.0.0
2.0.0 (2017-02-21)
Features
adapter: Split breaking changes into separate question (#44) (2d78e1d4, closes #17)
Breaking Changes
Breaking changes now automatically include the "BREAKING CHANGE: " prefix.
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.0.0 of cz-conventional-changelog just got published.
The version 2.0.0 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 cz-conventional-changelog. 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.0.02.0.0 (2017-02-21)
Features
Breaking Changes
closes #17
(2d78e1d4)
Commits
The new version differs by 17 commits .
2d78e1d
feat(adapter): Split breaking changes into separate question (#44)
042eadc
Merge pull request #45 from commitizen/greenkeeper/commitizen-2.9.6
cb65107
chore(package): update commitizen to version 2.9.6
7025425
Merge pull request #40 from commitizen/greenkeeper/commitizen-2.9.5
55c74f0
chore(package): update commitizen to version 2.9.5
dadb1a2
Merge pull request #39 from commitizen/greenkeeper/commitizen-2.9.4
0d3aac1
chore(package): update commitizen to version 2.9.4
dcd7ccc
Merge pull request #38 from commitizen/greenkeeper/commitizen-2.9.3
aae8ab7
chore(package): update commitizen to version 2.9.3
0c55157
Merge pull request #37 from commitizen/greenkeeper/commitizen-2.9.2
d6315d5
chore(package): update commitizen to version 2.9.2
3d654d8
Merge pull request #35 from commitizen/greenkeeper/commitizen-2.9.0
5fb09cb
chore(package): update commitizen to version 2.9.0
ac1c81f
Merge pull request #34 from commitizen/greenkeeper/commitizen-2.8.7
a7ee137
chore(package): update commitizen to version 2.8.7
There are 17 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: