leizongmin / leizongmin/node-segment
An in-range update of should is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
Version 13.2.0 of should was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | should |
| Current Version | 13.1.3 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
should 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
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
Start with the linked Travis CI build and the Greenkeeper branch comparison for should 13.2.0. Determine which build or test failure the dependency update introduces, then verify that the project build passes with the compatible dependency version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100