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.
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.
This release fixes an issue with `useLazyQuery` where changes to the `pollInterval` were not being applied between renders.
Developers using `useLazyQuery` with dynamic `pollInterval` values are affected.
Update to version 4.2.1 to ensure `pollInterval` changes are applied correctly.