The devDependency codecov was updated from `2.2.0` to `3.2.0`.

This version 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.

Find out more about this release.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper bot :palm_tree:

Feb 13 '19 02:02 greenkeeper[bot]

Codecov Report

Merging #299 into master will not change coverage. The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #299   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           4      4           
  Lines          77     77           
=====================================
  Hits           77     77

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update e3e23c1...fb51f53. Read the comment docs.

Feb 13 '19 02:02 codecov-io

The devDependency codecov was updated from 2.2.0 to 3.3.0.

Update to this version instead 🚀

Release Notes for v3.3.0

Added pipe --pipe, -l

Commits

The new version differs by 21 commits.

d81c4f4 Merge pull request #111 from TomSputz/pipe
aa5a2b0 feat(services): add Cirrus CI (#117)
00d484b v3.2.0
ad51194 Satisfy ESLint configuration
5f2d0e6 Fixed path to npm bin folder
afcf3e5 Fixed merge conflicts
145cb46 updated PR with changes from upstream
2b2ad02 merge package-lock.json from upstream
bf0c751 added documentation
9445f72 fixed wrong fixture file names
348cf7b lock dependencies
fbf17d2 remove timer because slow CI servers need more than half a second before data is flowing - switch to use --pipe or -l as signal to codecov to recieve data via stdin
b145b19 Merge branch 'master' into pipe
d460065 check if the stale state was due to using the data event instead of the readable event
e8ca9ed be very explicit about exiting process and clearing timeout