coveralls
commented
7 years ago Coverage increased (+0.3%) to 89.298% when pulling 20509f135fb4e3cfff3d21fb67cd3ac20442e3cf on greenkeeper-karma-phantomjs-launcher-1.0.3 into 020295bc1dc418c4a58c8145d4b75139f2a4baa6 on master.
instantlinux
Hello lovely humans,
karma-phantomjs-launcher just published its new version 1.0.3.
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 karma-phantomjs-launcher. 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 5 commits .
00c3321chore: release v1.0.3c342607chore: update contributorsdb7ebc3chore: add yarn.lockfe013cdMerge pull request #131 from leightarasenko/master482eba5fix: path issue with phantomjs and phantomjs-prebuiltSee the full diff.
Screencast
Try it today. Free for private repositories during beta.