litentry / archived-litentry-mobile-app

GNU General Public License v3.0
73 stars 15 forks source link

Bump @apollo/client from 3.5.10 to 3.8.5 #1433

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @apollo/client from 3.5.10 to 3.8.5.

Release notes

Sourced from @​apollo/client's releases.

v3.8.5

Patch Changes

v3.8.4

Patch Changes

  • #11195 9e59b251d Thanks @​phryneas! - For invariant.log etc., error arguments are now serialized correctly in the link to the error page.

v3.8.3

Patch Changes

v3.8.2

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 the errorPolicy set in client.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 wrong data 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 the VariablesA before the response for VariablesB is returned. Previously this would result in the data for VariablesB to be displayed while VariablesA was active. The data is for VariablesA is now properly returned.

  • #11163 a8a9e11e9 Thanks @​bignimbus! - Fix typo in error message: "occured" -> "occurred"

  • #11180 7d9c481e5 Thanks @​jerelmiller! - Fixes an issue where refetching from useBackgroundQuery via refetch with an error after an error was already fetched would get stuck in a loading state.

v3.8.1

Patch Changes

  • #11141 c469b1616 Thanks @​jerelmiller! - Remove newly exported response iterator helpers that caused problems on some installs where @types/node was not available.

    IMPORTANT

    The following exports were added in version 3.8.0 that are removed with this patch.

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

3.8.5

Patch Changes

3.8.4

Patch Changes

  • #11195 9e59b251d Thanks @​phryneas! - For invariant.log etc., error arguments are now serialized correctly in the link to the error page.

3.8.3

Patch Changes

3.8.2

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 the errorPolicy set in client.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 wrong data 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 the VariablesA before the response for VariablesB is returned. Previously this would result in the data for VariablesB to be displayed while VariablesA was active. The data is for VariablesA is now properly returned.

  • #11163 a8a9e11e9 Thanks @​bignimbus! - Fix typo in error message: "occured" -> "occurred"

  • #11180 7d9c481e5 Thanks @​jerelmiller! - Fixes an issue where refetching from useBackgroundQuery via refetch with an error after an error was already fetched would get stuck in a loading state.

3.8.1

Patch Changes

  • #11141 c469b1616 Thanks @​jerelmiller! - Remove newly exported response iterator helpers that caused problems on some installs where @types/node was not available.

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #1434.