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 patch release fixes a rerendering issue in `useLazyQuery` where components would not update with new variables until the network request completed when variables changed during an in-flight request.
Developers using `useLazyQuery` with in-flight requests and variable changes are affected.
Update to version 4.3.1 to fix the `useLazyQuery` rerendering issue.
This release introduces changes to how field policies and `inputObjects` handle arrays of scalars, requiring updates to configurations. It also improves the accuracy of `dataState` in streaming scenarios and adds a helper for creating `Scalar` instances from `GraphQLScalarType`.
Developers using field policies and `inputObjects` with arrays of scalars or scalar values that are arrays are affected by the breaking changes.
Review and update field policies and `inputObjects` configurations to use the new GraphQL list syntax for scalar lists.
This release introduces a new GraphQL Codegen plugin for Apollo Client that generates configuration objects for custom scalars, including input object and type policy configurations.
Developers using custom scalars in Apollo Client will benefit from the new code generation capabilities.
Update to version 2.2.0 to take advantage of the new custom scalar configuration generation features.
This release marks `skip` as deprecated in `useQuery` and `useSubscription` hooks, encouraging the use of `skipToken` instead.
Developers using `skip` in `useQuery` or `useSubscription` hooks are affected.
Replace `skip` with `skipToken` in `useQuery` and `useSubscription` hooks.
This release adds support for emitting GraphQL list syntax in `inputObjects` and `scalarTypePolicies` within the `@apollo/client-graphql-codegen/custom-scalars` plugin.
Developers using the `@apollo/client-graphql-codegen/custom-scalars` plugin for input objects and scalar type policies are affected.
Update to this version if you need GraphQL list syntax support in custom scalars.
This release introduces changes to how field policies and `inputObjects` handle scalar arrays, requiring explicit list syntax for scalar fields. It also removes the optional modifier from the `variables` property in mutation update functions.
Developers using field policies or `inputObjects` with scalar arrays are affected by the breaking changes.
Update field policies and `inputObjects` to use the new list syntax for scalar arrays.
This release is a version bump to `rc` with no significant changes or new features.
view source on github->This release is a version bump to `rc` with no significant changes or new features.
view source on github->This alpha release introduces type-safe subscription skipping with `skipToken` and replaces a custom type utility with TypeScript's native `NoInfer`.
Developers using `useSubscription` with required variables will benefit from improved type safety.
Update usage of `useSubscription` to use `skipToken` for better type safety with required variables.
This release raises the minimum supported TypeScript version to 5.9.x and introduces the ability to enforce stricter type policies for fragment APIs through the new `FromOptionValue` key on the `TypeOverrides` interface.
Users on TypeScript versions below 5.9.x will need to upgrade, and developers can now enforce stricter type policies for fragment APIs.
Upgrade TypeScript to version 5.9.x if using an older version.
This alpha release introduces type overrides for GraphQL Codegen to better handle `@defer` operations when data loading is complete.
Developers using GraphQL Codegen with @defer operations may be affected.
This alpha release introduces a minor change to improve the parsing of scalar fields for `no-cache` queries.
Developers using `no-cache` queries with scalar fields may be affected.
Update to this version to ensure proper parsing of scalar fields in `no-cache` queries.
Fixes an issue where multi-byte UTF-8 characters could be corrupted when split across multipart response chunks in GraphQL responses.
Users processing GraphQL responses with multi-byte UTF-8 characters may be affected by character corruption.
Upgrade to @apollo/client@4.2.12 if you process GraphQL responses containing multi-byte UTF-8 characters.
This alpha release introduces a development warning for query data overwrites and fixes cache feud issues by ensuring network results are written to cache before delivery. It also prevents repeated refetches in cache-feud scenarios.
Developers using Apollo Client with queries that may overwrite each other's data or have cache feuds are affected.
Review queries that may overwrite each other's data and consider adding key fields or merge functions to field policies.
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.