The version 2.1.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of cz-conventional-changelog.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv2.1.0
<a name"2.1.0">
2.1.0 (2017-10-27)
Features
prompt: add confirmation fields + edit for clarity (#58) (d40ac2c5)
Commits
The new version differs by 20 commits.
d40ac2cfeat(prompt): add confirmation fields + edit for clarity (#58)
f7a770eMerge pull request #57 from Epitrochoid/remove-unused-dep
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 310443e9611c1765fc0b978147444a40c2c78bc2 on greenkeeper/cz-conventional-changelog-2.1.0 into 2721cfc2e3529403d27a3753b62e207f1f83211c on master.
Version 2.1.0 of cz-conventional-changelog was just published.
The version 2.1.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of cz-conventional-changelog.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.1.0<a name"2.1.0">
2.1.0 (2017-10-27)
Features
Commits
The new version differs by 20 commits.
d40ac2c
feat(prompt): add confirmation fields + edit for clarity (#58)
f7a770e
Merge pull request #57 from Epitrochoid/remove-unused-dep
2d1095b
Removed unused pad-right dependency
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
There are 20 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: