An in-range update of @angular/http is breaking the build 🚨 #101
Comments
|
After pinning to 4.2.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.2.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.3 of @angular/http just got published.
This version is covered by your current version range and after updating it in your project the build failed.
@angular/http is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
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 🌴
The text was updated successfully, but these errors were encountered: