ci: Version Packages (rc) - #11568
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch has not been deployed
This file contains hidden or 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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to solid-query-v6-pre, this PR will be updated.
solid-query-v6-preis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonsolid-query-v6-pre.Releases
@tanstack/solid-query@6.0.0-rc.5
Patch Changes
#11543
cb63f07- Follow Solid 2.0.0-rc.9. The packages build with@solidjs/babel-plugin(the Solid 2.0 compiler, matching the rc.9 runtime's delegated-event contract) and test under vite 8; thesolid-js/@solidjs/webpeer floor is2.0.0-rc.9.useQuery's setup-time snapshots (the meta projection's seed, the mount counts) now read the cache directly instead of through the hook's version signal. Under hydration, priming writes that signal during setup, and a write made during the hydration pass is held: a computation in the pass that reads it — tracked or not — is served the pre-write value and replays when the pass ends. For the hook's own derived nodes that replay is the takeover; for the computation instantiating the component (a<Loading>boundary's children) it was a remount, re-creating the hydrated component as a client render and letting cache writes reach the DOM while the stream was still open.@tanstack/solid-query-devtools@6.0.0-rc.5
Patch Changes
#11543
cb63f07- Follow Solid 2.0.0-rc.9. The packages build with@solidjs/babel-plugin(the Solid 2.0 compiler, matching the rc.9 runtime's delegated-event contract) and test under vite 8; thesolid-js/@solidjs/webpeer floor is2.0.0-rc.9.useQuery's setup-time snapshots (the meta projection's seed, the mount counts) now read the cache directly instead of through the hook's version signal. Under hydration, priming writes that signal during setup, and a write made during the hydration pass is held: a computation in the pass that reads it — tracked or not — is served the pre-write value and replays when the pass ends. For the hook's own derived nodes that replay is the takeover; for the computation instantiating the component (a<Loading>boundary's children) it was a remount, re-creating the hydrated component as a client render and letting cache writes reach the DOM while the stream was still open.Updated dependencies [
cb63f07]:@tanstack/solid-query-persist-client@6.0.0-rc.5
Patch Changes
#11543
cb63f07- Follow Solid 2.0.0-rc.9. The packages build with@solidjs/babel-plugin(the Solid 2.0 compiler, matching the rc.9 runtime's delegated-event contract) and test under vite 8; thesolid-js/@solidjs/webpeer floor is2.0.0-rc.9.useQuery's setup-time snapshots (the meta projection's seed, the mount counts) now read the cache directly instead of through the hook's version signal. Under hydration, priming writes that signal during setup, and a write made during the hydration pass is held: a computation in the pass that reads it — tracked or not — is served the pre-write value and replays when the pass ends. For the hook's own derived nodes that replay is the takeover; for the computation instantiating the component (a<Loading>boundary's children) it was a remount, re-creating the hydrated component as a client render and letting cache writes reach the DOM while the stream was still open.Updated dependencies [
cb63f07]: