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

## The devDependency [glob](https://github.com/isaacs/node-glob) was updated from `7.1.3` to `7.1.4`.

🚨 [View failing branch](https://github.com/benjamn/recast/compare/master...benjamn:greenkeeper%2Fglob-7.1.4).

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

glob 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

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/benjamn/recast/builds/529565792?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 5 commits.

• 2da9af3 7.1.4


• 28c2237 Add logo to license


• 92923a6 website link


• 17cf014 png vs svg


• 0af8a58 adding the globby

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](https://greenkeeper.io) Bot :palm_tree:

Start by reproducing the failed Travis CI build from the linked failing branch and inspect the project's devDependency entry for glob. Determine which build or test step breaks with glob 7.1.4, then verify that the build passes with the appropriate dependency resolution.

Written by the indexing model from the issue text.