The version 11.4.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 nyc.
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.
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).
Version 11.4.1 of nyc was just published.
The version 11.4.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 nyc.
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 13 commits.
b473820chore(release): 11.4.14e4f428fix: explicitly update spawn-wrap (#748)456fa20docs: hide the header in the issue template on render [skip ci] (#731)e8225d5chore(release): 11.4.093efc55chore: upgrading to newer spawn-wrap (#730)879631arefactor: slight tweak to how we extract the --nycrc-path785fccbfeat: allow alternate path for .nycrc to be specified (#724)4ff7a38docs: fix package.json examples: s/script/scripts (#722)9f2894fchore: babel-preset-es2015 => babel-preset-env (#705)2dee543docs: correct check-coverage shorthand example (#715)7ea96bafix: always invoke instrumenter callback, set appropriate exit-code (#703)7294308docs: Correct examples in README.md (#702)6286bf8docs: update exclude defaults (#701)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: