ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
router
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
7805
1d20a9dc Always execute beforeLoad for client lanes (#7922) * Always execute beforeLoad for client lanes * Simplify hydration handoff validation * ci: apply automated fixes * doc update
by Flo
F
Succeeded
7805
1d20a9dc Always execute beforeLoad for client lanes (#7922) * Always execute beforeLoad for client lanes * Simplify hydration handoff validation * ci: apply automated fixes * doc update
by Flo
F
Failed
7805
Environment issue
→
1d20a9dc Always execute beforeLoad for client lanes (#7922) * Always execute beforeLoad for client lanes * Simplify hydration handoff validation * ci: apply automated fixes * doc update
by Flo
F
Succeeded
fix-router-core-lane-match-loader
fe9cd448 test: add regression coverage for existing router behavior (#7886)
by Flo
F
Succeeded
main
3a557562 test: add regression coverage for existing router behavior (#7886)
by Flo
F
Succeeded
7805
fd8e2564 Merge branch 'main' into fix-router-core-lane-match-loader
by Flo
F
Succeeded
7805
fd8e2564 Merge branch 'main' into fix-router-core-lane-match-loader
by Flo
F
Succeeded
7805
baa18cd9 fix(router): final-review regressions, changeset, and byte recovery (#7883) * fix(router): final-review regressions, changeset, and byte recovery Fixes the regressions vs main found in the final review of #7805: - restore history-subscription cleanup on router provider unmount in all three adapters (react returns the unsubscribe unconditionally, solid uses onCleanup, vue uses onUnmounted), pinned by new transitioner-remount tests — a discarded router could previously keep loading on back/forward as a zombie - same-destination navigations now join the in-flight transaction instead of aborting and restarting it (double-click no longer reruns loaders); reloads and same-location redirects keep restart semantics - commitMatches cache retention can no longer resurrect a one-generation-old loaderData when a newer committed success exists for the same match id - same-location dedup keeps __tempLocation/__tempKey so masked vs real same-href navigations commit their state again Adds the missing release changeset enumerating the removed/changed public API with migration hints. Byte recovery: merges rendered-matches.ts, route-chunks.ts and hydrate.ts into load-client.ts so the client bundle shares gzip dictionary context across what were separate module boundaries (-104..-186 gzip B per start scenario; plain router scenarios remain net-negative vs main and hydration still tree-shakes out of them). The solid/vue store-update-count pins were re-adjusted after verifying the published update sequences are byte-identical: the counts only shifted because a one-microtask timing change moves the tests' waitFor-sampled window boundary (5 of 7 counts decreased). * test(router-devtools-core): keep panel chunk warm-up out of the test budget The cache-replacement test warmed Vite's lazy transform of BaseTanStackRouterDevtoolsPanel inside the test body, so on slow CI runners the transform alone could blow the 5s test timeout (observed at 5.89s). Move the warm-up to a beforeAll with its own generous timeout and give the test itself explicit headroom. Pre-existing flake on the lane branch tip, surfaced by this PR's CI being the first to run on it. * refactor(router-core): extend lane typestate to matches and commits The lane pipeline already carried phase brands at lane granularity (Lane<'matched'|'contextualized'|'reduced'|'projected'>); this finishes the pattern at the two granularities it was missing, at zero runtime cost (all emitted dist JS verified byte-identical): - settleInto becomes the sole granter of a SettledMatch brand via an assertion signature, and cacheLoaderMatch requires it — the loader -> settle -> cache ordering is now compiler-enforced. The one legitimate phase jump (hydration cache-seeding of already-settled dehydrated data) is a single named, commented boundary cast. - commitMatches/commitRefreshMatches only accept a projected lane's matches (LaneMatches<'projected'>), so committing an earlier-phase lane no longer compiles. - LoadTransaction's dev-only refresh triple collapses into one optional slot [presentation, handoff?], making a half-armed refresh state unrepresentable and shrinking the clear/read sites.
by Flo
F
Succeeded
7805
9043f4f2 Merge branch 'main' into fix-router-core-lane-match-loader
by Flo
F
Succeeded
7805
9043f4f2 Merge branch 'main' into fix-router-core-lane-match-loader
by Flo
F
Canceled
7805
03a1fde2 perf(router): reduce SSR lane loading overhead (#7875) * perf(router): reduce SSR lane loading overhead * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Flo
F
Succeeded
7805
03a1fde2 perf(router): reduce SSR lane loading overhead (#7875) * perf(router): reduce SSR lane loading overhead * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Flo
F
Failed
7805
1f271022 fix(router-core): harden lane loading lifecycle (#7869) * fix(router-core): harden lane loading lifecycle * ci: apply automated fixes * fix(router-core): optimize lane loading followups * fix(router-core): simplify redirect limit handling * refactor(router-core): clarify loader state and caches --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Flo
F
Succeeded
7858
dd7fb57e perf(ssr): reduce request cancellation overhead (#7862)
by Flo
F
Succeeded
main
f1513caa test: add more regression coverage for existing router behavior (#7822)
by Flo
F
Succeeded
main
f1513caa test: add more regression coverage for existing router behavior (#7822)
by Flo
F
Succeeded
main
f1513caa test: add more regression coverage for existing router behavior (#7822)
by Flo
F
Succeeded
main
f1513caa test: add more regression coverage for existing router behavior (#7822)
by Flo
F
Succeeded
main
f1513caa test: add more regression coverage for existing router behavior (#7822)
by Flo
F
Succeeded
main
f1513caa test: add more regression coverage for existing router behavior (#7822)
by Flo
F
Previous page
Previous
Next
Next page