Overview - Router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
upgrade-solidjs-rc-0
59cf4375 Version Packages: solid family to 2.0.0-rc.0 Manually applied `changeset version` and normalized the prerelease counters to 0. Changesets continues each package's counter across a pre-tag switch (beta.30 would have become rc.31), and the counter is derived from the current versions, so a literal rc.0 is only reachable by hand. All six @tanstack/solid-* packages move to 2.0.0-rc.0; the pending solid changesets are recorded as consumed in .changeset/pre.json, so CI's next version run has nothing further to apply. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
8058
56cc90ea Upgrade solidjs rc 0 and rename vite-plugin-solid to @solidjs/vite-plugin `vite-plugin-solid` has been renamed to `@solidjs/vite-plugin`. Its final release under the old name (`3.0.0-next.27`) is a re-export shim over the new package, and `next.28`+ ships only under the new name. The rename and the `rc` bump are forced together: `@solidjs/vite-plugin@3.0.0-next.28` peer-requires `solid-js`/`@solidjs/web` `^2.0.0-rc.0`. - solid-js, @solidjs/web, babel-preset-solid: 2.0.0-beta.32 -> ^2.0.0-rc.0 - vite-plugin-solid ^3.0.0-next.23 -> @solidjs/vite-plugin ^3.0.0-next.28 - @tanstack/solid-query + solid-query-devtools -> ^6.0.0-rc.0 (solid-query rc.0 peer-requires solid-js >=2.0.0-rc.0) - @tanstack/query-core converged on 5.101.4: solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two structurally incompatible `QueryClient` types, failing @tanstack/solid-router-ssr-query's build `packages/router-devtools-core` intentionally stays on `vite-plugin-solid@^2.11.10` — it builds against Solid 1.9.12 and `@solidjs/vite-plugin` has no 2.x line. `@tanstack/router-plugin` is intentionally untouched: it detects the Solid JSX plugin by its Vite plugin name (`solid`), which the renamed package still registers, and its `vite-plugin-solid` peer is optional — so it keeps working for both Solid 1 and Solid 2 consumers without a change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Canceled
8058
56cc90ea Upgrade solidjs rc 0 and rename vite-plugin-solid to @solidjs/vite-plugin `vite-plugin-solid` has been renamed to `@solidjs/vite-plugin`. Its final release under the old name (`3.0.0-next.27`) is a re-export shim over the new package, and `next.28`+ ships only under the new name. The rename and the `rc` bump are forced together: `@solidjs/vite-plugin@3.0.0-next.28` peer-requires `solid-js`/`@solidjs/web` `^2.0.0-rc.0`. - solid-js, @solidjs/web, babel-preset-solid: 2.0.0-beta.32 -> ^2.0.0-rc.0 - vite-plugin-solid ^3.0.0-next.23 -> @solidjs/vite-plugin ^3.0.0-next.28 - @tanstack/solid-query + solid-query-devtools -> ^6.0.0-rc.0 (solid-query rc.0 peer-requires solid-js >=2.0.0-rc.0) - @tanstack/query-core converged on 5.101.4: solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two structurally incompatible `QueryClient` types, failing @tanstack/solid-router-ssr-query's build `packages/router-devtools-core` intentionally stays on `vite-plugin-solid@^2.11.10` — it builds against Solid 1.9.12 and `@solidjs/vite-plugin` has no 2.x line. `@tanstack/router-plugin` is intentionally untouched: it detects the Solid JSX plugin by its Vite plugin name (`solid`), which the renamed package still registers, and its `vite-plugin-solid` peer is optional — so it keeps working for both Solid 1 and Solid 2 consumers without a change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Canceled
8058
56cc90ea Upgrade solidjs rc 0 and rename vite-plugin-solid to @solidjs/vite-plugin `vite-plugin-solid` has been renamed to `@solidjs/vite-plugin`. Its final release under the old name (`3.0.0-next.27`) is a re-export shim over the new package, and `next.28`+ ships only under the new name. The rename and the `rc` bump are forced together: `@solidjs/vite-plugin@3.0.0-next.28` peer-requires `solid-js`/`@solidjs/web` `^2.0.0-rc.0`. - solid-js, @solidjs/web, babel-preset-solid: 2.0.0-beta.32 -> ^2.0.0-rc.0 - vite-plugin-solid ^3.0.0-next.23 -> @solidjs/vite-plugin ^3.0.0-next.28 - @tanstack/solid-query + solid-query-devtools -> ^6.0.0-rc.0 (solid-query rc.0 peer-requires solid-js >=2.0.0-rc.0) - @tanstack/query-core converged on 5.101.4: solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two structurally incompatible `QueryClient` types, failing @tanstack/solid-router-ssr-query's build `packages/router-devtools-core` intentionally stays on `vite-plugin-solid@^2.11.10` — it builds against Solid 1.9.12 and `@solidjs/vite-plugin` has no 2.x line. `@tanstack/router-plugin` is intentionally untouched: it detects the Solid JSX plugin by its Vite plugin name (`solid`), which the renamed package still registers, and its `vite-plugin-solid` peer is optional — so it keeps working for both Solid 1 and Solid 2 consumers without a change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
8058
c407efef Upgrade solidjs rc 0 and rename vite-plugin-solid to @solidjs/vite-plugin `vite-plugin-solid` has been renamed to `@solidjs/vite-plugin`. Its final release under the old name (`3.0.0-next.27`) is a re-export shim over the new package, and `next.28`+ ships only under the new name. The rename and the `rc` bump are forced together: `@solidjs/vite-plugin@3.0.0-next.28` peer-requires `solid-js`/`@solidjs/web` `^2.0.0-rc.0`. - solid-js, @solidjs/web, babel-preset-solid: 2.0.0-beta.32 -> ^2.0.0-rc.0 - vite-plugin-solid ^3.0.0-next.23 -> @solidjs/vite-plugin ^3.0.0-next.28 - @tanstack/solid-query + solid-query-devtools -> ^6.0.0-rc.0 (solid-query rc.0 peer-requires solid-js >=2.0.0-rc.0) - @tanstack/query-core converged on 5.101.4: solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two structurally incompatible `QueryClient` types, failing @tanstack/solid-router-ssr-query's build `packages/router-devtools-core` intentionally stays on `vite-plugin-solid@^2.11.10` — it builds against Solid 1.9.12 and `@solidjs/vite-plugin` has no 2.x line. `@tanstack/router-plugin` declares `@solidjs/vite-plugin` as an optional peer alongside the existing `vite-plugin-solid` one so both Solid 1 and Solid 2 consumers resolve. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
8058
7fb276d4 Upgrade solidjs rc 0 and rename vite-plugin-solid to @solidjs/vite-plugin `vite-plugin-solid` has been renamed to `@solidjs/vite-plugin`. Its final release under the old name (`3.0.0-next.27`) is a re-export shim over the new package, and `next.28`+ ships only under the new name. The rename and the `rc` bump are forced together: `@solidjs/vite-plugin@3.0.0-next.28` peer-requires `solid-js`/`@solidjs/web` `^2.0.0-rc.0`. - solid-js, @solidjs/web, babel-preset-solid: 2.0.0-beta.32 -> ^2.0.0-rc.0 - vite-plugin-solid ^3.0.0-next.23 -> @solidjs/vite-plugin ^3.0.0-next.28 - @tanstack/solid-query + solid-query-devtools -> ^6.0.0-rc.0 (solid-query rc.0 peer-requires solid-js >=2.0.0-rc.0) - @tanstack/query-core converged on 5.101.4: solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two structurally incompatible `QueryClient` types, failing @tanstack/solid-router-ssr-query's build `packages/router-devtools-core` intentionally stays on `vite-plugin-solid@^2.11.10` — it builds against Solid 1.9.12 and `@solidjs/vite-plugin` has no 2.x line. `@tanstack/router-plugin` declares `@solidjs/vite-plugin` as an optional peer alongside the existing `vite-plugin-solid` one so both Solid 1 and Solid 2 consumers resolve. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck