Bump apollo-client from 2.6.4 to 2.6.10

[dependabot-preview]

Bumps apollo-client from 2.6.4 to 2.6.10.

Release notes

Sourced from apollo-client's releases.

2.6.8

Apollo Client 2.6.8

Apollo Client (2.6.8)

• Update the fetchMore type signature to accept context. @koenpunt in #5147

• Fix type for Resolver and use it in the definition of Resolvers. @peoplenarthax in #4943

• Local state resolver functions now receive a fragmentMap: FragmentMap object, in addition to the field: FieldNode object, via the info parameter. @mjlyons in #5388

• Documentation updates. @tomquirk in #5645 @Sequoia in #5641 @phryneas in #5628 @AryanJ-NYC in #5560

GraphQL Anywhere (4.2.6)

• Fix filter edge case involving null. @lifeiscontent in #5110

Apollo Boost (0.4.7)

• Replace GlobalFetch reference with WindowOrWorkerGlobalScope. @abdonrd in #5373

• Add assumeImmutableResults typing to apollo boost PresetConfig interface. @bencoullie in #5571

Changelog

Sourced from apollo-client's changelog.

Apollo Client 3.0.0 (TBD - not yet released)

⚠️ Note: As of 3.0.0, Apollo Client uses a new package name: @apollo/client

Improvements

• [BREAKING] InMemoryCache will no longer merge the fields of written objects unless the objects are known to have the same identity, and the values of fields with the same name will not be recursively merged unless a custom merge function is defined by a field policy for that field, within a type policy associated with the __typename of the parent object.
  @benjamn in #5603

• [BREAKING] Eliminate "generated" cache IDs to avoid normalizing objects with no meaningful ID, significantly reducing cache memory usage. This is a backwards-incompatible change if your code depends on the precise internal representation of normalized data in the cache.
  @benjamn in #5146

• [BREAKING] Removed graphql-anywhere since it's no longer used by Apollo Client.
  @hwillson in #5159

• [BREAKING] Removed apollo-boost since Apollo Client 3.0 provides a boost like getting started experience out of the box.
  @hwillson in #5217

• [BREAKING] The queryManager property of ApolloClient instances is now marked as private, paving the way for a more aggressive redesign of its API.

• [BREAKING] FragmentMatcher, HeuristicFragmentMatcher, and IntrospectionFragmentMatcher have all been removed. We now recommend using InMemoryCache’s possibleTypes option instead. For more information see the Defining possibleTypes manually section of the docs.
  @benjamn in #5073

• [BREAKING] As promised in the Apollo Client 2.6 blog post, all cache results are now frozen/immutable.
  @benjamn in #5153

• [BREAKING] ApolloClient is now only available as a named export. The default ApolloClient export has been removed.
  @hwillson in #5425

• [BREAKING] The QueryOptions, MutationOptions, and SubscriptionOptions React Apollo interfaces have been renamed to QueryDataOptions, MutationDataOptions, and SubscriptionDataOptions (to avoid conflicting with similarly named and exported Apollo Client interfaces).

• [BREAKING] We are no longer exporting certain (intended to be) internal utilities. If you are depending on some of the lesser known exports from apollo-cache, apollo-cache-inmemory, or apollo-utilities, they may no longer be available from @apollo/client.
  @hwillson in #5437 and #5514

• [BREAKING?] Remove fixPolyfills.ts, except when bundling for React Native. If you have trouble with Map or Set operations due to frozen key objects in React Native, either update React Native to version 0.59.0 (or 0.61.x, if possible) or investigate why fixPolyfills.native.js is not included in your bundle.
  @benjamn in #5962

• [BREAKING] Apollo Client 2.x allowed @client fields to be passed into the link chain if resolvers were not set in the constructor. This allowed @client fields to be passed into Links like apollo-link-state. Apollo Client 3 enforces that @client fields are local only, meaning they are no longer passed into the link chain, under any circumstances.
  @hwillson in #5982

• [BREAKING] InMemoryCache now throws when data with missing or undefined query fields is written into the cache, rather than just warning in development.
  @benjamn in #6055

• [BREAKING] client|cache.writeData have been fully removed. writeData usage is one of the easiest ways to turn faulty assumptions about how the cache represents data internally, into cache inconsistency and corruption. client|cache.writeQuery, client|cache.writeFragment, and/or cache.modify can be used to update the cache.
  @benjamn in #5923

• [BREAKING] Apollo Client will no longer deliver "stale" results to ObservableQuery consumers, but will instead log more helpful errors about which cache fields were missing.
  @benjamn in #6058

• [BREAKING] ApolloError's thrown by Apollo Client no longer prefix error messages with GraphQL error: or Network error:. To differentiate between GraphQL/network errors, refer to ApolloError's public graphQLErrors and networkError properties.
  

... (truncated)

Commits

• 64cda6a chore: Publish
• 48718ca Add "private: true" to apollo-client/package.json to fix lerna
• d22394c chore: Publish
• 747ed10 Merge pull request #6258 from apollographql/graphql15-update
• 753cb60 Changes to accommodate [email protected]
• 854b1c4 chore(deps): update dependency gatsby-theme-apollo-docs to v3.1.12
• 49fbacf chore(deps): update dependency typedoc to v0.15.6
• d488038 chore(deps): update dependency rollup to v1.27.14
• 258f598 Use 'npx rollup' instead of relative path in bundle scripts.
• 1deb021 Update fsevents to latest version so jest-haste-map won't install it.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)