The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of karma.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv2.0.0
Bug Fixes
config: Call debug log methods after setting the loglevel based upon config/cli-options. (99fd3f0)
config: Call debug log methods after setting the loglevel based upon config/cli-options. (a340dae)
config: Retry install with appveyor-retry. (17d5791)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 93.846% when pulling 661f454dc2fc0ee61023a3238d85b4b04c743a8a on greenkeeper/karma-2.0.0 into 0c7b5a422f3b1c63eceeeee88bcf392b68b20a67 on master.
Version 2.0.0 of karma was just published.
The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of karma.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0Bug Fixes
Features
Commits
The new version differs by 73 commits.
db41e8e
chore: release v2.0.0
0a1a8ef
chore: update contributors
1afcb09
chore: add yarn.lock
f64e1e0
Merge pull request #2899 from outsideris/fix-bad-url-in-stacktrace
78ad12f
refactor(server): move compile step to first run
34dc7d3
fix(reporter): show file path correctly when urlRoot specified
b53929a
Merge pull request #2712 from macjohnny/patch-1
c9e1ca9
feat: better string representation of errors
10fac07
Merge pull request #2885 from karma-runner/prep-2
00e3f88
chore: remove yarn.lock for now
60dfc5c
feat: drop core-js and babel where possible
0e1907d
test: improve linting and fix test on node 4
af0efda
test(e2e): update cucumber step definitions
c3ccc5d
chore(ci): focus on even node versions
bf25094
chore(deps): update to latest
There are 73 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: