Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @apollo/client from 3.11.2 to 3.11.4 #160

Closed
wants to merge 1 commit into from

Conversation

xorinzor
Copy link
Member

snyk-top-banner

Snyk has created this PR to upgrade @apollo/client from 3.11.2 to 3.11.4.

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

  • The recommended version was released on 23 days ago.

Release notes
Package name: @apollo/client
  • 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

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.

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:

Snyk has created this PR to upgrade @apollo/client from 3.11.2 to 3.11.4.

See this package in npm:
@apollo/client

See this project in Snyk:
https://app.snyk.io/org/shoutz0r-shared/project/71a76727-a61b-4cc8-aecd-bfff7773f421?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@apollo/[email protected] network Transitive: environment, eval +20 7.94 MB apollo-bot

🚮 Removed packages: npm/@apollo/[email protected])

View full report↗︎

Copy link

sonarcloud bot commented Aug 30, 2024

@xorinzor xorinzor closed this Aug 31, 2024
@xorinzor xorinzor deleted the snyk-upgrade-97bce13fcf34bb8f65299342fa3f91a2 branch September 11, 2024 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants