ci: Version Packages (rc) - #11518
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 |
e757e57 to
57b3e04
Compare
|
View your CI Pipeline Execution ↗ for commit 3388445
☁️ 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 📦
|
57b3e04 to
3388445
Compare
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.4
Patch Changes
#11449
fd3f1c9- fix: finish server renders that read a disabled query. Reading.datafrom auseQuerywithenabled: falseand nothing cached stopped an SSR render fromever completing — no bytes at all, since the data node was handed a promise
that can never settle. That parking is intended client behaviour (the reader
suspends into the nearest
<Loading>until an enable, refetch or cache writerevives the compute), but on the server there is no later: the render has to
finish, and nothing will enable the query or write the cache before it does.
A disabled query with no data now commits its idle state on the server, which
is the contract the scalar metadata channel already honoured and the state the
client hydrates to. Client behaviour is unchanged.
#11517
09f2666- The single-flight consumer appliesX-Revalidateon responses that carried no slice for the query cache (no collector registered, a redirect leaving the app) instead of throwing on the missing payload — nothing is covered, so the declared scope is swept in full. The header's three states are three scopes: absent leaves the cache alone, an empty declaration (revalidate: []) sweeps nothing, and the reserved key*(revalidate: '*') invalidates every query the payload did not cover.#11360
0e6ff54- fix: stop a mounted observer from re-creating and refetching a removedquery. The read layer bumps its per-hook version signal on every cache
event for its hash,
removedincluded, and the recompute that followedcalled
queryCache.build(), which put the entry the caller had justdeleted straight back. The resurrection was not passive: the rebuilt
entry also re-pointed the still-live observer, whose mount-fetch policy
then refetched and repopulated the key, so
removeQueries()(andclear()) could not be made to stick while any hook observed the key.query()now reuses the entry it last read when the cache no longerholds that hash, and only builds when the hash is genuinely new, so a
removal leaves the cache empty and fires no fetch, while the mounted
reader holds its last value until options change or a real entry returns
through
setQueryData, a refetch or a later mount. This is the behaviorof the other adapters, and of solid-query at 6.0.0-rc.0.
@tanstack/solid-query-devtools@6.0.0-rc.4
Patch Changes
fd3f1c9,09f2666,0e6ff54]:@tanstack/solid-query-persist-client@6.0.0-rc.4
Patch Changes
fd3f1c9,09f2666,0e6ff54]: