what stackpulse tracks
Apollo Client releases from GitHub
StackPulse watches Apollo Client release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Fully-featured caching GraphQL client StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Apollo Client release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This alpha release introduces a change to field policies with the `scalar` option, ignoring `read` and `merge` functions when `scalar` is configured. It also fixes the `dataState` reporting for `@defer` fields when `returnPartialData` is true.
Developers using field policies with the `scalar` option may see warnings if they also provide `read` or `merge` functions.
Review field policies using the `scalar` option to ensure they do not include unnecessary `read` or `merge` functions.
This alpha release of Apollo Client focuses on fixing issues with `@defer` and `@stream` directives, particularly around pruning behavior and data state reporting. The changes make results more predictable by better matching network delivery patterns.
Developers using `@defer` and `@stream` directives with Apollo Client may need to adjust their code due to changes in pruning behavior and the addition of `label` arguments.
Review usage of `@defer` and `@stream` directives in your queries to ensure compatibility with the new pruning behavior and `label` argument requirements.
This patch release fixes type signatures in `DocumentationTypes` for better documentation display and adds a development-only warning for partial cache results when writing network results to the cache.
Developers using Apollo Client may encounter improved type signatures and new development warnings for cache-related issues.
Update to version 4.2.11 to benefit from improved type signatures and development warnings.
This patch release fixes several TypeScript type issues in Apollo Client, including incorrect widening of mutation return types, query variable types, and lazy query error policy types.
Developers using Apollo Client's TypeScript types for mutations, queries, or lazy queries may encounter more accurate type checking with this release.
Update to @apollo/client@4.2.10 to benefit from improved TypeScript type accuracy.
This release fixes bugs related to GraphQL variable default values and `@export` queries not reacting to cache updates.
Developers using GraphQL variables with default values or `@export` queries may be affected by these fixes.
Update to version 4.2.9 to resolve these issues.
This alpha release focuses on fixing issues related to cache data leakage in incremental queries and improving performance for cache diffs.
Developers using `network-only` incremental queries with `@defer` or `@stream` boundaries in Apollo Client may be affected by cache data leakage.
Update to this version to fix cache data leakage issues in incremental queries.
This release addresses a minor issue with the `connectToDevtools` function, preventing unnecessary `setTimeout` calls in environments where the devtools suggestion would not be shown.
Developers using Apollo Client in non-Chrome/Firefox environments or test environments may see improved test reliability.
Update to version 4.2.8 to avoid unnecessary `setTimeout` calls in `connectToDevtools`.
Fixes accuracy of `dataState` in complex streaming scenarios and addresses issues with field `read` functions and `@stream` queries.
Developers using `dataState` for incremental streaming queries may need to adjust their logic.
Review and update any logic relying on `dataState` for streaming status checks.
This release focuses on internal cleanup and removing unused code.
Developers relying on internal Apollo Client APIs may be affected if unused internals were removed.
File an issue if you notice any unexpected behavior after upgrading.
This release introduces a new GraphQL Codegen plugin for generating input object and type policy configurations to handle custom scalars in Apollo Client's `InMemoryCache`.
Developers using custom scalars in Apollo Client will benefit from automated configuration generation.
Integrate the new GraphQL Codegen plugin to simplify custom scalar handling in `InMemoryCache`.
This release includes performance improvements for cache writes and fixes an issue with relay multipart subscriptions.
Users utilizing @stream directives or relay multipart subscriptions will be affected by these changes.
Upgrade to version 4.2.6 if you are using the affected features.
This patch release fixes an issue where runtime files were accidentally omitted in the latest minor release.
Users who encountered missing runtime files in the previous minor release are affected.
Update to version 2.1.1 to resolve the missing files issue.
This release adds support for the latest major versions of GraphQL Codegen packages used as peer dependencies.
Developers using GraphQL Codegen packages with Apollo Client may need to update their dependencies.
Update GraphQL Codegen packages to their latest major versions if using this release.
This patch release exports previously internal types `KeyArgsFunction` and `RelayFieldPolicy` from public entrypoints.
This release introduces comprehensive support for custom scalar types in Apollo Client, including parsing, serialization, and cache integration. It provides helpers and configuration options for working with custom scalars throughout the GraphQL request cycle.
Developers working with custom scalar types in Apollo Client will benefit from enhanced type safety and serialization capabilities.
Review the new custom scalar documentation and consider implementing scalar type definitions for your GraphQL schema.
This patch release fixes an issue where `client.readFragment` and `client.readQuery` ignored the `optimistic` option when passed in the options object.
Developers using `client.readFragment` or `client.readQuery` with the `optimistic` option are affected.
Upgrade to version 4.2.4 to ensure the `optimistic` option is correctly handled.
This alpha release aligns cache generic constraints with `Cache.Implementation`, ensuring consistency across deprecated React mutation types and internal query-related types.
Developers using deprecated React mutation types or internal query-related types may need to review their code for alignment with cache API constraints.
Review and update any usage of deprecated React mutation types to ensure compatibility with the updated cache API constraints.
This release introduces the ability to define the cache type for the Apollo Client, allowing for stricter type enforcement when using custom cache implementations.
Developers using custom cache implementations with Apollo Client are affected.
Update your TypeScript definitions to specify the cache type using the `TypeOverrides` interface if needed.
This release adds support for `graphql` v17 as a valid peer dependency, ensuring compatibility with the latest version of the GraphQL library.
Users relying on `graphql` v17 will benefit from this update.
Update to this version if you are using `graphql` v17.
This patch release focuses on improving referential equality of masked data during refetch operations, ensuring consistency when results are deeply equal to previous ones.
Developers relying on Apollo Client's refetch behavior may notice improved consistency in referential equality.