This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of update-notifier.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage increased (+0.02%) to 98.002% when pulling c8f4860db6a054770e5cb9610419f1530fb9fd63 on greenkeeper-update-notifier-2.0.0 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Hello lovely humans,
update-notifier just published its new version 2.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of update-notifier. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
Drops support for Node.js 0.10 and 0.12.
v1.0.3...v2.0.0
The new version differs by 18 commits .
d295cf3
2.0.0
fda96b6
ES2015ify
ac47d69
Improve readme
f1de1bf
Update dependencies
01fcd25
Bump minimum supported
node
version tonode@4
. (#102)e36671d
1.0.3
d66245c
Exit process on SIGINT (#98)
384e846
get tests passing on Travis CI with latest xo, etc (#97)
b72bf7f
1.0.2
c2a9565
Lazy load dependencies (#82)
38aa83a
1.0.1
32b5197
fix opts.defer check (#90)
58ed26e
fix XO lint issues
bc3ba72
docs: h3 -> h4 for options.boxenOpts (#87)
aff41f7
docs: add align: 'center' to default boxenOpts (#86)
There are 18 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.