karma-ng-scenario
karma-ng-scenario copied to clipboard
karma-runner
[email protected] breaks build ⚠️
Hello lovely humans,
karma just published its new version 1.6.0.
| State | Failing tests :warning: |
|---|---|
| Dependency | karma |
| New version | 1.6.0 |
| Type | devDependency |
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:
Bug Fixes
- client: add proxy support to stringify (be10116)
- file-list: always use file from first matcher (74bfdf3)
- middleware: does not work with mootools (#2591) (2685e13)
- reporter: keep users exact formatError result (17c2c43)
Features
- browser: add browser_info event (09ac7d7), closes #2192
- launcher: output stderr for failing launchers (7d33398)
- proxy: add proxy events to config (f5d99fb)
| ✨ Try the all new Greenkeeper GitHub Integration ✨ |
|---|
With Integrations first-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. |
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.
- If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
- If you signed the CLA as a corporation, please let us know the company's name.
