chore(deps): update apollo graphql packages

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
apollo-cache	devDependencies	minor	1.2.1 -> 1.3.5
apollo-cache-inmemory	devDependencies	minor	1.5.1 -> 1.6.6
apollo-client	devDependencies	minor	2.5.1 -> 2.6.10
apollo-link	devDependencies	patch	1.2.11 -> 1.2.14
graphql-tag	devDependencies	minor	2.10.1 -> 2.11.0
react-apollo	devDependencies	patch	2.5.4 -> 2.5.8

---

Release Notes

apollographql/apollo-client

v1.3.5

Compare Source

v1.3.4

Compare Source

v1.3.2

Compare Source

• Reimplement isEqual without pulling in massive lodash.isequal.
  
  @​benjamn in #​4924

v1.3.1

Compare Source

• The isEqual function has been reimplemented using the lodash.isequal npm package, to better support circular references. Since the lodash.isequal package is already used by react-apollo, this change is likely to decrease total bundle size.
  
  @​capaj in #​4915

v1.3.0

Compare Source

apollographql/apollo-link

v1.2.14

Compare Source

v1.2.13

Compare Source

v1.2.12

Compare Source

• Avoid importing graphql/language/printer for getKey.
  
  @​benjamn in #​992

• Documentation updates.
  
  @​jsjoeio in #​1044

• Bump apollo-utilities to reduce total bundle size.
  
  @​salzhrani in #​1044

apollographql/graphql-tag

v2.11.0

Compare Source

• package.json sideEffects changes to clearly identify that graphql-tag doesn't have side effects.
  
  @​hwillson in #​313

v2.10.4

Compare Source

• Bump dev/peer deps to accommodate graphql 15.
  
  @​adriencohen in #​299

v2.10.3

Compare Source

• Further adjustments to the TS index.d.ts declaration file.
  
  @​Guillaumez in #​289

v2.10.2

Compare Source

• Update/fix the existing TS index.d.ts declaration file.
  
  @​hwillson in #​285

apollographql/react-apollo

v2.5.8

Compare Source

2.5.8 (2019-06-21)

Bug Fixes

• Makes the use of apollo-client 2.6.3's ObservableQuery.resetQueryStoreErrors
  method optional, for people who can't update to react-apollo's new
  apollo-client peer dep of 2.6.3.
  @​hwillson in #​3151

v2.5.7

Compare Source

Improvements

• Make sure MockedProvider is using the proper CJS/ESM bundle, when
  referencing ApolloProvider.
  
  @​jure in #​3029.
• Adjust the ApolloContext definition to play a bit more nicely with
  React.createContext types.
  
  @​JoviDeCroock in #​3018
• The result of a mutation is now made available to the wrapped component,
  when using the graphql HOC.
  
  @​andycarrell in #​3008
• Check equality of stringified variables in the MockLink to improve
  debugging experience used by MockedProvider.
  
  @​evans in #​3078

Bug Fixes

• Removed leftover apollo-client@beta peer dep.
  
  @​brentertz in #​3064
• Stop setting optional input to null, when using the graphql HOC.
  
  @​ZhengYuTay in #​3056
• Fix typescript error caused by query being mandatory in the fetchMore signature.
  
  @​HsuTing in #​3065
• Fixes an issue that caused the Query component to get stuck in an always
  loading state, caused by receiving an error (meaning subsequent valid
  responses couldn't be handled). The Query component can now handle an
  error in a response, then continue to handle a valid response afterwards.
  
  @​hwillson in #​3107
• Reorder Subscription component code to avoid setting state on unmounted
  component.
  
  @​jasonpaulos in #​3139
• Fix component stuck in loading state for network-only fetch policy.
  
  @​jasonpaulos in #​3126

v2.5.6

Compare Source

Improvements

• Both the Query component and graphql HOC now accept a
  returnPartialData prop. This is an important new feature, that should
  help address a lot of open Apollo Client / React Apollo issues, so we'll
  explain it here with an example. Before this release, if you run a query
  that looks like:

  const GET_MEMBER = gql`
    query GetMember($id: ID!) {
      member(id: $id) {
        id
        name
      }
    }
  `;

  in one component, the results are cached, then you run a superset query like
  the following in another component:

  const GET_MEMBER_WITH_PLANS = gql`
    query GetMemberWithPlans($id: ID!) {
      member(id: $id) {
        id
        name
        plans {
          id
          title
          duration
        }
      }
    }
  `;

  Apollo Client will not re-use the partial data that was cached from the first
  query, when it preps and displays the second component. It can't find a
  cache hit for the full second query, so it fires the full query over the
  network.

  With this release, if you set a returnPartialData prop to true on the
  second component, the data available to that component will be
  automatically pre-loaded with the parts of the query that can be found in the
  cache, before the full query is fired over the network. This means you can
  do things like showing partial data in your components, while the rest of the
  data is being loaded over the network.

v2.5.5

Compare Source

Improvements

• Export the Apollo Context provider (ApolloContext).
  
  @​MrLoh in #​2961

---

Renovate configuration

📅 Schedule: "after 11pm,before 6am" in timezone Europe/Warsaw.

🚦 Automerge: Disabled due to failing status checks.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.