Release 3.6.0 #9067
Merged
Release 3.6.0 #9067
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
…e-3.6. Merging into `release-3.6` before merging into `main` so we can do some additional testing with beta releases.
* add use-sync-external-store * Initial work on using useSyncExternalStore * fix useLazyQuery tests * update use-sync-external-store version * update timings to useMutation tests * change the timing in a Mutation component test which changed for no ostensible reason * fix the hoc tests agane * bring back the bad boy code block by popular demand * update useSyncExternalStore to handle ssr * use published useSyncExternalStore types * update dependencies and add beta to react peer range
The specific failure is an integrity hash mismatch:
5:44:05 PM: npm ERR! code EINTEGRITY
5:44:05 PM: npm ERR! sha512-yXbYeFy+jUuYd3/CDcg2NkIYE991XYX/bje7LmjJigUciaeO1JR4XxXgCIV1/Zc/dRuFEyw1L0pbA+qynJkW5Q==
integrity checksum failed when using sha512: wanted sha512-yXbYeFy+jUuYd3/CDcg2NkIYE991XYX/bje7LmjJigUciaeO1JR4XxXgCIV1/Zc/dRuFEyw1L0pbA+qynJkW5Q==
but got sha512-U1riIR+lBSNi3IbxtaHOIKdH8sLFv3NYfNv8sg7ZsNhcfl4HF2++BfqqrNAxoCLQW1iiylOj76ecnaUxz+z9yw==
Example failed deployment (or see any of the recent failures in #9067):
https://app.netlify.com/sites/apollo-client-docs/deploys/619d6dc222deda1694aa37a6
Although the error doesn't mention the package name, I was able to grep
for the expected hash in package-lock.json, which pointed to the `acorn`
package. As you can tell from this commit's changes, the actual hash
displayed above (ending in +z9yw==) happens to be the hash for
[email protected], whereas the expected hash was that of [email protected].
TODO Make the 5000 constant configurable.
…-frame Fix extra `useQuery` result frames (as demonstrated by #9508).
|
Now that we've released the first release candidate (RC), This release includes support for React 18 and many other improvements. See the |
I noticed while updating an internal application that sometimes the observableQuery.options.query document could be !== watch.query, so there were cases where the watched query had already been updated and was even included in updatedQuerySet, but we (harmlessly/needlessly) call reobserveCacheFirst again in the finally block, just because options.query !== watch.query. This commit reinforces observableQuery.options.query as the source of truth for the transformed query document, while also providing the same object as observableQuery.query, a TypedDocumentNode<TData, TVariables> which should always be === observableQuery.queryInfo.document.
We will remove the tag once branch release-3.6 is merged into main.
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Like the Release 3.5.0 PR, this PR will serve to collect significant new features, deprecation warnings, and minor breaking changes that we intend to release in
@apollo/[email protected].If you want to test these changes, run
in your application, where the
nin-beta.ncomes from the most recent commit message likeUntil v3.6.0 is released, we can continue merging smaller changes into
mainand releasing them, without worrying about larger changes on therelease-3.6branch.TODO for the 3.6 release
useQueryfor finer-grainedoptionscontrol #9223nextFetchPolicyfunctions #9222useBackgroundQueryanduseFragmentAPI and usage docs