An in-range update of apollo-client is breaking the build 🚨

## There have been updates to the *apollo-client* monorepo:

+ - The `dependency` [graphql-anywhere](https://github.com/apollographql/apollo-client) was updated from `4.2.1` to `4.2.2`.

🚨 [View failing branch](https://github.com/brysgo/monoquery/compare/master...brysgo:greenkeeper%2Fmonorepo.apollo-client-20190521224159).

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 [apollo-client group definition](https://github.com/greenkeeperio/monorepo-definitions).

apollo-client 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

- ❌ **ci/circleci:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/brysgo/monoquery/42?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

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 with the failing CircleCI run linked in the issue and compare the failing branch against master to identify what broke after graphql-anywhere changed from 4.2.1 to 4.2.2. Done means the project build and tests pass with the dependency update.

Written by the indexing model from the issue text.