We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
name
version specification
new version
@apollo/client
^3.7.14
3.9.8
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of @apollo/client for this test run.
#117068619bc7 Thanks @jerelmiller! - Fix issue in all suspense hooks where returning an empty array after calling fetchMore would rerender the component with an empty list.
#11694835d5f3 Thanks @phryneas! - Expose setErrorMessageHandler from @apollo/client/dev entrypoint.
#11689cb8ffe5 Thanks @jerelmiller! - Fix issue where passing a new from option to useFragment would first render with the previous value before rerendering with the correct value.
#11713642092c Thanks @jerelmiller! - Fix issue where setting a default watchQuery option in the ApolloClient constructor could break startTransition when used with suspense hooks.
We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of @apollo/client for this test run.
What changed?
✳️ @apollo/client (^3.7.14 → 3.9.8) · Repo · Changelog
Release Notes
3.9.8
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
Version Packages (#11695)
Fix issue where setting `defaultOptions` would sometimes break `startTransition` for suspense hooks (#11713)
Fix issue where an empty array returned from `fetchMore` would rerender with an empty list (#11706)
chore: skip prerelease versioning step if head commit contains version packages (#11703)
expose `setErrorMessageHandler` (#11694)
chore: remove NODE_VERSION from netlify.toml to unblock preview deploys (#11697)
chore(deps): update all devdependencies (#11691)
chore(deps): update all devdependencies (major) (#11637)
chore(deps): update jaywcjlove/github-action-package action to v2 (#11621)
chore(deps): update all dependencies - patch updates (#11690)
chore(deps): bump follow-redirects in /integration-tests (#11692)
Fix issue with `useFragment` where it returned wrong data when changing the `from` option (#11689)
fix: options links and remove @ link syntax (#11693)