This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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.
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.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 90.845% when pulling 3f7cca9afeb74f739de9b2b85df434e532e5f675 on greenkeeper-coveralls-2.11.16 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 3f7cca9afeb74f739de9b2b85df434e532e5f675 on greenkeeper-coveralls-2.11.16 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 3f7cca9afeb74f739de9b2b85df434e532e5f675 on greenkeeper-coveralls-2.11.16 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 3f7cca9afeb74f739de9b2b85df434e532e5f675 on greenkeeper-coveralls-2.11.16 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Coverage remained the same at 90.845% when pulling 3f7cca9afeb74f739de9b2b85df434e532e5f675 on greenkeeper-coveralls-2.11.16 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Hello lovely humans,
coveralls just published its new version 2.11.16.
This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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 109 commits .
8dfcfd6
version bump
4bc93ac
Merge branch 'master' of github.com:nickmerwin/node-coveralls
671acca
removed codeship badge
f390392
Merge pull request #152 from ndaidong/master
de968b0
Merge pull request #147 from hyperlink/update-request-dep
72a4046
Merge pull request #154 from a0viedo/patch-1
87b27f7
Merge pull request #142 from Hirse/feature/travis-pr
3edbecb
Merge pull request #155 from kasperlewau/master
d117e3d
reenable drone
dd230f6
don't hardcode minor version
cc0882d
Update outdate dependencies
99edf1a
Fix node-uuid deprecation by updating request dependency
c81c084
version bump
d15a6f8
Merge pull request #144 from a11smiles/master
f9c3697
implemented code to parse concatenated file paths (fixes #143)
There are 109 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.