New version of @apollo/client (3.8.6) broke the build #554
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 #561. |
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.6) · Repo · Changelog
Release Notes
3.8.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Version Packages (#11283)`cache.modify`: less strict types & dev runtime warnings (#11206)MockedProvider: default `connectToDevTools: false` (#11289)Don't crash if some (but not all) Error Codes are loaded (#11291)chore(deps): update all dependencies - patch updates (#11244)Update bug template instructionschore(deps): update stefanzweifel/git-auto-commit-action action to v5 (#11280)chore(deps): update cimg/node docker tag to v20.8.0 (#11279)chore(deps): update all devdependencies (#11278)SECOPS-2268: Add Gitleaks to CI (#11282)Fix auto dispose timeout that could cause components to suspend indefinitely (#11274)add `onQueryUpdated` to `useMutation` execution option docschore(deps): update dependency @microsoft/api-extractor to v7.38.0 (#11263)chore(deps): update cimg/node docker tag to v20.7.0 (#11246)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