An in-range update of codecov is breaking the build π¨
greenkeeper opened this issue Β· 4 comments
The devDependency codecov was updated from 3.1.0 to 3.2.0.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Commits
The new version differs by 3 commits.
e427d90feat(services): add azure pipelines (#114)023d204Use small HTTP dependency (#110)500f308Update Readme
See the full diff
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 π΄
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.
- The
devDependencycodecov was updated from3.2.0to3.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.
d81c4f4Merge pull request #111 from TomSputz/pipeaa5a2b0feat(services): add Cirrus CI (#117)00d484bv3.2.0ad51194Satisfy ESLint configuration5f2d0e6Fixed path to npm bin folderafcf3e5Fixed merge conflicts145cb46updated PR with changes from upstream2b2ad02merge package-lock.json from upstreambf0c751added documentation9445f72fixed wrong fixture file names348cf7block dependenciesfbf17d2remove 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 stdinb145b19Merge branch 'master' into piped460065check if the stale state was due to using the data event instead of the readable evente8ca9edbe very explicit about exiting process and clearing timeout
There are 21 commits in total.
See the full diff