Overview - Router

routerWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

router

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

routerWorkspace

Average execution time

11m 20s

98 CI pipeline executions

Computation time saved

13d 6h

Cache hit rate

31%

Time to Green

1h 32m

Was 2h 43m, improved by 44%

Succeeded
solid-router-v2-pre
0dc3a9e3 chore(solid): bump to solid-js 2.0.0-rc.9 and @solidjs/vite-plugin 3.0.0-next.44 (#8467) rc.9 renamed the id-based server-function URL helpers to serverFunctionActionUrl / parseServerFunctionActionUrl (solidjs/solid#3440). @rsbuild/plugin-solid 2.0.0-rc.0 pins the rc.6 compiler, whose delegated-event key the rc.9 runtime no longer reads, so its compiler is overridden to rc.9. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-router-v2-pre
4fbd65c5 ci: Version Packages (rc) (#8360) ci: changeset release (rc) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-router-v2-pre
2946ffff chore(solid): bump @tanstack/solid-query to 6.0.0-rc.4 (#8465) * chore(solid): bump @tanstack/solid-query to 6.0.0-rc.4 Catalog entry and the solid-router-ssr-query devDependency move from rc.1 to rc.4. rc.2 gave QueryClientProvider its own "sq" single-flight consumer and dehydrateSettled, rc.3 sweeps X-Revalidate keys, rc.4 fixes disabled-query SSR renders and removed-query resurrection. Peer range now wants solid-js >=2.0.0-rc.6; the branch is on rc.8. @tanstack/solid-query-devtools stays on rc.1, now pinned exactly: its rc.2-rc.4 builds import patchableRaw, registerPatch, registerRowOps and registerSlotPatch from solid-js, which 2.0.0-rc.8 does not export, so every app rendering the devtools fails to bundle. A caret on rc.1 would let pnpm re-resolve to rc.4 (its peer range admits solid-query rc.4), which is exactly what happened on the first pass. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * test(solid-start): expect solid-query's flight source on the single-flight request solid-query 6.0.0-rc.2+ subscribes QueryClientProvider under its own "sq" single-flight source, so the mutation's request header now lists it next to the router's "tsr". The response still folds only "tsr": this app registers no "sq" collector. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Brenley Dueck <brenleydueck@Brenleys-Mac-mini.local> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-router-v2-pre
bf7f924b feat(solid-router): consume server-function response metadata (#8461) * feat(solid-router): consume server-function response metadata RouterContextProvider registers the router as the unnamed single-flight consumer of Solid's server-function transport on the client, so the response helpers a mutation returns take effect without the caller wrapping the call. redirect(): the carrier delivers an absolute target, so the soft/hard split is a real origin comparison — same-origin navigates under the router with replace (the destination takes the submission's place in history), any other origin goes through navigate({ href }) so the document reload still passes the protocol allowlist and blockers. Route data: any declaration of a write — redirect(), reload({ revalidate }), respond(value, { revalidate }), the reserved '*' — reloads through router.invalidate(). An empty declaration (revalidate: []) is honored as nothing to reload. Navigation runs before invalidation so a redirect costs one load: invalidate's load already reads the destination as the latest location, and the adapter's follow-up load adopts those loader flights rather than restarting them, so the destination commits with shared layouts reloaded and the abandoned page never reruns its own loaders (the other order does). X-Revalidate keys name entries in caches the router does not own and are left to those caches' consumers. Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com> * test(solid-start): expect both flight sources on the single-flight request The router now registers as the unnamed flight-data consumer, so the transport advertises it on the request leg under the reserved id "true" next to Start's "tsr". The response still folds only "tsr". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Brenley Dueck <brenleydueck@Brenleys-Mac-mini.local> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
by Ryan Carniato
Succeeded
solid-router-v2-pre
d46b8ee0 fix(solid-router): preserve caller roles on enabled links (#8109)
by Fnine59
Succeeded
solid-router-v2-pre
465d15a1 fix(solid-router): don't install intent-preload listeners when preloading is off (#8179) * fix(solid-router): don't install intent-preload listeners when preloading is off useLinkProps handed out onFocus/onBlur/onMouseEnter/onMouseLeave (plus the mouseover/mouseout/touchstart trio) unconditionally, with the `preload() !== 'intent'` check inside each handler. Solid does not delegate mouseenter, mouseleave, focus or blur, so every anchor installed four real listeners whose only job was to bail out — four per row on list views. Resolve those props through getters instead: with intent preloading off the property yields the consumer's own handler (or undefined, which spread()/assign() treats as removal), so nothing is attached. The getters stay reactive, so switching preload back to 'intent' re-runs the consuming spread and attaches the composed handler. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * ci: apply automated fixes --------- Co-authored-by: russelgal <intensivelider@gmail.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Russell
Succeeded
solid-router-v2-pre
9de3573f feat(solid-router): declare navigations to Solid's observe tier (#8399) On Solid's dev and observe builds the match publish inside startTransition is wrapped in OBSERVE.attribution.withOrigin: the ref names the destination route (fullPath, params, to/from pathnames) and dates from the history change that started the load, so the record spans the loader wait even though the publish comes after it. The pending offer, the initial load and same-location reloads are published undeclared. Production is unchanged (OBSERVE is undefined). Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato
Succeeded
solid-router-v2-pre
8981eb78 chore(solid): bump to solid-js 2.0.0-rc.8 and @solidjs/vite-plugin 3.0.0-next.43 (#8348) * chore(solid): bump to solid-js 2.0.0-rc.7 and @solidjs/vite-plugin 3.0.0-next.42 Moves solid-js/@solidjs/web to ^2.0.0-rc.7, @solidjs/vite-plugin to ^3.0.0-next.42, @rsbuild/plugin-solid to ^2.0.0-rc.0 and the webpack example's @solidjs/babel-plugin to ^2.0.0-rc.7 across the monorepo. @tanstack/solid-start now normalizes Request subclasses (srvx's Node adapter) into native Requests before Solid's server-function handler sees them: rc.7 buffers every POST body via `new Request(request, { body })`, which undici only accepts for its own instances, so every POST answered 400 under srvx. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * chore(solid): bump to solid-js 2.0.0-rc.8 and @solidjs/vite-plugin 3.0.0-next.43 Moves solid-js/@solidjs/web to ^2.0.0-rc.8, @solidjs/vite-plugin to ^3.0.0-next.43 and the webpack example's @solidjs/babel-plugin to ^2.0.0-rc.8. rc.8 is ESM-only with engines.node >= 22.12. rc.8 ships the upstream fix for the buffered server-function request (a71e42e), so the srvx Request normalization from the rc.7 commit is dropped again. @solidjs/vite-plugin next.43 honors the host's resolve.noExternal patterns when externalizing the dependencies of Solid consumers (solidjs/solid-vite-plugin#360), which is what broke `vite dev` with "Package import specifier '#tanstack-router-entry' is not defined" on next.41/42. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-router-v2-pre
a35eeb50 ci: Version Packages (rc) (#8290) ci: changeset release (rc) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-router-v2-pre
a09b50ca fix(solid-router): respect server flag during development SSR (#8254)
by Brenley Dueck
Succeeded
solid-router-v2-pre
79e938f2 ci: Version Packages (rc) (#8239) ci: changeset release (rc) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-router-v2-pre
cc25e822 fix(solid-router): remove router-owned Loading boundaries, ack startTransition at settlement (#8236)
by Ryan Carniato
Succeeded
solid-router-v2-pre
8ca0beac ci: Version Packages (rc) (#8219) ci: changeset release (rc) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-router-v2-pre
c753d0a2 fix(examples): migrate remaining legacy createEffect calls to Solid 2.0 two-phase signature (#8223) fix(examples): migrate remaining React-style createEffect calls to Solid 2.0 two-phase signature Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato
Succeeded
solid-router-v2-pre
b445b892 feat(solid-router): native SSR match transfer, hydration-claiming boot, provider-owned dispatch (#8213) * refactor(solid): retire solid-router-ssr-query — Solid's native channels carry the Router + Query pairing solid-query v6's QueryClientProvider serializes the request's cache into Solid's hydration registry during SSR and primes the client cache from it, so running the ssr-query transport alongside it ships every query payload twice. The package's two runtime conveniences are each a few lines of userland composition on public APIs: the provider wrap via the router's Wrap option, and cache-driven redirect() errors handed to router.navigate from the caches' config.onError. Converts the three Solid Start e2e apps to the composition (all suites green, including the redirect-from-query tests) and marks the package deprecated for the v2 line. Co-authored-by: Cursor <cursoragent@cursor.com> * chore: changeset for the solid-router-ssr-query deprecation notice Co-authored-by: Cursor <cursoragent@cursor.com> * feat(solid-start): named single-flight source for router flight data Solid's single-flight channel is becoming multi-source (solidjs/solid 653dd41e): mutation responses carry a keyed envelope of per-cache slices, each routed to the consumer subscribed under its source id. Today Start claims the single unnamed slot on both halves, which means any other cache wanting mutation-response data (e.g. solid-query, whose provider subscribes under "sq" in TanStack/query#11326) displaces the router's — whichever registers last wins, silently. The router's flight data now rides its own source id ("tsr"): the server collector registers additively with registerFlightDataSource and the client subscribes its consumer under the same id, so router loader/match state and other caches' slices coexist on one round trip. A user-supplied collectFlightData hook keeps the unnamed slot to itself, adding data alongside the router's instead of displacing it. Both halves feature-detect the protocol on the installed @solidjs/web (it ships in the release after 2.0.0-rc.4) and fall back to the exact previous unnamed-slot behavior on older versions; since client and server resolve the same install, the halves cannot disagree. Co-authored-by: Cursor <cursoragent@cursor.com> * feat(solid-router): loadFlightTarget, the cache-agnostic single-flight trigger The router's half of flight collection as a public primitive: derive the flight request for the mutation's target, run the matched routes' data functions, hand the loaded router to the caller's collect() — any cache (the router's own state, a query client) composes its extraction on top. Start's collector now consumes it; errors are contained per Solid Router's collector convention (flight data is an optimization, never a mutation error). Co-authored-by: Cursor <cursoragent@cursor.com> * refactor(solid-start): require named flight sources, drop the pre-rc.5 fallback @solidjs/web 2.0.0-rc.5 ships the multi-source single-flight protocol, so the feature detection and cast shims bridging unreleased types come out: the client subscribes directly under SOLID_START_FLIGHT_SOURCE, the server registers its collector via registerFlightDataSource unconditionally (the unnamed collectFlightData slot now always belongs to the user), and the @solidjs/web peer floor moves to rc.5. Co-authored-by: Cursor <cursoragent@cursor.com> * test(e2e): expect the named single-flight source header With the pre-rc.5 fallback stripped, the client advertises its named source and the server echoes what it folded: X-Single-Flight is "tsr" on both sides, not the legacy "true". Co-authored-by: Cursor <cursoragent@cursor.com> * chore(solid): bump solid-js, @solidjs/web, @solidjs/signals to 2.0.0-rc.6 Repo-wide (packages, examples, e2e apps, benchmarks) — a scoped bump leaves the workspace mixed, and examples/benchmarks then build workspace solid-start dists (which import registerFlightDataSource, rc.5+) against their own @solidjs/web rc.4 resolution. rc.6 ships the named flight-data source API this branch requires plus the settle-walk fix that unblocks the Solid Query pairing. @tanstack/solid-start's peer floor moves to rc.6. The SSR bench helpers move onto rc.6's wire shape: scripted callers use the data address (`<endpoint>/data/<id>`) — the bare address now answers document traffic with the no-JS convention. Co-authored-by: Cursor <cursoragent@cursor.com> * spike(solid-router): Phase 1 — registry match transfer + hydration-claiming boot Proves the RFC's Phase 1 claims on the external-SSR harness, against published core (web 2.0.0-rc.5): - Server render serializes each match's loaderData/status into Solid's hydration registry, content-addressed (`tsr:<matchId>`), the identical mechanism solid-query v6 ships queries through — no `__TSR_SSR__` script channel. - The client boot matches synchronously, primes match state from the registry (populated at document parse), and commits — no `router.load()` before hydrate, loaders do not re-run (0 client runs), hydration claims the server DOM identically, and post-hydration navigation with an unresolved chunk still shows pending UI and settles under its boundary. Spike-level notes: the commit must happen before hydrate() (store writes inside the hydration render are owned-scope writes), the transfer covers settled matches (promise-valued entries for pending loaders are the same serialize call, next step), and the serialization-context guard keys on `ctx.serialize` presence (`ctx.async` is not set under this web version's renderToString). Co-authored-by: Cursor <cursoragent@cursor.com> * feat(solid-router): native SSR match transfer + hydration-claiming boot (Phase 1) Grows the spike into the adapter. RouterProvider serializes each settled match's state (loaderData, status, error, notFound, beforeLoadContext, ssr) into Solid's hydration registry during server render — content-addressed (`tsr:<matchId>`), the same channel solid-query v6 ships queries through, no `__TSR_SSR__` script injection. The Router constructor owns the client half: when the registry holds entries for the synchronously matched routes, it primes and commits match state at creation — always outside a render, after the document (and therefore the entries) parsed, before hydrate(). No load pass before hydration, no loader re-runs; route chunks resolve at the read point under the boundaries the server rendered. Both halves are inert outside the bare pairing: the server skips when `router.serverSsr` marks the Start contract, and the boot falls through on the first missing entry (SPA pages, Start's own channel). Placement is load-bearing: committing inside the hydration render — even with writes moved off the owner — leaves the claiming walk's registry bookkeeping desynced (nodes reuse correctly but audit as unclaimed). Router creation is the client's natural pre-render moment, and the harness A/B proved it clean. Validated: external-SSR harness green end to end (registry primed, zero client loader runs, identical DOM claimed, pending UI on post-hydration nav), solid-router unit suite 865 tests green, and all 37 Solid Start e2e tests green against the rc.6-candidate core (workspace tarballs) with the named-source strips in place. The harness now contains zero transfer code. Pending matches are skipped, not deferred — promise-valued entries (streaming SSR) are the next increment. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(rfc): record Phase 1 landed state — transfer + boot in the adapter, boundary bullet corrected Co-authored-by: Cursor <cursoragent@cursor.com> * feat(solid-router): provider-owned server dispatch + streamed loaderData RouterProvider now owns router.load() on the server, parking the render on it through an async memo — no more explicit await router.load() in entries; blocking semantics ride Solid's async SSR. The bare-pairing harness moves to renderToStream and proves deferred loaderData promises stream natively (fallback in the shell chunk, value in a later chunk, settled through hydration without <Await>). Co-authored-by: Cursor <cursoragent@cursor.com> * chore: changeset for Phase 1 native SSR transfer Co-authored-by: Cursor <cursoragent@cursor.com> * ci: apply automated fixes * fix(solid): unbreak CI after the solid-js rc.6 bump Two things were failing the Test job: - @tanstack/solid-router test:eslint: the repro-external-ssr harness is not part of the package tsconfig, so the typed parser rejected its .tsx files. Ignore the harness in the package eslint config; it is a standalone vite script, not shipped code. - Four example builds (basic-solid-query, basic-solid-query-file-based, kitchen-sink-file-based, kitchen-sink-solid-query) run tsc, and the rc.6 types no longer accept the one-argument createEffect form. Convert the eleven call sites to the two-argument createEffect(source, effect) form already used by the sibling examples and e2e apps. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: Brenley Dueck <brenleydueck@gmail.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
by Ryan Carniato
Succeeded
solid-router-v2-pre
96f50d94 feat(solid): named single-flight source + loadFlightTarget, the cache-agnostic trigger (#8192) * refactor(solid): retire solid-router-ssr-query — Solid's native channels carry the Router + Query pairing solid-query v6's QueryClientProvider serializes the request's cache into Solid's hydration registry during SSR and primes the client cache from it, so running the ssr-query transport alongside it ships every query payload twice. The package's two runtime conveniences are each a few lines of userland composition on public APIs: the provider wrap via the router's Wrap option, and cache-driven redirect() errors handed to router.navigate from the caches' config.onError. Converts the three Solid Start e2e apps to the composition (all suites green, including the redirect-from-query tests) and marks the package deprecated for the v2 line. Co-authored-by: Cursor <cursoragent@cursor.com> * chore: changeset for the solid-router-ssr-query deprecation notice Co-authored-by: Cursor <cursoragent@cursor.com> * feat(solid-start): named single-flight source for router flight data Solid's single-flight channel is becoming multi-source (solidjs/solid 653dd41e): mutation responses carry a keyed envelope of per-cache slices, each routed to the consumer subscribed under its source id. Today Start claims the single unnamed slot on both halves, which means any other cache wanting mutation-response data (e.g. solid-query, whose provider subscribes under "sq" in TanStack/query#11326) displaces the router's — whichever registers last wins, silently. The router's flight data now rides its own source id ("tsr"): the server collector registers additively with registerFlightDataSource and the client subscribes its consumer under the same id, so router loader/match state and other caches' slices coexist on one round trip. A user-supplied collectFlightData hook keeps the unnamed slot to itself, adding data alongside the router's instead of displacing it. Both halves feature-detect the protocol on the installed @solidjs/web (it ships in the release after 2.0.0-rc.4) and fall back to the exact previous unnamed-slot behavior on older versions; since client and server resolve the same install, the halves cannot disagree. Co-authored-by: Cursor <cursoragent@cursor.com> * feat(solid-router): loadFlightTarget, the cache-agnostic single-flight trigger The router's half of flight collection as a public primitive: derive the flight request for the mutation's target, run the matched routes' data functions, hand the loaded router to the caller's collect() — any cache (the router's own state, a query client) composes its extraction on top. Start's collector now consumes it; errors are contained per Solid Router's collector convention (flight data is an optimization, never a mutation error). Co-authored-by: Cursor <cursoragent@cursor.com> * refactor(solid-start): require named flight sources, drop the pre-rc.5 fallback @solidjs/web 2.0.0-rc.5 ships the multi-source single-flight protocol, so the feature detection and cast shims bridging unreleased types come out: the client subscribes directly under SOLID_START_FLIGHT_SOURCE, the server registers its collector via registerFlightDataSource unconditionally (the unnamed collectFlightData slot now always belongs to the user), and the @solidjs/web peer floor moves to rc.5. Co-authored-by: Cursor <cursoragent@cursor.com> * test(e2e): expect the named single-flight source header With the pre-rc.5 fallback stripped, the client advertises its named source and the server echoes what it folded: X-Single-Flight is "tsr" on both sides, not the legacy "true". Co-authored-by: Cursor <cursoragent@cursor.com> * chore(solid): bump solid-js, @solidjs/web, @solidjs/signals to 2.0.0-rc.6 Repo-wide (packages, examples, e2e apps, benchmarks) — a scoped bump leaves the workspace mixed, and examples/benchmarks then build workspace solid-start dists (which import registerFlightDataSource, rc.5+) against their own @solidjs/web rc.4 resolution. rc.6 ships the named flight-data source API this branch requires plus the settle-walk fix that unblocks the Solid Query pairing. @tanstack/solid-start's peer floor moves to rc.6. The SSR bench helpers move onto rc.6's wire shape: scripted callers use the data address (`<endpoint>/data/<id>`) — the bare address now answers document traffic with the no-JS convention. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: apply automated fixes --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Ryan Carniato
Succeeded
solid-router-v2-pre
5a6935f2 refactor(solid): retire solid-router-ssr-query — native channels carry the Router + Query pairing (#8193) * refactor(solid): retire solid-router-ssr-query — Solid's native channels carry the Router + Query pairing solid-query v6's QueryClientProvider serializes the request's cache into Solid's hydration registry during SSR and primes the client cache from it, so running the ssr-query transport alongside it ships every query payload twice. The package's two runtime conveniences are each a few lines of userland composition on public APIs: the provider wrap via the router's Wrap option, and cache-driven redirect() errors handed to router.navigate from the caches' config.onError. Converts the three Solid Start e2e apps to the composition (all suites green, including the redirect-from-query tests) and marks the package deprecated for the v2 line. Co-authored-by: Cursor <cursoragent@cursor.com> * chore: changeset for the solid-router-ssr-query deprecation notice Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato
Succeeded
solid-router-v2-pre
5010e89a ci: Version Packages (rc) (#8190) ci: changeset release (rc) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
solid-router-v2-pre
22fd367d chore(solid): bump to solid-js 2.0.0-rc.4 and @solidjs/vite-plugin 3.0.0-next.35 (#8189) * chore(solid): bump to solid-js 2.0.0-rc.4 and @solidjs/vite-plugin 3.0.0-next.35 Also: - Migrate the webpack example and docs off the deleted babel-preset-solid onto @solidjs/babel-plugin (compiler packages were renamed in rc.3). - Bump @rsbuild/plugin-solid to ^2.0.0-beta.2 so the rsbuild path compiles with the rc-line preset. - Adapt the server function transport to rc.4: function ids resolve from the request url pathname (X-Server-Function header removed), and the client reference derives its url from the configured endpoint. - Wire per-call AbortSignals through Solid's new invoke() channel and re-enable the previously skipped abort e2e tests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(solid-start): rc.4 CI fallout — rsbuild native loader ssr mode, benchmark wire protocol - @rsbuild/plugin-solid >= 2.0.0-beta.1 compiles through its own solid loader (native compiler) instead of registering babel-preset-solid, so the babel preset patch never fired and node-target rsbuild bundles were compiled in dom mode, throwing "Client-only API called on the server side" at import. Patch the loader's solid options (generate ssr on node targets, hydratable) alongside the legacy preset patch. - The benchmark server-function request builders still spoke the pre-rc.4 wire protocol (id in the removed X-Server-Function-Id header, bare endpoint url). Ids now ride the url pathname. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * chore(solid): bump @tanstack/solid-query to 6.0.0-rc.1 The rc.1 adapter is rewritten onto Solid 2.0's native async model (TanStack/query#11308) and peer-requires solid-js >=2.0.0-rc.4, so it rides this branch's rc.4 bump. Catalog entry plus the non-catalogued solid-query-devtools pins move in lockstep. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-router-v2-pre
5f657835 ci: Version Packages (rc) (#8173) ci: changeset release (rc) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...