[Snyk] Upgrade @apollo/client from 3.11.8 to 3.12.10

[xorinzor]

Snyk has created this PR to upgrade @apollo/client from 3.11.8 to 3.12.10.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 20 versions ahead of your current version.

• The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	479	No Known Exploit
	Cross-site Scripting (XSS) SNYK-JS-AXIOS-6671926	479	No Known Exploit

Release notes

Package name: @apollo/client

• 3.12.10 - 2025-02-06
  

  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

• 3.12.9 - 2025-02-03
  

  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);
    }

    <span class="pl-k">return</span> <span class="pl-c1">true</span><span class="pl-kos">;</span>
    

    },
    });

• 3.12.8 - 2025-01-27
  

  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.

• 3.12.7 - 2025-01-22
  

  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.

• 3.12.6 - 2025-01-14
  

  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.

• 3.12.5 - 2025-01-09
  

  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";
      }
    }

• 3.12.4 - 2024-12-19
  

  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.
• 3.12.3 - 2024-12-12
  

  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.

• 3.12.2 - 2024-12-05
  

  Patch Changes

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

  Patch Changes

  • #12171 e1efe74 Thanks @ phryneas! - Fix import extension in masking entry point.
• 3.12.0 - 2024-12-04
• 3.12.0-rc.4 - 2024-11-27
• 3.12.0-rc.3 - 2024-11-20
• 3.12.0-rc.2 - 2024-11-19
• 3.12.0-rc.1 - 2024-11-15
• 3.12.0-rc.0 - 2024-11-13
• 3.12.0-alpha.0 - 2024-10-01
• 3.11.11-rc.0 - 2024-11-13
• 3.11.10 - 2024-11-11
• 3.11.9 - 2024-11-07
• 3.11.8 - 2024-09-05

from @apollo/client GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud