@apollo/client 4.0.0-alpha.9 → 4.0.0-rc.1

package/CHANGELOG.md

@@ -1,5 +1,1058 @@
 # @apollo/client
 
+## 4.0.0-rc.1
+
+### Major Changes
+
+- [#12735](https://github.com/apollographql/apollo-client/pull/12735) [`5159880`](https://github.com/apollographql/apollo-client/commit/51598808851e16af722baaefbd1f90534332e07a) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove deprecated `resultCacheMaxSize` option from `InMemoryCache` options.
+
+- [#12735](https://github.com/apollographql/apollo-client/pull/12735) [`5159880`](https://github.com/apollographql/apollo-client/commit/51598808851e16af722baaefbd1f90534332e07a) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove deprecated `connectToDevtools` option from `ApolloClientOptions`. Use `devtools.enabled` instead.
+
+### Minor Changes
+
+- [#12725](https://github.com/apollographql/apollo-client/pull/12725) [`89ac725`](https://github.com/apollographql/apollo-client/commit/89ac7256a34b3b04fe2cf83937b5494b375ce36d) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add `operationType` to `operation` in `ApolloLink`. This means that determining whether a `query` is a specific operation type can now be compared with this property instead of using `getMainDefinition`.
+
+  ```diff
+  - import { getMainDefinition } from "@apollo/client/utilities";
+  + import { OperationTypeNode } from "graphql";
+
+  ApolloLink.split(
+  - ({ query }) => {
+  -   const definition = getMainDefinition(query);
+  -   return (
+  -     definition.kind === 'OperationDefinition' &&
+  -     definition.operation === 'subscription'
+  -   );
+  -   return
+  - },
+  + ({ operationType }) => {
+  +   return operationType === OperationTypeNode.SUBSCRIPTION;
+  + },
+    conditionTrueLink,
+    conditionFalseLink,
+  );
+  ```
+
+### Patch Changes
+
+- [#12728](https://github.com/apollographql/apollo-client/pull/12728) [`07a0c8c`](https://github.com/apollographql/apollo-client/commit/07a0c8c52774793b254ecc91e5d4632bfdf48093) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Export the `IgnoreModifier` type from `@apollo/client/cache`.
+
+- [#12735](https://github.com/apollographql/apollo-client/pull/12735) [`5159880`](https://github.com/apollographql/apollo-client/commit/51598808851e16af722baaefbd1f90534332e07a) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Change the `unsafePreviousData` argument on `UpdateQueryMapFn` and `SubscribeToMoreQueryFn` to a `DeepPartial` since the result may contain partial data.
+
+- [#12734](https://github.com/apollographql/apollo-client/pull/12734) [`037979d`](https://github.com/apollographql/apollo-client/commit/037979dc47ffb7125429707471d901a08db49283) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Don't warn about a missing resolver if a `@client` does not have a configured resolver. It is possible the cache contains a `read` function for the field and the warning added confusion.
+
+  Note that `read` functions without a defined resolver will receive the `existing` argument as `null` instead of `undefined` even when data hasn't been written to the cache. This is because `LocalState` sets a default value of `null` when a resolver is not defined to ensure that the field contains a value in case a `read` function is not defined rather than omitting the field entirely.
+
+- [#12725](https://github.com/apollographql/apollo-client/pull/12725) [`89ac725`](https://github.com/apollographql/apollo-client/commit/89ac7256a34b3b04fe2cf83937b5494b375ce36d) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Export `getMainDefinition` from `@apollo/client/utilities`.
+
+- [#12729](https://github.com/apollographql/apollo-client/pull/12729) [`699c830`](https://github.com/apollographql/apollo-client/commit/699c8305639ff69bab36fd2214defbe1ac6f0b18) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Ensure `useQuery` rerenders when `notifyOnNetworkStatusChange` is `false` and a `refetch` that changes variables returns a result deeply equal to previous variables.
+
+## 4.0.0-rc.0
+
+### Major Changes
+
+- [#12718](https://github.com/apollographql/apollo-client/pull/12718) [`ecfc02a`](https://github.com/apollographql/apollo-client/commit/ecfc02a37908b58d1f799f0e817cdeab98482720) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Version bump only to release latest as `rc`.
+
+## 4.0.0-alpha.23
+
+### Major Changes
+
+- [#12712](https://github.com/apollographql/apollo-client/pull/12712) [`bbb2b61`](https://github.com/apollographql/apollo-client/commit/bbb2b61d259da54560a79813b130a977dae10523) Thanks [@jerelmiller](https://github.com/jerelmiller)! - An error is now thrown when trying to call `fetchMore` on a `cache-only` query.
+
+- [#12712](https://github.com/apollographql/apollo-client/pull/12712) [`bbb2b61`](https://github.com/apollographql/apollo-client/commit/bbb2b61d259da54560a79813b130a977dae10523) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `cache-only` queries are no longer refetched when calling `client.reFetchObservableQueries` when `includeStandby` is `true`.
+
+- [#12705](https://github.com/apollographql/apollo-client/pull/12705) [`a60f411`](https://github.com/apollographql/apollo-client/commit/a60f411e58cc67730d0dc4513e4045f004027ded) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `cache-only` queries will now initialize with `loading: false` and `networkStatus: NetworkStatus.ready` when there is no data in the cache.
+
+  This means `useQuery` will no longer render a short initial loading state before rendering `loading: false` and `ObservableQuery.getCurrentResult()` will now return `loading: false` immediately.
+
+- [#12712](https://github.com/apollographql/apollo-client/pull/12712) [`bbb2b61`](https://github.com/apollographql/apollo-client/commit/bbb2b61d259da54560a79813b130a977dae10523) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `cache-only` queries are now excluded from `client.refetchQueries` in all situations. `cache-only` queries affected by `updateCache` are also excluded from `refetchQueries` when `onQueryUpdated` is not provided.
+
+- [#12681](https://github.com/apollographql/apollo-client/pull/12681) [`b181f98`](https://github.com/apollographql/apollo-client/commit/b181f98476e635ba3eccab170c09d91f5408060c) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Changing most options when rerendering `useQuery` will no longer trigger a `reobserve` which may cause network fetches. Instead, the changed options will be applied to the next cache update or fetch.
+
+  Options that now trigger a `reobserve` when changed between renders are:
+
+  - `query`
+  - `variables`
+  - `skip`
+  - Changing `fetchPolicy` to or from `standby`
+
+- [#12714](https://github.com/apollographql/apollo-client/pull/12714) [`0e39469`](https://github.com/apollographql/apollo-client/commit/0e394692eaf0f8d8e506d8304935deafa952accf) Thanks [@phryneas](https://github.com/phryneas)! - Rework option handling for `fetchMore`.
+
+  - Previously, if the `query` option was specified, no options would be inherited
+    from the underlying `ObservableQuery`.
+    Now, even if `query` is specified, all unspecified options except for `variables` will be inherited from the underlying `ObservableQuery`.
+  - If `query` is not specified, `variables` will still be shallowly merged with the `variables` of the underlying `ObservableQuery`. If a `query` option is specified, the `variables` passed to `fetchMore` are used instead.
+  - `errorPolicy` of `fetchMore` will now always default to `"none"` instead of inherited from the `ObservableQuery` options. This can prevent accidental cache writes of partial data for a paginated query. To opt into receive partial data that may be written to the cache, pass an `errorPolicy` to `fetchMore` to override the default.
+
+- [#12700](https://github.com/apollographql/apollo-client/pull/12700) [`8e96e08`](https://github.com/apollographql/apollo-client/commit/8e96e0862c306df17c09c232704041196a72a466) Thanks [@phryneas](https://github.com/phryneas)! - Added a new `Streaming` type that will mark `data` in results while `dataStatus`
+  is `"streaming"`.
+
+  `Streaming<TData>` defaults to `TData`, but can be overwritten in userland to
+  integrate with different codegen dialects.
+
+  You can override this type globally - this example shows how to override it
+  with `DeepPartial<TData>`:
+
+  ```ts
+  import { HKT, DeepPartial } from "@apollo/client/utilities";
+
+  type StreamingOverride<TData> = DeepPartial<TData>;
+
+  interface StreamingOverrideHKT extends HKT {
+    return: StreamingOverride<this["arg1"]>;
+  }
+
+  declare module "@apollo/client" {
+    export interface TypeOverrides {
+      Streaming: StreamingOverrideHKT;
+    }
+  }
+  ```
+
+- [#12499](https://github.com/apollographql/apollo-client/pull/12499) [`ce35ea2`](https://github.com/apollographql/apollo-client/commit/ce35ea2b3a87d6dd6757e9be50ecc42837bebe56) Thanks [@phryneas](https://github.com/phryneas)! - Enable React compiler for hooks in ESM builds.
+
+- [#12704](https://github.com/apollographql/apollo-client/pull/12704) [`45dba43`](https://github.com/apollographql/apollo-client/commit/45dba43b6ba0c306aad8cfbcfd4029265f5e9106) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The `ErrorResponse` object passed to the `disable` and `retry` callback options provided to `createPersistedQueryLink` no longer provides separate `graphQLErrors` and `networkError` properties and instead have been combined to a single `error` property of type `ErrorLike`.
+
+  ```diff
+  // The following also applies to the `retry` function since it has the same signature
+  createPersistedQueryLink({
+  - disable: ({ graphQLErrors, networkError }) => {
+  + disable: ({ error }) => {
+  -   if (graphQLErrors) {
+  +   if (CombinedGraphQLErrors.is(error)) {
+        // ... handle GraphQL errors
+      }
+
+  -   if (networkError) {
+  +   if (error) {
+        // ... handle link errors
+      }
+
+      // optionally check for a specific kind of error
+  -   if (networkError) {
+  +   if (ServerError.is(error)) {
+        // ... handle a server error
+      }
+  });
+  ```
+
+  The `response` property has also been renamed to `result`.
+
+  ```diff
+  createPersistedQueryLink({
+  -  disable: ({ response }) => {
+  +  disable: ({ result }) => {
+        // ... handle GraphQL errors
+      }
+    }
+  });
+  ```
+
+- [#12712](https://github.com/apollographql/apollo-client/pull/12712) [`bbb2b61`](https://github.com/apollographql/apollo-client/commit/bbb2b61d259da54560a79813b130a977dae10523) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `cache-only` queries no longer poll when a `pollInterval` is set. Instead a warning is now emitted that polling has no effect. If the `fetchPolicy` is changed to `cache-only` after polling is already active, polling is stopped.
+
+- [#12704](https://github.com/apollographql/apollo-client/pull/12704) [`45dba43`](https://github.com/apollographql/apollo-client/commit/45dba43b6ba0c306aad8cfbcfd4029265f5e9106) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The `response` property in `onError` link has been renamed to `result`.
+
+  ```diff
+  - onError(({ response }) => {
+  + onError(({ result }) => {
+      // ...
+  });
+  ```
+
+- [#12715](https://github.com/apollographql/apollo-client/pull/12715) [`0be0b3f`](https://github.com/apollographql/apollo-client/commit/0be0b3f54a1b533c95c69d3698c5c3bdbd6279fe) Thanks [@phryneas](https://github.com/phryneas)! - All links are now available as classes. The old creator functions have been deprecated.
+
+  Please migrate these function calls to class creations:
+
+  ```diff
+  import {
+  - setContext
+  + SetContextLink
+  } from "@apollo/client/link/context"
+
+  -const link = setContext(...)
+  +const link = new SetContextLink(...)
+  ```
+
+  ```diff
+  import {
+  - createHttpLink
+  + HttpLink
+  } from "@apollo/client/link/http"
+
+  -const link = createHttpLink(...)
+  +const link = new HttpLink(...)
+  ```
+
+  ```diff
+  import {
+  - createPersistedQueryLink
+  + PersistedQueryLink
+  } from "@apollo/client/link/persisted-queries"
+
+  -const link = createPersistedQueryLink(...)
+  +const link = new PersistedQueryLink(...)
+  ```
+
+  ```diff
+  import {
+  - removeTypenameFromVariables
+  + RemoveTypenameFromVariablesLink
+  } from "@apollo/client/link/remove-typename"
+
+  -const link = removeTypenameFromVariables(...)
+  +const link = new RemoveTypenameFromVariablesLink(...)
+  ```
+
+### Minor Changes
+
+- [#12711](https://github.com/apollographql/apollo-client/pull/12711) [`f730f83`](https://github.com/apollographql/apollo-client/commit/f730f83346d4e3c20116da6f55fdd1381114416c) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add an `extensions` property to `CombinedGraphQLErrors` to capture any extensions from the original response.
+
+- [#12700](https://github.com/apollographql/apollo-client/pull/12700) [`8e96e08`](https://github.com/apollographql/apollo-client/commit/8e96e0862c306df17c09c232704041196a72a466) Thanks [@phryneas](https://github.com/phryneas)! - The callback function that can be passed to the `ApolloClient.mutate`
+  `refetchQueries` option will now receive a `FormattedExecutionResult` with an
+  additional `dataState` option that describes if the result is `"streaming"`
+  or `"complete"`.
+  This indicates whether the `data` value is of type
+
+  - `Unmasked<TData>` (if `"complete"`)
+  - `Streaming<Unmasked<TData>>` (if `"streaming"`)
+
+- [#12714](https://github.com/apollographql/apollo-client/pull/12714) [`0e39469`](https://github.com/apollographql/apollo-client/commit/0e394692eaf0f8d8e506d8304935deafa952accf) Thanks [@phryneas](https://github.com/phryneas)! - Allow passing `errorPolicy` option to `fetchMore` and change default value to "none".
+
+- [#12714](https://github.com/apollographql/apollo-client/pull/12714) [`0e39469`](https://github.com/apollographql/apollo-client/commit/0e394692eaf0f8d8e506d8304935deafa952accf) Thanks [@phryneas](https://github.com/phryneas)! - The `FetchMoreQueryOptions` type has been inlined into `FetchMoreOptions`, and
+  `FetchMoreQueryOptions` has been removed.
+
+- [#12700](https://github.com/apollographql/apollo-client/pull/12700) [`8e96e08`](https://github.com/apollographql/apollo-client/commit/8e96e0862c306df17c09c232704041196a72a466) Thanks [@phryneas](https://github.com/phryneas)! - Prioritize usage of `FormattedExecutionResult` over `FetchResult` where applicable.
+
+  Many APIs used `FetchResult` in place of `FormattedExecutionResult`, which could
+  cause inconsistencies.
+
+  - `FetchResult` is now used to refer to an unhandled "raw" result as returned from
+    a link.
+    This can also include incremental results that use a different format.
+  - `FormattedExecutionResult` from the `graphql` package is now used to represent
+    the execution of a standard GraphQL request without incremental results.
+
+  If your custom links access the `data` property, you might need to first check if
+  the result is a standard GraphQL result by using the `isFormattedExecutionResult`
+  helper from `@apollo/client/utilities`.
+
+- [#12700](https://github.com/apollographql/apollo-client/pull/12700) [`8e96e08`](https://github.com/apollographql/apollo-client/commit/8e96e0862c306df17c09c232704041196a72a466) Thanks [@phryneas](https://github.com/phryneas)! - The `mutationResult` option passed to the `updateQueries` callback now has an
+  additional property, `dataState` with possible values of `"complete"` and `"streaming"`.
+  This indicates whether the `data` value is of type
+  - `Unmasked<TData>` (if `"complete"`)
+  - `Streaming<Unmasked<TData>>` (if `"streaming"`)
+
+### Patch Changes
+
+- [#12709](https://github.com/apollographql/apollo-client/pull/12709) [`9d42e2a`](https://github.com/apollographql/apollo-client/commit/9d42e2a08d3ddfdfdfc7ac65bd66985da5642e7d) Thanks [@phryneas](https://github.com/phryneas)! - Remove these incremental-format-specific types:
+
+  - `ExecutionPatchIncrementalResult`
+  - `ExecutionPatchInitialResult`
+  - `ExecutionPatchResult`
+  - `IncrementalPayload`
+  - `Path`
+
+- [#12677](https://github.com/apollographql/apollo-client/pull/12677) [`94e58ed`](https://github.com/apollographql/apollo-client/commit/94e58ed75fc547ff037d9efeeba929fd61b20c4c) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Downgrade minimum supported `rxjs` peer dependency version to 7.3.0.
+
+- [#12709](https://github.com/apollographql/apollo-client/pull/12709) [`9d42e2a`](https://github.com/apollographql/apollo-client/commit/9d42e2a08d3ddfdfdfc7ac65bd66985da5642e7d) Thanks [@phryneas](https://github.com/phryneas)! - Slightly rework multipart response parsing.
+
+  This removes last incremental-protocol-specific details from `HttpLink` and `BatchHttpLink`.
+
+- [#12700](https://github.com/apollographql/apollo-client/pull/12700) [`8e96e08`](https://github.com/apollographql/apollo-client/commit/8e96e0862c306df17c09c232704041196a72a466) Thanks [@phryneas](https://github.com/phryneas)! - The incremental delivery (`@defer` support) implementation is now pluggable.
+
+  `ApolloClient` now per default ships without an incremental format implementation
+  and allows you to swap in the format that you want to use.
+
+  Usage looks like this:
+
+  ```ts
+  import {
+    // this is the default
+    NotImplementedHandler,
+    // this implements the `@defer` transport format that ships with Apollo Router
+    Defer20220824Handler,
+    // this implements the `@defer` transport format that ships with GraphQL 17.0.0-alpha.2
+    GraphQL17Alpha2Handler,
+  } from "@apollo/client/incremental";
+
+  const client = new ApolloClient({
+    cache: new InMemoryCache({
+      /*...*/
+    }),
+    link: new HttpLink({
+      /*...*/
+    }),
+    incrementalHandler: new Defer20220824Handler(),
+  });
+  ```
+
+  We will add handlers for other response formats that can be swapped this way
+  during the lifetime of Apollo Client 4.0.
+
+## 4.0.0-alpha.22
+
+### Major Changes
+
+- [#12673](https://github.com/apollographql/apollo-client/pull/12673) [`cee90ab`](https://github.com/apollographql/apollo-client/commit/cee90abcd2a9c91c5fdf872cf2d1c12deaa6593e) Thanks [@phryneas](https://github.com/phryneas)! - The `includeExtensions` option of `HttpLink` and `BatchHttpLink` now defaults
+  to `true`.
+
+  If `includeExtensions` is `true`, but `extensions` is not set or empty, extensions
+  will not be included in outgoing requests.
+
+- [#12673](https://github.com/apollographql/apollo-client/pull/12673) [`cee90ab`](https://github.com/apollographql/apollo-client/commit/cee90abcd2a9c91c5fdf872cf2d1c12deaa6593e) Thanks [@phryneas](https://github.com/phryneas)! - The `ApolloClient` constructor options `name` and `version` that are used to
+  configure the client awareness feature have moved onto a `clientAwareness` key.
+
+  ```diff
+  const client = new ApolloClient({
+    // ..
+  -  name: "my-app",
+  -  version: "1.0.0",
+  +  clientAwareness: {
+  +    name: "my-app",
+  +    version: "1.0.0",
+  +  },
+  });
+  ```
+
+- [#12690](https://github.com/apollographql/apollo-client/pull/12690) [`5812759`](https://github.com/apollographql/apollo-client/commit/5812759b6659df49277635e89492c0d72c3b57d6) Thanks [@phryneas](https://github.com/phryneas)! - Aliasing any other field to `__typename` is now forbidden.
+
+- [#12690](https://github.com/apollographql/apollo-client/pull/12690) [`5812759`](https://github.com/apollographql/apollo-client/commit/5812759b6659df49277635e89492c0d72c3b57d6) Thanks [@phryneas](https://github.com/phryneas)! - Aliasing a field to an alias beginning with `__ac_` is now forbidden - this namespace is now reserved for internal use.
+
+- [#12673](https://github.com/apollographql/apollo-client/pull/12673) [`cee90ab`](https://github.com/apollographql/apollo-client/commit/cee90abcd2a9c91c5fdf872cf2d1c12deaa6593e) Thanks [@phryneas](https://github.com/phryneas)! - Adds enhanced client awareness to the client.
+
+  `HttpLink` and `BatchHttpLink` will now per default send information about the
+  client library you are using in `extensions`.
+
+  This could look like this:
+
+  ```json
+  {
+    "query": "query GetUser($id: ID!) { user(id: $id) { __typename id name } }",
+    "variables": {
+      "id": 5
+    },
+    "extensions": {
+      "clientLibrary": {
+        "name": "@apollo/client",
+        "version": "4.0.0"
+      }
+    }
+  }
+  ```
+
+  This feature can be disabled by passing `enhancedClientAwareness: { transport: false }` to your
+  `ApolloClient`, `HttpLink` or `BatchHttpLink` constructor options.
+
+### Minor Changes
+
+- [#12698](https://github.com/apollographql/apollo-client/pull/12698) [`be77d1a`](https://github.com/apollographql/apollo-client/commit/be77d1a6ddf719cab4780a0679fcd98556ac7f22) Thanks [@phryneas](https://github.com/phryneas)! - Adjusted the accept header for multipart requests according to the new GraphQL over HTTP spec with these changes:
+
+  ```diff
+  -multipart/mixed;boundary=graphql;subscriptionSpec=1.0,application/json
+  +multipart/mixed;boundary=graphql;subscriptionSpec=1.0,application/graphql-response+json,application/json;q=0.9
+  ```
+
+  ```diff
+  -multipart/mixed;deferSpec=20220824,application/json
+  +multipart/mixed;deferSpec=20220824,application/graphql-response+json,application/json;q=0.9
+  ```
+
+- [#12673](https://github.com/apollographql/apollo-client/pull/12673) [`cee90ab`](https://github.com/apollographql/apollo-client/commit/cee90abcd2a9c91c5fdf872cf2d1c12deaa6593e) Thanks [@phryneas](https://github.com/phryneas)! - Add the new `ClientAwarenessLink`.
+
+  This link is already included in `HttpLink` and `BatchHttpLink` to enable the
+  "client awareness" and "enhanced client awareness" features, but you can also use
+  `ClientAwarenessLink` directly in your link chain to combine it with other
+  terminating links.
+
+  If you want to save the bundle size that `ClientAwarenessLink` adds to `HttpLink`
+  and `BatchHttpLink`, you can use `BaseHttpLink` or `BaseBatchHttpLink` instead.
+  These links come without the `ClientAwarenessLink` included.
+
+  For example:
+
+  ```diff
+  import {
+    ApolloClient,
+  -  HttpLink,
+  } from "@apollo/client";
+  +import { BaseHttpLink } from "@apollo/client/link/http";
+
+  const client = new ApolloClient({
+  -  link: new HttpLink({
+  +  link: new BaseHttpLink({
+      uri,
+    }),
+    cache: new InMemoryCache(),
+  });
+  ```
+
+- [#12698](https://github.com/apollographql/apollo-client/pull/12698) [`be77d1a`](https://github.com/apollographql/apollo-client/commit/be77d1a6ddf719cab4780a0679fcd98556ac7f22) Thanks [@phryneas](https://github.com/phryneas)! - Adds an `accept` option to `HttpOptions` that allows to add additional `Accept` headers to be merged in without overriding user-specified or default accept headers.
+
+### Patch Changes
+
+- [#12673](https://github.com/apollographql/apollo-client/pull/12673) [`cee90ab`](https://github.com/apollographql/apollo-client/commit/cee90abcd2a9c91c5fdf872cf2d1c12deaa6593e) Thanks [@phryneas](https://github.com/phryneas)! - Fixed a bug in `PersistedQueryLink` where the `persistedQuery` extension would still be sent after a `PersistedQueryNotSupported` if `includeExtensions` was enabled on `HttpLink`.
+
+## 4.0.0-alpha.21
+
+### Major Changes
+
+- [#12686](https://github.com/apollographql/apollo-client/pull/12686) [`dc4b1d0`](https://github.com/apollographql/apollo-client/commit/dc4b1d0d2479a37067113b7bd161a550fb8e4df6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - A `@defer` query that has not yet finished streaming is now considered loading and thus the `loading` flag will be `true` until the response has completed. A new `NetworkStatus.streaming` value has been introduced and will be set as the `networkStatus` while the response is streaming.
+
+- [#12685](https://github.com/apollographql/apollo-client/pull/12685) [`3b74800`](https://github.com/apollographql/apollo-client/commit/3b748003df89ec69a6ad045fb47bbe9c3e62104c) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove the check and warning for `cache.fragmentMatches` when applying data masking. `cache.fragmentMatches` is a required API and data masking may crash when `cache.fragmentMatches` does not exist.
+
+- [#12684](https://github.com/apollographql/apollo-client/pull/12684) [`e697431`](https://github.com/apollographql/apollo-client/commit/e697431a9995fd1900e625c30a9065edd71111d9) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove `context` from `useLazyQuery` hook options. If used, `context` must now be provided to the `execute` function. `context` will reset to `{}` if not provided as an option to `execute`.
+
+## 4.0.0-alpha.20
+
+### Major Changes
+
+- [#12675](https://github.com/apollographql/apollo-client/pull/12675) [`8f1d974`](https://github.com/apollographql/apollo-client/commit/8f1d974881ff54339b6b6593a219ba6d5fd013c0) Thanks [@phryneas](https://github.com/phryneas)! - `ObservableQuery` no longer has a `queryId` property.
+  `ApolloClient.getObservableQueries` no longer returns a `Map<string, ObservableQuery>`, but a `Set<ObservableQuery>`.
+
+- [#12647](https://github.com/apollographql/apollo-client/pull/12647) [`a70fac6`](https://github.com/apollographql/apollo-client/commit/a70fac6dd8f26b46c813723a7206e55bfb677690) Thanks [@phryneas](https://github.com/phryneas)! - `ObservableQuery`s will now only be registered with the `ApolloClient` while they
+  have subscribers.
+
+  That means that `ApolloClient.getObservableQueries` and `ApolloClient.refetchQueries`
+  will only be able to return/refetch queries that have at least one subscriber.
+
+  This changes the previous meaning of `active` and `inactive` queries:
+
+  - `inactive` queries are queries with a subscriber that are skipped from a
+    React hook or have a `fetchPolicy` of `standby`
+  - `active` queries are queries with at least one subscriber that are not skipped or in `standby`.
+
+  `ObservableQuery`s without subscribers but with an active ongoing network request
+  (e.g. caused by calling `reobserve`) will be handled as if they had a subscriber
+  for the duration of the query.
+
+- [#12678](https://github.com/apollographql/apollo-client/pull/12678) [`91a876b`](https://github.com/apollographql/apollo-client/commit/91a876b059042828e431931e7a3c2e0365c387b8) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `queryRef`s created by `preloadQuery` no longer have a `.toPromise()` function. Instead `preloadQuery` now has a `toPromise` function that accepts a queryRef and will resolve when the underlying promise has been resolved.
+
+  ```diff
+  const queryRef = preloadQuery(query, options);
+
+  - await queryRef.toPromise();
+  + await preloadQuery.toPromise(queryRef);
+  ```
+
+- [#12647](https://github.com/apollographql/apollo-client/pull/12647) [`a70fac6`](https://github.com/apollographql/apollo-client/commit/a70fac6dd8f26b46c813723a7206e55bfb677690) Thanks [@phryneas](https://github.com/phryneas)! - `ApolloClient.stop()` now cleans up more agressively to prevent memory leaks:
+
+  - It will now unsubscribe all active `ObservableQuery` instances by emitting a `completed` event.
+  - It will now reject all currently running queries with `"QueryManager stopped while query was in flight"`.
+  - It will remove all queryRefs from the suspense cache.
+
+### Minor Changes
+
+- [#12647](https://github.com/apollographql/apollo-client/pull/12647) [`a70fac6`](https://github.com/apollographql/apollo-client/commit/a70fac6dd8f26b46c813723a7206e55bfb677690) Thanks [@phryneas](https://github.com/phryneas)! - Added a new `.stop` function on `ObservableQuery`.
+  Calling this method will unsubscribe all current subscribers by sending a `complete` event from the observable and tear down the `ObservableQuery`.
+
+## 4.0.0-alpha.19
+
+### Major Changes
+
+- [#12663](https://github.com/apollographql/apollo-client/pull/12663) [`01512f2`](https://github.com/apollographql/apollo-client/commit/01512f2429dd394fb72b8ba9284047a09ade666f) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Unsubscribing from an `ObservableQuery` before a value has been emitted will remove the query from the tracked list of queries and will no longer be eligible for query deduplication.
+
+### Minor Changes
+
+- [#12663](https://github.com/apollographql/apollo-client/pull/12663) [`01512f2`](https://github.com/apollographql/apollo-client/commit/01512f2429dd394fb72b8ba9284047a09ade666f) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Subscriptions created by `client.subscribe()` can now be restarted. Restarting a subscription will terminate the connection with the link chain and recreate the request. Restarts also work across deduplicated subscriptions so calling `restart` on an `observable` who's request is deduplicated will restart the connection for each observable.
+
+  ```ts
+  const observable = client.subscribe({ query: subscription });
+
+  // Restart the connection to the link
+  observable.restart();
+  ```
+
+- [#12663](https://github.com/apollographql/apollo-client/pull/12663) [`01512f2`](https://github.com/apollographql/apollo-client/commit/01512f2429dd394fb72b8ba9284047a09ade666f) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Deduplicating subscription operations is now supported. Previously it was possible to deduplicate a subscription only if the new subscription was created before a previously subscribed subscription emitted any values. As soon as a value was emitted from a subscription, new subscriptions would create new connections. Deduplication is now active for as long as a subscription connection is open (i.e. the source observable hasn't emitted a `complete` or `error` notification yet.)
+
+  To disable deduplication and force a new connection, use the `queryDeduplication` option in `context` like you would a query operation.
+
+  As a result of this change, calling the `restart` function returned from `useSubscription` will now restart the connection on deduplicated subscriptions.
+
+## 4.0.0-alpha.18
+
+### Minor Changes
+
+- [#12670](https://github.com/apollographql/apollo-client/pull/12670) [`0a880ea`](https://github.com/apollographql/apollo-client/commit/0a880ea4c2360a985fdd2edadb94fcc4b82bad73) Thanks [@phryneas](https://github.com/phryneas)! - Provide a mechanism to override the DataMasking types.
+
+  Up until now, our types `Masked`, `MaskedDocumentNode`, `FragmentType`, `MaybeMasked` and `Unmasked` would assume that you are stictly using the type output format of GraphQL Codegen.
+
+  With this change, you can now modify the behaviour of those types if you use a different form of codegen that produces different types for your queries.
+
+  A simple implementation that would override the `Masked` type to remove all fields starting with `_` from a type would look like this:
+
+  ```ts
+  // your actual implementation of `Masked`
+  type CustomMaskedImplementation<TData> = {
+    [K in keyof TData as K extends `_${string}` ? never : K]: TData[K];
+  };
+
+  import { HKT } from "@apollo/client/utilities";
+  // transform this type into a higher kinded type that can be evaulated at a later time
+  interface CustomMaskedType extends HKT {
+    arg1: unknown; // TData
+    return: CustomMaskedImplementation<this["arg1"]>;
+  }
+
+  // create an "implementation interface" for the types you want to override
+  export interface CustomDataMaskingImplementation {
+    Masked: CustomMaskedType;
+    // other possible keys: `MaskedDocumentNode`, `FragmentType`, `MaybeMasked` and `Unmasked`
+  }
+  ```
+
+  then you would use that `CustomDataMaskingImplementation` interface in your project to extend the `TypeOverrides` interface exported by `@apollo/client` with it's functionality:
+
+  ```ts
+  declare module "@apollo/client" {
+    export interface TypeOverrides extends CustomDataMaskingImplementation {}
+  }
+  ```
+
+  After that, all internal usage of `Masked` in Apollo Client as well as all usage in your code base will use the new `CustomMaskedType` implementation.
+
+  If you don't specify overrides, Apollo Client will still default to the GraphQL Codegen data masking implementation.
+  The types for that are also explicitly exported as the `GraphQLCodegenDataMasking` namespace in `@apollo/client/masking`.
+
+## 4.0.0-alpha.17
+
+### Major Changes
+
+- [#12649](https://github.com/apollographql/apollo-client/pull/12649) [`0be92ad`](https://github.com/apollographql/apollo-client/commit/0be92ad51cf8de444fa1cc507bab2c21d230a44e) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The `TData` generic provided to types that return a `dataState` property is now modified by the given `DataState` generic instead of passing a modified `TData` type. For example, a `QueryRef` that could return partial data was defined as `QueryRef<DeepPartial<TData>, TVariables>`. Now `TData` should be provided unmodified and a set of allowed states should be given instead: `QueryRef<TData, TVariables, 'complete' | 'streaming' | 'partial'>`.
+
+  To migrate, use the following guide to replace your type with the right set of states (all types listed below are changed the same way):
+
+  ```diff
+  - QueryRef<TData, TVariables>
+  // `QueryRef`'s default is 'complete' | 'streaming' so this can also be left alone if you prefer
+  // All other types affected by this change default to all states
+  + QueryRef<TData, TVariables>
+  + QueryRef<TData, TVariables, 'complete' | 'streaming'>
+
+  - QueryRef<TData | undefined, TVariables>
+  + QueryRef<TData, TVariables, 'complete' | 'streaming' | 'empty'>
+
+  - QueryRef<DeepPartial<TData>, TVariables>
+  + QueryRef<TData, TVariables, 'complete' | 'streaming' | 'partial'>
+
+  - QueryRef<DeepPartial<TData> | undefined, TVariables>
+  + QueryRef<TData, TVariables, 'complete' | 'streaming' | 'partial' | 'empty'>
+  ```
+
+  The following types are affected. Provide the allowed `dataState` values to the `TDataState` generic:
+
+  - `ApolloQueryResult`
+  - `QueryRef`
+  - `PreloadedQueryRef`
+  - `useLazyQuery.Result`
+  - `useQuery.Result`
+  - `useReadQuery.Result`
+  - `useSuspenseQuery.Result`
+
+  All `*QueryRef` types default to `complete | streaming` states while the rest of the types default to `'complete' | 'streaming' | 'partial' | 'empty'` states. You shouldn't need to provide the states unless you need to either allow for partial data/empty values (`*QueryRef`) or a restricted set of states.
+
+- [#12649](https://github.com/apollographql/apollo-client/pull/12649) [`0be92ad`](https://github.com/apollographql/apollo-client/commit/0be92ad51cf8de444fa1cc507bab2c21d230a44e) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove the deprecated `QueryReference` type. Please use `QueryRef` instead.
+
+- [#12633](https://github.com/apollographql/apollo-client/pull/12633) [`9bfb51f`](https://github.com/apollographql/apollo-client/commit/9bfb51fdbca69560da71f9012c74ee172b6c2b69) Thanks [@phryneas](https://github.com/phryneas)! - If the `execute` function of `useLazyQuery` is executed, previously started queries
+  from the same `useLazyQuery` usage will be rejected with an `AbortError` unless
+  `.retain()` is called on the promise returned by previous `execute` calls.
+
+  Please keep in mind that `useLazyQuery` is primarily meant as a means to synchronize
+  your component to the status of a query and that it's purpose it not to make a
+  series of network calls.
+  If you plan on making a series of network calls without the need to synchronize
+  the result with your component, consider using `ApolloClient.query` instead.
+
+### Minor Changes
+
+- [#12633](https://github.com/apollographql/apollo-client/pull/12633) [`9bfb51f`](https://github.com/apollographql/apollo-client/commit/9bfb51fdbca69560da71f9012c74ee172b6c2b69) Thanks [@phryneas](https://github.com/phryneas)! - `ObservableQuery.refetch` and `ObservableQuery.reobserve` and the `execute` function of `useLazyQuery` now return a
+  `ResultPromise` with an additional `.retain` method.
+  If this method is called, the underlying network operation will be kept running even if the `ObservableQuery` itself does
+  not require the result anymore, and the Promise will resolve with the final result instead of resolving with an intermediate
+  result in the case of early cancellation.
+
+- [#12649](https://github.com/apollographql/apollo-client/pull/12649) [`0be92ad`](https://github.com/apollographql/apollo-client/commit/0be92ad51cf8de444fa1cc507bab2c21d230a44e) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add a new `dataState` property that determines the completeness of the `data` property. `dataState` helps narrow the type of `data`. `dataState` is now emitted from `ObservableQuery` and returned from all React hooks that return a `data` property.
+
+  The `dataState` values are:
+
+  - `empty`: No data could be fulfilled from the cache or the result is incomplete. `data` is `undefined`.
+  - `partial`: Some data could be fulfilled from the cache but `data` is incomplete. This is only possible when `returnPartialData` is `true`.
+  - `streaming`: `data` is incomplete as a result of a deferred query and the result is still streaming in.
+  - `complete`: `data` is a fully satisfied query result fulfilled either from the cache or network.
+
+  Example:
+
+  ```ts
+  const { data, dataState } = useQuery<TData>(query);
+
+  if (dataState === "empty") {
+    expectTypeOf(data).toEqualTypeOf<undefined>();
+  }
+
+  if (dataState === "partial") {
+    expectTypeOf(data).toEqualTypeOf<DeepPartial<TData>>();
+  }
+
+  if (dataState === "streaming") {
+    expectTypeOf(data).toEqualTypeOf<TData>();
+  }
+
+  if (dataState === "complete") {
+    expectTypeOf(data).toEqualTypeOf<TData>();
+  }
+  ```
+
+## 4.0.0-alpha.16
+
+### Major Changes
+
+- [#12644](https://github.com/apollographql/apollo-client/pull/12644) [`fe2f005`](https://github.com/apollographql/apollo-client/commit/fe2f005c34913ae082b96a807dc240e2785d50bd) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Replace the `result` property on `ServerError` with `bodyText`. `bodyText` is set to the raw string body. `HttpLink` and `BatchHttpLink` no longer try and parse the response body as JSON when a `ServerError` is thrown.
+
+- [#12644](https://github.com/apollographql/apollo-client/pull/12644) [`fe2f005`](https://github.com/apollographql/apollo-client/commit/fe2f005c34913ae082b96a807dc240e2785d50bd) Thanks [@jerelmiller](https://github.com/jerelmiller)! - More strictly adhere to the [GraphQL over HTTP spec](https://graphql.github.io/graphql-over-http/draft/). This change adds support for the `application/graphql-response+json` media type and modifies the behavior of the `application/json` media type.
+
+  - The client will parse the response as a well-formed GraphQL response when the server encodes `content-type` using `application/graphql-response+json` with a non-200 status code.
+  - The client will now throw a `ServerError` when the server encodes `content-type` using `application/json` and returns a non-200 status code.
+  - The client will now throw a `ServerError` when the server encodes using any other `content-type` and returns a non-200 status code.
+
+  NOTE: If you use a testing utility to mock requests in your test, you may experience different behavior than production if your testing utility responds as `application/json` but your production server responds as `application/graphql-response+json`. If a `content-type` header is not set, the client interprets the response as `application/json`.
+
+- [#12644](https://github.com/apollographql/apollo-client/pull/12644) [`fe2f005`](https://github.com/apollographql/apollo-client/commit/fe2f005c34913ae082b96a807dc240e2785d50bd) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Change the default `Accept` header to `application/graphql-response+json,application/json;q=0.9`.
+
+- [#12644](https://github.com/apollographql/apollo-client/pull/12644) [`fe2f005`](https://github.com/apollographql/apollo-client/commit/fe2f005c34913ae082b96a807dc240e2785d50bd) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `HttpLink` and `BatchHttpLink` no longer emit a `next` notification with the JSON-parsed response body when a well-formed GraphQL response is returned and a `ServerError` is thrown.
+
+## 4.0.0-alpha.15
+
+### Major Changes
+
+- [#12639](https://github.com/apollographql/apollo-client/pull/12639) [`1bdf489`](https://github.com/apollographql/apollo-client/commit/1bdf4893abb173c97877c71012afa15f9d3da8e6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Move internal testing utilities in `@apollo/client/testing` to `@apollo/client/testing/internal` and remove deprecated testing utilities. Some of the testing utilities exported from the `@apollo/client/testing` endpoint were not considered stable. As a result of this change, testing utilities or types exported from `@apollo/client/testing` are now considered stable and will not undergo breaking changes.
+
+  The following APIs were removed. To migrate, update usages of the following APIs as such:
+
+  **`createMockClient`**
+
+  ```diff
+  - const client = createMockClient(data, query, variables);
+  + const client = new ApolloClient({
+  +   cache: new InMemoryCache(),
+  +   link: new MockLink([
+  +     {
+  +       request: { query, variables },
+  +       result: { data },
+  +     }
+  +   ]),
+  + });
+  ```
+
+  **`mockObservableLink`**
+
+  ```diff
+  - const link = mockObservableLink();
+  + const link = new MockSubscriptionLink();
+  ```
+
+  **`mockSingleLink`**
+
+  ```diff
+  - const link = mockSingleLink({
+  -   request: { query, variables },
+  -   result: { data },
+  - });
+  + const link = new MockLink([
+  +   {
+  +     request: { query, variables },
+  +     result: { data },
+  +   }
+  + ]);
+  ```
+
+- [#12637](https://github.com/apollographql/apollo-client/pull/12637) [`d2a60d4`](https://github.com/apollographql/apollo-client/commit/d2a60d45e734a2518dad2443f85d82553cd6456a) Thanks [@phryneas](https://github.com/phryneas)! - `useQuery`: only advance `previousData` if `data` actually changed
+
+- [#12631](https://github.com/apollographql/apollo-client/pull/12631) [`b147cac`](https://github.com/apollographql/apollo-client/commit/b147cac5c96c44bfc3deb72c12c7521981584c12) Thanks [@phryneas](https://github.com/phryneas)! - `ObservableQuery` will now return a `loading: false` state for `fetchPolicy` `standby`, even before subscription
+
+- [#12639](https://github.com/apollographql/apollo-client/pull/12639) [`1bdf489`](https://github.com/apollographql/apollo-client/commit/1bdf4893abb173c97877c71012afa15f9d3da8e6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove the `@apollo/client/testing/core` entrypoint in favor of `@apollo/client/testing`.
+
+### Minor Changes
+
+- [#12639](https://github.com/apollographql/apollo-client/pull/12639) [`1bdf489`](https://github.com/apollographql/apollo-client/commit/1bdf4893abb173c97877c71012afa15f9d3da8e6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Move `MockLink` types to `MockLink` namespace. This affects the `MockedResponse`, `MockLinkOptions`, and `ResultFunction` types. These types are still exported but are deprecated in favor of the namespace. To migrate, use the types on the `MockLink` namespace instead.
+
+  ```diff
+  import {
+  - MockedResponse,
+  - MockLinkOptions,
+  - ResultFunction,
+  + MockLink
+  } from "@apollo/client/testing";
+
+  - const mocks: MockedResponse = [];
+  + const mocks: MockLink.MockedResponse = [];
+
+  - const result: ResultFunction = () => {/* ... */ }
+  + const result: MockLink.ResultFunction = () => {/* ... */ }
+
+  - const options: MockLinkOptions = {}
+  + const options: MockLink.Options = {}
+  ```
+
+### Patch Changes
+
+- [#12631](https://github.com/apollographql/apollo-client/pull/12631) [`b147cac`](https://github.com/apollographql/apollo-client/commit/b147cac5c96c44bfc3deb72c12c7521981584c12) Thanks [@phryneas](https://github.com/phryneas)! - When updating `skip` from `false` to `true` in `useQuery`, retain `data` if it is available rather than setting it to `undefined`.
+
+- [#12631](https://github.com/apollographql/apollo-client/pull/12631) [`b147cac`](https://github.com/apollographql/apollo-client/commit/b147cac5c96c44bfc3deb72c12c7521981584c12) Thanks [@phryneas](https://github.com/phryneas)! - The `error` property is no longer present when `skip` is `true` in `useQuery`.
+
+## 4.0.0-alpha.14
+
+### Major Changes
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The `getCacheKey` function is no longer available from `operation.getContext()` in the link chain. Use `operation.client.cache.identify(obj)` in the link chain instead.
+
+- [#12556](https://github.com/apollographql/apollo-client/pull/12556) [`c3fceda`](https://github.com/apollographql/apollo-client/commit/c3fceda86c5e0f499d0b5fa54ea7dc4c4391ae2c) Thanks [@phryneas](https://github.com/phryneas)! - `ObservableQuery` will now keep previous `data` around when emitting a `loading` state, unless `query` or `variables` changed.
+  Note that `@exports` variables are not taken into account for this, so `data` will stay around even if they change.
+
+- [#12556](https://github.com/apollographql/apollo-client/pull/12556) [`c3fceda`](https://github.com/apollographql/apollo-client/commit/c3fceda86c5e0f499d0b5fa54ea7dc4c4391ae2c) Thanks [@phryneas](https://github.com/phryneas)! - Removed `getLastResult`, `getLastError` and `resetLastResults` from `ObservableQuery`
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Removes the `resolvers` option from `ApolloClient`. Local resolvers have instead been moved to the new `LocalState` instance which is assigned to the `localState` option in `ApolloClient`. To migrate, move the `resolvers` values into a `LocalState` instance and assign that instance to `localState`.
+
+  ```diff
+  new ApolloClient({
+  - resolvers: { /* ... */ }
+  + localState: new LocalState({
+  +   resolvers: { /* ... */ }
+  + }),
+  });
+  ```
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove local resolvers APIs from `ApolloClient` in favor of `localState`. Methods removed are:
+
+  - `addResolvers`
+  - `getResolvers`
+  - `setResolvers`
+  - `setLocalStateFragmentMatcher`
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Third-party caches must now implement the `fragmentMatches` API. Additionally `fragmentMatches` must be able to handle both `InlineFragmentNode` and `FragmentDefinitionNode` nodes.
+
+  ```ts
+  class MyCache extends ApolloCache {
+    // This is now required
+    public fragmentMatches(
+      fragment: InlineFragmentNode | FragmentDefinitionNode,
+      typename: string
+    ): boolean {
+      return; // ... logic to determine if typename matches fragment
+    }
+  }
+  ```
+
+- [#12556](https://github.com/apollographql/apollo-client/pull/12556) [`c3fceda`](https://github.com/apollographql/apollo-client/commit/c3fceda86c5e0f499d0b5fa54ea7dc4c4391ae2c) Thanks [@phryneas](https://github.com/phryneas)! - Reworked the logic for then a loading state is triggered. If the link chain responds synchronously, a loading state will be omitted, otherwise it will be triggered.
+  If local resolvers are used, the time window for "sync vs async" starts as soon as `@exports` variables are resolved.
+
+- [#12556](https://github.com/apollographql/apollo-client/pull/12556) [`c3fceda`](https://github.com/apollographql/apollo-client/commit/c3fceda86c5e0f499d0b5fa54ea7dc4c4391ae2c) Thanks [@phryneas](https://github.com/phryneas)! - Dropped the `saveAsLastResult` argument from `ObservableQuery.getCurrentResult`
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The resolver function's `context` argument (the 3rd argument) has changed to provide additional information without the possibility of name clashes. Previously the `context` argument would spread request context and override the `client` and `cache` properties to give access to both inside of a resolver. The `context` argument takes now takes the following shape:
+
+  ```ts
+  {
+    // the request context. By default `TContextValue` is of type `DefaultContext`,
+    // but can be changed if a `context` function is provided.
+    requestContext: TContextValue,
+    // The client instance making the request
+    client: ApolloClient,
+    // Whether the resolver is run as a result of gathering exported variables
+    // or resolving the value as part of the result
+    phase: "exports" | "resolve"
+  }
+  ```
+
+  To migrate, pull any request context from `requestContext` and the `cache` from the `client` property:
+
+  ```diff
+  new LocalState({
+    resolvers: {
+      Query: {
+  -     myResolver: (parent, args, { someValue, cache }) => {
+  +     myResolver: (parent, args, { requestContext, client }) => {
+  +       const someValue = requestContext.someValue;
+  +       const cache = client.cache;
+        }
+      }
+    }
+  });
+  ```
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Apollo Client no longer ships with support for `@client` fields out-of-the-box and now must be opt-in. To opt in to use `@client` fields, pass an instantiated `LocalState` instance to the `localState` option. If a query contains `@client` and local state hasn't been configured, an error will be thrown.
+
+  ```ts
+  import { LocalState } from "@apollo/client/local-state";
+
+  new ApolloClient({
+    localState: new LocalState(),
+  });
+  ```
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove the `fragmentMatcher` option from `ApolloClient`. Custom fragment matchers used with local state are no longer supported. Fragment matching is now performed by the configured `cache` via the `cache.fragmentMatches` API.
+
+- [#12556](https://github.com/apollographql/apollo-client/pull/12556) [`c3fceda`](https://github.com/apollographql/apollo-client/commit/c3fceda86c5e0f499d0b5fa54ea7dc4c4391ae2c) Thanks [@phryneas](https://github.com/phryneas)! - A call to `ObservableQuery.setVariables` with different variables or a `ObservableQuery.refetch` call will always now guarantee that a value will be emitted from the observable, even if it is deep equal to the previous value.
+
+### Minor Changes
+
+- [#12614](https://github.com/apollographql/apollo-client/pull/12614) [`d2851e2`](https://github.com/apollographql/apollo-client/commit/d2851e2c74541995760a86904b1e3ab4bd736e62) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Revamp local resolvers and fix several issues from the existing `resolvers` option.
+
+  - Throwing errors in a resolver will set the field value as `null` and add an error to the response's `errors` array.
+  - Remote results are dealiased before they are passed as the parent object to a resolver so that you can access fields by their field name.
+  - You can now specify a `context` function that you can use to customize the `requestContext` given to resolvers.
+  - The `LocalState` class accepts a `Resolvers` generic that provides autocompletion and type checking against your resolver types to ensure your resolvers are type-safe.
+  - `data: null` is now handled correctly and does not call your local resolvers when the server does not provide a result.
+  - Additional warnings have been added to provide hints when resolvers behave unexpectedly.
+
+  ```ts
+  import { LocalState } from "@apollo/client/local-state";
+
+  import { Resolvers } from "./path/to/local-resolvers-types.ts";
+
+  // LocalState now accepts a `Resolvers` generic.
+  const localState = new LocalState<Resolvers>({
+    // The return value of this funciton
+    context: (options) => ({
+      // ...
+    }),
+    resolvers: {
+      // ...
+    },
+  });
+
+  // You may also pass a `ContextValue` generic used to ensure the `context`
+  // function returns the correct type. This type is inferred from your resolvers
+  // if not provided.
+  new LocalState<Resolvers, ContextValue>({
+    // ...
+  });
+  ```
+
+## 4.0.0-alpha.13
+
+### Major Changes
+
+- [#12600](https://github.com/apollographql/apollo-client/pull/12600) [`34ff6aa`](https://github.com/apollographql/apollo-client/commit/34ff6aa25b47c3e84d0b18e2c69bc995814bf2f2) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Move most of the utilities in `@apollo/client/utilities` to `@apollo/client/utilities/internal`. Many of the utilities exported from the `@apollo/client/utilities` endpoint were not considered stable.
+
+  As a result of this change, utilities or types exported from `@apollo/client/utilities` are now documented and considered stable and will not undergo breaking changes.
+
+- [#12595](https://github.com/apollographql/apollo-client/pull/12595) [`60bb49c`](https://github.com/apollographql/apollo-client/commit/60bb49ccea9aecf3e6a212b5a1f71907e60af886) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove the `@apollo/client/testing/experimental` test utilities. Use [GraphQL Testing Library](https://github.com/apollographql/graphql-testing-library) instead.
+
+### Patch Changes
+
+- [#12618](https://github.com/apollographql/apollo-client/pull/12618) [`e4a3ecf`](https://github.com/apollographql/apollo-client/commit/e4a3ecfe50bc5b462067574a0ffb1951549fb60f) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove code that strips `@client` fields in `HttpLink` and `BatchHttpLink`. This was unused code since core handles removing `@client` fields and should have no observable change.
+
+## 4.0.0-alpha.12
+
+### Major Changes
+
+- [#12586](https://github.com/apollographql/apollo-client/pull/12586) [`605db8e`](https://github.com/apollographql/apollo-client/commit/605db8e94fe2ce74c0a395f38f6873d40f431365) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove the `typeDefs` option from `ApolloClient`.
+
+- [#12588](https://github.com/apollographql/apollo-client/pull/12588) [`eed825a`](https://github.com/apollographql/apollo-client/commit/eed825a2549f1d21fff2ec179815206b3baf0fcb) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Remove `TContext` generic argument from all types that use it. `TContext` is replaced with `DefaultContext` which can be modified using declaration merging.
+
+- [#12590](https://github.com/apollographql/apollo-client/pull/12590) [`a005e82`](https://github.com/apollographql/apollo-client/commit/a005e822de7b24783f85be45df142ffbb9bc561b) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Drop `graphql` v15 as a valid peer dependency.
+
+- [#12591](https://github.com/apollographql/apollo-client/pull/12591) [`a7e7383`](https://github.com/apollographql/apollo-client/commit/a7e738328951f5dac25a5fe48d28b3640a3e0eb9) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Rename the `@apollo/client/link/core` entrypoint to `@apollo/client/link`.
+
+- [#12589](https://github.com/apollographql/apollo-client/pull/12589) [`15f5a1c`](https://github.com/apollographql/apollo-client/commit/15f5a1c29ac05015387a7bbc2dbe9a91d09fedfa) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Require the `link` option when instantiating `ApolloClient`. This removes the `uri`, `credentials` and `headers` options from `ApolloClient` in favor of passing an instantiated `HttpLink` directly. To migrate:
+
+  **If using `uri`, `credentials`, or `headers` options**
+
+  ```diff
+  new ApolloClient({
+    // ...
+  - uri,
+  - credentials,
+  - headers,
+  + link: new HttpLink({ uri, credentials, headers }),
+  // or if you prefer the function call approach:
+  + link: createHttpLink({ uri, credentials, headers }),
+  });
+  ```
+
+  **If creating a client without the `link` option**
+
+  ```diff
+  new ApolloClient({
+    // ...
+  + link: ApolloLink.empty()
+  });
+  ```
+
+## 4.0.0-alpha.11
+
+### Major Changes
+
+- [#12576](https://github.com/apollographql/apollo-client/pull/12576) [`a92ff78`](https://github.com/apollographql/apollo-client/commit/a92ff780abee60896bb9632867e90c82d0829255) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The `cache` and `forceFetch` properties are no longer available on context when calling `operation.getContext()`. `cache` can be accessed through the `operation` with `operation.client.cache` instead. `forceFetch` has been replaced with `queryDeduplication` which specifies whether `queryDeduplication` was enabled for the request or not.
+
+- [#12576](https://github.com/apollographql/apollo-client/pull/12576) [`a92ff78`](https://github.com/apollographql/apollo-client/commit/a92ff780abee60896bb9632867e90c82d0829255) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `ApolloLink.execute` now requires a third argument which provides the `client` that initiated the request to the link chain. If you use `execute` directly, add a third argument with a `client` property:
+
+  ```ts
+  ApolloLink.execute(link, operation, { client });
+
+  // or if you import the `execute` function directly:
+  execute(link, operation, { client });
+  ```
+
+- [#12566](https://github.com/apollographql/apollo-client/pull/12566) [`ce4b488`](https://github.com/apollographql/apollo-client/commit/ce4b488bef13f2f5ce1b348d8c3196e198165dd6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Don't `broadcastQueries` when a query is torn down.
+
+### Minor Changes
+
+- [#12576](https://github.com/apollographql/apollo-client/pull/12576) [`a92ff78`](https://github.com/apollographql/apollo-client/commit/a92ff780abee60896bb9632867e90c82d0829255) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Provide an extension to define types for `context` passed to the link chain. To define your own types, use [declaration merging](https://www.typescriptlang.org/docs/handbook/declaration-merging.html) to add properties to the `DefaultContext` type.
+
+  ```ts
+  // @apollo-client.d.ts
+  // This import is necessary to ensure all Apollo Client imports
+  // are still available to the rest of the application.
+  import "@apollo/client";
+
+  declare module "@apollo/client" {
+    interface DefaultContext extends Record<string, any> {
+      myProperty: string;
+    }
+  }
+  ```
+
+  Links that provide context options can be used with this type to add those context types to `DefaultContext`. For example, to add context options from `HttpLink`, add the following code:
+
+  ```ts
+  import { HttpLink } from "@apollo/client";
+
+  declare module "@apollo/client" {
+    interface DefaultContext extends HttpLink.ContextOptions {
+      myProperty: string;
+    }
+  }
+  ```
+
+  At this time, the following built-in links support context options:
+
+  - `HttpLink.ContextOptions`
+  - `BatchHttpLink.ContextOptions`
+
+- [#12576](https://github.com/apollographql/apollo-client/pull/12576) [`a92ff78`](https://github.com/apollographql/apollo-client/commit/a92ff780abee60896bb9632867e90c82d0829255) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add a `client` property to the `operation` passed to the link chain. This `client` is set as the `client` making the request to the link chain.
+
+### Patch Changes
+
+- [#12574](https://github.com/apollographql/apollo-client/pull/12574) [`0098ec9`](https://github.com/apollographql/apollo-client/commit/0098ec9f860e4e08a2070823f723dce401ae588a) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Export `gql` from the `@apollo/client/react` entrypoint.
+
+- [#12572](https://github.com/apollographql/apollo-client/pull/12572) [`3dc50e6`](https://github.com/apollographql/apollo-client/commit/3dc50e6476dcedf82ed3856bf9f4571a32a760a6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Adjust `useMutation` types to better handle required variables. When required variables are missing, TypeScript will now complain if they are not provided either to the hook or the returned `mutate` function. Providing required variables to `useMutation` will make them optional in the returned `mutate` function.
+
+## 4.0.0-alpha.10
+
+### Major Changes
+
+- [#12559](https://github.com/apollographql/apollo-client/pull/12559) [`49ace0e`](https://github.com/apollographql/apollo-client/commit/49ace0e2119b7fd5997dcf051002ebd4ba2e0bc4) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `ObservableQuery.variables` can now be reset back to empty when calling `reobserve` with `variables: undefined`. Previously the `variables` key would be ignored so `variables` would remain unchanged.
+
+- [#12559](https://github.com/apollographql/apollo-client/pull/12559) [`49ace0e`](https://github.com/apollographql/apollo-client/commit/49ace0e2119b7fd5997dcf051002ebd4ba2e0bc4) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `never` is no longer supported as a valid `TVariables` generic argument for APIs that require `variables` as part of its type. Use `Record<string, never>` instead.
+
+- [#12559](https://github.com/apollographql/apollo-client/pull/12559) [`49ace0e`](https://github.com/apollographql/apollo-client/commit/49ace0e2119b7fd5997dcf051002ebd4ba2e0bc4) Thanks [@jerelmiller](https://github.com/jerelmiller)! - When passing a `variables` key with the value `undefined`, the value will be replaced by the default value in the query, if it is provided, rather than leave it as `undefined`.
+
+  ```ts
+  // given this query
+  const query = gql`
+    query PaginatedQuery($limit: Int! = 10, $offset: Int) {
+      list(limit: $limit, offset: $offset) {
+        id
+      }
+    }
+  `;
+
+  const observable = client.query({
+    query,
+    variables: { limit: 5, offset: 0 },
+  });
+  console.log(observable.variables); // => { limit: 5, offset: 0 }
+
+  observable.reobserve({ variables: { limit: undefined, offset: 10 } });
+  // limit is now `10`. This would previously be `undefined`
+  console.log(observable.variables); // => { limit: 10, offset: 10 }
+  ```
+
+- [#12562](https://github.com/apollographql/apollo-client/pull/12562) [`90bf0e6`](https://github.com/apollographql/apollo-client/commit/90bf0e61516a382182f212ac8ab891099e2eb009) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `client.query` no longer supports a `fetchPolicy` of `standby`. `standby` does not fetch and did not return `data`. `standby` is meant for watched queries where fetching should be on hold.
+
+### Minor Changes
+
+- [#12557](https://github.com/apollographql/apollo-client/pull/12557) [`51d26ae`](https://github.com/apollographql/apollo-client/commit/51d26ae631c6631a189c98ea9357b18e77a9a876) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add ability to specify message formatter for `CombinedGraphQLErrors` and `CombinedProtocolErrors`. To provide your own message formatter, override the static `formatMessage` property on these classes.
+
+  ```ts
+  CombinedGraphQLErrors.formatMessage = (
+    errors,
+    { result, defaultFormatMessage }
+  ) => {
+    return "Some formatted message";
+  };
+
+  CombinedProtocolErrors.formatMessage = (errors, { defaultFormatMessage }) => {
+    return "Some formatted message";
+  };
+  ```
+
+- [#12546](https://github.com/apollographql/apollo-client/pull/12546) [`5dffbbe`](https://github.com/apollographql/apollo-client/commit/5dffbbe407eb1d9adbcb0fff89f2d3a75dc1ad2b) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add a static `is` method to error types defined by Apollo Client. `is` makes it simpler to determine whether an error is a specific type, which can be helpful in cases where you'd like to narrow the error type in order to use specific properties from that error.
+
+  This change applies to the following error types:
+
+  - `CombinedGraphQLErrors`
+  - `CombinedProtocolErrors`
+  - `ServerError`
+  - `ServerParseError`
+  - `UnconventionalError`
+
+  **Example**
+
+  ```ts
+  import { CombinedGraphQLErrors } from "@apollo/client";
+
+  if (CombinedGraphQLErrors.is(error)) {
+    console.log(error.message);
+    error.errors.forEach((graphQLError) => console.log(graphQLError.message));
+  }
+  ```
+
+- [#12561](https://github.com/apollographql/apollo-client/pull/12561) [`99d72bf`](https://github.com/apollographql/apollo-client/commit/99d72bfdb38e3d9679f60b9acb065a84e3b42fd6) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Add the ability to detect if an error was an error was emitted from the link chain. This is useful if your application throws custom errors in other areas of the application and you'd like to differentiate them from errors emitted by the link chain itself.
+
+  To detect if an error was emitted from the link chain, use `LinkError.is`.
+
+  ```ts
+  import { LinkError } from "@apollo/client";
+
+  client.query({ query }).catch((error) => {
+    if (LinkError.is(error)) {
+      // This error originated from the link chain
+    }
+  });
+  ```
+
+### Patch Changes
+
+- [#12559](https://github.com/apollographql/apollo-client/pull/12559) [`49ace0e`](https://github.com/apollographql/apollo-client/commit/49ace0e2119b7fd5997dcf051002ebd4ba2e0bc4) Thanks [@jerelmiller](https://github.com/jerelmiller)! - The `variables` option used with various APIs are now enforced more consistently across the client when `TVariables` contains required variables. If required `variables` are not provided, TypeScript will now complain that it requires a `variables` option.
+
+  This change affects the following APIs:
+
+  - `client.query`
+  - `client.mutate`
+  - `client.subscribe`
+  - `client.watchQuery`
+  - `useBackgroundQuery`
+  - `useQuery`
+  - `useSubscription`
+  - `useSuspenseQuery`
+
+- [#12559](https://github.com/apollographql/apollo-client/pull/12559) [`49ace0e`](https://github.com/apollographql/apollo-client/commit/49ace0e2119b7fd5997dcf051002ebd4ba2e0bc4) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Fix type of `variables` returned from `useLazyQuery`. When `called` is `false`, `variables` is now `Partial<TVariables>` instead of `TVariables`.
+
+- [#12562](https://github.com/apollographql/apollo-client/pull/12562) [`90bf0e6`](https://github.com/apollographql/apollo-client/commit/90bf0e61516a382182f212ac8ab891099e2eb009) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `client.query` no longer supports `notifyOnNetworkStatusChange` in options. An error will be thrown if this option is set. The effects of this option were not observable by `client.query` since `client.query` emits a single result.
+
+- [#12557](https://github.com/apollographql/apollo-client/pull/12557) [`51d26ae`](https://github.com/apollographql/apollo-client/commit/51d26ae631c6631a189c98ea9357b18e77a9a876) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Update format of the error message for `CombinedGraphQLErrors` and `CombinedProtocolErrors` to be more like v3.x.
+
+  ```diff
+  console.log(error.message);
+  - `The GraphQL server returned with errors:
+  - - Email not found
+  - - Username already in use`
+  + `Email not found
+  + Username already in use`
+  ```
+
+- [#12559](https://github.com/apollographql/apollo-client/pull/12559) [`49ace0e`](https://github.com/apollographql/apollo-client/commit/49ace0e2119b7fd5997dcf051002ebd4ba2e0bc4) Thanks [@jerelmiller](https://github.com/jerelmiller)! - `ObservableQuery.variables` has been updated to return `TVariables` rather than `TVariables | undefined`. This is more consistent with the runtime value where an empty object (`{}`) will be returned when the `variables` option is not provided.
+
 ## 4.0.0-alpha.9
 
 ### Major Changes
@@ -788,6 +1841,12 @@
 
 - [#12384](https://github.com/apollographql/apollo-client/pull/12384) [`6aa6fd3`](https://github.com/apollographql/apollo-client/commit/6aa6fd316cfdb31ebbe3e3133cca2965604e7ca1) Thanks [@jerelmiller](https://github.com/jerelmiller)! - Don't emit a partial cache result from `cache-only` queries when `returnPartialData` is `false`.
 
+## 3.13.8
+
+### Patch Changes
+
+- [#12567](https://github.com/apollographql/apollo-client/pull/12567) [`c19d415`](https://github.com/apollographql/apollo-client/commit/c19d41513cac0cc143aa7358f26c89c9408da102) Thanks [@thearchitector](https://github.com/thearchitector)! - Fix in-flight multipart urql subscription cancellation
+
 ## 3.13.7
 
 ### Patch Changes