An in-range update of execa is breaking the build 🚨

[greenkeeper]

The dependency execa was updated from 2.0.3 to 2.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

execa 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v2.0.4

Bug fixes

• Fix errors being thrown when detached: true or cleanup: false is used (#360) 211febe

v2.0.3...v2.0.4

Commits

The new version differs by 2 commits.

• ac2bc15 2.0.4
• 211febe Fix errors being thrown when detached: true or cleanup: false is used (#360)

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 🌴

[greenkeeper]

After pinning to 2.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The dependency execa was updated from 2.0.4 to 2.0.5.

Your tests are still failing with this version. Compare changes

Release Notes for v2.0.5

Bug fixes

• Make execa compatible with Node.js 13.0.0-pre (#370) d268fd1

v2.0.4...v2.0.5

Commits

The new version differs by 2 commits.

• 603537a 2.0.5
• d268fd1 Make execa compatible with Node.js 13.0.0-pre (#370)

See the full diff

[greenkeeper]

• The dependency execa was updated from 2.0.5 to 2.1.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 6 commits.

• e98561a 2.1.0
• c6a24ec Add error.originalMessage property (#373)
• f9bd317 Upgrade cross-spawn to 7.0.0 (#367)
• f620305 Document the reasons why the returned promise might fail (#364)
• 7c19345 Revert "Add a sentence about job search (#293)" (#352)
• 48067c4 Properly clean up child processes created during tests (#349)

See the full diff