An in-range update of semver 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 semver was updated from 5.5.1 to 5.6.0.
This version is covered by your current version range and after updating it in your project the build failed.
semver 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/semver-5.6.0 at 12.808% (Details).
- ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (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.
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 by comparing the semver 5.5.1 and 5.6.0 dependency update on the linked failing branch with the repository's current build and CI results. Determine whether semver causes the reported failure, then leave the project building successfully with a verified dependency choice.
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
- 20/100