This version is covered by your current version range and after updating it in your project the build failed.
level-errors is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/ralphtheninja/pgdown/builds/273853046?utm_source=github_status&utm_medium=notification)
Commits
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
After pinning to 1.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 1.1.1 of level-errors just got published.
This version is covered by your current version range and after updating it in your project the build failed.
level-errors is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/ralphtheninja/pgdown/builds/273853046?utm_source=github_status&utm_medium=notification)Commits
The new version differs by 3 commits.
df4adb0
1.1.1
75657e0
Merge pull request #9 from MeirionHughes/master
d74d190
fix: error cause param
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: