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

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

+ - The `devDependency` [apollo-cache-inmemory](https://github.com/apollographql/apollo-client) was updated from `1.5.1` to `1.6.0`.
- The `devDependency` [apollo-client](https://github.com/apollographql/apollo-client) was updated from `2.5.1` to `2.6.0`.

🚨 [View failing branch](https://github.com/brysgo/react-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 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

- ❌ **ci/circleci:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/brysgo/react-monoquery/128?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 by comparing the Greenkeeper failing branch with master and inspect the failed CircleCI run linked in the issue. Identify which build or test step is affected by the apollo-client and apollo-cache-inmemory updates; done means the project builds and its CI checks pass with a compatible dependency state.

Written by the indexing model from the issue text.