An in-range update of serve-static is breaking the build 🚨

[greenkeeper]

Version 1.12.3 of serve-static just got published.

Branch	Build failing 🚨
Dependency	serve-static
Current Version	1.12.2
Type	devDependency

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

As serve-static 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.12.3

• deps: send@0.15.3
  • deps: debug@2.6.7

Commits

The new version differs by 3 commits.

• 281475f 1.12.3
• b39c5c8 deps: send@0.15.3
• b28d2b0 build: eslint-plugin-markdown@1.0.0-beta.6

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]

Version 1.12.4 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

1.12.4

• deps: send@0.15.4
  • deps: debug@2.6.8
  • deps: depd@~1.1.1
  • deps: http-errors@~1.6.2

Commits

The new version differs by 6 commits.

• c16b4d1 1.12.4
• 52c2ece deps: send@0.15.4
• ba7c65b build: support Node.js 8.x
• 93a7d2c build: eslint-plugin-node@5.1.0
• c36df59 build: eslint-plugin-import@2.6.1
• c3e33f5 build: Node.js@7.10

See the full diff