The version 11.0.3 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 nyc.
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.
Commits
The new version differs by 17 commits.
e9fad9fdocs: add note about tap-nyc to README (#614)
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 11.0.3 of nyc just got published.
The version 11.0.3 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 nyc. 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.
Commits
The new version differs by 17 commits.
e9fad9fdocs: add note about tap-nyc to README (#614)f86b0b1chore(release): 11.0.3923b062fix: upgrade to spawn-wrap version that works with babel-register (#617)b1eb4d6fix: update help link to list of reporters (#601)e4eff12chore(release): 11.0.20c2ef43chore: upgrade to newer version of spawn-wrap (#592)9d47986chore(release): 11.0.1fa1097achore: acutally swap in new copy of signals.js8662357chore: hack to fix SIGPROF binding issue on node 8d90aed6chore(release): 11.0.02f68559chore: hack to prevent SIGPROF warning, until new spawn-wrap is availablef18f780fix: add support for ES6 modules0e6b277chore: formatting nit80ef0a3docs: mention the ability to publish configuration in docs33829b8feat: upgrade to version of yargs with support for presetsThere are 17 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: