This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage increased (+0.02%) to 98.002% when pulling 88d93fe668a0c1aa249042559b2c7da08c0f45ff on greenkeeper-cz-conventional-changelog-2.0.0 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Hello lovely humans,
cz-conventional-changelog just published its new version 2.0.0.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
2.0.0 (2017-02-21)
Features
Breaking Changes
closes #17
(2d78e1d4)
The new version differs by 22 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 22 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.