An in-range update of @types/jasmine is breaking the build 🚨
greenkeeper opened this issue · 5 comments
Version 2.8.7 of @types/jasmine was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency |
@types/jasmine
|
| Current Version | 2.8.6 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/jasmine 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
- ❌ continuous-integration/travis-ci/push The Travis CI build failed 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 🌴
After pinning to 2.8.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 2.8.8 just got published.
Your tests are still failing with this version. Compare the changes 🚨
- The
devDependency@types/jasmine was updated from2.8.8to2.8.9.
Your tests are still failing with this version. Compare changes
- The
devDependency@types/jasmine was updated from2.8.9to2.8.10.
Your tests are still failing with this version. Compare changes
- The
devDependency@types/jasmine was updated from2.8.10to2.8.11.
Your tests are still failing with this version. Compare changes