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

[greenkeeper[bot]]

Version 17.0.3 of jest just got published.

Branch	Build failing 🚨
Dependency	jest
Current Version	17.0.2
Type	devDependency

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

As jest 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 :muscle:

---

Status Details

- ✅ **wercker/build** Wercker pipeline passed [Details](https://app.wercker.com/summer-snowflake/anime-music/runs/build/582d5f73961f6301001cc737) - ✅ **wercker/brakeman** Wercker pipeline passed [Details](https://app.wercker.com/summer-snowflake/anime-music/runs/brakeman/582d5f84961f6301001cc753) - ❌ **wercker/test** Wercker pipeline failed [Details](https://app.wercker.com/summer-snowflake/anime-music/runs/test/582d5fb6b0d62f01004df89f)

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:

[greenkeeper[bot]]

After pinning to 17.0.2 your tests are passing again. Downgrade this dependency 📌.

[kaekasui]

125 にて対応