fix(deps): update apollo graphql packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/client (source)	3.11.1 -> 3.11.10
@apollo/client-react-streaming	0.10.0 -> 0.11.6

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

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

v3.11.10

Compare Source

Patch Changes

• #​12093 1765668 Thanks @​mgmolisani! - Fixed a bug when evaluating the devtools flag with the new syntax devtools.enabled that could result to true when explicitly set to false.

v3.11.9

Compare Source

Patch Changes

• #​12110 a3f95c6 Thanks @​jerelmiller! - Fix an issue where errors returned from a fetchMore call from a Suspense hook would cause a Suspense boundary to be shown indefinitely.

v3.11.8

Compare Source

Patch Changes

• #​12054 35cf186 Thanks @​phryneas! - Fixed a bug where incorrect object access in some Safari extensions could cause a crash.

v3.11.7

Compare Source

Patch Changes

• #​12052 e471cef Thanks @​jerelmiller! - Fixes a regression from where passing an invalid identifier to from in useFragment would result in the warning TypeError: Cannot read properties of undefined (reading '__typename').

v3.11.6

Compare Source

Patch Changes

• #​12049 9c26892 Thanks @​phryneas and @​maciesielka! - Fix a bug where useFragment did not re-render as expected

• #​12044 04462a2 Thanks @​DoctorJohn! - Cache the useSubscription hook's restart function definition between re-renders.

v3.11.5

Compare Source

Patch Changes

• #​12027 eb3e21b Thanks @​JavaScriptBach! - Type MutationResult.reset as an arrow function

• #​12020 82d8cb4 Thanks @​jerelmiller! - Better conform to Rules of React by avoiding write of ref in render for useFragment.

v3.11.4

Compare Source

Patch Changes

• #​11994 41b17e5 Thanks @​jerelmiller! - Update the Modifier function type to allow cache.modify to return deeply partial data.

• #​11989 e609156 Thanks @​phryneas! - Fix a potential crash when calling clearStore while a query was running.

  Previously, calling client.clearStore() while a query was running had one of these results:

  • useQuery would stay in a loading: true state.
  • useLazyQuery would stay in a loading: true state, but also crash with a "Cannot read property 'data' of undefined" error.

  Now, in both cases, the hook will enter an error state with a networkError, and the promise returned by the useLazyQuery execute function will return a result in an error state.

• #​11994 41b17e5 Thanks @​jerelmiller! - Prevent accidental distribution on cache.modify field modifiers when a field is a union type array.

v3.11.3

Compare Source

Patch Changes

• #​11984 5db1659 Thanks @​jerelmiller! - Fix an issue where multiple fetches with results that returned errors would sometimes set the data property with an errorPolicy of none.

• #​11974 c95848e Thanks @​jerelmiller! - Fix an issue where fetchMore would write its result data to the cache when using it with a no-cache fetch policy.

• #​11974 c95848e Thanks @​jerelmiller! - Fix an issue where executing fetchMore with a no-cache fetch policy could sometimes result in multiple network requests.

• #​11974 c95848e Thanks @​jerelmiller! -

Potentially disruptive change

When calling fetchMore with a query that has a no-cache fetch policy, fetchMore will now throw if an updateQuery function is not provided. This provides a mechanism to merge the results from the fetchMore call with the query's previous result.

v3.11.2

Compare Source

Patch Changes

• #​11980 38c0a2c Thanks @​jerelmiller! - Fix missing getServerSnapshot error when using useSubscription on the server.

apollographql/apollo-client-nextjs (@​apollo/client-react-streaming)

v0.11.6

Compare Source

v0.11.5

Compare Source

v0.11.4

Compare Source

v0.11.3

Compare Source

v0.11.2

Compare Source

v0.11.1

Compare Source

v0.11.0

Compare Source

v0.10.1

Compare Source

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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 was generated by Mend Renovate. View the repository job log.