-
Notifications
You must be signed in to change notification settings - Fork 4
An in-range update of @types/jest is breaking the build 🚨 #25
Comments
After pinning to 24.0.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
The devDependency @types/jest was updated from
24.0.11
to24.0.12
.🚨 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
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 🌴
The text was updated successfully, but these errors were encountered: