An in-range update of detect-port is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
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
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 🌴
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the dependency declaration for detect-port and compare the current 1.1.4 range with the Greenkeeper detect-port-1.2.0 branch and its CI results. Reproduce the build failure, identify whether the CLI tweak causes it, and consider the issue done when the dependency update passes the project’s CircleCI and AppVeyor builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100