[Snyk] Upgrade @apollo/client from 3.9.5 to 3.10.6 #9
Conversation
Snyk has created this PR to upgrade @apollo/client from 3.9.5 to 3.10.6. See this package in npm: @apollo/client See this project in Snyk: https://app.snyk.io/org/venkatoriga/project/79a0543f-4f4e-4b7f-b959-5557ca519ebb?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
We have skipped reviewing this pull request. Here's why:
- It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
- We don't review packaging changes - Let us know if you'd like us to change this.
|
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.9.5 to 3.10.6.
ℹ️ 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 16 versions ahead of your current version.
The recommended version was released on a month ago.
Issues fixed by the recommended upgrade:
SNYK-JS-WEBPACKDEVMIDDLEWARE-6476555
SNYK-JS-WS-7266574
SNYK-JS-WS-7266574
SNYK-JS-BRACES-6838727
SNYK-JS-MICROMATCH-6838728
SNYK-JS-EJS-6689533
SNYK-JS-EXPRESS-6474509
SNYK-JS-FOLLOWREDIRECTS-6444610
Release notes
Package name: @apollo/client
Patch Changes
f745558Thanks @ phryneas! -useMutation: useuseIsomorphicLayoutEffectinstead ofuseLayoutEffectPatch Changes
#11888
7fb7939Thanks @ phryneas! - switchuseRenderGuardto an approach not accessing React's internals#11511
6536369Thanks @ phryneas! -useLoadableQuery: ensure thatloadQueryis updated if the ApolloClient instance changes#11860
8740f19Thanks @ alessbell! - Fixes #11849 by reevaluatingwindow.fetcheach timeBatchHttpLinkuses it, if not configured viaoptions.fetch. Takes the same approach as PR #8603 which fixed the same issue inHttpLink.#11852
d502a69Thanks @ phryneas! - Fix a bug where calling theuseMutationresetfunction would point the hook to an outdatedclientreference.#11329
3d164eaThanks @ PaLy! - Fix graphQLErrors in Error Link if networkError.result is an empty string#11852
d502a69Thanks @ phryneas! - Prevent writing to a ref in render inuseMutation.As a result, you might encounter problems in the future if you call the mutation's
executefunction during render. Please note that this was never supported behavior, and we strongly recommend against it.#11848
ad63924Thanks @ phryneas! - Ensure covariant behavior:MockedResponse<X,Y>should be assignable toMockedResponse#11851
45c47beThanks @ phryneas! - Avoid usage of useRef in useInternalState to prevent ref access in render.#11877
634d91aThanks @ phryneas! - Add missing name to tuple member (fix TS5084)#11851
45c47beThanks @ phryneas! - Fix a bug whereuseLazyQuerywould not pick up a client change.Patch Changes
#11838
8475346Thanks @ alex-kinokon! - Don’t prompt for DevTools installation for browser extension page#11839
6481fe1Thanks @ 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
86984f2Thanks @ jerelmiller! - Honor the@ nonreactivedirective when usingcache.watchFragmentor theuseFragmenthook to avoid rerendering when using these directives.#11824
47ad806Thanks @ phryneas! - Create brandedQueryReftype without exposed properties.This change deprecates
QueryReferencein favor of aQueryReftype that doesn't expose any properties.This change also updates
preloadQueryto return a newPreloadedQueryReftype, which exposes thetoPromisefunction as it does today. This means that query refs produced byuseBackgroundQueryanduseLoadableQuerynow returnQueryReftypes that do not have access to atoPromisefunction, 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
toPromisefunction that would otherwise have broken at runtime.Note that this is a TypeScript-only change. At runtime,
toPromiseis 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 thePreloadedQueryRefuse case.Migration is as simple as replacing all references to
QueryReferencewithQueryRef, so it should be possible to do this with a search & replace in most code bases:+import { QueryRef } from '@ apollo/client'
- function Component({ queryRef }: { queryRef: QueryReference<TData> }) {
+ function Component({ queryRef }: { queryRef: QueryRef<TData> }) {
// ...
}
#11845
4c5c820Thanks @ jerelmiller! - Remove@ nonreactivedirectives from queries passed toMockLinkto ensure they are properly matched.#11837
dff15b1Thanks @ jerelmiller! - Fix an issue where a polled query created in React strict mode may not stop polling after the component unmounts while using thecache-and-networkfetch policy.Patch Changes
#11811
d67d7f9Thanks @ phryneas! - Adjust some types for React 19 compat#11834
7d8aad4Thanks @ psamim! - Fix error "Cannot convert object to primitive value"Patch Changes
#11821
2675d3cThanks @ jerelmiller! - Fix a regression where rerendering a component withuseBackgroundQuerywould recreate thequeryRefinstance when used with React's strict mode.#11821
2675d3cThanks @ jerelmiller! - Revert the change introduced in3.9.10 via #11738 that disposed of queryRefs synchronously. This change caused too many issues with strict mode.
Important
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: