-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of nodemon is breaking the build 🚨 #14
Comments
After pinning to 1.17.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 1.18.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits.
See the full diff |
Version 1.18.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.18.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.18.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.17.5 of nodemon was just published.
nodemon
This version is covered by your current version range and after updating it in your project the build failed.
nodemon 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
Release Notes
v1.17.51.17.5 (2018-05-23)
Bug Fixes
Commits
The new version differs by 2 commits.
b3fc3a9
fix: in watch, use fully filtered ignore rules
ff79835
chore: update stalebot
See the full diff
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: