ci: Version Packages (rc) - #11568
github-actions[bot] wants to merge 1 commit into
Conversation
|
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 |
a70203b to
5130646
Compare
|
View your CI Pipeline Execution ↗ for commit 5130646
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
size-limit report 📦
|
This branch has not been deployed
1 participant
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
#11751
8a13b15- Move off Solid's internalsharedConfigonto its public hydration API. The hydrating-mount checks readisHydrating(), the server cache stream writes throughgetHydrationWriter()gated onisHydratable()(so<NoHydration>is still respected), anduseQueryconsumes its streamed entry withtakeHydrationValue().sharedConfigis internal in Solid 2.0 and absent from the publishedsolid-jsdeclarations, so the previous imports no longer type-check.These APIs ship in Solid
2.0.0-rc.13, so thesolid-js/@solidjs/webpeer floor is now>=2.0.0-rc.13.#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
#11751
8a13b15- Move off Solid's internalsharedConfigonto its public hydration API. The hydrating-mount checks readisHydrating(), the server cache stream writes throughgetHydrationWriter()gated onisHydratable()(so<NoHydration>is still respected), anduseQueryconsumes its streamed entry withtakeHydrationValue().sharedConfigis internal in Solid 2.0 and absent from the publishedsolid-jsdeclarations, so the previous imports no longer type-check.These APIs ship in Solid
2.0.0-rc.13, so thesolid-js/@solidjs/webpeer floor is now>=2.0.0-rc.13.#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 [
8a13b15,cb63f07]:@tanstack/solid-query-persist-client@6.0.0-rc.5
Patch Changes
#11751
8a13b15- Move off Solid's internalsharedConfigonto its public hydration API. The hydrating-mount checks readisHydrating(), the server cache stream writes throughgetHydrationWriter()gated onisHydratable()(so<NoHydration>is still respected), anduseQueryconsumes its streamed entry withtakeHydrationValue().sharedConfigis internal in Solid 2.0 and absent from the publishedsolid-jsdeclarations, so the previous imports no longer type-check.These APIs ship in Solid
2.0.0-rc.13, so thesolid-js/@solidjs/webpeer floor is now>=2.0.0-rc.13.#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 [
8a13b15,cb63f07]: