An in-range update of execa 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 0.5.1 of execa just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | execa |
| Current Version | 0.5.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As execa 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
Commits
The new version differs by 3 commits .
e5598cf0.5.139a6e50Document thetimedOuterror propertye96350dReimplement missing features. Fixes #30 & #32 (#68)
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 🌴
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 greenkeeper/execa-0.5.1 branch and inspect the failed AppVeyor build linked in the issue, comparing it with the passing CircleCI result. Identify which change in execa 0.5.1 causes the failure, then update or constrain the dependency so the project build passes again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100