fix(deps): update dependency @apollo/client to v3.12.11 #2068
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 contains the following updates:
3.12.6
->3.12.11
Release Notes
apollographql/apollo-client (@apollo/client)
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-level errors are emitted from multipart subscriptions.v3.12.8
Compare Source
Patch Changes
#12292
3abd944
Thanks @phryneas! - Remove unused dependencyresponse-iterator
#12287
bf313a3
Thanks @phryneas! - Fixes an issue whereclient.watchFragment
/useFragment
with@includes
crashes when a separate cache update writes to the conditionally included fields.v3.12.7
Compare Source
Patch Changes
#12281
d638ec3
Thanks @jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with theprotocolErrors
property.#12281
d638ec3
Thanks @jerelmiller! - Fix the array type for theerrors
field on theApolloPayloadResult
type. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.Configuration
📅 Schedule: Branch creation - "on the 10th day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.