chore(deps): update dependency @apollo/client to v4.2.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@apollo/client (source)	4.2.7 → 4.2.11

---

Release Notes

apollographql/apollo-client (@​apollo/client)

v4.2.11

Compare Source

Patch Changes

• #​13398 3dd3e9a Thanks @​phryneas! - Fix type signature of some DocumentationTypes to fix their display in our documentation.

• #​13392 d4f0771 Thanks @​jerelmiller! - Add a development-only warning when a network result is written to the cache but reading the query back from the cache returns a partial result. This usually points at a merge or read function that did not repair missing fields in the cache, which prevents Apollo Client from applying the cache result to the data received by the network.

v4.2.10

Compare Source

Patch Changes

• #​13385 bfb674e Thanks @​jerelmiller! - Fix accidental widening of the client.mutate return type when optimisticResponse was present.

• #​13382 365373e Thanks @​jerelmiller! - Fix result types widened when a query's variables had constant types (e.g. TypedDocumentNode<Data, { type: "main" }>). This caused options such as returnPartialData or errorPolicy to be reported as their widened types (e.g. boolean, ErrorPolicy) instead of the value that was passed which returned the wrong data and dataState types.

• #​13382 365373e Thanks @​jerelmiller! - Fix issue where unknown options were permitted by TypeScript when passed alongside a valid option to APIs with modern signatures.

• #​13383 5840f50 Thanks @​jerelmiller! - Update the return type of refetch, fetchMore and useLazyQuery's execute function on the provided errorPolicy. Previously these APIs all used the default type which typed data as TData | undefined and error as ErrorLike | undefined.

v4.2.9

Compare Source

Patch Changes

• #​13364 2f383e7 Thanks @​atharv-sys32! - Fix a bug where GraphQL variable default values were not applied during cache reads when variables with defaults were explicitly set to undefined. This caused @include/@skip directives to throw "Invalid variable referenced" errors when the variable was passed as undefined instead of being omitted entirely.

• #​13367 2b39cc8 Thanks @​jerelmiller! - Fix an issue where some @export queries would not react to cache updates when the fields keyed by exported variables were updated.

v4.2.8

Compare Source

Patch Changes

• #​13349 501a33b Thanks @​jerelmiller! - Prevent the setTimeout in connectToDevtools that shows the devtools suggestion from firing when the user agent does not match Chrome or Firefox. This check was previously done inside the setTimeout which meant the timer was scheduled for environments where we'd never show the message anyways. For test environments, this could cause flaky tests when that setTimeout outlived the tests and ran after any virtual DOM was torn down and removed.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

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

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.