Overview - Query

query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
solid-query-v6-pre
082a4ec3 ci: Version Packages (beta) (#11099) ci: changeset release (beta) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-query-v6-pre
dafe8066 chore: upgrade to solid v2 beta 21 (#11092) * chore: upgrade to solid v2 beta 21 - Bump solid-js 2.0.0-beta.15 -> 2.0.0-beta.21, vite-plugin-solid 3.0.0-next.5 -> 3.0.0-next.14, plus matching @solidjs/web and babel-preset-solid bumps across the solid packages, solid-vite integration, and solid examples - Add minimumReleaseAgeExclude for the Solid ecosystem packages so the freshly published betas install under the 24h release-age policy - Reset the reactive scheduler halt in solid-query-devtools test setup: the new betas permanently halt the scheduler when an error escapes all boundaries, which poisoned tests that follow intentional-throw tests in the same file Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore: add changeset for Solid beta 21 --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-query-v6-pre
4959c873 fix(release): remove unnecessary tag assignment for prerelease branches
by Birk Skyum
Succeeded
solid-query-v6-pre
89d51b9c ci: Version Packages (beta) (#10981) ci: changeset release (beta) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-query-v6-pre
89d51b9c ci: Version Packages (beta) (#10981) ci: changeset release (beta) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-query-v6-pre
b970e5f8 chore(changeset): split solid-query into its own fixed group (#10983) solid-query is tracking the Solid 1 -> 2 breaking jump and is on a v6 pre-release line, while query-core and the other adapters remain on v5. Because all of react/core/vue/solid shared a single `fixed` group, the solid v6 beta changesets dragged every package in that group to 6.0.0-beta.5, even though no changeset targets them. Carve the three solid packages into their own `fixed` group so they can version independently on the v6 line. This mirrors the existing svelte group (already on 6.x while core stays on 5.x) and matches the agreed policy that version-syncing should happen across majors only -- no v6 beta of unaffected adapters. Verified with `changeset version` (prerelease mode): only solid-query, solid-query-devtools and solid-query-persist-client bump to 6.0.0-beta.5; query-core/react-query/vue-query stay at 5.101.0 and svelte-query stays at 6.1.34. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
solid-query-v6-pre
18d1948c chore: upgrade to solid v2 beta 15 (#10616) * chore: upgrade to solid v2 beta 10 * chore: upgrade to solid v2 beta 14 * chore: upgrade to solid v2 beta 15 * fix(solid-query): fix tests and source errors for solid v2 beta 15 * fix(nx): cache dist-cjs output for lit-query build * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Brenley Dueck
Succeeded
solid-query-v6-pre
724706af fix(solid-query): render resolved SSR value for deferred queries (#10957) * fix(solid-query): render resolved SSR value for deferred queries When a deferred query (prefetched but not awaited) is read inside a Loading/Suspense boundary, SSR rendered the stale loading state and the client hydrated into a frozen subtree ("unclaimed server-rendered node"). On the server the result proxy forced a `queryResource()` read to create the Suspense dependency, but returned property values from the `state` store. When the boundary suspends and re-renders after the query settles, `state` is never synced (the server subscriber resolves the resource Promise but does not write the store), so the retry render read stale loading values. The serialized resource, however, held the resolved result — so server DOM (loading) and the hydrated resource (success) disagreed, breaking hydration. Read property values from the resolved resource instead of `state`, so the streamed SSR HTML matches the serialized resource the client hydrates against. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(solid-query): remove unnecessary truthy check on resolved resource --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-query-v6-pre
f74255f3 fix(solid-query-devtools): use onSettled for mount/unmount and flush() in tests The Solid 2.0 migration mounted the devtools instance via queueMicrotask and forwarded props via deferred createEffect, so the synchronous test assertions (forwarding + unmount-on-cleanup) never saw the calls. - Replace the queueMicrotask mount + onCleanup unmount with onSettled, the 2.0 lifecycle primitive that replaces onMount + onCleanup (setup runs after the first stable render, returned cleanup runs on disposal). devtools.mount renders a nested Solid app (creating reactive primitives), which is forbidden inside an owned scope, so escape the owner with runWithOwner(null). - In the tests, call flush() after render() (and before unmount) to run the deferred effects and onSettled synchronously, matching the existing synchronous assertions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Brenley Dueck