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]
Progress: resolved 28, reused 0, downloaded 26, added 0
demo/admin                               |  WARN  deprecated [email protected]
demo/admin                               |  WARN  deprecated [email protected]
Progress: resolved 37, reused 0, downloaded 35, added 0
Progress: resolved 42, reused 0, downloaded 40, added 0
Progress: resolved 48, reused 0, downloaded 46, added 0
Progress: resolved 52, reused 0, downloaded 50, added 0
Progress: resolved 58, reused 0, downloaded 56, added 0
Progress: resolved 61, reused 0, downloaded 59, added 0
Progress: resolved 61, reused 0, downloaded 60, added 0
Progress: resolved 84, reused 0, downloaded 82, added 0
Progress: resolved 93, reused 0, downloaded 91, added 0
Progress: resolved 105, reused 0, downloaded 103, added 0
Progress: resolved 131, reused 0, downloaded 129, added 0
Progress: resolved 144, reused 0, downloaded 142, added 0
Progress: resolved 144, reused 0, downloaded 143, added 0
Progress: resolved 165, reused 0, downloaded 165, added 0
Progress: resolved 171, reused 0, downloaded 171, added 0
Progress: resolved 171, reused 0, downloaded 172, added 0
Progress: resolved 187, reused 0, downloaded 175, added 0
Progress: resolved 222, reused 0, downloaded 207, added 0
Progress: resolved 245, reused 0, downloaded 231, added 0
Progress: resolved 341, reused 0, downloaded 327, added 0
Progress: resolved 419, reused 0, downloaded 405, added 0
Progress: resolved 434, reused 0, downloaded 420, added 0
Progress: resolved 449, reused 0, downloaded 436, added 0
Progress: resolved 481, reused 0, downloaded 470, added 0
Progress: resolved 492, reused 0, downloaded 481, added 0
Progress: resolved 504, reused 0, downloaded 493, added 0
Progress: resolved 547, reused 0, downloaded 536, added 0
Progress: resolved 606, reused 0, downloaded 595, added 0
Progress: resolved 662, reused 0, downloaded 651, added 0
Progress: resolved 718, reused 0, downloaded 707, added 0
Progress: resolved 783, reused 0, downloaded 772, added 0
Progress: resolved 888, reused 0, downloaded 887, added 0
Progress: resolved 983, reused 0, downloaded 982, added 0
Progress: resolved 1091, reused 0, downloaded 1090, added 0
Progress: resolved 1180, reused 0, downloaded 1179, added 0
Progress: resolved 1264, reused 0, downloaded 1261, added 0
Progress: resolved 1281, reused 0, downloaded 1272, added 0
Progress: resolved 1306, reused 0, downloaded 1292, added 0
Progress: resolved 1332, reused 0, downloaded 1318, added 0
Progress: resolved 1368, reused 0, downloaded 1355, added 0
Progress: resolved 1386, reused 0, downloaded 1371, added 0
Progress: resolved 1414, reused 0, downloaded 1376, added 0
Progress: resolved 1414, reused 0, downloaded 1377, added 0
Progress: resolved 1414, reused 0, downloaded 1378, added 0
Progress: resolved 1471, reused 0, downloaded 1457, added 0
Progress: resolved 1526, reused 0, downloaded 1512, added 0
Progress: resolved 1684, reused 0, downloaded 1670, added 0
Progress: resolved 1758, reused 0, downloaded 1744, added 0
Progress: resolved 1821, reused 0, downloaded 1807, added 0
Progress: resolved 1887, reused 0, downloaded 1873, added 0
Progress: resolved 1936, reused 0, downloaded 1922, added 0
Progress: resolved 2056, reused 0, downloaded 2043, added 0
Progress: resolved 2156, reused 0, downloaded 2144, added 0
Progress: resolved 2230, reused 0, downloaded 2219, added 0
Progress: resolved 2353, reused 0, downloaded 2345, added 0
Progress: resolved 2459, reused 0, downloaded 2451, 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.