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.10.4 to 3.10.5 #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Ramyromel
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade @apollo/client from 3.10.4 to 3.10.5.

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

  • The recommended version was released on 24 days ago.

Release notes
Package name: @apollo/client
  • 3.10.5 - 2024-06-12

    Patch Changes

    • #11888 7fb7939 Thanks @ phryneas! - switch useRenderGuard to an approach not accessing React's internals

    • #11511 6536369 Thanks @ phryneas! - useLoadableQuery: ensure that loadQuery is updated if the ApolloClient instance changes

    • #11860 8740f19 Thanks @ alessbell! - Fixes #11849 by reevaluating window.fetch each time BatchHttpLink uses it, if not configured via options.fetch. Takes the same approach as PR #8603 which fixed the same issue in HttpLink.

    • #11852 d502a69 Thanks @ phryneas! - Fix a bug where calling the useMutation reset function would point the hook to an outdated client reference.

    • #11329 3d164ea Thanks @ PaLy! - Fix graphQLErrors in Error Link if networkError.result is an empty string

    • #11852 d502a69 Thanks @ phryneas! - Prevent writing to a ref in render in useMutation.
      As a result, you might encounter problems in the future if you call the mutation's execute function during render. Please note that this was never supported behavior, and we strongly recommend against it.

    • #11848 ad63924 Thanks @ phryneas! - Ensure covariant behavior: MockedResponse<X,Y> should be assignable to MockedResponse

    • #11851 45c47be Thanks @ phryneas! - Avoid usage of useRef in useInternalState to prevent ref access in render.

    • #11877 634d91a Thanks @ phryneas! - Add missing name to tuple member (fix TS5084)

    • #11851 45c47be Thanks @ phryneas! - Fix a bug where useLazyQuery would not pick up a client change.

  • 3.10.4 - 2024-05-15

    Patch Changes

    • #11838 8475346 Thanks @ alex-kinokon! - Don’t prompt for DevTools installation for browser extension page

    • #11839 6481fe1 Thanks @ jerelmiller! - Fix a regression in 3.9.5 where a merge function that returned an incomplete result would not allow the client to refetch in order to fulfill the query.

    • #11844 86984f2 Thanks @ jerelmiller! - Honor the @ nonreactive directive when using cache.watchFragment or the useFragment hook to avoid rerendering when using these directives.

    • #11824 47ad806 Thanks @ phryneas! - Create branded QueryRef type without exposed properties.

      This change deprecates QueryReference in favor of a QueryRef type that doesn't expose any properties.
      This change also updates preloadQuery to return a new PreloadedQueryRef type, which exposes the toPromise function as it does today. This means that query refs produced by useBackgroundQuery and useLoadableQuery now return QueryRef types that do not have access to a toPromise function, which was never meant to be used in combination with these hooks.

      While we tend to avoid any types of breaking changes in patch releases as this, this change was necessary to support an upcoming version of the React Server Component integration, which needed to omit the toPromise function that would otherwise have broken at runtime.
      Note that this is a TypeScript-only change. At runtime, toPromise is still present on all queryRefs currently created by this package - but we strongly want to discourage you from accessing it in all cases except for the PreloadedQueryRef use case.

      Migration is as simple as replacing all references to QueryReference with QueryRef, so it should be possible to do this with a search & replace in most code bases:

      -import { QueryReference } from '@ apollo/client'
      +import { QueryRef } from '@ apollo/client'

    - function Component({ queryRef }: { queryRef: QueryReference<TData> }) {
    + function Component({ queryRef }: { queryRef: QueryRef<TData> }) {
    // ...
    }

  • #11845 4c5c820 Thanks @ jerelmiller! - Remove @ nonreactive directives from queries passed to MockLink to ensure they are properly matched.

  • #11837 dff15b1 Thanks @ jerelmiller! - Fix an issue where a polled query created in React strict mode may not stop polling after the component unmounts while using the cache-and-network fetch policy.

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.10.4 to 3.10.5.

See this package in npm:
@apollo/client

See this project in Snyk:
https://app.snyk.io/org/adek_terafas/project/0f68628f-2a2d-4e55-b1d3-52ec8929116f?utm_source=github&utm_medium=referral&page=upgrade-pr
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.

BatchHTTPLink is not monitoring friendly
2 participants