An in-range update of spike-core is breaking the build 🚨

[greenkeeper]

Version 1.1.0 of spike-core just got published.

Branch	Build failing 🚨
Dependency	spike-core
Current Version	1.0.0
Type	devDependency

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

As spike-core 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

- ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/11258011),- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/static-dev/spike-collections/builds/226166040)

---

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.2.0 just got published.

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

[greenkeeper]

Version 1.3.0 just got published.

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

Release Notes

v1.3.0

• Update to latest webpack and spike-util versions -- should fix some windows issues

[greenkeeper]

Version 1.3.1 just got published.

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