An in-range update of detect-port is breaking the build 🚨

[greenkeeper]

Version 1.2.0 of detect-port just got published.

Branch	Build failing 🚨
Dependency	detect-port
Current Version	1.1.4
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

detect-port is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ✅ coverage/coveralls First build on greenkeeper/detect-port-1.2.0 at 12.808% Details
• ✅ ci/circleci Your tests passed on CircleCI! Details
• ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
• ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details
• ✅ codecov/patch Coverage not affected when comparing fe5bfde...9e8884a Details

---

Commits

The new version differs by 1 commits.

• 4a9e127 cli tweak to verbose (#25)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 1.2.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• 31562b0 bump version to 1.2.1
• 398bc4f fix: handle 0.0.0.0:port binding (#26)

See the full diff

[greenkeeper]

Version 1.2.2 just got published.

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

Commits

The new version differs by 4 commits.

• 53331de tweak ignore
• dfd1366 tweak ci
• 47d9400 tweak project
• 3ba1f96 tweak readme

See the full diff