Update Apollo GraphQL packages

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
apollo-cache-inmemory	dependencies	minor	1.3.12 -> 1.6.5
apollo-client	dependencies	minor	2.4.8 -> 2.6.8
apollo-link-ws	dependencies	patch	1.0.12 -> 1.0.20
graphql-tag	devDependencies	patch	2.10.0 -> 2.10.3
graphql-tools	dependencies	patch	4.0.3 -> 4.0.8
react-apollo	dependencies	minor	2.3.1 -> 2.5.8

---

Release Notes

apollographql/apollo-client

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

v1.5.1

Compare Source

v1.5.0

Compare Source

v1.4.3

Compare Source

v1.4.2

Compare Source

v1.4.1

Compare Source

• The optimism npm package has been updated to a version (0.6.9) that
  provides its own TypeScript declarations, which should fix problems like
  Issue #​4327.
  
  PR #​4331

• Error messages involving GraphQL queries now print the queries using
  JSON.stringify instead of the print function exported by the
  graphql package, to avoid pulling unnecessary printing logic into your
  JavaScript bundle.
  
  PR #​4234

• The QueryKeyMaker abstraction has been removed, meaning that cache
  results for non-identical queries (or sub-queries) with equivalent
  structure will no longer be cached together. This feature was a nice
  optimization in certain specific use cases, but it was not worth the
  additional complexity or bundle size.
  
  PR #​4245

v1.4.0

Compare Source

• The speed and memory usage of optimistic reads and writes has been
  improved dramatically using a new layering technique that does not
  require copying the non-optimistic contents of the cache.
  
  PR #​4319

• The RecordingCache abstraction has been removed, and thus is no longer
  exported from apollo-cache-inmemory.
  
  PR #​4319

• Export the optimism wrap function using ES2015 export syntax, instead of
  CommonJS.
  
  @​ardatan in #​4158

apollographql/apollo-link

v1.0.20

Compare Source

v1.0.19

Compare Source

v1.0.18

Compare Source

• Fixes an issue introduced in #​984
  where subscriber next and/or error calls might have already deleted the
  key the new dedupe changes were intended to help with.
  
  @​JoviDeCroock in #​988

v1.0.17

Compare Source

• Fixes an issue caused by the DedupLink shared observable returning
  cleanup logic that unsubscribes from the real observable, without
  checking whether only one of the many (shared) subscribers are
  unsubscribing. This caused problems when using DedupLink in front of
  HttpLink, as this lead to HttpLink aborting HTTP requests while some
  callers were still waiting for a response.
  
  @​ms in #​984

v1.0.16

Compare Source

v1.0.15

Compare Source

v1.0.14

Compare Source

v1.0.13

Compare Source

apollographql/graphql-tag

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

v2.10.1

Compare Source

• Fix failures in IE11 by avoiding unsupported (by IE11) constructor arguments to Set by rocwang in #​190

apollographql/graphql-tools

v4.0.8

Compare Source

v4.0.7

Compare Source

• Filter extensions prior to passing them to buildASTSchema, in an effort to provide minimum compatibilty for graphql@14-compatible schemas with the upcoming graphql@15 release. This PR does not, however, bring support for newer graphql@15 features like interfaces implementing interfaces. #​1284

v4.0.6

Compare Source

• Use getIntrospectionQuery instead of deprecated introspectionQuery constant from graphql-js
  @​derek-miller in #​1228

v4.0.5

Compare Source

• Fixes a bug where schemas with scalars could not be merged when passed to
  mergeSchemas as a string or GraphQLSchema.
  
  @​hayes in #​1062
• Make mergeSchemas optionally merge directive definitions.
  
  @​freiksenet in #​1003
• Allow user-provided buildSchema options.
  
  @​trevor-scheer in #​1154
• Fix delegateToSchema to allow delegation to subscriptions with different root field names, allows
  the use of the RenameRootFields transform with subscriptions,
  pull request #​1104, fixes
  #​997.
  
• Add transformers to rename, filter, and arbitrarily transform object fields.
  
  Fixes #​819.

v4.0.4

Compare Source

• Make WrapQuery work for non-root fields
  
  @​mdlavin in
  #​1007
• Update resolvers.md to clarify array usage
  
  @​alvin777 in
  #​1005
• Add missing property to mergeSchemas api reference.
  
  @​PlayMa256 in
  #​1014
• Documentation updates for mockServer
  
  @​dougshamoo in #​1012
• Fix default merged resolver behavior
  
  @​mfix22 in #​983
• Use TArgs generic wherever IFieldResolver is used.
  
  @​brikou in #​955
• Include deprecations from string SDL in mergeSchemas.
  
  @​evans in #​1041

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

v2.5.2

Compare Source

Bug Fixes

• Export Context type from types.ts instead of walkTree.ts,
  to reenable import { Context } from 'react-apollo' (which has been
  broken since 2.4.0).
  
  @​benjamn in #​2825

Improvements

• Add examples/rollup
  to enable application-level bundle measurement and demonstrate Rollup configuration best practices.
  
  @​benjamn in #​2839

• Bundle size reductions inspired by examples/rollup app.
  
  @​benjamn in #​2842

v2.5.1

Compare Source

Bug Fixes

• Make sure MockedProvider enables Apollo Client 2.5's local state handling,
  and allow custom / mocked resolvers to be passed in as props, and used with
  the created test ApolloClient instance.
  
  @​hwillson in #​2825

v2.5.0

Compare Source

Improvements

• Ready to be used with Apollo Client 2.5 and its new local state management
  features, as well as many overall code improvements to help reduce the React
  Apollo bundle size.
  
  #​2758
• A function can now be set as a MockedResponse result when using
  MockedProvider, such that every time the mocked result is returned,
  the function is run to calculate the result. This opens up new testing
  possibilities, like being able to verify if a mocked result was actually
  requested and received by a test.
  
  @​hwillson in #​2788

v2.4.1

Compare Source

Improvements

• Adds a onSubscriptionComplete prop to the Subscription component, that
  can be passed a callback to be called when the subscription observable
  is completed.
  
  @​sujeetsr in #​2716

• During server-side rendering, ObservableQuery objects created in
  previous rendering passes will now be preserved in later passes (within
  the same getDataFromTree or getMarkupFromTree call), so that errors
  can be handled properly when using the errorPolicy: "all" option.
  
  PR #​2753

v2.4.0

Compare Source

Bug Fixes

• Invoke onCompleted/onError even if Mutation unmounts.
  
  PR #​2710

Improvements

• The walkTree function has been deprecated, since there's no way to
  make its behavior consistent with the latest versions of React. To save
  bundle size, walkTree is no longer exported from react-apollo,
  though you can still access it as follows:

  import { walkTree } from 'react-apollo/walkTree';

v2.3.3

Compare Source

Bug Fixes

• Add react-dom as a peer dependency (since it's used by getDataFromTree
  and renderToStringWithData).
  
  @​hwillson in #​2660

Improvements

• Drop react 14.x support, since the 14.x release line is 2 years old now,
  and react-apollo is no longer tested against it.
  
  @​hwillson in #​2660

v2.3.2

Compare Source

Improvements

Bug Fixes

• This package no longer imports react-dom/server unconditionally at the
  top level, making react-apollo safer to use in environments like React
  Native that are neither browser-like nor Node-like, and thus struggle to
  import react-dom/server and its dependencies. Additionally, the React
  Native bundler has been instructed to ignore all react-dom/server
  dependencies within react-apollo, so react-dom will not be bundled
  in React Native apps simply because they import react-apollo.
  PR #​2627

---

Renovate configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.