This repository has been archived by the owner on Jul 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
An in-range update of npm-check-updates is breaking the build 🚨 #74
Labels
Comments
After pinning to 3.1.25 your tests are passing again. Downgrade this dependency 📌. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 14 commits.
See the full diff |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The devDependency npm-check-updates was updated from
3.1.25
to3.1.26
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
npm-check-updates 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
Commits
The new version differs by 3 commits.
5a45980
3.1.26
a59f6a4
Merge pull request #601 from prokopsimek/fix/possible-memory-leak
2d1ef75
fix(api): prevent MaxListenersExceededWarning
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: