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

[greenkeeper[bot]]

The devDependency anymatch was updated from 3.0.3 to 3.1.0.

🚨 View failing branch.

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

anymatch 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

- ❌ **Travis CI - Branch:** The build **failed**.

---

Commits

The new version differs by 8 commits.

• abfaed6 Release 3.1.0.
• 36f6e0d License.
• c5fb0a1 Fix typo.
• 8c91e61 Clarify changelog.
• 2524236 Add pkg engine section. Closes gh-32.
• 36317fd Move returnIndex to a sub-option of 3rd arg.
• 8f96a00 Merge pull request #34 from bpasero/ben-picooptions
• 17c072e allow to specify picomatch options

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 3.0.3 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 anymatch was updated from 3.1.0 to 3.1.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 1 commits.

• e0ec3c0 Release 3.1.1.

See the full diff