coveralls
commented
6 years ago Coverage remained the same at 100.0% when pulling 8c81cbd629de3dd1c64cb6ada8a04300e9fc69d2 on greenkeeper/update-notifier-2.4.0 into c7b08d6e948dc4f3d31fa9757fab21ac6d988c87 on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 2.4.0 of update-notifier was just published.
The version 2.4.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 update-notifier.
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.
Commits
The new version differs by 6 commits.
edbe3d22.4.083c4daaAdd license fileaccc884Fix URI Scheme in package.json (#136)0ad8e5bUpdate URL to XO38d5679Disable on CI (#116)3e5cea0Fix typo in README (#128)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: