[Snyk] Upgrade @apollo/client from 3.0.0-beta.44 to 3.9.10 #551
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @apollo/client from 3.0.0-beta.44 to 3.9.10.
ℹ️ 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 fixes:
SNYK-JS-APOLLOCLIENT-1085706
Why? CVSS 5.3
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: @apollo/client
Patch Changes
#11738
b1a5eb8
Thanks @ jerelmiller! - Fix an issue where rerenderinguseBackgroundQuery
after thequeryRef
had been disposed, either via the auto dispose timeout or by unmountinguseReadQuery
, would cause thequeryRef
to be recreated potentially resulting in another network request.#11738
b1a5eb8
Thanks @ jerelmiller! - Allow queryRefs to be disposed of synchronously when a suspense hook unmounts. This prevents some situations where using a suspense hook with the same query/variables as the disposed queryRef accidentally used the disposed queryRef rather than creating a new instance.#11670
cc5c03b
Thanks @ phryneas! - Bail out ofexecuteSubSelectedArray
calls if the array has 0 elements.Patch Changes
466ef82
Thanks @ PiR1! - Immediately dispose of thequeryRef
ifuseBackgroundQuery
unmounts before the auto dispose timeout kicks in.Patch Changes
#11706
8619bc7
Thanks @ jerelmiller! - Fix issue in all suspense hooks where returning an empty array after callingfetchMore
would rerender the component with an empty list.#11694
835d5f3
Thanks @ phryneas! - ExposesetErrorMessageHandler
from@ apollo/client/dev
entrypoint.#11689
cb8ffe5
Thanks @ jerelmiller! - Fix issue where passing a newfrom
option touseFragment
would first render with the previous value before rerendering with the correct value.#11713
642092c
Thanks @ jerelmiller! - Fix issue where setting a defaultwatchQuery
option in theApolloClient
constructor could breakstartTransition
when used with suspense hooks.Patch Changes
#11659
652a61e
Thanks @ phryneas! - MakeuseRenderGuard
more resilient to changes in React internals.#11594
50b1097
Thanks @ alessbell! - Adds a fix for multipart subscriptions that terminate with payload: nullPatch Changes
#11617
f1d8bc4
Thanks @ phryneas! - Allow Apollo Client instance to intercept hook functionality#11638
bf93ada
Thanks @ jerelmiller! - Fix issue where callingfetchMore
from a suspense-enabled hook insidestartTransition
caused an unnecessary rerender.Patch Changes
#11595
8c20955
Thanks @ phryneas! - Bumps the dependencyrehackt
to 0.0.5#11592
1133469
Thanks @ Stephen2! - StrengthenMockedResponse.newData
type#11579
1ba2fd9
Thanks @ jerelmiller! - Fix issue where partial data is reported touseQuery
when usingnotifyOnNetworkStatusChange
after it errors while another overlapping query succeeds.#11579
1ba2fd9
Thanks @ jerelmiller! - Fix an issue where a partial cache write for an errored query would result in automatically refetching that query.#11562
65ab695
Thanks @ mspiess! - Mocks with an infinite delay no longer require result or errorPatch Changes
#11403
b0c4f3a
Thanks @ jerelmiller! - Fix issue inuseLazyQuery
that results in a double network call when calling the execute function with no arguments after having called it previously with another set of arguments.#11576
e855d00
Thanks @ alessbell! - Revert PR #11202 to fix caching bug reported in #11560Patch Changes
#11525
dce923a
Thanks @ vezaynk! - Allows passing in client via options to useFragment#11558
8cba16f
Thanks @ alessbell! - Fixunbound-method
linter error on ObservableQuery methods exposed on useQuery's QueryResult object.Patch Changes
6ac2b0c
Thanks @ jerelmiller! - Fix import inuseLazyRef
causing import issues in the nextjs package.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
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs