-
Notifications
You must be signed in to change notification settings - Fork 29
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 dependencies #3639
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
d2cb181
to
4fba8a5
Compare
4fba8a5
to
b693663
Compare
patches/[email protected]
Outdated
-declare function adapter(userPlugin: Plugin): Plugin$1<any>; | ||
+declare function adapter(userPlugin: Plugin): Plugin$1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CarlosCortizasCT Can you check / confirm that this was the actual patch?
7c991ac
to
e1382dc
Compare
e1382dc
to
9233f56
Compare
9233f56
to
9ec594d
Compare
9ec594d
to
1f0768a
Compare
1f0768a
to
b2dca2d
Compare
3af5a8c
to
0364284
Compare
0364284
to
e0006b8
Compare
|
e0006b8
to
99cf86a
Compare
99cf86a
to
cca4c3e
Compare
cca4c3e
to
b7f703c
Compare
b7f703c
to
9fa1934
Compare
9fa1934
to
0a04e00
Compare
0a04e00
to
52c89fb
Compare
52c89fb
to
89da8aa
Compare
This PR contains the following updates:
3.7.14
->3.13.1
3.7.14
->3.13.1
0.5.0
->0.5.1
2.27.5
->2.28.1
6.2.12
->6.6.1
6.2.12
->6.6.1
2.7.8
->2.11.1
0.21.4
->0.23.0
2.2.1
->2.2.3
1.30.7
->1.30.8
3.1.3
->3.1.4
2.6.2
->2.8.11
1.1.4
->1.1.6
7.119.1
->7.120.3
7.117.0
->7.120.3
7.117.0
->7.120.3
0.11.11
->0.12.0
2.6.11
->2.6.12
2.6.11
->2.6.12
17.0.25
->17.0.26
8.16.0
->8.17.1
8.3.0
->8.4.1
7.5.0
->7.7.0
16.4.5
->16.4.7
8.57.0
->8.57.1
8.57.0
->8.57.1
4.20.0
->4.21.2
4.20.0
->4.21.2
8.4.1
->8.5.1
16.8.2
->16.10.0
5.6.0
->5.6.3
5.6.0
->5.6.3
2.2.0
->2.2.1
0.15.2
->0.16.1
15.0.3
->15.0.4
2.6.0
->2.7.0
2.9.0
->2.9.2
9.15.4
->9.15.6
9.15.4+sha256.9bee59c7313a216722c079c1e22160dea7f88df4e0c3450b1d7b01b882336c6a
->9.15.6
v4.0.0
->v4.1.0
8.4.38
->8.5.3
8.4.38
->8.5.3
0.14.2
->0.16.0
5.8.0
->5.10.0
5.0.7
->5.0.10
7.6.2
->7.7.1
5.0.9
->5.0.10
6.1.5
->6.1.6
2.0.4
->2.0.10
5.3.10
->5.3.12
5.0.4
->5.7.3
5.0.4
->5.7.3
3.18.0
->3.19.3
~6.1.0
->~6.2.0
~6.1.0
->~6.2.0
0.17.0
->0.17.1
5.94.0
->5.98.0
5.94.0
->5.98.0
3.13.0
->3.17.0
Release Notes
apollographql/apollo-client (@apollo/client)
v3.13.1
Compare Source
Patch Changes
#12369
bdfc5b2
Thanks @phryneas! -ObervableQuery.refetch
: don't refetch withcache-and-network
, swich tonetwork-only
instead#12375
d3f8f13
Thanks @jerelmiller! - Export theUseSuspenseFragmentOptions
type.v3.13.0
Compare Source
Minor Changes
#12066
c01da5d
Thanks @jerelmiller! - Adds a newuseSuspenseFragment
hook.useSuspenseFragment
suspends untildata
is complete. It is a drop-in replacement foruseFragment
when you prefer to use Suspense to control the loading state of a fragment. See the documentation for more details.#12174
ba5cc33
Thanks @jerelmiller! - Ensure errors thrown in theonCompleted
callback fromuseMutation
don't callonError
.#12340
716d02e
Thanks @phryneas! - Deprecate theonCompleted
andonError
callbacks ofuseQuery
anduseLazyQuery
.For more context, please see the related issue on GitHub.
#12276
670f112
Thanks @Cellule! - Provide a more type-safe option for the previous data value passed toobservableQuery.updateQuery
. Using it could result in crashes at runtime as this callback could be called with partial data even though its type reported the value as a complete result.The
updateQuery
callback function is now called with a new type-safepreviousData
property and a newcomplete
property in the 2nd argument that determines whetherpreviousData
is a complete or partial result.As a result of this change, it is recommended to use the
previousData
property passed to the 2nd argument of the callback rather than using the previous data value from the first argument since that value is not type-safe. The first argument is now deprecated and will be removed in a future version of Apollo Client.#12174
ba5cc33
Thanks @jerelmiller! - Reject the mutation promise if errors are thrown in theonCompleted
callback ofuseMutation
.Patch Changes
#12276
670f112
Thanks @Cellule! - Fix the return type of theupdateQuery
function to allow forundefined
.updateQuery
had the ability to bail out of the update by returning a falsey value, but the return type enforced a query value.#12296
2422df2
Thanks @Cellule! - Deprecate optionignoreResults
inuseMutation
.Once this option is removed, existing code still using it might see increase in re-renders.
If you don't want to synchronize your component state with the mutation, please use
useApolloClient
to get your ApolloClient instance and callclient.mutate
directly.#12338
67c16c9
Thanks @phryneas! - In case of a multipart response (e.g. with@defer
), query deduplication willnow keep going until the final chunk has been received.
#12276
670f112
Thanks @Cellule! - Fix the type of thevariables
property passed as the 2nd argument to thesubscribeToMore
callback. This was previously reported as thevariables
type for the subscription itself, but is now properly typed as the queryvariables
.v3.12.11
Compare Source
Patch Changes
#12351
3da908b
Thanks @jerelmiller! - Fixes an issue where the wrongnetworkStatus
andloading
value was emitted fromobservableQuery
when callingfetchMore
with ano-cache
fetch policy. ThenetworkStatus
now properly reports asready
andloading
asfalse
after the result is returned.#12354
a24ef94
Thanks @phryneas! - Fix missingmain.d.cts
filev3.12.10
Compare Source
Patch Changes
#12341
f2bb0b9
Thanks @phryneas! -useReadQuery
/useQueryRefHandlers
: Fix a "hook order" warning that might be emitted in React 19 dev mode.#12342
219b26b
Thanks @phryneas! - Addgraphql-ws
^6.0.3
as a validpeerDependency
v3.12.9
Compare Source
Patch Changes
#12321
daa4f33
Thanks @jerelmiller! - Fix type ofextensions
inprotocolErrors
forApolloError
and theonError
link. According to the multipart HTTP subscription protocol, fatal tranport errors follow the GraphQL error format which requireextensions
to be a map as its value instead of an array.#12318
b17968b
Thanks @jerelmiller! - AllowRetryLink
to retry an operation when fatal [transport-levConfiguration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.