Closed greenkeeperio-bot closed 8 years ago
@@ master #38 diff @@
==========================================
Files 26 26
Lines 882 882
Methods 138 138
Messages 0 0
Branches 132 132
==========================================
Hits 653 653
Misses 229 229
Partials 0 0
Powered by Codecov. Last update 7cf3ef0...d374cef
Hello lovely humans,
karma-mocha just published its new version 1.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 karma-mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a 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:
The new version differs by 8 commits .
d061e42
chore: release v1.1.0
fd6fa14
chore: update contributors
fe04ebb
feat(deps): update dependencies
a619350
Merge pull request #100 from christian-schulze/allow-requiring-files-after-mocka-but-before-adapter-is-initialised
f00d6b3
feat: allow requiring files via karma.conf.js
6dcb82a
chore: erge pull request #92 from Maloric/master
fd74e0b
fixup git attributes file after it was clobbered by 1.0 upgrade process
cfe7255
Updated mocha to v2.4.5
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade