coveralls
commented
8 years ago Coverage remained the same at 100.0% when pulling 2a5936fe2282f536c25fb18ed935f4b647246f86 on greenkeeper-postcss-5.1.0 into 7916e50c47e3cc991920f07ae0d1e54dbff0f752 on master.
Hello lovely humans,
postcss just published its new version 5.1.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As postcss is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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:
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade