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.12.11					peerDependencies	patch
@apollo/client (source)	^3.12.2 -> ^3.12.11					devDependencies	patch
@apollo/client (source)	^3.12.2 -> ^3.12.11					dependencies	patch
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.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/[email protected]
demo/admin                               |  WARN  deprecated [email protected]
demo/admin                               |  WARN  deprecated [email protected]
Progress: resolved 30, reused 0, downloaded 28, added 0
Progress: resolved 36, reused 0, downloaded 34, added 0
Progress: resolved 46, reused 0, downloaded 44, added 0
Progress: resolved 48, reused 0, downloaded 46, added 0
Progress: resolved 53, reused 0, downloaded 51, added 0
Progress: resolved 61, reused 0, downloaded 59, added 0
Progress: resolved 61, reused 0, downloaded 60, added 0
Progress: resolved 86, reused 0, downloaded 84, added 0
Progress: resolved 93, reused 0, downloaded 91, added 0
Progress: resolved 103, reused 0, downloaded 101, added 0
Progress: resolved 121, reused 0, downloaded 119, added 0
Progress: resolved 143, reused 0, downloaded 141, added 0
Progress: resolved 143, reused 0, downloaded 142, added 0
Progress: resolved 167, reused 0, downloaded 167, added 0
Progress: resolved 167, reused 0, downloaded 168, added 0
Progress: resolved 184, reused 0, downloaded 175, added 0
Progress: resolved 223, reused 0, downloaded 208, added 0
Progress: resolved 269, reused 0, downloaded 255, added 0
Progress: resolved 393, reused 0, downloaded 379, added 0
Progress: resolved 433, reused 0, downloaded 419, added 0
Progress: resolved 477, reused 0, downloaded 466, added 0
Progress: resolved 502, reused 0, downloaded 491, added 0
Progress: resolved 526, reused 0, downloaded 515, added 0
Progress: resolved 588, reused 0, downloaded 577, added 0
Progress: resolved 658, reused 0, downloaded 647, added 0
Progress: resolved 735, reused 0, downloaded 724, added 0
Progress: resolved 806, reused 0, downloaded 795, added 0
Progress: resolved 881, reused 0, downloaded 880, added 0
Progress: resolved 951, reused 0, downloaded 950, added 0
Progress: resolved 1004, reused 0, downloaded 1003, added 0
Progress: resolved 1032, reused 0, downloaded 1031, added 0
Progress: resolved 1145, reused 0, downloaded 1144, added 0
Progress: resolved 1218, reused 0, downloaded 1217, added 0
Progress: resolved 1264, reused 0, downloaded 1259, added 0
Progress: resolved 1308, reused 0, downloaded 1277, added 0
Progress: resolved 1320, reused 0, downloaded 1292, added 0
Progress: resolved 1321, reused 0, downloaded 1292, added 0
Progress: resolved 1321, reused 0, downloaded 1294, added 0
Progress: resolved 1321, reused 0, downloaded 1303, added 0
Progress: resolved 1342, reused 0, downloaded 1328, added 0
Progress: resolved 1369, reused 0, downloaded 1355, added 0
Progress: resolved 1532, reused 0, downloaded 1518, added 0
Progress: resolved 1629, reused 0, downloaded 1615, added 0
Progress: resolved 1730, reused 0, downloaded 1716, added 0
Progress: resolved 1827, reused 0, downloaded 1813, added 0
Progress: resolved 1945, reused 0, downloaded 1931, added 0
Progress: resolved 2076, reused 0, downloaded 2064, added 0
Progress: resolved 2221, reused 0, downloaded 2208, added 0
Progress: resolved 2331, reused 0, downloaded 2321, added 0
Progress: resolved 2426, reused 0, downloaded 2418, added 0
 WARN  25 deprecated subdependencies found: @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @babel/[email protected], @humanwhocodes/[email protected], @humanwhocodes/[email protected], @types/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
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.