Open greenkeeper[bot] opened 6 years ago
devDependency
karma-coverage-istanbul-reporter was updated from 1.4.3
to 2.0.5
.Update to this version instead ๐
The new version differs by 9 commits.
a7cc756
chore(release): 2.0.5
ec01a4c
Merge pull request #61 from peitschie/master
ab284d4
build: upgrade other dependencies
475bfc2
build: upgrade istanbul-api and other dependencies to fix npm audit vulns
9987287
test: fix tests with latest istanbul changes
b0c364d
chore: add .idea to gitignore
66fd2ef
build: fix coverage-generating tests on windows
38087c2
fix: don't double-report files with mixed slashes in their names on windows
3c48bf8
fix: correctly strip source file prefixes when no webpack.context is defined
See the full diff
devDependency
karma-coverage-istanbul-reporter was updated from 1.4.3
to 2.0.6
.Update to this version instead ๐
The new version differs by 11 commits.
8fee4a9
chore(release): 2.0.6
7a34b47
Merge branch 'master' of github.com:mattlewis92/karma-coverage-istanbul-reporter
ca17ed1
build: fix code coverage
619d90d
fix: get source code from sourceMapStore on write report
5496d47
style: reformat code with prettier
0261f70
build: upgrade dependencies
a2c359b
docs: format readme
df3d5df
chore: share probot config
b55478f
build: add issue template enforcer
65e0b5d
docs: add patreon
ce38d2d
test: fix tests on node 6
See the full diff
devDependency
karma-coverage-istanbul-reporter was updated from 1.4.3
to 2.1.0
.
Version 2.0.0 of karma-coverage-istanbul-reporter was just published.
karma-coverage-istanbul-reporter
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-coverage-istanbul-reporter.
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.
Commits
The new version differs by 3 commits.
18f2c67
chore(release): 2.0.0
9f0cb11
build: fix linting rules
26ad3af
feat: drop support for node 4
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: