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

## There have been updates to the *babel7* monorepo:

+ - The `devDependency` [@babel/parser](https://www.npmjs.com/package/@babel/parser) was updated from `7.2.3` to `7.3.0`.
- The `devDependency` [@babel/types](https://www.npmjs.com/package/@babel/types) was updated from `7.2.2` to `7.3.0`.

🚨 [View failing branch](https://github.com/benjamn/ast-types/compare/master...benjamn:greenkeeper%2Fmonorepo.babel7-20190122012906).

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

This monorepo update includes releases of one or more dependencies which all belong to the [babel7 group definition](https://github.com/greenkeeperio/monorepo-definitions).

babel7 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/ast-types/builds/482681833?utm_source=github_status&utm_medium=notification)).

---

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:

Begin with the failing branch comparison and the linked Travis CI build; inspect the @babel/parser and @babel/types updates alongside the reported failure. Done means the dependency update is compatible with the project or is reverted, with the Travis CI build passing.

Written by the indexing model from the issue text.