TL;DR

Apollo Client now correctly updates polling intervals for useLazyQuery and preserves data references during refetches, improving performance and preventing unexpected re-renders.

Fixes Worth Knowing

• useLazyQuery now correctly applies updated pollInterval values (automatic data refresh).
• Referential equality of data is preserved on refetch when data hasn’t changed, optimizing component updates.

TL;DR

Apollo Client now correctly merges refetchOn options, allowing defaults to apply when per-query settings are incomplete, improving control over data refetching behavior.

Fixes Worth Knowing

• refetchOn merging is fixed: default options now apply to unspecified events when configuring watchQuery.
• A deprecation warning for older function signatures (function overloads) has been corrected to only apply to explicitly typed signatures, encouraging use of TypedDocumentNode (strongly typed queries).
• Type safety for preloadQuery (pre-fetching data) has been improved, ensuring correct data states.

Before You Upgrade

If you’re explicitly setting refetchOn with objects, verify that your desired events are configured; otherwise, your default refetchOn settings will now apply.

TL;DR

Apollo Client now correctly silences deprecation warnings, even when used in different parts of your application, improving console clarity.

Fixes Worth Knowing

Deprecation warnings are now consistently muted when globally disabled, resolving issues where warnings reappeared unexpectedly.

Before You Upgrade

If you globally muted deprecation warnings, verify they remain silenced after upgrading.

TL;DR

Apollo Client’s code generation tooling now requires updating your GraphQL code generation dependencies due to major version bumps.

Breaking

• GraphQL code generation dependencies (tools for generating code) must be updated to the latest major versions.

Before You Upgrade

• Update your GraphQL code generation packages (e.g., graphql, graphql-tag) to their latest major versions.

TL;DR

Apollo Client now supports generating resolver types for LocalState (client-side data management) using a new GraphQL Codegen plugin, streamlining type safety for local data.

Breaking

• Codemod Required: A codemod is available to update import paths from Apollo Client v3 to v4. Run npx @apollo/client-codemod-migrate-3-to-4 --parser tsx ./src/**/*.{ts,tsx}.
• gql Import: gql is no longer exported from @apollo/client/react; import it directly from @apollo/client.
• ApolloClient Type: The TCacheShape type argument has been removed from ApolloClient usages.

New

• Local State Codegen Plugin: Generate resolver types for LocalState using the @apollo/client-graphql-codegen/local-state plugin.
• Comprehensive Codemod: A codemod automates several key migration steps, including updating HttpLink configuration and LocalState setup.

Fixes Worth Knowing

• Corrected an issue where networkStatus wasn’

TL;DR

Apollo Client v4 migration is now easier with a new codemod (code modification tool) that automates many upgrade steps, including configuration and import updates.

Breaking

• uri, headers, and credentials must be moved to the link option and use a new HttpLink instance. (Configuration change)
• name and version are now part of clientAwareness. (Configuration change)
• typeDefs and fragmentMatcher options are removed; use localState with a LocalState instance instead. (Configuration change)
• disableNetworkFetches is renamed to prioritizeCacheValues. (Configuration change)
• Legacy import paths (e.g., @apollo/client/main.cjs) are updated to new entry points. (Import change)

New

No new features.

Fixes Worth Knowing

No fixes worth knowing.

Before You Upgrade

Run the clientSetup codemod step to automate most configuration changes before updating to Apollo Client v4.

TL;DR

Apollo Client is preparing for version 4.0 with deprecation warnings on older APIs, helping developers identify code that will require updates.

Breaking

• APIs used with client.query, client.mutate, and client.subscribe are deprecated (methods for fetching/modifying data).
• Using a standby fetch policy with client.query now triggers a warning (controls caching behavior).

Before You Upgrade

Review console warnings for deprecated API usage and plan migration paths to ensure compatibility with Apollo Client 4.0.