The version 2.0.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 condition-circle.
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.
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 decreased (-5.8%) to 72.816% when pulling b21643f94f47edca02e84d959c0cd6216b182f91 on greenkeeper/condition-circle-2.0.0 into 649cd4f39525d337ded8ff82372ff449eb6b7e0c on master.
Version 2.0.0 of condition-circle was just published.
The version 2.0.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 condition-circle.
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.0.02.0.0 (2017-12-12)
break
semantic-release
11.x upgrade (26da8a0)Bug Fixes
simple-commit-message
to work w/semantic-release
11.x (de9e786)BREAKING CHANGES
semantic-release
11.x isn'tcompatible with previous versions of
condition-circle
.Commits
The new version differs by 7 commits.
ea8490a
Merge pull request #11 from bahmutov/semantic-release-11-fixes
26da8a0
break: force breaking change for
semantic-release
11.x upgrade6a8ef4f
Merge pull request #10 from bahmutov/semantic-release-11-fixes
de9e786
fix: wrap
simple-commit-message
to work w/semantic-release
11.x2a0586d
chore: add
semantic-release
11.x topeerDependencies
890f9f0
Semantic release 11 fixes (#8)
468de38
Fix publish (#7)
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: