An in-range update of commander 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
The dependency commander was updated from 2.18.0 to 2.19.0.
This version is covered by your current version range and after updating it in your project the build failed.
commander is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ✅ ci/circleci: Your tests passed on CircleCI! (Details).
- ✅ coverage/coveralls: First build on greenkeeper/commander-2.19.0 at 12.808% (Details).
- ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
- ✅ codecov/project: No report found to compare against (Details).
- ❌ Build: Google Cloud Platform project is not set up correctly for this GitHub app. Please reinstall the app and go through the setup flow again.
Release Notes for v2.19.0
Commits
The new version differs by 6 commits.
78b7dbdversion bump 2.19.06aafa20prefixed error messages with "error:"6c0c1f6removed newline above and below errorsb6549f2removed indentation from errors2c20e91removed newline after options and commands headers4c294c1Fix to change default value to string
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 🌴
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
Compare commander 2.18.0 with 2.19.0 using the linked failing branch and release notes, then reproduce the build failure locally. Inspect the project's build entry point and CI results to identify the incompatible behavior. Done means the dependency-related failure is resolved and the build and tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100