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.10
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.
#11738b1a5eb8 Thanks @jerelmiller! - Fix an issue where rerendering useBackgroundQuery after the queryRef had been disposed, either via the auto dispose timeout or by unmounting useReadQuery, would cause the queryRef to be recreated potentially resulting in another network request.
#11738b1a5eb8 Thanks @jerelmiller! - Allow queryRefs to be disposed of synchronously when a suspense hook unmounts. This prevents some situations where using a suspense hook with the same query/variables as the disposed queryRef accidentally used the disposed queryRef rather than creating a new instance.
#11670cc5c03b Thanks @phryneas! - Bail out of executeSubSelectedArray calls if the array has 0 elements.
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.10) · Repo · Changelog
Release Notes
3.9.10
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
Version Packages (#11728)
Allow queryRefs to be disposed of synchronously (#11738)
chore: use delimiter in accorance with docs to handle strings with newlines per GHA docs (#11741)
chore(deps): update all dependencies - patch updates (#11739)
chore(deps): update cimg/node docker tag to v21.7.1 (#11740)
chore: configure git user directly in prerelease workflows (#11734)
chore(deps): bump express from 4.18.2 to 4.19.2 in /integration-tests (#11730)
chore: manually set bot user info in prerelease workflows
chore(deps): update all dependencies - patch updates (#11725)
fix: skip PR creation if no prerelease changesets exist (#11729)
bail out of `executeSubSelectedArray` calls for empty arrays (#11670)