The version 12.0.2 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).
Coverage remained the same at 100.0% when pulling 479174b27561758e36ee1895df6f186b63be3659 on greenkeeper/nyc-12.0.2 into 348fb5b62fcd01f93cfc768859a82458e093d035 on master.
Coverage remained the same at 100.0% when pulling 479174b27561758e36ee1895df6f186b63be3659 on greenkeeper/nyc-12.0.2 into 348fb5b62fcd01f93cfc768859a82458e093d035 on master.
Version 12.0.2 of nyc was just published.
nyc
The version 12.0.2 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 95 commits.
adb310c
chore(release): 12.0.2
ddc9331
fix: stop bundling istanbul-lib-instrument due to npm issue on Node 6 (#854)
b4c325b
fix: don't bundle istanbul-lib-instrument due to Node 6 issues
9fc20e4
chore(release): 12.0.1
3e087d4
chore: upgrade to version of istanbul with optional catch binding (#851)
eaf3f70
chore(release): 12.0.0
19b7d21
chore: upgrade to newest version of istanbul codebase (#848)
570a08a
chore(release): 11.9.0
1329a3b
feat: add option that allows instrument to exit on error (#850)
bc9ffe5
chore(release): 11.8.0
9def3eb
feat: merge together multiple istanbul format reports (#840)
43bda0c
chore(release): 11.7.3
c20f8da
security: address all vulnerabilities (#836)
4bdd42c
chore(release): 11.7.2
bd77538
test: cache clear was breaking build (#835)
There are 95 commits in total.
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: