Update coveralls to the latest version 🚀 #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
1 similar comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
e7ae2bfversion bump; logger test fix9b892bfVerbose use log leveldebug9cfb496Add buildkite support (#177)aa8c257Done callback waits for unlink in testRepoTokenDetection to prevent race condition (#179)18c71c2Fix a mistype in tests: fs.exists -> fs.existsSync (#184)bd667c6Add Semaphore support (#180)10d8b3eUpdate examples to include Jest (#183)720ee7cAdd license (#175)83ff2cbAdd mention about AppVeyor to the README (#164)2ed4d09major version bump for node > 4.x5ebe57fbump version428780cExpand allowed dependency versions to all API compatible versions (#172)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴