-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
chore(deps): update dependency @apollo/client to v3.8.7 #2020
Conversation
|
💻 Website PreviewThe latest changes are available as preview in: https://a47b6178.apollo-angular.pages.dev |
793f74a
to
f3cf24b
Compare
f3cf24b
to
f64f2c5
Compare
f64f2c5
to
33e85e8
Compare
33e85e8
to
7477d9d
Compare
7477d9d
to
1889254
Compare
1889254
to
4c0ee8f
Compare
4c0ee8f
to
0f9721a
Compare
0f9721a
to
570c1d4
Compare
6ab047f
to
93943d8
Compare
93943d8
to
de50189
Compare
de50189
to
28da899
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
3.8.1
->3.8.7
Release Notes
apollographql/apollo-client (@apollo/client)
v3.8.7
Compare Source
Patch Changes
#11297
c8c76a522
Thanks @jerelmiller! - Add an explicit return type for theuseReadQuery
hook calledUseReadQueryResult
. Previously the return type of this hook was inferred from the return value.#11337
bb1da8349
Thanks @phryneas! - #11206 used the TypeScript syntaxinfer X extends Y
that was introduced in TS 4.8.This caused some problems for some users, so we are rolling back to a more backwars-compatible (albeit slightly less performant) type.
v3.8.6
Compare Source
Patch Changes
#11291
2be7eafe3
Thanks @ArioA! - Fix a bug that allows to only callloadErrorMessages
without also callingloadDevErrorMessages
.#11274
b29f000f3
Thanks @jerelmiller! - Start the query ref auto dispose timeout after the initial promise has settled. This prevents requests that run longer than the timeout duration from keeping the component suspended indefinitely.#11289
b5894dbf0
Thanks @phryneas! -MockedProvider
: defaultconnectToDevTools
tofalse
in createdApolloClient
instance.This will prevent the mocked
ApolloClient
instance from trying to connect to the DevTools, which would start asetTimeout
that might keep running after a test has finished.#11206
dd2ce7687
Thanks @phryneas! -cache.modify
: Less strict types & new dev runtime warnings.v3.8.5
Compare Source
v3.8.4
Compare Source
Patch Changes
9e59b251d
Thanks @phryneas! - Forinvariant.log
etc., error arguments are now serialized correctly in the link to the error page.v3.8.3
Compare Source
Patch Changes
fd2a4cf0c
Thanks @phryneas! - Call devtools registration after ApolloClient is fully set up.v3.8.2
Compare Source
Patch Changes
#10072
51045c336
Thanks @Huulivoide! - Fixes race conditions in useReactiveVar that may prevent updates to the reactive variable from propagating through the hook.#11162
d9685f53c
Thanks @jerelmiller! - Ensures GraphQL errors returned in subscription payloads adhere to theerrorPolicy
set inclient.subscribe(...)
calls.#11134
96492e142
Thanks @alessbell! - Use separate type imports in useSuspenseQuery and useBackgroundQuery to workaround SWC compiler issue.#11117
6b8198109
Thanks @phryneas! - Adds a new devtools registration mechanism and tweaks the mechanism behind the"devtools not found" mechanic.
#11186
f1d429f32
Thanks @jerelmiller! - Fix an issue where race conditions when rapidly switching between variables would sometimes result in the wrongdata
returned from the query. Specifically this occurs when a query is triggered with an initial set of variables (VariablesA
), then triggers the same query with another set of variables (VariablesB
) but switches back to theVariablesA
before the response forVariablesB
is returned. Previously this would result in the data forVariablesB
to be displayed whileVariablesA
was active. The data is forVariablesA
is now properly returned.#11163
a8a9e11e9
Thanks @bignimbus! - Fix typo in error message: "occured" -> "occurred"#11180
7d9c481e5
Thanks @jerelmiller! - Fixes an issue where refetching fromuseBackgroundQuery
viarefetch
with an error after an error was already fetched would get stuck in a loading state.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.