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 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.
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.
Coverage remained the same at 87.302% when pulling 8981c524e0a8b5716ff2febbad15a3cb914338d5 on greenkeeper-nyc-8.3.0 into db9191fee1c38b0ecf39d78d8b7943909a8a05e2 on master.
Coverage remained the same at 87.302% when pulling 9424a523702f9cb5595818e514267999af483ff0 on greenkeeper-nyc-8.3.0 into f6c8a8140c59b60a8983505181a6338dfe374cdf on master.
Coverage remained the same at 87.302% when pulling ec1645851d1e161c60df41c3fd1bd9f7dd718b98 on greenkeeper-nyc-8.3.0 into 296441951f25615705d4f7c143044550670ab3b4 on master.
Hello lovely humans,
nyc just published its new version 8.3.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 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.
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:
The new version differs by 22 commits .
0aae39d
chore(release): 8.3.0
b7a413a
fix: add a feature which allows us to bust the cache when breaking changes are introduced (#394)
1c2349b
feat: add support for .nycrc (#391)
bc0a99a
chore: accidentally left lib/config.js in merge conflict
a9bdf0f
fix: upgrade to newer versions of source-map, signal-exit, and instrument (#389)
99dbbb3
feat: refactored config to fix precedence of config vs. args (#388)
9ebaea8
fix: add shim for check-coverage on node 0.10 (#386)
ec2920f
chore(package): update requirejs to version 2.3.0 (#380)
0e095bc
chore(package): update which to version 1.2.11 (#382)
b9c0aea
chore(release): 8.2.0
fabe5f3
feat: gather process tree information (#364)
64c68b7
fix: upgrade standard, and a few other dependencies. fix standard nits (#375)
6d32604
cleanup: simplify istanbul-lib-coverage API usage (#369)
d9709f8
chore(package): update tap to version 7.0.0 (#368)
1189f3a
docs: update README.md (#366)
There are 22 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade