build(deps): bump @apollo/client from 3.3.6 to 3.12.11

[dependabot]

Bumps @apollo/client from 3.3.6 to 3.12.11.

Release notes

Sourced from @​apollo/client's releases.

v3.12.11

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

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

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

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

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

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

3.12.11

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

3.12.10

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

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

3.12.8

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

Patch Changes

• #12281 d638ec3 Thanks @​jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with the protocolErrors property.

... (truncated)

Commits

• d79aec0 Version Packages (#12355)
• 3da908b Fix emitted fetchMore result from observableQuery for no-cache queries (#...
• a24ef94 fix missing main.d.cts (#12354)
• 1855684 Remove addTypename setting in testing docs (#12353)
• 60a3ba0 remove cci-based security scans (#12339)
• 0a0f801 Version Packages (#12343)
• f2bb0b9 useReadQuery/useQueryRefHandlers: Fix a "hook order" warning that might b...
• 219b26b Add graphql-ws ^6.0.3 as a valid peerDependency (#12342)
• cc47e1c Update ROADMAP.md
• e63a326 chore(deps): update cimg/node docker tag to v23.7.0 (#12336)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/@apollo/client	3.12.11	🟢 5.5	Details Check Score Reason Code-Review 🟢 7 Found 14/20 approved changesets -- score normalized to 7 Maintained 🟢 10 30 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions License 🟢 10 license file detected Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 8 branch protection is not maximal on development and all release branches Signed-Releases ⚠️ -1 no releases found Security-Policy 🟢 10 security policy file detected Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 Fuzzing ⚠️ 0 project is not fuzzed SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Vulnerabilities ⚠️ 0 55 existing vulnerabilities detected

Scanned Files

• package.json

[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

[dependabot]

Superseded by #2232.