Skip to content

release: data-table-pro v5.0.0 - #3

Merged
Dastari merged 4 commits into
mainfrom
agent/column-groups
Aug 13, 2026
Merged

release: data-table-pro v5.0.0#3
Dastari merged 4 commits into
mainfrom
agent/column-groups

Conversation

@Dastari

@Dastari Dastari commented Aug 12, 2026

Copy link
Copy Markdown
Owner

What changed

  • Upgrade @tanstack/react-table from v8.21.3 to v9.1.2.
  • Replace useReactTable with useTable and register the table features, row models, and function registries explicitly.
  • Adapt v9 state, selection, sorting, aggregation, row-model, and logical pinning APIs behind project-owned types.
  • Preserve the wrapper-owned left / right pinning contract for props, persistence, saved views, URL state, and API snapshots.
  • Bump the package to 5.0.0 and commit regenerated distribution declarations and bundles.
  • Record all breaking changes, compatibility guarantees, and before/after migration examples in the changelog, README, API reference, migration guide, and roadmap.

Why

TanStack React Table v9 changes table construction, feature registration, type generics, state access, sorting and aggregation APIs, pinning terminology, and instance method behavior. This major release adopts those APIs directly without the deprecated legacy bridge.

Consumer impact

Direct TanStack-facing column definitions and table-instance code must follow the documented v9 migration. The component-level DataTable state API, existing package entrypoints, persisted state, saved views, URL-state formats, and physical left / right pinning contract remain supported.

Validation

  • 318 unit/integration tests with coverage
  • 11 Chromium accessibility and layout tests
  • package and demo lint/typechecks/builds
  • deterministic committed dist output and current public API snapshot
  • packed 5.0.0 consumer typecheck and build
  • package contents and bundle budgets
  • frozen lockfile installation and dependency audit

@Dastari
Dastari merged commit e7586ad into main Aug 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant