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.8.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.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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.8.9) · Repo · Changelog
Release Notes
3.8.9
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
Version Packages (#11469)
fix: behavior of delay: Infinity in a mock response (#11472)
Remove unnecessary check from parseAndCheckHttpResponse (#11470)
Avoid excessive `cache.watch` / unsubscribe on every render in `useFragment` (#11464)
chore(deps): update all devdependencies (#11467)
remove references to "dom" ts lib (#11449)
Bump @babel/core and @babel/traverse from 7.16.7 to 7.23.7 (#11457)
chore(deps): update cimg/node docker tag to v21.5.0 (#11468)
chore(deps): update all dependencies - patch updates (#11466)
docs: fix typos and code examples (#11455)
fix `reportErrors` link example in docs (#11450)
chore(deps): update all devdependencies (#11454)
chore(deps): update all dependencies - patch updates (#11453)
chore(deps): update dependency ts-morph to v21 (#11407)
Update ROADMAP.md (#11441)
chore(deps): update all dependencies - patch updates (#11432)
Remove docs changeset to avoid patch change (#11436)
docs: queries > update link to suspense doc (#11269)
chore(deps): update dependency eslint to v8.56.0 (#11433)
chore(deps): update all dependencies - patch updates (#11421)
Bump @adobe/css-tools from 4.3.1 to 4.3.2 (#11401)
chore(deps): update all devdependencies (#11406)
chore(deps): update cimg/node docker tag to v21.4.0 (#11422)
chore(deps): update actions/stale action to v9 (#11423)
Update react-native.md - Adds react native devtool supported by flipper (#11364)
Update netlify.toml
Copy and use ApiDoc components from docs repo (#11416)
Update ROADMAP.md
chore(deps): update all dependencies - patch updates (#11405)
Add more documentation on how to use the `removeTypenameFromVariables` link to reduce confusion (#11395)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands