An in-range update of jsdoc-to-markdown is breaking the build 🚨
Closed this issue · 1 comments
greenkeeper commented
Version 3.0.2 of jsdoc-to-markdown was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | jsdoc-to-markdown |
| Current Version | 3.0.1 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
jsdoc-to-markdown 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
- ❌ bitHound - Dependencies null Details
- ❌ bitHound - Code null Details
- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
- ✅ coverage/coveralls First build on greenkeeper/jsdoc-to-markdown-3.0.2 at 93.162% Details
- ✅ security/snyk No new issues Details
- ❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details
- ✅ codecov/project 93.16% remains the same compared to b8b0a47 Details
- ✅ codecov/patch Coverage not affected when comparing b8b0a47...a647480 Details
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 🌴
greenkeeper commented
After pinning to 3.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.