This version is covered by your current version range and after updating it in your project the build failed.
As body-parser 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/alsatian-test/alsatian-website/builds/200555105)
Release Notes1.16.1
deps: debug@2.6.1
Fix deprecation messages in WebStorm and other editors
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).
Version 1.16.1 of body-parser just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As body-parser 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/alsatian-test/alsatian-website/builds/200555105)Release Notes
1.16.1DEBUG_FDset to1or2Commits
The new version differs by 5 commits .
7b630f71.16.1de574bfbuild: eslint@3.15.0889bcc9build: Node.js@7.5dba8ac4deps: debug@2.6.195a3ebbdocs: fix history file with incorrect qs versionSee 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: