An in-range update of @angular/router is breaking the build 🚨 #24
Comments
|
After pinning to 5.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 5.2.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.8 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.9 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.10 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.1 of @angular/router was just published.
This version is covered by your current version range and after updating it in your project the build failed.
@angular/router is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
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: