Open greenkeeper[bot] opened 7 years ago
After pinning to 1.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 30 commits .
cc6accd
chore: release v1.5.0
8b78aa5
chore: update contributors
153880f
chore: upgrade dev dependencies
e095411
fix(client): don't crash if receive array-like results
89a7a1c
fix: filter browser logging by level of LOG
eaeffe9
docs(config): update note on config languages to include TypeScript
b40af7e
docs(dev): fix browsers_ready event heading level
aa42c41
feat: add an option to run the tests by dynamically loading test scripts without iframe
eb407ab
feat: add support for node@7
18757e6
Merge pull request #2555 from karma-runner/greenkeeper-supertest-3.0.0
01b35c4
docs(config): fix typescript comment syntax
e7dd612
Merge pull request #2564 from dryajov/master
6a7a22f
Merge pull request #2561 from danielcompton/docs-commit-msg-example
3e7eaeb
fix: make window.parent.karma available in debugged context
7f55f4f
docs(contributing): add sample commit message
There are 30 commits in total. See the full diff.
Version 1.4.0 of karma just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As karma 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:
Status Details
- ❌ **continuous-integration/codeship** Build in progress [Details](https://app.codeship.com/projects/144819/builds/21713293) - ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/rohan-buchner/MHWDashboard_Alpha/runs/build/587a80ff79d7e701008e1a12)Release Notes
v1.4.0Bug Fixes
Buffer
usage (3d94b8c)Features
config.parseConfig
on the public api (7d2c1ae)Commits
The new version differs by 42 commits .
99d647b
chore: release v1.4.0
c168b79
chore: update contributors
fbbeccf
fix(reporter): strip only hostname/port
3a618b3
feat(client): capture confirm & prompt
35965d9
fix(browser): filter browser logging by level
305df2c
fix(reporters): cannot read property map of undefined
79bc193
Merge pull request #2510 from karma-runner/greenkeeper-useragent-2.1.10
e89f092
Merge pull request #2527 from karma-runner/greenkeeper-qunitjs-2.1.1
85beac2
Merge pull request #2530 from karma-runner/greenkeeper-eslint-plugin-react-6.9.0
daeb31e
Merge pull request #2531 from karma-runner/greenkeeper-grunt-auto-release-0.0.7
ea40f15
chore(package): update grunt-auto-release to version 0.0.7
495ab0c
chore(package): update eslint-plugin-react to version 6.9.0
c20d004
chore(package): update qunitjs to version 2.1.1
13cefee
Merge pull request #2503 from karma-runner/greenkeeper-eslint-3.12.1
c9a3a63
docs(config): add jsdom to the browser launchers list
There are 42 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: