The version 3.0.1 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 coveralls.
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 remained the same at 91.346% when pulling 43acd4905020b22e4132d327bc3e5988dd7fa56f on greenkeeper/coveralls-3.0.1 into e341df21e116435fa2f644cd8a8621ced1bdd506 on master.
Version 3.0.1 of coveralls was just published.
The version 3.0.1 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 coveralls.
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
Additional CI supportMaintenance:
Commits
The new version differs by 12 commits ahead by 12, behind by 1.
e7ae2bf
version bump; logger test fix
9b892bf
Verbose use log level
debug
9cfb496
Add buildkite support (#177)
aa8c257
Done callback waits for unlink in testRepoTokenDetection to prevent race condition (#179)
18c71c2
Fix a mistype in tests: fs.exists -> fs.existsSync (#184)
bd667c6
Add Semaphore support (#180)
10d8b3e
Update examples to include Jest (#183)
720ee7c
Add license (#175)
83ff2cb
Add mention about AppVeyor to the README (#164)
2ed4d09
major version bump for node > 4.x
5ebe57f
bump version
428780c
Expand allowed dependency versions to all API compatible versions (#172)
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: