Update dependency @tanstack/react-table to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@tanstack/react-table (source)	^8.21.3 → ^9.0.0

---

Release Notes

TanStack/table (@​tanstack/react-table)

v9.1.2

Compare Source

Patch Changes

• Updated dependencies [ff43666]:
  • @​tanstack/table-core@​9.1.2

v9.1.1

Compare Source

Patch Changes

• Updated dependencies [269e0d8]:
  • @​tanstack/table-core@​9.1.1

v9.1.0

Compare Source

Patch Changes

• Updated dependencies [09598d2]:
  • @​tanstack/table-core@​9.1.0

v9.0.1

Compare Source

Patch Changes

• #​6521 10accb2 - Column defs built with legacyCreateColumnHelper now accept the built-in filterFn, sortFn, and aggregationFn names, matching the registries useLegacyTable registers at runtime.

• Updated dependencies []:

  • @​tanstack/table-core@​9.0.1

v9.0.0

Compare Source

Major Changes

• #​6512 2327f80 - TanStack Table v9 stable release. See the "Migrating to V9" guide for your framework (e.g. React) for upgrade instructions.

Patch Changes

• Updated dependencies [2327f80]:
  • @​tanstack/table-core@​9.0.0

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • Between 12:00 AM and 11:59 PM (* 0-23 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
adminv2	Error		Aug 20, 2026 5:52am

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-beautiful-dnd@13.1.1
npm error Found: react@19.2.4
npm error node_modules/react
npm error   react@"19.2.4" from the root project
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     @emotion/react@"^11.14.0" from the root project
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       @emotion/styled@"^11.14.1" from the root project
npm error       4 more (@mui/lab, @mui/material, @mui/styled-engine, @mui/system)
npm error     5 more (@mui/lab, @mui/material, @mui/styled-engine, ...)
npm error   30 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error node_modules/react-beautiful-dnd
npm error   react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error   node_modules/react-beautiful-dnd
npm error     react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-20T03_32_52_605Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-20T03_32_52_605Z-debug-0.log