Update Apollo GraphQL packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@apollo/client (source)	^3.12.2 -> ^3.13.1					peerDependencies	minor
@apollo/client (source)	^3.12.2 -> ^3.13.1					devDependencies	minor
@apollo/client (source)	^3.12.2 -> ^3.13.1					dependencies	minor
apollo-server-core (source)	^3.13.0 -> ^4.0.0					dependencies	replacement
apollo-server-express (source)	^3.13.0 -> ^4.0.0					dependencies	replacement

This is a special PR that replaces apollo-server-core with the community suggested minimal stable replacement version.

This is a special PR that replaces apollo-server-express with the community suggested minimal stable replacement version.

---

Release Notes

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

v3.13.1

Compare Source

Patch Changes

• #​12369 bdfc5b2 Thanks @​phryneas! - ObervableQuery.refetch: don't refetch with cache-and-network, swich to network-only instead

• #​12375 d3f8f13 Thanks @​jerelmiller! - Export the UseSuspenseFragmentOptions type.

v3.13.0

Compare Source

Minor Changes

• #​12066 c01da5d Thanks @​jerelmiller! - Adds a new useSuspenseFragment hook.

  useSuspenseFragment suspends until data is complete. It is a drop-in replacement for useFragment when you prefer to use Suspense to control the loading state of a fragment. See the documentation for more details.

• #​12174 ba5cc33 Thanks @​jerelmiller! - Ensure errors thrown in the onCompleted callback from useMutation don't call onError.

• #​12340 716d02e Thanks @​phryneas! - Deprecate the onCompleted and onError callbacks of useQuery and useLazyQuery.
  For more context, please see the related issue on GitHub.

• #​12276 670f112 Thanks @​Cellule! - Provide a more type-safe option for the previous data value passed to observableQuery.updateQuery. Using it could result in crashes at runtime as this callback could be called with partial data even though its type reported the value as a complete result.

  The updateQuery callback function is now called with a new type-safe previousData property and a new complete property in the 2nd argument that determines whether previousData is a complete or partial result.

  As a result of this change, it is recommended to use the previousData property passed to the 2nd argument of the callback rather than using the previous data value from the first argument since that value is not type-safe. The first argument is now deprecated and will be removed in a future version of Apollo Client.

  observableQuery.updateQuery(
    (unsafePreviousData, { previousData, complete }) => {
      previousData;
      // ^? TData | DeepPartial<TData> | undefined
  
      if (complete) {
        previousData;
        // ^? TData
      } else {
        previousData;
        // ^? DeepPartial<TData> | undefined
      }
    }
  );

• #​12174 ba5cc33 Thanks @​jerelmiller! - Reject the mutation promise if errors are thrown in the onCompleted callback of useMutation.

Patch Changes

• #​12276 670f112 Thanks @​Cellule! - Fix the return type of the updateQuery function to allow for undefined. updateQuery had the ability to bail out of the update by returning a falsey value, but the return type enforced a query value.

  observableQuery.updateQuery(
    (unsafePreviousData, { previousData, complete }) => {
      if (!complete) {
        // Bail out of the update by returning early
        return;
      }
  
      // ...
    }
  );

• #​12296 2422df2 Thanks @​Cellule! - Deprecate option ignoreResults in useMutation.
  Once this option is removed, existing code still using it might see increase in re-renders.
  If you don't want to synchronize your component state with the mutation, please use useApolloClient to get your ApolloClient instance and call client.mutate directly.

• #​12338 67c16c9 Thanks @​phryneas! - In case of a multipart response (e.g. with @defer), query deduplication will
  now keep going until the final chunk has been received.

• #​12276 670f112 Thanks @​Cellule! - Fix the type of the variables property passed as the 2nd argument to the subscribeToMore callback. This was previously reported as the variables type for the subscription itself, but is now properly typed as the query variables.

v3.12.11

Compare Source

Patch Changes

• #​12351 3da908b Thanks @​jerelmiller! - Fixes an issue where the wrong networkStatus and loading value was emitted from observableQuery when calling fetchMore with a no-cache fetch policy. The networkStatus now properly reports as ready and loading as false after the result is returned.

• #​12354 a24ef94 Thanks @​phryneas! - Fix missing main.d.cts file

v3.12.10

Compare Source

Patch Changes

• #​12341 f2bb0b9 Thanks @​phryneas! - useReadQuery/useQueryRefHandlers: Fix a "hook order" warning that might be emitted in React 19 dev mode.

• #​12342 219b26b Thanks @​phryneas! - Add graphql-ws ^6.0.3 as a valid peerDependency

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.

---

Configuration

📅 Schedule: 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.

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 8 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
demo/admin                               |  WARN  deprecated @gitbeaker/node@35.8.1
demo/admin                               |  WARN  deprecated eslint@8.56.0
Progress: resolved 28, reused 0, downloaded 26, added 0
demo/admin                               |  WARN  deprecated rimraf@3.0.2
Progress: resolved 37, reused 0, downloaded 35, added 0
Progress: resolved 46, reused 0, downloaded 44, added 0
Progress: resolved 47, reused 0, downloaded 45, added 0
Progress: resolved 62, reused 0, downloaded 60, added 0
Progress: resolved 62, reused 0, downloaded 61, added 0
Progress: resolved 85, reused 0, downloaded 83, added 0
Progress: resolved 102, reused 0, downloaded 100, added 0
Progress: resolved 121, reused 0, downloaded 119, added 0
Progress: resolved 135, reused 0, downloaded 133, added 0
Progress: resolved 135, reused 0, downloaded 134, added 0
Progress: resolved 165, reused 0, downloaded 163, added 0
Progress: resolved 166, reused 0, downloaded 165, added 0
Progress: resolved 166, reused 0, downloaded 166, added 0
Progress: resolved 175, reused 0, downloaded 175, added 0
Progress: resolved 217, reused 0, downloaded 202, added 0
Progress: resolved 293, reused 0, downloaded 279, added 0
Progress: resolved 392, reused 0, downloaded 378, added 0
Progress: resolved 434, reused 0, downloaded 420, added 0
Progress: resolved 474, reused 0, downloaded 463, added 0
Progress: resolved 493, reused 0, downloaded 482, added 0
Progress: resolved 507, reused 0, downloaded 496, added 0
Progress: resolved 552, reused 0, downloaded 541, added 0
Progress: resolved 606, reused 0, downloaded 595, added 0
Progress: resolved 671, reused 0, downloaded 660, added 0
Progress: resolved 755, reused 0, downloaded 744, added 0
Progress: resolved 902, reused 0, downloaded 901, added 0
Progress: resolved 1033, reused 0, downloaded 1032, added 0
Progress: resolved 1107, reused 0, downloaded 1106, added 0
Progress: resolved 1155, reused 0, downloaded 1154, added 0
Progress: resolved 1277, reused 0, downloaded 1266, added 0
Progress: resolved 1286, reused 0, downloaded 1281, added 0
Progress: resolved 1309, reused 0, downloaded 1303, added 0
Progress: resolved 1347, reused 0, downloaded 1320, added 0
Progress: resolved 1356, reused 0, downloaded 1339, added 0
Progress: resolved 1359, reused 0, downloaded 1342, added 0
Progress: resolved 1359, reused 0, downloaded 1343, added 0
Progress: resolved 1372, reused 0, downloaded 1356, added 0
Progress: resolved 1410, reused 0, downloaded 1394, added 0
Progress: resolved 1462, reused 0, downloaded 1446, added 0
Progress: resolved 1599, reused 0, downloaded 1583, added 0
Progress: resolved 1724, reused 0, downloaded 1708, added 0
Progress: resolved 1785, reused 0, downloaded 1770, added 0
Progress: resolved 1857, reused 0, downloaded 1843, added 0
Progress: resolved 1948, reused 0, downloaded 1934, added 0
Progress: resolved 2035, reused 0, downloaded 2021, added 0
Progress: resolved 2157, reused 0, downloaded 2145, added 0
Progress: resolved 2230, reused 0, downloaded 2221, added 0
Progress: resolved 2328, reused 0, downloaded 2320, added 0
Progress: resolved 2434, reused 0, downloaded 2426, added 0
 WARN  25 deprecated subdependencies found: @babel/plugin-proposal-class-properties@7.18.6, @babel/plugin-proposal-nullish-coalescing-operator@7.18.6, @babel/plugin-proposal-numeric-separator@7.18.6, @babel/plugin-proposal-object-rest-spread@7.20.7, @babel/plugin-proposal-optional-chaining@7.21.0, @babel/plugin-proposal-private-methods@7.18.6, @babel/plugin-proposal-private-property-in-object@7.21.11, @humanwhocodes/config-array@0.11.14, @humanwhocodes/object-schema@2.0.3, @types/loud-rejection@2.0.0, abab@2.0.6, acorn-import-assertions@1.9.0, domexception@2.0.1, fstream@1.0.12, glob@7.2.3, glob@8.1.0, har-validator@5.1.5, inflight@1.0.6, intl-messageformat-parser@6.4.3, multer@1.4.4, request@2.88.2, rimraf@2.7.1, subscriptions-transport-ws@0.11.0, uuid@3.4.0, w3c-hr-time@1.0.2
Progress: resolved 2460, reused 0, downloaded 2452, added 0
Progress: resolved 2460, reused 0, downloaded 2452, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

demo/api
└─┬ @apollo/server 4.11.3
  └── ✕ unmet peer graphql@^16.6.0: found 15.9.0

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.