Open greenkeeper[bot] opened 6 years ago
After pinning to 3.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
Security fixes
Your tests are still failing with this version. Compare the changes π¨
Custom Yaml file
Token from .codecov.yml
The new version differs by 7 commits.
0ce3c76
v3.1.0
7c1f16e
fix: support .codecov.yml
/codecov.yml
files for token (#108)
1fff4dc
Allow custom yaml
file. (#107)
77d7a5e
Add ESLint (#93)
625807c
Removing Makefile (#104)
94cd1c6
Change from istanbul to nyc (#103)
b0b580b
Update README.md
See the full diff
devDependency
codecov was updated from 3.1.0
to 3.2.0
.Your tests are still failing with this version. Compare changes
devDependency
codecov was updated from 3.2.0
to 3.3.0
.Your tests are still failing with this version. Compare changes
Added pipe --pipe
, -l
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
Version 3.0.3 of codecov was just published.
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
- β **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/acinader/parse-aws-firehose-logger-adapter/builds/400726962?utm_source=github_status&utm_medium=notification)Release Notes
v3.0.3Fix for not git repos
Commits
The new version differs by 3 commits.
15cdae3
v3.0.3
39dc2d8
Support non-git/hg root dirs (#75)
a19efbe
Updated readme
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: