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

[greenkeeper[bot]]

The devDependency concurrently was updated from 4.1.0 to 4.1.1.

🚨 View failing branch.

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

concurrently 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

- ❌ **now:** Deployment has failed ([Details](https://github.com/ewolfe/prlint/commit/8acc36d7668f507f079b0e2f8f9616f2c63e31ef#comments)). - ✅ **continuous-integration/travis-ci/push:** The Travis CI build passed ([Details](https://travis-ci.org/ewolfe/prlint/builds/550501155?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v4.1.1

• bin: pass --prefix-length argument through (#189)

Commits

The new version differs by 2 commits.

• 9181965 4.1.1
• 9529c5e Use prefixLength (#189)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

• The devDependency concurrently was updated from 4.1.1 to 4.1.2.

Your tests are still failing with this version. Compare changes

Release Notes for v4.1.2

• Don't strip quotes if they are impaired (#118, #194)