prs-gpt-.md

TanStack Table open-PR closure audit

Generated 2026-07-30 from a fresh scan of all 126 open pull requests in TanStack/table.

Result

• 117 PRs can close now: all 107 targeting main (v8), both targeting v7, and all 8 targeting the superseded v9 alpha branch.
• 9 PRs should remain open: all target the current v9 beta branch.
• 2 current-beta PRs have merge conflicts: #6313 and #6443.
• 1 additional beta PR has a failing required check: #6361 is mergeable, but @tanstack/table-core:test:types fails.
• No PRs, issues, labels, reviews, or comments were changed as part of this audit.

Audit baseline

• Current/default branch: beta at 79cbfb6722246baab6fa070966363700aca92298 (v9.0.0-beta.62)
• v8 branch: main at d08af367e11c539bb7e18c2472aa761149ef6db6 (v8.21.3)
• Superseded v9 branch: alpha at 4f855fe4ed088c1d5d5149a3649518587b426d6c (v9.0.0-alpha.54)
• Legacy branch: v7 at 06703a56890122cedf1b2fa4b82982999537774e (v7.8.0)
• Evidence checked: PR bodies, diffs, changed files, discussions/reviews, linked issue state, replacement PRs, current beta source, GitHub mergeability, draft state, and check rollups.
• Branch rule: close work based on main, v7, or alpha; retain work based on the current beta branch.
• Conflict rule: only GitHub's current mergeable: false / mergeable_state: dirty result is called a merge conflict. A failing or incomplete check is reported separately.

Summary

Category	Count	Recommended action
Resolved or Superseded in V9	41	Close; the behavior, docs, or architecture is already present or replaced in beta.
Revisit with a Fresh V9 PR	19	Close the stale PR, retain the issue/idea, and implement anew from beta if pursued.
Non-consequential to Port	38	Close; do not spend v9 migration effort on the stale docs/example/type cleanup.
Wrong Direction for the Library	16	Close with the current API/design boundary or supported alternative.
Too Conflict-heavy to Rescue	3	Close; conflict resolution would effectively be a rewrite.
Keep Open — Beta Clean	4	Keep; current beta target, clean merge state, and passing checks.
Keep Open — Beta Needs Attention	3	Keep; resolve CI, incomplete checks, or an outstanding design decision.
Keep Open — Beta Merge Conflicts	2	Keep, but rebase and resolve conflicts before further review.
Total	126	117 close candidates; 9 keep open.

Suggested response language

Use the response for the PR's category and add the PR-specific evidence from its audit line.

Resolved or Superseded in V9

Thanks for the contribution. We are closing PRs against the pre-beta code lines as we consolidate development on v9 beta. This change is already covered by the current beta implementation or by a replacement PR, so there is nothing useful to port from this branch. We appreciate the work and report that helped identify it.

Revisit with a Fresh V9 PR

Thanks for working on this. The underlying issue/idea is legitimate, but this PR targets an obsolete code line and the current v9 architecture has moved too far for the patch to be carried forward safely. We are closing this PR while retaining the linked issue or audit note. If we pursue it, it should be a fresh PR from beta with a focused current-v9 regression test.

Non-consequential to Port

Thanks for the cleanup. We are closing stale PRs targeting pre-beta branches. Since this is limited to docs, examples, types, or minor cleanup in an area that has since moved, we are not going to spend migration effort porting it. A fresh current-branch PR is welcome if the same problem is still visible and consequential.

Wrong Direction for the Library

Thanks for exploring this. After reviewing it against the current v9 API and design boundaries, we do not want to take the library in this direction. We are closing the PR rather than porting it. The rationale or supported alternative is noted below.

Too Conflict-heavy to Rescue

Thanks for the substantial work here. This branch has diverged enough from the current v9 beta that resolving the conflicts would amount to rewriting the change, and the old diff is no longer a safe review unit. We are closing this PR. If the need still exists, please start with a narrowly scoped proposal or fresh PR from beta.

Close now

Resolved or Superseded in V9 (41)

• #5479 — Improve typing for RowSelectionState — Beta already types selection as Record<string, true>, incorporating the exact true-only state model proposed here.
• #5499 — fix: getIsSomeRowsSelected on all selection — Beta's some-selection predicate now treats every nonempty selection, including all rows selected, consistently; the v8 implementation no longer applies.
• #5519 — ensure columnPinning.[property] is not accessed unsafely — V9 replaced the v8/Qwik state path with registered atoms and logical start/end pinning; the unsafe optional physical state access is gone.
• #5667 — Fix: allow TValue to be specified in display and group column helpers — V9 rewrote column-helper and feature typing, replacing the v8 declaration-merging variance failure this patch works around.
• #5747 — Improve contextDocument handling in ColumnSizing feature — Duplicate of merged #5989, which resolved the document-selection issue on the v8 line.
• #5754 — Refactor example and fix ESLint error — The old editable-data example structure does not exist in beta; current examples use the v9 adapter/rendering architecture.
• #5789 — docs: Fixed links in Columns Definitions Guide — The current docs tree and later link cleanup already contain valid column-definition targets.
• #5879 — fix(react-table): fix improper state update on unmounted component — V9's React adapter uses TanStack Store subscriptions rather than the v8 local-setState path behind #5026.
• #5902 — Check whether filter value is an array — Beta already guards the numeric-range auto-remove path with Array.isArray, resolving #5901.
• #5933 — docs: Fix links in custom-features.md — The v9 guide tree and later mass link migration supersede these v8-relative link edits.
• #5934 — Fix Table API doc link — Current v9 table guides point at the rebuilt core API documentation.
• #5937 — docs: make global filter work in row selection example — Beta's row-selection example registers global filtering and has end-to-end coverage for the filter input.
• #5963 — Update column-sizing.md — The broken v8 relative links were superseded by the later documentation link migration.
• #6005 — fix: export GroupColumnDefBase — V9's public GroupColumnDef declarations emit without leaking the private v8 base type, resolving #6004 without this export.
• #6015 — Update column-sizing.md — This is another superseded attempt at the v8 documentation-link problem handled by the later link migration.
• #6017 — fix(table-core): correctly count only truthy selected rows in getIsSomeRowsSelected — Beta's true-only selection-state type and updated predicate remove false-valued IDs from this calculation.
• #6026 — fix: Avoid duplicate call to autoreset by removing the wrap in _queue — V9 removed the v8 microtask _queue architecture that caused #6025.
• #6055 — Add missing equalsStringSenstivie — Beta already exports and registers equalsStringSensitive.
• #6056 — fix(table-core): Correct getAutoSortingFn logic when row count is less then 10 — Beta samples with slice(0, 10), so #4908 is already fixed.
• #6067 — fix(doc): column filtering typo — The exact #6064 wording was already fixed by merged #5509.
• #6072 — docs: fix non-existent example value for globalFilterFn — V9 replaced the affected guide and filtering examples with its feature-registered API.
• #6084 — fix: clear multi-sort when clicking column without shift key — Current beta PR #6431 is the focused v9 replacement for the same canonical regression in #4309.
• #6088 — docs: add missing import type for TableMeta module declaration — V9 uses per-table tableMeta typing instead of the affected global v8 TableMeta declaration-merging pattern.
• #6094 — Fix calculation of leafRows in getGroupedRowModel — V9's grouping rewrite already corrected the depth-dependent leaf-row calculation from #6093.
• #6098 — fix(table-core): CoreOptions columns and data are readonly — Beta's core options already accept readonly data and column-definition arrays.
• #6134 — fix(table-core): Pass column to resolveFilterValue — V9 replaced the mismatched v8 signature with an intentional one-argument resolveFilterValue contract.
• #6154 — docs: fix broken global filter example link — Superseded by merged #6231, which fixed the guide links comprehensively.
• #6156 — fix(core): avoid Date.now() calls in memo when debug is disabled — V9 only performs timing work when debugging is enabled and no longer has the unconditional v8 render-time Date.now() path.
• #6161 — fix(table-core): clear stale columnFiltersMeta in getFilteredRowModel — Beta resets columnFilters and columnFiltersMeta for every flat row on each filtered-model pass.
• #6168 — fix: add variance annotations to fix file-order-dependent type errors — V9's rewritten recursive table/column types already carry explicit variance annotations, resolving #6167.
• #6171 — Fix broken documentation link for global filters example — Another duplicate superseded by merged #6231.
• #6187 — fix(table-core): consistent alphanumeric sorting for mixed letter/digit strings — V9 replaced the misaligned regex chunk comparator and covers the #6174 mixed-character case.
• #6193 — docs: fix broken filters-global example link in global filtering guide — A third duplicate superseded by merged #6231.
• #6208 — fix(pagination): autoResetPageIndex should reset to 0, not initialState pageIndex — Merged beta PR #6411 implements the current-v9 fix and closed #6207.
• #6239 — fix: preserve undefined in deep accessor types — Merged beta PR #6444 is the current-v9 version and closed #6238.
• #6282 — fix(grouping): aggregate grouped columns at shallower group levels — Merged beta PR #6421 restored the required aggregation context for #6228.
• #6337 — fix(table-core): prototype-named column ids poisoning row value caches — Beta already creates null-prototype maps and uses safe hasOwn checks for row value caches.
• #6354 — docs: fix missing word in column filtering guide — The same missing word was fixed earlier by merged #5509.
• #6451 — docs: complete truncated sentence in columns guide — The beta Columns Guide already contains the completed sentence and corrected “rendering” spelling, resolving #5761.
• #5942 — Don't try to @render svelte components in FlexRender (alpha) — Beta replaced the alpha Svelte FlexRender.svelte implementation with the current Svelte 5 adapter/rendering path.
• #6252 — fix(table-core): scan rows for first non-nullish value in getColumnCanGlobalFilter (alpha) — Current beta PR #6438 is the focused replacement with a current regression test.

Revisit with a Fresh V9 PR (19)

• #5031 — Fix an issue where pageIndex becomes invalid when data is changed — #4994 still fails a focused beta regression when shrunken data leaves an invalid page index; keep the issue and implement the clamp against v9's pagination atoms.
• #5373 — fix(table-core): Avoid process not defined in environments not setting a process variable — The underlying unbundled-ESM concern remains tracked by #6078, but this old patch overlaps #6185 and predates v9's reorganized source; retain one current reproduction and start fresh.
• #5414 — feat: add autoResetSorting — The opt-in use case may be valid, but the v8 patch defaults the reset on for client sorting despite the maintainer discussion and has no current state-scheduling tests; reconsider as a beta-first design.
• #5582 — fix: invalidate cached values after updating accessor functions — #5363 still fails on beta, but v9's row/column construction and caches differ substantially; preserve the regression and rewrite from beta.
• #5790 — fix(table-core): ensure isSubRowSelected returns false if no subRows are selectable — #5173 remains a verified beta bug; consolidate this and #6177 into one fresh v9 predicate fix with disabled-descendant coverage.
• #5823 — fix: crash when ungrouping after aggregation row was pinned — #5822 still throws on beta when a stale synthetic group ID remains pinned; the v9 row-pinning/grouping code needs a fresh patch.
• #5890 — Add header.getAfter API — Beta has logical start/end pinning and column.getAfter, but no header equivalent; if grouped end-pinning still needs it, design and test a logical v9 API rather than porting the physical-right v8 patch.
• #5978 — fix: Duplicate sub-rows in pagination row model — #5833 still produces duplicate beta flatRows; carry the failing regression into a fresh v9 pagination-model fix.
• #6075 — fix: retain columnFiltersMeta when leaf row filtering — #6074 still loses beta filter metadata after filterFromLeafRows; reimplement against v9's new filter-row utilities.
• #6116 — [BUG] ignore non expandable rows when the expanded state changes — #6115 remains plausible in beta, but needs a current expansion-depth regression and an explicit semantic decision before a new implementation.
• #6176 — Added server.allowed hosts to vite config — #6175 remains a valid examples-infrastructure issue, but the 73 v8 example configs are no longer the current set; generate a focused beta-era configuration change.
• #6177 — fix: table-core's getIsAllSubRowsSelected returns false when subrows are unselectable — This is the second stale approach to verified beta issue #5173; close both old PRs and use one fresh beta fix.
• #6178 — fix(table-core): respect custom filterFn.autoRemove in shouldAutoRemoveFilter — #6101 is a valid API inconsistency; consolidate this with duplicate #6195 into a tested beta implementation.
• #6184 — fix(table-core): skip state update in toggleExpanded when state is unchanged — #6136 needs a current React commit/render regression before changing beta; consolidate this with duplicate #6194.
• #6185 — fix(table-core): guard process.env checks for non-bundled environments — This is the newer duplicate of #5373 for #6078; verify the published beta browser export, then write one current patch if it still fails.
• #6186 — fix(vue-table): return null for empty string in FlexRender to prevent hydration mismatch — #6077 is plausible, but the Vue v9 adapter was rewritten; require a current SSR hydration regression before a fresh fix.
• #6194 — fix: skip toggleExpanded when state already matches desired value — Duplicate v8 approach to #6136; use the same current-v9 investigation/fresh-PR path as #6184.
• #6195 — fix: respect custom filterFn.autoRemove over default empty string check — Duplicate v8 approach to valid issue #6101; use the same fresh-beta path as #6178.
• #6417 — fix(table-core): refresh faceted values on option updates — #6081 still fails a focused beta regression, but this PR targets main; recreate its option-update cache test and fix from beta.

Non-consequential to Port (38)

• #5729 — docs(expansion/table): tip use table option getRowId if data may change — V8-only documentation for a long-closed v7-era issue; no v9 code or urgent documentation gap.
• #5750 — Fix: Corrected typo in example code — One-character v8 guide typo in documentation that has since been rewritten.
• #5862 — docs: improve vanilla js installation docs — V8-only installation wording, with no code or current beta reproduction.
• #5878 — fix: improve typing on makeStateUpdater function — Internal v8 type-guard/cast cleanup; v9 replaced the updater implementation.
• #5886 — Update fuzzy-filtering.md — A one-line wording edit in an old guide.
• #5915 — refactor: remove unnecessary code — Unused import and ref dependency cleanup in two v8 examples.
• #5960 — docs: typo in guide/sorting.md — Single v8 documentation typo.
• #5967 — Improve type for Editable Data React example — Example-only TypeScript narrowing for an example absent from beta.
• #5982 — Fix typo in table-state.md — Single v8 React guide typo.
• #6020 — Improve match-sorter-util performance by replacing string comparisons — Seven-line micro-optimization without a benchmark or linked user-visible regression; not worth a stale-branch port.
• #6023 — docs(typo): fix typo — One-word v8 tables-guide edit.
• #6027 — Fixed typo it’s to its — One-character Vue documentation edit.
• #6031 — Fix DeepKeys to handle arrays properly — Type-only v8 accessor-path expansion with no linked regression or consumer test to justify porting.
• #6037 — docs: add forgotten “mean” to column filtering docs — Single missing word in old docs.
• #6038 — docs: remove unused footer column def — Six-line cleanup in a v8 example.
• #6045 — docs: typos in guide/table-state.md — Three small wording fixes in a v8 guide.
• #6052 — fix: add ref to drag handle button for improved DnD functionality — Example-only DnD wiring owned by the renderer/integration, not Table core.
• #6053 — Fix writing in column-filtering.md — Two grammar changes in old docs.
• #6054 — docs: fixed API docs link — Source-comment link correction with no runtime impact.
• #6095 — fix: next section is actually previous section — One-word cross-reference correction.
• #6103 — Update column-filtering.md — Removes one duplicated word from a v8 guide.
• #6105 — Update headers.md — Documentation-only colspan to colSpan casing.
• #6107 — Update table-state.md, fix parens typo — One-character Vue guide correction.
• #6108 — docs: fix typo in column filtering guide — One grammar edit in the v8 guide.
• #6110 — docs(expanding): clarify description of autoResetExpanded setting — V8-only option wording; v9 reset behavior and docs have been rebuilt.
• #6125 — Fix syntax error in pagination example — Duplicate one-character Vue example correction in the same area as #6107.
• #6146 — Fix punctuation in introduction.md — Punctuation-only old-docs change.
• #6147 — Fix typo in column filtering documentation — Grammar-only old-docs change.
• #6160 — docs: fix a few small typos — Three small wording changes across v8 guides.
• #6163 — docs: fix TanStack Start link in README — One ecosystem link; harmless to close with the v8 batch and re-open from beta only if still prioritized.
• #6169 — Fix TanStack virtual example link — One example comment link.
• #6204 — Docs: fix what seems to be a copy-paste error — Small v8 cells-guide correction.
• #6205 — Docs: fix typo in table state documentation — One Angular guide typo.
• #6210 — Docs: fix typo in column filtering documentation — One old-guide typo.
• #5920 — chore(svelte-table): cleanup package.json (alpha) — Package-manifest cleanup against a superseded alpha package layout; no behavioral fix.
• #6203 — update coderabbit logo (alpha) — Sponsor/logo presentation only.
• #6155 — docs(v7): use github source link instead of broken v7 doc site (v7) — Legacy docs-only link; the associated #6008 was closed as completed on 2026-07-27 with the archived Netlify URL documented.
• #6165 — Fix link to FAQ in useTable documentation (v7) — One link in end-of-life v7 documentation.

Wrong Direction for the Library (16)

• #5274 — Do not select subrows if enableSubRowSelection is false — enableSubRowSelection controls cascading from a toggled parent; select-all intentionally evaluates each independently selectable row. Use enableRowSelection to exclude rows.
• #5401 — update logic to fix selection of disabled rows — Disabled is a current interaction capability, not immutable selection state; bulk deselection must still be able to clear controlled/persisted IDs.
• #5514 — reduce memory leak by remove memo function — Blanket removal of feature memoization trades away computation without isolating a leak; v9 addressed allocations through shared prototypes and targeted row/cell architecture changes.
• #5697 — fix: array filterFns — arrIncludes, arrIncludesAll, and arrIncludesSome intentionally filter array-valued cells. Scalar cells should use equals or a custom function.
• #5950 — add filterRowsUtils export — The recursive filter utility is an implementation detail tied to internal row-model invariants; custom row models should not depend on that unstable private surface.
• #5964 — Remove console.error log from table.getColumn(id) — V9 deliberately retains a development-only missing-column warning to expose stale IDs while still returning undefined.
• #5974 — support unsetting getPaginationRowModel — Dynamic client/server pagination should use manualPagination; treating removal of a row-model factory as a runtime mode switch complicates cache ownership.
• #5996 — Prevent deletion of non-selectable rows on RowSelectionChange — Same capability-versus-immutability problem as #5401: non-selectable rows may still need their stale selection IDs cleared.
• #6062 — feat(RowSelection): support indeterminate states — The proposal makes a parent's explicit selection ID a derived mirror of descendants. Current Table semantics expose explicit and descendant predicates separately so renderers can combine them.
• #6085 — docs: add Excel-like sorting guide for null/undefined handling — Excel-style coercion and empty-value ordering are application-specific collation policy; use a custom sortingFn rather than establish it as an official Table behavior.
• #6120 — fix API to calculate max expanded row depth — Collapsing a parent should not erase descendant expansion choices; preserving them allows nested state to return when the parent is reopened.
• #6123 — add existingTable param to useReactTable — V9 supports external ownership through atoms/stores; threading an existing instance through every framework adapter couples hook lifecycles and includes removed Qwik code.
• #6129 — toggleAllRowsSelected should respect row selection rules — enableRowSelection gates whether a row can be interactively selected, not whether a bulk command may remove an already-stored ID.
• #6240 — type column contexts with React table (alpha) — Core cell/header contexts must remain framework-neutral. React's Subscribe helper is intentionally an adapter component, not part of the core Table context type.
• #6241 — added IgnoreDiacritics sort functions (alpha) — Four built-ins encode locale-sensitive collation policy and expand the registry; applications can supply an Intl.Collator-backed custom sorting function.
• #6295 — clamp column size during resize drag (alpha) — Current v8/v9 getters already clamp committed sizes to minSize/maxSize, and #5997 could not be reproduced under the supported rendering path.

Too Conflict-heavy to Rescue (3)

• #5865 — docs: update router example and types — Conflicting 2025 dependency/example migration with 775 additions, 189 deletions, a lockfile rewrite, and an obsolete router API; rebuilding the current beta example is safer.
• #6086 — feat: add sortEmpty option for comprehensive empty value handling — Conflicting 11-file, 1,092-line API/deprecation/example change. It also needs a new design decision on app-specific empty-value policy, so conflict resolution would not rescue a reviewable patch.
• #6242 — WIP: adapt solid-table to Solid v2 beta reactivity model (alpha) — Conflicting draft spanning 83 files with 1,050 additions and 454 deletions against an older Solid v2 beta and v9 alpha; any remaining Solid work must start from current beta.

Keep open

Beta Clean (4)

• #6431 — fix sorting replacement in single-sort mode — Draft, mergeable/clean, and all checks pass. It fixes the verified #4309 beta regression with focused tests; keep and move out of draft when review-ready.
• #6438 — fix global filtering with undefined first values — Draft, mergeable/clean, and all checks pass. It fixes verified #4783 and supersedes alpha #6252.
• #6439 — honor explicit global filter opt-in — Draft, mergeable/clean, and all checks pass. It fixes verified object-valued global filtering in #4673.
• #6442 — toggle group column visibility — Draft, mergeable/clean, and all checks pass. It supplies the beta design/test for valid group visibility issue #5497.

Beta Needs Attention (3)

• #6361 — include sub-rows in flatRows when maxLeafRowFilterDepth truncates recursion — Keep: non-draft and mergeable, and it targets verified #5987. The required Test check currently fails at @tanstack/table-core:test:types; update to current beta types and rerun.
• #6385 — Allow Manual Override of Pagination canNextPage/canPreviousPage — Keep: draft and mergeable with no conflict. GitHub reports UNSTABLE and the normal full test/preview rollup is absent; it also needs maintainer agreement on whether navigation capability belongs in pagination state or options.
• #6445 — perf: compute NODE_ENV up-front & flip opt-in — Keep: draft and mergeable with no conflict. GitHub reports UNSTABLE with only review/security checks present; decide the !== 'production' behavior, then run the full required suite.

Beta Merge Conflicts (2)

• #6313 — exclude non-numeric values from inNumberRange filter — Keep, but GitHub reports CONFLICTING/dirty. It fixes verified #6007; rebase onto current beta, preserve the finite-number regression coverage, and rerun checks.
• #6443 — reset expansion when data changes — Keep, but the draft is CONFLICTING/dirty and its Test check fails. It fixes verified #5801; rebase onto current beta and revalidate the core-row-model reset hook.