Skip to content
This repository has been archived by the owner on Jul 13, 2020. It is now read-only.

An in-range update of npm-check-updates is breaking the build 🚨 #79

Open
greenkeeper bot opened this issue Oct 29, 2019 · 4 comments
Open

An in-range update of npm-check-updates is breaking the build 🚨 #79

greenkeeper bot opened this issue Oct 29, 2019 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 29, 2019

The devDependency npm-check-updates was updated from 3.1.25 to 3.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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 29, 2019

After pinning to 3.1.25 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 3, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 6 commits.

  • fbe27f0 3.2.0
  • c417828 Cleanup
  • 742dbce Merge pull request #602 from webdevium/master
  • a67d8a3 Added --engines-node functionality
  • 3598bdf Merge pull request #603 from brettz9/printUpgrades-return
  • d84b61d - Refactoring: Avoid variable suggesting a Promise is returned from printUpgrades

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 7, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 10 commits.

  • 026ec05 3.2.1
  • af5f486 Merge pull request #609 from webdevium/master
  • c6ff937 Fixed bug #608: invalid range and versions
  • 4f2152d README: Add --engines-node.
  • fbe27f0 3.2.0
  • c417828 Cleanup
  • 742dbce Merge pull request #602 from webdevium/master
  • a67d8a3 Added --engines-node functionality
  • 3598bdf Merge pull request #603 from brettz9/printUpgrades-return
  • d84b61d - Refactoring: Avoid variable suggesting a Promise is returned from printUpgrades

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 24, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 14 commits.

  • 0526054 3.2.2
  • 7578264 Upgrade during interactive mode by default.
  • ec85d80 Merge pull request #610 from webdevium/master
  • 15f1b33 Added tests for invalid and wildCard ranges with --newest option
  • 026ec05 3.2.1
  • af5f486 Merge pull request #609 from webdevium/master
  • c6ff937 Fixed bug #608: invalid range and versions
  • 4f2152d README: Add --engines-node.
  • fbe27f0 3.2.0
  • c417828 Cleanup
  • 742dbce Merge pull request #602 from webdevium/master
  • a67d8a3 Added --engines-node functionality
  • 3598bdf Merge pull request #603 from brettz9/printUpgrades-return
  • d84b61d - Refactoring: Avoid variable suggesting a Promise is returned from printUpgrades

See the full diff

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants