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

[nfgallimore]

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

ℹ️ 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 7 versions ahead of your current version.

• The recommended version was released on a month ago.

Release notes

Package name: @apollo/client

• 3.11.8 - 2024-09-05
  

  Patch Changes

  • #12054 35cf186 Thanks @ phryneas! - Fixed a bug where incorrect object access in some Safari extensions could cause a crash.
• 3.11.7 - 2024-09-04
  

  Patch Changes

  • #12052 e471cef Thanks @ jerelmiller! - Fixes a regression from where passing an invalid identifier to from in useFragment would result in the warning TypeError: Cannot read properties of undefined (reading '__typename').
• 3.11.6 - 2024-09-03
  

  Patch Changes

  • #12049 9c26892 Thanks @ phryneas and @ maciesielka! - Fix a bug where useFragment did not re-render as expected

  • #12044 04462a2 Thanks @ DoctorJohn! - Cache the useSubscription hook's restart function definition between re-renders.

• 3.11.5 - 2024-08-28
  

  Patch Changes

  • #12027 eb3e21b Thanks @ JavaScriptBach! - Type MutationResult.reset as an arrow function

  • #12020 82d8cb4 Thanks @ jerelmiller! - Better conform to Rules of React by avoiding write of ref in render for useFragment.

• 3.11.4 - 2024-08-07
  

  Patch Changes

  • #11994 41b17e5 Thanks @ jerelmiller! - Update the Modifier function type to allow cache.modify to return deeply partial data.

  • #11989 e609156 Thanks @ phryneas! - Fix a potential crash when calling clearStore while a query was running.

    Previously, calling client.clearStore() while a query was running had one of these results:

    • useQuery would stay in a loading: true state.
    • useLazyQuery would stay in a loading: true state, but also crash with a "Cannot read property 'data' of undefined" error.

    Now, in both cases, the hook will enter an error state with a networkError, and the promise returned by the useLazyQuery execute function will return a result in an error state.

  • #11994 41b17e5 Thanks @ jerelmiller! - Prevent accidental distribution on cache.modify field modifiers when a field is a union type array.

• 3.11.3 - 2024-08-05
  

  Patch Changes

  • #11984 5db1659 Thanks @ jerelmiller! - Fix an issue where multiple fetches with results that returned errors would sometimes set the data property with an errorPolicy of none.

  • #11974 c95848e Thanks @ jerelmiller! - Fix an issue where fetchMore would write its result data to the cache when using it with a no-cache fetch policy.

  • #11974 c95848e Thanks @ jerelmiller! - Fix an issue where executing fetchMore with a no-cache fetch policy could sometimes result in multiple network requests.

  • #11974 c95848e Thanks @ jerelmiller! -

    Potentially disruptive change

    When calling fetchMore with a query that has a no-cache fetch policy, fetchMore will now throw if an updateQuery function is not provided. This provides a mechanism to merge the results from the fetchMore call with the query's previous result.

• 3.11.2 - 2024-07-31
  

  Patch Changes

  • #11980 38c0a2c Thanks @ jerelmiller! - Fix missing getServerSnapshot error when using useSubscription on the server.
• 3.11.1 - 2024-07-23
  

  Patch Changes

  • #11969 061cab6 Thanks @ jerelmiller! - Remove check for window.__APOLLO_CLIENT__ when determining whether to connect to Apollo Client Devtools when connectToDevtools or devtools.enabled is not specified. This now simply checks to see if the application is in development mode.

  • #11971 ecf77f6 Thanks @ jerelmiller! - Prevent the setTimeout for suggesting devtools from running in non-browser environments.

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.
• Snyk has automatically assigned this pull request, set who gets assigned.

---

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
• 👩‍💻 Set who automatically gets assigned
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs