An in-range update of morgan is breaking the build 🚨

[greenkeeper]

Version 1.9.0 of morgan just got published.

Branch	Build failing 🚨
Dependency	morgan
Current Version	1.8.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As morgan is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

1.9.0

• Use res.headersSent when available
• deps: basic-auth@~2.0.0
  • Use safe-buffer for improved Buffer API
• deps: debug@2.6.9
• deps: depd@~1.1.1
  • Remove unnecessary Buffer loading

Commits

The new version differs by 16 commits.

• 4def0fa 1.9.0
• b29fc88 docs: update license
• ddf4f8c Use res.headersSent when available
• 7348b5c docs: add example of split / dual logging
• 98d62ee docs: fix block formatting
• 6fdf1a0 docs: fix typo
• a028ae7 deps: basic-auth@~2.0.0
• 4e4f07f deps: debug@2.6.9
• 67a1be6 build: Node.js@8.6
• 188826e build: Node.js@6.11
• a5acdee build: eslint-plugin-node@5.1.1
• 1ec7060 build: eslint-plugin-import@2.7.0
• b6c0d71 build: split@1.0.1
• bbcadcf deps: depd@~1.1.1
• bb8717a build: support Node.js 8.x

There are 16 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 1.8.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.