An in-range update of codecov is breaking the build 🚨

[dgac]

An in-range update of codecov is breaking the build 🚨

[greenkeeper]

After pinning to 3.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency codecov was updated from 3.2.0 to 3.3.0.

Your tests are still failing with this version. Compare changes

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

There are 21 commits in total.

See the full diff

[greenkeeper]

• The devDependency codecov was updated from 3.3.0 to 3.4.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

• bdb3769 v3.4.0
• 25a4e6b Add support for heroku CI (#127)
• b811a12 Update to use Jest (#124)
• a19d8f6 v3.3.0

See the full diff