Update update-notifier to the latest version 🚀

[greenkeeper[bot]]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.5.0 of update-notifier was just published.

Dependency	update-notifier
Current Version	2.4.0
Type	dependency

The version 2.5.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.

---

Release Notes

v2.5.0

Add ability to bypass isNpm check with shouldNotifyInNpmScript option.

Commits

The new version differs by 2 commits.

• 5cd6577 2.5.0
• ac0d3cb Add ability to bypass isNpm check with shouldNotifyInNpmScript option (#127)

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:

[coveralls]

Coverage remained the same at 100.0% when pulling e90d7cb130bb4eeb33ff929e91b4303503033032 on greenkeeper/update-notifier-2.5.0 into 76b47e114fdf27d2ce5cec5b795a7ae2aacee83f on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e90d7cb130bb4eeb33ff929e91b4303503033032 on greenkeeper/update-notifier-2.5.0 into 76b47e114fdf27d2ce5cec5b795a7ae2aacee83f on master.