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

[greenkeeper]

The devDependency @types/jest was updated from 24.0.21 to 24.0.22.

🚨 View failing branch.

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

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ Test on node 12.x and macOS-latest: null
• ❌ Test on node 12.x and windows-latest: There are 2 failures, 0 warnings, and 0 notices.
• ✅ Test on node 12.x and ubuntu-latest: null
• ✅ Test on node 10.x and macOS-latest: null
• ❌ Test on node 10.x and windows-latest: There are 2 failures, 0 warnings, and 0 notices.
• ✅ Test on node 10.x and ubuntu-latest: null
• ✅ Test on node 8.12.x and macOS-latest: null
• ❌ Test on node 8.12.x and windows-latest: There are 1 failures, 0 warnings, and 0 notices.
• ✅ Test on node 8.12.x and ubuntu-latest: null

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• The devDependency @types/jest was updated from 24.0.22 to 24.0.23.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/jest was updated from 24.0.23 to 24.0.24.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

[greenkeeper]

• The devDependency @types/jest was updated from 24.0.24 to 24.0.25.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

[agilgur5]

This was probably failing due to the intermittent persistent CI errors that #504 fixed.