🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
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.
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 196 commits (ahead by 196, behind by 1).
Hello lovely humans,
nyc just published its new version 10.3.2.
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 196 commits (ahead by 196, behind by 1).
e062a86chore(release): 10.3.2213206ffix: we should not create a cache folder if cache is false (#567)75713d8chore(release): 10.3.11bf74fdfix: introduced a bug that resulted in source-maps not being loaded approriately on second test run (#566)55e826dchore(release): 10.3.089dc7a6chore: explicit update of istanbul dependnecies (#562)1887d1cfeat: add support for --no-clean, to disable deleting raw coverage output (#558)ff73b18fix: source-maps were not being cached in the parent process when --all was being used (#556)2ff8f3bchore: test node 6 on travis (#553)3c0d81fdocs(readme): move advanced features to docs site (#551)fdf3e97docs: switch to conventional commits badge9f2d45fdocs(readme): link to available reporters (#546)455619fchore(release): 10.2.095cc09afeat: upgrade to version of yargs with extend support (#541)43535f9chore: explicit update of istanbuljs dependencies (#535)There are 196 commits in total. See the full diff.