Update Apollo GraphQL packages - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
apollo-cache-inmemory	1.5.1 -> 1.6.6
apollo-client	2.5.1 -> 2.6.10
apollo-link	1.2.11 -> 1.2.14
apollo-link-error	1.1.10 -> 1.1.13
apollo-link-http	1.5.14 -> 1.5.17
apollo-link-ws	1.0.17 -> 1.0.20
apollo-utilities	1.2.1 -> 1.3.4
graphql-tag	2.10.1 -> 2.12.6
react-apollo	2.5.2 -> 2.5.8

---

Release Notes

apollographql/apollo-client

v1.6.6

Compare Source

v1.6.5

Compare Source

v1.6.3

Compare Source

v1.6.2

Compare Source

v1.6.1

Compare Source

• Pretend that __typename exists on the root Query when matching fragments.
  
  @​benjamn in #​4853

v1.6.0

Compare Source

• Support new InMemoryCache({ freezeResults: true }) to help enforce immutability.
  
  @​benjamn in #​4514

• Allow IntrospectionFragmentMatcher to match fragments against the root Query, as HeuristicFragmentMatcher does.
  
  @​rynobax in #​4620

• Rerential identity (===) of arrays in cache results will now be preserved for unchanged data.
  
  @​benjamn in commit f3091d6a

• Avoid adding __typename field to @client selection sets that have been @exported as input variables.
  
  @​benjamn in #​4784

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.12.6

Compare Source

• Update peer dependencies to allow graphql ^16.0.0.
  
  @​brainkim in #​530

v2.12.5

Compare Source

• Also publish src/ directory to npm, enabling source maps.
  
  @​maclockard in #​403

v2.12.4

Compare Source

• Allow fragments to be imported by name when using the webpack loader.
  
  @​dobesv in #​257

v2.12.3

Compare Source

• Update tslib dependency to version 2.1.0.
  
  @​benjamn in #​381

v2.12.2

Compare Source

• Avoid using Object.assign to attach extra properties to gql.
  
  @​benjamn in #​380

v2.12.1

Compare Source

• To accommodate older versions of TypeScript, usage of the import type ... syntax (introduced by #​325) has been removed, fixing issue #​345.
  
  @​benjamn in #​352

v2.12.0

Compare Source

• The graphql-tag repository has been converted to TypeScript, adding type safety and enabling both ECMAScript and CommonJS module exports. While these changes are intended to be as backwards-compatible as possible, we decided to bump the minor version to reflect the significant refactoring.
  
  @​PowerKiKi and @​benjamn in #​325

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

v2.5.4

Compare Source

Bug Fixes

• Fixes Could not find "client" in the context of ApolloConsumer errors when
  using MockedProvider.
  
  @​hwillson in #​2907
• Ensure Query components using a fetchPolicy of no-cache have their
  data preserved when the components tree is re-rendered.
  
  @​hwillson in #​2914

Improvements

• Documentation updates.
  
  @​afenton90 in #​2932

v2.5.3

Compare Source

Bug Fixes

• Fixed an infinite loop caused by using setState in the
  onError / onCompleted callbacks of the Query component.
  
  @​chenesan in #​2751
• Fixed an issue that prevented good results from showing up in a Query
  component, after an error was received, variables were adjusted, and then
  the good data was fetched.
  
  @​MerzDaniel in #​2718
• Fixed an issue that prevented Query component updates from firing (under
  certain circumstances) due to the internal lastResult value (that's used
  to help prevent unnecessary re-renders) not being updated.
  
  @​Glennrs in #​2840

Improvements

• MockedProvider now accepts a childProps prop that can be used to pass
  props down to a child component.
  
  @​miachenmtl in #​2482

• onCompleted callbacks now use a destructuring-friendly type definition.
  
  @​jozanza in #​2496

• @connection directives are now properly stripped from MockedResponse's,
  when using MockedProvider.
  
  @​ajmath in #​2523

• MockedProvider has been updated to stop setting a default resolvers
  value of {}, which means by default Apollo Client 2.5 local resolver
  functionality is not enabled when mocking with MockedProvider. This allows
  @client fields to be passed through the mocked link chain, like people
  were used to before AC 2.5. When using this default mode you will see a
  dev only warning message about this like:

  Found @​client directives in query but no client resolvers were specified.
  You can now pass apollo-link-state resolvers to the ApolloClient
  constructor.

  This message can be safely ignored. If you want to use MockedProvider
  with AC 2.5's new local resolver functionality, you can pass your local
  resolver map into the MockedProvider resolvers prop.
  
  @​ajmath in #​2524

• Improvements to the graphql HOC generics for fetchMore and refetch.
  
  @​EricMcRay in #​2525

• The ApolloProvider / ApolloConsumer implementations have been refactored
  to use React 16.3's new context API.
  
  @​wzrdzl in #​2540

• All dependencies and devDependencies have been updated to their latest
  versions, and related Typescript changes have been applied.
  
  @​hwillson in #​2873

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.