[js] Update dependency @apollo/client to v3.12.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/client (source)	3.11.9 -> 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.

---

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.

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

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit cee5674)

Action: Format / Check format script run

Failed stage: Run Bazel [❌]

Failure summary: The action failed because the pnpm-lock.yaml file was updated during the build process, which requires a rebuild: The error occurred during the fetch of repository 'aspect_rules_js~~npm~npm' The build system detected changes in pnpm-lock.yaml and requires a new build This is a known issue referenced in [Bug]: update_pnpm_lock fails under Bzlmod, retry fixes it aspect-build/rules_js#1445 The build process was unable to proceed with target '//:buildifier' due to this lock file update

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 970: Package 'php-symfony-debug-bundle' is not installed, so not removed 971: Package 'php-symfony-dependency-injection' is not installed, so not removed 972: Package 'php-symfony-deprecation-contracts' is not installed, so not removed 973: Package 'php-symfony-discord-notifier' is not installed, so not removed 974: Package 'php-symfony-doctrine-bridge' is not installed, so not removed 975: Package 'php-symfony-doctrine-messenger' is not installed, so not removed 976: Package 'php-symfony-dom-crawler' is not installed, so not removed 977: Package 'php-symfony-dotenv' is not installed, so not removed 978: Package 'php-symfony-error-handler' is not installed, so not removed ... 1868: �[32mLoading:�[0m 0 packages loaded 1869: currently loading: 1870: �[32mLoading:�[0m 0 packages loaded 1871: currently loading: 1872: �[32mINFO: �[0mRepository aspect_rules_js~~npm~npm instantiated at: 1873: <builtin>: in <toplevel> 1874: Repository rule npm_translate_lock_rule defined at: 1875: /home/runner/.bazel/external/aspect_rules_js~/npm/private/npm_translate_lock.bzl:146:42: in <toplevel> 1876: �[31m�[1mERROR: �[0mAn error occurred during the fetch of repository 'aspect_rules_js~~npm~npm': 1877: Traceback (most recent call last): 1878: File "/home/runner/.bazel/external/aspect_rules_js~/npm/private/npm_translate_lock.bzl", line 112, column 21, in _npm_translate_lock_impl 1879: fail(msg) 1880: Error in fail: 1881: INFO: pnpm-lock.yaml file updated. Please run your build again. 1882: See https://github.com/aspect-build/rules_js/issues/1445 1883: �[32mLoading:�[0m 0 packages loaded 1884: currently loading: 1885: �[35mWARNING: �[0mTarget pattern parsing failed. 1886: �[31m�[1mERROR: �[0mSkipping '//:buildifier': no such package '@@aspect_rules_js~~npm~npm//': 1887: INFO: pnpm-lock.yaml file updated. Please run your build again. 1888: See https://github.com/aspect-build/rules_js/issues/1445 1889: �[31m�[1mERROR: �[0mno such package '@@aspect_rules_js~~npm~npm//': 1890: INFO: pnpm-lock.yaml file updated. Please run your build again. 1891: See https://github.com/aspect-build/rules_js/issues/1445 1892: �[32mINFO: �[0mElapsed time: 21.209s 1893: �[32mINFO: �[0m0 processes. 1894: �[31m�[1mERROR: �[0mBuild did NOT complete successfully 1895: �[31m�[1mERROR: �[0mBuild failed. Not running target 1896: �[0m 1897: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.