Skip to content

ci: Version Packages (rc) - #11568

Open
github-actions[bot] wants to merge 1 commit into
solid-query-v6-prefrom
changeset-release/solid-query-v6-pre
Open

github-actions[bot] wants to merge 1 commit into
solid-query-v6-prefrom
changeset-release/solid-query-v6-pre

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

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-pre is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on solid-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; the solid-js / @solidjs/web peer floor is 2.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; the solid-js / @solidjs/web peer floor is 2.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@6.0.0-rc.5

@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; the solid-js / @solidjs/web peer floor is 2.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@6.0.0-rc.5

@coderabbitai

coderabbitai Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: a6d46111-08bc-4bdc-84fa-a635c0e1b653

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants