chore(deps): update dependency @apollo/client to v3.12.4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/client (source)	3.10.8 -> 3.12.4

---

Release Notes

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

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.

v3.11.1

Compare Source

Patch Changes

• #​11969 061cab6 Thanks @​jerelmiller! - Remove check for window.__APOLLO_CLIENT__ when determining whether to connect to Apollo Client Devtools when connectToDevtools or devtools.enabled is not specified. This now simply checks to see if the application is in development mode.

• #​11971 ecf77f6 Thanks @​jerelmiller! - Prevent the setTimeout for suggesting devtools from running in non-browser environments.

v3.11.0

Compare Source

Potentially Breaking Fixes

• #​11789 5793301 Thanks @​phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

  This was a type bug - these errors were never GraphQLError instances
  to begin with, and the GraphQLError class has additional properties that can
  never be correctly rehydrated from a GraphQL result.
  The correct type to use here is GraphQLFormattedError.

  Similarly, please ensure to use the type FormattedExecutionResult
  instead of ExecutionResult - the non-"Formatted" versions of these types
  are for use on the server only, but don't get transported over the network.

• #​11626 228429a Thanks @​phryneas! - Call nextFetchPolicy with "variables-changed" even if there is a fetchPolicy specified.

  Previously this would only be called when the current fetchPolicy was equal to the fetchPolicy option or the option was not specified. If you use nextFetchPolicy as a function, expect to see this function called more often.

  Due to this bug, this also meant that the fetchPolicy might be reset to the initial fetchPolicy, even when you specified a nextFetchPolicy function. If you previously relied on this behavior, you will need to update your nextFetchPolicy callback function to implement this resetting behavior.

  As an example, if your code looked like the following:

  useQuery(QUERY, {
    nextFetchPolicy(currentFetchPolicy, info) {
      // your logic here
    }
  );

  Update your function to the following to reimplement the resetting behavior:

  useQuery(QUERY, {
    nextFetchPolicy(currentFetchPolicy, info) {
      if (info.reason === 'variables-changed') {
        return info.initialFetchPolicy;
      }
      // your logic here
    }
  );

Minor Changes

• #​11923 d88c7f8 Thanks @​jerelmiller! - Add support for subscribeToMore function to useQueryRefHandlers.

• #​11854 3812800 Thanks @​jcostello-atlassian! - Support extensions in useSubscription

• #​11923 d88c7f8 Thanks @​jerelmiller! - Add support for subscribeToMore function to useLoadableQuery.

• #​11863 98e44f7 Thanks @​phryneas! - Reimplement useSubscription to fix rules of React violations.

• #​11869 a69327c Thanks @​phryneas! - Rewrite big parts of useQuery and useLazyQuery to be more compliant with the Rules of React and React Compiler

• #​11936 1b23337 Thanks @​jerelmiller! - Add the ability to specify a name for the client instance for use with Apollo Client Devtools. This is useful when instantiating multiple clients to identify the client instance more easily. This deprecates the connectToDevtools option in favor of a new devtools configuration.

  new ApolloClient({
    devtools: {
      enabled: true,
      name: "Test Client",
    },
  });

  This option is backwards-compatible with connectToDevtools and will be used in the absense of a devtools option.

• #​11923 d88c7f8 Thanks @​jerelmiller! - Add support for subscribeToMore function to useBackgroundQuery.

• #​11930 a768575 Thanks @​jerelmiller! - Deprecates experimental schema testing utilities introduced in 3.10 in favor of recommending @apollo/graphql-testing-library.

Patch Changes

• #​11951 0de03af Thanks @​phryneas! - add React 19 RC to peerDependencies

• #​11927 2941824 Thanks @​phryneas! - Add restart function to useSubscription.

• #​11949 4528918 Thanks @​alessbell! - Remove deprecated watchFragment option, canonizeResults

• #​11937 78332be Thanks @​phryneas! - createSchemaFetch: simulate serialized errors instead of an ApolloError instance

• #​11902 96422ce Thanks @​phryneas! - Add cause field to ApolloError.

• #​11806 8df6013 Thanks @​phryneas! - MockLink: add query default variables if not specified in mock request

• #​11926 3dd6432 Thanks @​phryneas! - watchFragment: forward additional options to diffOptions

• #​11946 7d833b8 Thanks @​jerelmiller! - Fix issue where mutations were not accessible by Apollo Client Devtools in 3.11.0-rc.0.

• #​11944 8f3d7eb Thanks @​sneyderdev! - Allow IgnoreModifier to be returned from a optimisticResponse function when inferring from a TypedDocumentNode when used with a generic argument.

• #​11954 4a6e86a Thanks @​phryneas! - Document (and deprecate) the previously undocumented errors property on the useQuery QueryResult type.

• #​11719 09a6677 Thanks @​phryneas! - Allow wrapping createQueryPreloader

• #​11921 70406bf Thanks @​phryneas! - add ignoreResults option to useSubscription

---

Configuration

📅 Schedule: Branch creation - "after 8pm every weekday,before 7pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.