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.11.9
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.
#12110a3f95c6 Thanks @jerelmiller! - Fix an issue where errors returned from a fetchMore call from a Suspense hook would cause a Suspense boundary to be shown indefinitely.
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.11.9) · Repo · Changelog
Release Notes
3.11.9
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 26 commits:
Version Packages (#12111)
`ObservableStream` use `ReadableStream` instead of iterator (#12112)
Fix Suspense boundary indefinitely shown when fetchMore returns error (#12110)
Update ROADMAP.md
Update ROADMAP.md
use external `@testing-library/react-render-stream` (#12090)
Merge pull request #12095 from apollographql/main-docs-replatform
Remove docs-publish workflow
Merge branch 'main' into main-docs-replatform
2024-10-07 Roadmap update
Merge branch 'main' into main-docs-replatform
Merge pull request #12084 from apollographql/ms/docs-cleanup
Cleanup
Remove empty file
Remove Summit callouts
Make it clearer that fetchMore variables merge is a shallow merge in docs (#12080)
Update api extractor to latest (#12077)
Merge pull request #12070 from apollographql/renovate/cimg-node-22.x
chore(deps): update cimg/node docker tag to v22.9.0
Update ROADMAP.md
Update ROADMAP.md
chore(deps): update slackapi/slack-github-action action to v1.27.0 (#12047)
chore(deps): update cimg/node docker tag to v22.8.0 (#12031)
add pkg.pr.new to publish pr releases (#12061)
docs(community-links): add printer link (#12060)
Update ROADMAP.md