Overview - Query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
solid-query-v6-pre
c6002fb5 chore: upgrade to solid v2 beta 29 (#11133) - Bump solid-js 2.0.0-beta.21 -> 2.0.0-beta.29, vite-plugin-solid 3.0.0-next.14 -> 3.0.0-next.21, plus matching @solidjs/web, babel-preset-solid, and @solidjs/signals bumps across the solid packages, solid-vite integration, and solid examples - No source changes were needed; the solid-query, solid-query-devtools, and solid-query-persist-client suites pass unchanged (357 tests, no type errors) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11133
f95a1c2b chore: upgrade to solid v2 beta 29 - Bump solid-js 2.0.0-beta.21 -> 2.0.0-beta.29, vite-plugin-solid 3.0.0-next.14 -> 3.0.0-next.21, plus matching @solidjs/web, babel-preset-solid, and @solidjs/signals bumps across the solid packages, solid-vite integration, and solid examples - No source changes were needed; the solid-query, solid-query-devtools, and solid-query-persist-client suites pass unchanged (357 tests, no type errors) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
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
11092
09094cfe chore: add changeset for Solid beta 21
by Brenley Dueck
Succeeded
11092
741e1bc5 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>
by Brenley Dueck
Succeeded
11017
b0b0726f fix(solid-query): restore observer subscription after SSR hydration Solid restores useBaseQuery's resource memo from the serialized server value during hydration, so the compute's wiring never runs on the client: - sync-serialized values (query settled on the server before the shell flushed) skip the compute entirely - async-serialized values (query streamed as a pending promise) replay it under a constructor-less MockPromise stub that silently drops the Promise executor's side effects Either way the QueryObserver subscription that lives inside the resource Promise executor is never established: the component renders the hydrated snapshot correctly but is permanently inert — setQueryData, refetches and invalidations notify zero subscribers. Recovery now runs on unowned setTimeout polls after hydration has fully completed: 1. recoverAfterHydration() waits for sharedConfig.done (boundary hydration is asynchronous; subscribing earlier delivers an immediate updateResult() notification whose store write re-renders the component mid-walk and breaks DOM claiming), then re-establishes the observer subscription with a guarded store catch-up that only writes when the result actually changed. 2. finishPendingRecovery() (streamed-pending queries only) waits for the hydrated resource to settle, seeds the cache from the snapshot's hydrationData when nothing fresher exists, then refreshes the resource so the compute re-runs under the native Promise and performs the full normal wiring. Owned computations are deliberately avoided in both stages: a client-only createRenderEffect created during the hydration walk shifts the hydration key of every subsequent computation in the component, so JSX claiming fails ("unclaimed server-rendered node" warnings, duplicated inert DOM).
by Brenley Dueck
Succeeded
10989
2c4e7d93 fix(release): avoid pre dist tag for prereleases
by Brenley Dueck
Succeeded
main
e6ad3fc4 fix(release): avoid pre dist tag for prereleases (#10986)
by Brenley Dueck
Failed
10986
7d200f9c fix(release): avoid pre dist tag for prereleases
by Brenley Dueck
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
10616
f1c9baf8 chore: upgrade to solid v2 beta 15
by Brenley Dueck
Canceled
10616
f1c9baf8 chore: upgrade to solid v2 beta 15
by Brenley Dueck
Failed
10616
f1c9baf8 chore: upgrade to solid v2 beta 15
by Brenley Dueck
Failed
10616
f1c9baf8 chore: upgrade to solid v2 beta 15
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
10957
a42e54f6 Merge branch 'solid-query-v6-pre' into fix/solid-query-ssr-deferred-hydration
by Brenley Dueck
Failed
10957
a42e54f6 Merge branch 'solid-query-v6-pre' into fix/solid-query-ssr-deferred-hydration
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
Succeeded
10953
558c1447 WIP: Solid query main merge
by Brenley Dueck
Failed
10953
83c11cb9 WIP: Solid query main merge
by Brenley Dueck