-
Notifications
You must be signed in to change notification settings - Fork 0
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 🚨 #8
Comments
After pinning to 1.14.7 your tests are passing again. Downgrade this dependency 📌. |
Version 1.14.9 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 1.14.10 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 5 commits.
See the full diff |
Version 1.14.11 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv1.14.111.14.11 (2018-01-11)Bug Fixes
CommitsThe new version differs by 8 commits.
See the full diff |
Version 1.14.12 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 14 commits.
See the full diff |
Version 1.15.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 1.15.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 23 commits.
There are 23 commits in total. See the full diff |
Version 1.16.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Version 1.16.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Version 1.17.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv1.17.01.17.0 (2018-02-27)Bug Fixes
Features
Note: due to an oddity in the automated build process, nodemon was bumped two minor versions instead of one. Nothing to worry about though. CommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Version 1.17.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 30 commits.
There are 30 commits in total. See the full diff |
Version 1.17.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Version 1.17.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 36 commits.
There are 36 commits in total. See the full diff |
Version 1.17.5 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 45 commits.
There are 45 commits in total. See the full diff |
Version 1.18.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 55 commits.
There are 55 commits in total. See the full diff |
Version 1.18.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 57 commits.
There are 57 commits in total. See the full diff |
Version 1.18.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 60 commits.
There are 60 commits in total. See the full diff |
Version 1.18.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 61 commits.
There are 61 commits in total. See the full diff |
Version 1.18.4 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 64 commits.
There are 64 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 65 commits.
There are 65 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 83 commits.
There are 83 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v1.19.01.19.0 (2019-05-01)Bug Fixes
FeaturesCommitsThe new version differs by 87 commits.
There are 87 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v1.19.11.19.1 (2019-05-25)Bug Fixes
CommitsThe new version differs by 92 commits.
There are 92 commits in total. See the full diff |
Version 1.14.8 of nodemon was just published.
This version is covered by your current version range and after updating it in your project the build failed.
nodemon 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
Release Notes
v1.14.81.14.8 (2018-01-06)
Bug Fixes
Commits
The new version differs by 3 commits.
64a82ff
fix: fail gracefully if postinstall fails
2582d96
fix: clarify which config files are actually used
8cb26bf
refactor: small tweaks to ES6-ish
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: