New version of @apollo/client (3.8.9) broke the build #575
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Closed in favor of #579. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.tomlCopy and use ApiDoc components from docs repo (#11416)Update ROADMAP.mdchore(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