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.12.9
@apollo/client-react-streaming	0.10.0 -> 0.11.8

---

Warning

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

---

Release Notes

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

v3.12.9

Compare Source

Patch Changes

• #​12321 daa4f33 Thanks @​jerelmiller! - Fix type of extensions in protocolErrors for ApolloError and the onError link. According to the multipart HTTP subscription protocol, fatal tranport errors follow the GraphQL error format which require extensions to be a map as its value instead of an array.

• #​12318 b17968b Thanks @​jerelmiller! - Allow RetryLink to retry an operation when fatal transport-level errors are emitted from multipart subscriptions.

  const retryLink = new RetryLink({
    attempts: (count, operation, error) => {
      if (error instanceof ApolloError) {
        // errors available on the `protocolErrors` field in `ApolloError`
        console.log(error.protocolErrors);
      }
  
      return true;
    },
  });

v3.12.8

Compare Source

Patch Changes

• #​12292 3abd944 Thanks @​phryneas! - Remove unused dependency response-iterator

• #​12287 bf313a3 Thanks @​phryneas! - Fixes an issue where client.watchFragment/useFragment with @includes crashes when a separate cache update writes to the conditionally included fields.

v3.12.7

Compare Source

Patch Changes

• #​12281 d638ec3 Thanks @​jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with the protocolErrors property.

  const errorLink = onError(({ protocolErrors }) => {
    if (protocolErrors) {
      console.log(protocolErrors);
    }
  });

• #​12281 d638ec3 Thanks @​jerelmiller! - Fix the array type for the errors field on the ApolloPayloadResult type. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.

v3.12.6

Compare Source

Patch Changes

• #​12267 d57429d Thanks @​jerelmiller! - Maintain the TData type when used with Unmasked when TData is not a masked type generated from GraphQL Codegen.

• #​12270 3601246 Thanks @​jerelmiller! - Fix handling of tagged/branded primitive types when used as scalar values with Unmasked.

v3.12.5

Compare Source

Patch Changes

• #​12252 cb9cd4e Thanks @​jerelmiller! - Changes the default behavior of the MaybeMasked type to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.

  A new mode option has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.

Migrating from <= v3.12.4

If you've adopted data masking and have opted in to using masked types by setting the enabled property to true, you can remove this configuration entirely:

-declare module "@​apollo/client" {
-  interface DataMasking {
-    mode: "unmask"
-  }
-}

If you prefer to specify the behavior explicitly, change the property from enabled: true, to mode: "preserveTypes":

declare module "@​apollo/client" {
  interface DataMasking {
-    enabled: true
+    mode: "preserveTypes"
  }
}

If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the mode to unmask:

declare module "@​apollo/client" {
  interface DataMasking {
    mode: "unmask";
  }
}

v3.12.4

Compare Source

Patch Changes

• #​12236 4334d30 Thanks @​charpeni! - Fix an issue with refetchQueries where comparing DocumentNodes internally by references could lead to an unknown query, even though the DocumentNode was indeed an active query—with a different reference.

v3.12.3

Compare Source

Patch Changes

• #​12214 8bfee88 Thanks @​phryneas! - Data masking: prevent infinite recursion of ContainsFragmentsRefs type

• #​12204 851deb0 Thanks @​jerelmiller! - Fix Unmasked unwrapping tuple types into an array of their subtypes.

• #​12204 851deb0 Thanks @​jerelmiller! - Ensure MaybeMasked does not try and unwrap types that contain index signatures.

• #​12204 851deb0 Thanks @​jerelmiller! - Ensure MaybeMasked does not try to unwrap the type as Unmasked if the type contains any.

v3.12.2

Compare Source

Patch Changes

• #​12175 84af347 Thanks @​jerelmiller! - Update peer deps to allow for React 19 stable release.

v3.12.1

Compare Source

Patch Changes

• #​12171 e1efe74 Thanks @​phryneas! - Fix import extension in masking entry point.

v3.12.0

Compare Source

Minor Changes

Data masking 🎭

• #​12042 1c0ecbf Thanks @​jerelmiller! - Introduces data masking in Apollo Client.

  Data masking enforces that only the fields requested by the query or fragment is available to that component. Data masking is best paired with colocated fragments.

  To enable data masking in Apollo Client, set the dataMasking option to true.

  new ApolloClient({
    dataMasking: true,
    // ... other options
  });

  For detailed information on data masking, including how to incrementally adopt it in an existing applications, see the data masking documentation.

• #​12131 21c3f08 Thanks @​jerelmiller! - Allow null as a valid from value in useFragment.

More Patch Changes

• #​12126 d10d702 Thanks @​jerelmiller! - Maintain the existing document if its unchanged by the codemod and move to more naive whitespace formatting

• #​12150 9ed1e1e Thanks @​jerelmiller! - Fix issue when using Unmasked with older versions of TypeScript when used with array fields.

• #​12116 8ae6e4e Thanks @​jerelmiller! - Prevent field accessor warnings when using @unmask(mode: "migrate") on objects that are passed into cache.identify.

• #​12120 6a98e76 Thanks @​jerelmiller! - Provide a codemod that applies @unmask to all named fragments for all operations and fragments.

  Learn how to use the codemod in the incremental adoption documentation.

• #​12134 cfaf4ef Thanks @​jerelmiller! - Fix issue where data went missing when an unmasked fragment in migrate mode selected fields that the parent did not.

• #​12154 d933def Thanks @​phryneas! - Data masking types: handle overlapping nested array types and fragments on interface types.

• #​12139 5a53e15 Thanks @​phryneas! - Fix issue where masked data would sometimes get returned when the field was part of a child fragment from a fragment unmasked by the parent query.

• #​12123 8422a30 Thanks @​jerelmiller! - Warn when using data masking with "no-cache" operations.

• #​12139 5a53e15 Thanks @​phryneas! - Fix issue where the warning emitted by @unmask(mode: "migrate") would trigger unnecessarily when the fragment was used alongside a masked fragment inside an inline fragment.

• #​12114 1d4ce00 Thanks @​jerelmiller! - Fix error when combining @unmask and @defer directives on a fragment spread when data masking is enabled.

• #​12130 1e7d009 Thanks @​jerelmiller! - Fix error thrown when applying unmask migrate mode warnings on interface types with selection sets that contain inline fragment conditions.

• #​12152 78137ec Thanks @​phryneas! - Add a helper that will skip the TS unmasking alorithm when no fragments are present on type level

• #​12126 d10d702 Thanks @​jerelmiller! - Ensure documents unchanged by the codemod are left untouched.

• #​12133 a6ece37 Thanks @​jerelmiller! - Ensure null is retained in nullable types when unmasking a type with the Unmasked helper type.

• #​12139 5a53e15 Thanks @​phryneas! - Fix issue that threw errors when masking partial data with @unmask(mode: "migrate").

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.8

Compare Source

Patch Changes

• 251bec9: Change package publishing to Changesets
• Updated dependencies [251bec9]
• Updated dependencies [2f779cd]
  • @​apollo/client-react-streaming@​0.11.8

v0.11.7

Compare Source

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.