what stackpulse tracks
Apollo Client releases from GitHub
StackPulse watches Apollo Client release notes and keeps the original source link close to every summary.
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.
Fragment APIs now obtain fragment arguments and operation variables from the object passed to `from`, so callers can read fragments with the correct values without separately providing variables. `CombinedGraphQLErrors` and `CombinedProtocolErrors` now extend the standard `AggregateError`, requiring an ES2021 library target in TypeScript configuration.
Users of the fragment APIs gain automatic argument and variable resolution, while TypeScript users of the error classes need ES2021 library declarations.
If using TypeScript, ensure the configured `lib` includes `es2021` or `es2021.promise`.
This prerelease adds support for GraphQL 17 experimental fragment arguments. Fragment definitions can declare variables, and fragment spreads can provide values for those variables.
Applications that want to use experimental GraphQL 17 fragment arguments are affected.
To use fragment arguments, enable them with `enableExperimentalFragmentVariables()` before parsing any GraphQL documents.
Apollo Client 4.3.8 adds the `batchHybridRequests` option to `BatchHttpLink`. When enabled, it allows persisted and non-persisted queries to be combined in a shared batch.
Users of `BatchHttpLink` can opt into batching persisted and non-persisted queries together.
This patch release fixes an `AbortError` in a specific skipped-and-re-enabled `useBackgroundQuery`/`useReadQuery` lifecycle. It also fixes a React transition race in `useSuspenseQuery` so pending state remains active while chained `refetch` and `fetchMore` requests complete.
Applications using these React query hooks may be affected by the corrected error and pending-state behavior; no API changes are described.
Upgrade to 4.3.7 if your application encounters either of the described hook issues.
This patch release corrects `dataState` typing and behavior for no-cache queries, ensuring it is never `partial`. It also passes coerced scalar values to mutation-related callbacks and adds a warning about missing `possibleTypes` that could lead to data loss.
Apollo Client users of no-cache queries, mutation callbacks, or cache configurations with missing `possibleTypes` are affected.
This patch release fixes issues with custom scalar serialization and subscription handling. It ensures proper serialization of non-JSON-serializable custom scalar values and correct parsing of custom scalar fields in subscription results with 'no-cache' policy.
Developers using custom scalar values or subscriptions with the 'no-cache' policy are affected by fixes in this release.
Update to version 4.3.5 to benefit from bug fixes related to custom scalar serialization and subscription handling.
This patch release fixes several bugs related to `@defer` and `@stream` directives, including issues with field selection, error handling, and state management.
Developers using `@defer` and `@stream` directives in Apollo Client may encounter improved behavior and fewer errors.
Upgrade to version 4.3.4 to benefit from the bug fixes.
This patch release fixes a memory leak related to `isDeferredFragment` and `isStreamField` in Apollo Client.
Users experiencing memory leaks with deferred fragments or stream fields in Apollo Client are affected.
Update to version 4.3.3 to fix the memory leak.
This patch release fixes an unhandled AbortError promise rejection that occurred when unsubscribing from a multipart HTTP subscription.
Users utilizing multipart HTTP subscriptions may have experienced unhandled AbortError promise rejections when unsubscribing.
Update to version 4.3.2 to fix the unhandled AbortError promise rejection issue.
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 details view source on github->This release is a version bump to `rc` with no significant changes or new features.
view details 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.