Skip to content

Bump @apollo/client from 3.13.9 to 4.3.7 - #4197

Draft
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/apollo/client-4.3.5
Draft

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/apollo/client-4.3.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @apollo/client from 3.13.9 to 4.3.7.

Release notes

Sourced from @​apollo/client's releases.

@​apollo/client@​4.3.7

Patch Changes

  • #13518 b302e5a Thanks @​jerelmiller! - Fix an issue where an AbortError was thrown by useReadQuery when a useBackgroundQuery query is skipped, its useReadQuery component unmounts, and the query is then re-enabled in the same render that useReadQuery mounts again.

  • #13516 d7cb685 Thanks @​trevor-scheer! - Fix a race when chaining refetch and fetchMore calls with useSuspenseQuery inside React transitions.

    For example, an app can refresh the first page of a list with refetch(), then immediately load the next page with fetchMore() from the refetch promise's .then callback. A timer from the completed refetch could make useTransition's isPending become false before the next page arrived, hiding the pending indicator while the list still showed only the first page. Keep the transition pending until the next page is available. This also applies when the first request is another fetchMore().

@​apollo/client@​4.3.6

Patch Changes

  • #13484 9462324 Thanks @​SunilRathod27! - Exclude "partial" from the dataState union returned from useQuery, useLazyQuery, useSuspenseQuery, useBackgroundQuery, useLoadableQuery, and preloadQuery (createQueryPreloader) when fetchPolicy is "no-cache". This means that dataState is never "partial" when fetchPolicy is "no-cache", regardless of whether returnPartialData is true or false.

  • #13486 165aa72 Thanks @​phryneas! - Pass coerced scalars into refetchQueries, updateQueries and update mutation callback options

  • #13487 237a2a1 Thanks @​phryneas! - Introduce a warning for missing possibleTypes that might lead to data loss.

  • #13486 165aa72 Thanks @​phryneas! - Coerce scalars in no-cache mutations

@​apollo/client@​4.3.5

Patch Changes

  • #13498 04b12e5 Thanks @​jerelmiller! - Fix an issue where custom scalar values that are not JSON-serializable caused errors. These values are properly serialized when used as input for variables or when used as a key field value so that cache writes and calls to cache.identify succeed.

  • #13500 a23ea85 Thanks @​jerelmiller! - Require the variables option in useFragment when the fragment has required variables. This matches the behavior of useSuspenseFragment and the query hooks.

  • #13501 303d80f Thanks @​kgssystem! - Parse custom scalar fields in subscription results when using the no-cache fetch policy.

@​apollo/client@​4.3.4

Patch Changes

  • #13497 41d604c Thanks @​jerelmiller! - Fix an issue where a list field selected more than once with different selection sets lost the fields that only one of the selections included while a @defer boundary elsewhere in the query was still pending when using the GraphQL17Alpha9Handler. The results of all selections of the list field are now merged.

  • #13457 22746bb Thanks @​phryneas! - Fixed a bug where streamFieldInfo might not have been passed into custom merge functions for @stream directives that had an aliased field in the path.

  • #13457 22746bb Thanks @​phryneas! - Fix Missing field errors being logged when writing @defer results where a parent field is selected both inside and outside of a deferred fragment. Fields whose @defer boundary has not been delivered from the network are no longer reported as missing.

  • #13453 9bb3a41 Thanks @​wassim-k! - Unregister the watch when an immediate cache.watch broadcast throws. Previously the watch was added to the cache before its first read, and a read that threw left the watch registered while the caller never received the unsubscribe function, so it could not be removed and every later broadcast ran into the same failing read.

  • #13457 22746bb Thanks @​phryneas! - Defer20220824Handler: fix a situation where dataState would show up as completed with incremental errors instead of staying streaming.

@​apollo/client@​4.3.3

Patch Changes

@​apollo/client@​4.3.2

Patch Changes

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

4.3.7

Patch Changes

  • #13518 b302e5a Thanks @​jerelmiller! - Fix an issue where an AbortError was thrown by useReadQuery when a useBackgroundQuery query is skipped, its useReadQuery component unmounts, and the query is then re-enabled in the same render that useReadQuery mounts again.

  • #13516 d7cb685 Thanks @​trevor-scheer! - Fix a race when chaining refetch and fetchMore calls with useSuspenseQuery inside React transitions.

    For example, an app can refresh the first page of a list with refetch(), then immediately load the next page with fetchMore() from the refetch promise's .then callback. A timer from the completed refetch could make useTransition's isPending become false before the next page arrived, hiding the pending indicator while the list still showed only the first page. Keep the transition pending until the next page is available. This also applies when the first request is another fetchMore().

4.3.6

Patch Changes

  • #13484 9462324 Thanks @​SunilRathod27! - Exclude "partial" from the dataState union returned from useQuery, useLazyQuery, useSuspenseQuery, useBackgroundQuery, useLoadableQuery, and preloadQuery (createQueryPreloader) when fetchPolicy is "no-cache". This means that dataState is never "partial" when fetchPolicy is "no-cache", regardless of whether returnPartialData is true or false.

  • #13486 165aa72 Thanks @​phryneas! - Pass coerced scalars into refetchQueries, updateQueries and update mutation callback options

  • #13487 237a2a1 Thanks @​phryneas! - Introduce a warning for missing possibleTypes that might lead to data loss.

  • #13486 165aa72 Thanks @​phryneas! - Coerce scalars in no-cache mutations

4.3.5

Patch Changes

  • #13498 04b12e5 Thanks @​jerelmiller! - Fix an issue where custom scalar values that are not JSON-serializable caused errors. These values are properly serialized when used as input for variables or when used as a key field value so that cache writes and calls to cache.identify succeed.

  • #13500 a23ea85 Thanks @​jerelmiller! - Require the variables option in useFragment when the fragment has required variables. This matches the behavior of useSuspenseFragment and the query hooks.

  • #13501 303d80f Thanks @​kgssystem! - Parse custom scalar fields in subscription results when using the no-cache fetch policy.

4.3.4

Patch Changes

  • #13497 41d604c Thanks @​jerelmiller! - Fix an issue where a list field selected more than once with different selection sets lost the fields that only one of the selections included while a @defer boundary elsewhere in the query was still pending when using the GraphQL17Alpha9Handler. The results of all selections of the list field are now merged.

  • #13457 22746bb Thanks @​phryneas! - Fixed a bug where streamFieldInfo might not have been passed into custom merge functions for @stream directives that had an aliased field in the path.

  • #13457 22746bb Thanks @​phryneas! - Fix Missing field errors being logged when writing @defer results where a parent field is selected both inside and outside of a deferred fragment. Fields whose @defer boundary has not been delivered from the network are no longer reported as missing.

  • #13453 9bb3a41 Thanks @​wassim-k! - Unregister the watch when an immediate cache.watch broadcast throws. Previously the watch was added to the cache before its first read, and a read that threw left the watch registered while the caller never received the unsubscribe function, so it could not be removed and every later broadcast ran into the same failing read.

  • #13457 22746bb Thanks @​phryneas! - Defer20220824Handler: fix a situation where dataState would show up as completed with incremental errors instead of staying streaming.

4.3.3

Patch Changes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​apollo/client since your current version.


@williamjallen
williamjallen marked this pull request as draft November 3, 2026 15:04
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/apollo/client-4.3.5 branch from b11baea to 0bbd0b9 Compare November 3, 2026 15:12
@dependabot dependabot Bot changed the title Bump @apollo/client from 3.13.9 to 4.3.5 Bump @apollo/client from 3.13.9 to 4.3.6 Nov 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/apollo/client-4.3.5 branch from 0bbd0b9 to c979128 Compare November 12, 2026 01:47
Bumps [@apollo/client](https://github.com/apollographql/apollo-client) from 3.13.9 to 4.3.7.
- [Release notes](https://github.com/apollographql/apollo-client/releases)
- [Changelog](https://github.com/apollographql/apollo-client/blob/main/CHANGELOG.md)
- [Commits](https://github.com/apollographql/apollo-client/compare/v3.13.9...@apollo/client@4.3.7)

---
updated-dependencies:
- dependency-name: "@apollo/client"
  dependency-version: 4.3.5
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump @apollo/client from 3.13.9 to 4.3.6 Bump @apollo/client from 3.13.9 to 4.3.7 Nov 13, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/apollo/client-4.3.5 branch from c979128 to 59cb8f0 Compare November 13, 2026 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant