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
fix(deps): update all non-major dependencies #124
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
5d64360
to
b0f92f6
Compare
b0f92f6
to
5b1a0f5
Compare
5b1a0f5
to
2638a82
Compare
2638a82
to
e4ec901
Compare
e4ec901
to
da4bee4
Compare
da4bee4
to
48eb0f6
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
48eb0f6
to
d22372c
Compare
d22372c
to
a5fd7c6
Compare
a5fd7c6
to
ae6403e
Compare
ae6403e
to
5f6a65f
Compare
5f6a65f
to
2489187
Compare
2489187
to
7b894d6
Compare
a83a6c6
to
7f7d65c
Compare
7f7d65c
to
3d112bc
Compare
3d112bc
to
0f38c03
Compare
0f38c03
to
152541f
Compare
152541f
to
6b6b6ec
Compare
6b6b6ec
to
240448f
Compare
240448f
to
bf479c0
Compare
bf479c0
to
7e6a17b
Compare
7e6a17b
to
767d7cd
Compare
767d7cd
to
b3394b6
Compare
b3394b6
to
e53b606
Compare
e53b606
to
4f7b44d
Compare
4f7b44d
to
42a86ec
Compare
42a86ec
to
cd54540
Compare
This PR contains the following updates:
3.7.15
->3.10.4
7.22.5
->7.24.5
7.22.5
->7.24.5
1.7.15
->1.7.19
2.0.18
->2.1.3
3.1.1
->3.4.2
0.12.14
->0.12.18
0.2.0
->0.4.1
7.0.20
->7.6.19
7.0.20
->7.6.19
7.0.20
->7.6.19
7.0.20
->7.6.19
7.0.20
->7.6.19
0.1.0
->0.2.2
0.5.3
->0.5.7
5.16.5
->5.17.0
14.0.0
->14.3.1
4.1.1
->4.3.0
18.2.12
->18.3.2
5.59.11
->5.62.0
5.59.11
->5.62.0
0.32.0
->0.34.7
10.4.14
->10.4.19
29.5.0
->29.7.0
9.1.2
->9.1.3
0.6.0
->0.7.0
8.2.0
->8.2.2
8.42.0
->8.57.0
13.4.5
->13.5.6
8.8.0
->8.10.0
0.6.12
->0.8.0
16.6.0
->16.8.1
13.2.2
->13.3.0
1.8.1
->1.9.1
1.2.2
->1.3.3
13.4.5
->13.5.6
4.22.1
->4.24.7
0.3.2
->0.4.2
18.16.0
->18.20.2
8.4.24
->8.4.38
8.4.24
->8.4.38
18.2.0
->18.3.1
18.2.0
->18.3.1
7.44.3
->7.51.4
0.16.0
->0.22.0
2.1.4
->2.3.2
2.4.1
->2.10.0
7.0.20
->7.6.19
3.3.2
->3.4.3
5.1.3
->5.4.5
4.3.9
->4.5.3
0.32.0
->0.34.6
0.12.15
->0.12.19
1.2.0
->1.4.0
Release Notes
apollographql/apollo-client (@apollo/client)
v3.10.4
Compare Source
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 usingcache.watchFragment
or theuseFragment
hook to avoid rerendering when using these directives.#11824
47ad806
Thanks @phryneas! - Create brandedQueryRef
type without exposed properties.This change deprecates
QueryReference
in favor of aQueryRef
type that doesn't expose any properties.This change also updates
preloadQuery
to return a newPreloadedQueryRef
type, which exposes thetoPromise
function as it does today. This means that query refs produced byuseBackgroundQuery
anduseLoadableQuery
now returnQueryRef
types that do not have access to atoPromise
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 thePreloadedQueryRef
use case.Migration is as simple as replacing all references to
QueryReference
withQueryRef
, so it should be possible to do this with a search & replace in most code bases:#11845
4c5c820
Thanks @jerelmiller! - Remove@nonreactive
directives from queries passed toMockLink
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 thecache-and-network
fetch policy.v3.10.3
Compare Source
Patch Changes
#11811
d67d7f9
Thanks @phryneas! - Adjust some types for React 19 compat#11834
7d8aad4
Thanks @psamim! - Fix error "Cannot convert object to primitive value"v3.10.2
Compare Source
Patch Changes
#11821
2675d3c
Thanks @jerelmiller! - Fix a regression where rerendering a component withuseBackgroundQuery
would recreate thequeryRef
instance when used with React's strict mode.#11821
2675d3c
Thanks @jerelmiller! - Revert the change introduced in3.9.10 via #11738 that disposed of queryRefs synchronously. This change caused too many issues with strict mode.
v3.10.1
Compare Source
Patch Changes
#11792
5876c35
Thanks @phryneas! - AutoCleanedCache: only schedule batched cache cleanup if the cache is full (fixes #11790)#11799
1aca7ed
Thanks @phryneas! -RenderPromises
: usecanonicalStringify
to serializevariables
to ensure query deduplication is properly applied even whenvariables
are specified in a different order.#11803
bf9dd17
Thanks @phryneas! - Update therehackt
dependency to^0.1.0
#11756
60592e9
Thanks @henryqdineen! - Fix operation.setContext() typev3.10.0
Compare Source
Minor Changes
#11605
e2dd4c9
Thanks @alessbell! - AddscreateMockFetch
utility for integration testing that includes the link chain#11760
acd1982
Thanks @alessbell! -createTestSchema
now uses graphql-toolsmergeResolvers
to merge resolvers instead of a shallow merge.#11764
f046aa9
Thanks @alessbell! - RenamecreateProxiedSchema
tocreateTestSchema
andcreateMockFetch
tocreateSchemaFetch
.#11777
5dfc79f
Thanks @alessbell! - CallcreateMockSchema
insidecreateTestSchema
.#11774
2583488
Thanks @alessbell! - Add ability to set min and max delay increateSchemaFetch
#11605
e2dd4c9
Thanks @alessbell! - Adds proxiedSchema and createMockSchema testing utilities#11465
7623da7
Thanks @alessbell! - AddwatchFragment
method to the cache and expose it on ApolloClient, refactoruseFragment
usingwatchFragment
.#11743
78891f9
Thanks @jerelmiller! - Remove alpha designation forqueryRef.toPromise()
to stabilize the API.#11743
78891f9
Thanks @jerelmiller! - Remove alpha designation forcreateQueryPreloader
to stabilize the API.#11783
440563a
Thanks @alessbell! - Moves new testing utilities to their own entrypoint,testing/experimental
Patch Changes
#11757
9825295
Thanks @phryneas! - AdjustuseReadQuery
wrapper logic to work with transported objects.#11771
e72cbba
Thanks @phryneas! - WrapuseQueryRefHandlers
inwrapHook
.#11754
80d2ba5
Thanks @alessbell! - ExportWatchFragmentOptions
andWatchFragmentResult
from main entrypoint and fix bug wherethis
wasn't bound to thewatchFragment
method onApolloClient
.v3.9.11
Compare Source
Patch Changes
04132af
Thanks @jerelmiller! - Fix an issue where usingskipToken
or theskip
option withuseSuspenseQuery
in React's strict mode would perform a network request.v3.9.10
Compare Source
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 [`cc5c