deps(npm): bump @tanstack/react-table from 8.21.3 to 9.1.2 - #261
Conversation
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![mergestorm-vortex[bot]](https://avatars.githubusercontent.com/in/3924858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review progress ██████████ 1/1 files
Request changes — found 1 issue(s) at 1a20139.
Actionable comment posted: 1
🤖 Prompt for AI agents
Verify each finding against current code. Fix only still-valid concrete bugs, skip the
rest with a brief reason, keep changes minimal, and validate. Skip Decision required,
policy forks, and "consider X" alternatives. Do not add new features, refactors, or
architecture beyond the fix; prefer the smallest diff.
Findings to address:
1. In `@apps/web/package.json` (line 27, Blocker):
`"@tanstack/react-table": "^9.1.2"`
`bun.lock` was not updated in this PR: the workspace entry still declares `"@tanstack/react-table": "^8.20.0"` (bun.lock:88) and resolves `@tanstack/react-table@8.21.3` / `@tanstack/table-core@8.21.3` (bun.lock:683-685). Because the new range can't resolve to the pinned 8.21.3, Bun must rewrite the lockfile — and `bun install --frozen-lockfile` (`.github/workflows/ci.yml:216`, the "Web Brand Color" job, which is gated on `apps/web/**` and asserted as required at `ci.yml:665`) errors with "lockfile had changes, but lockfile is frozen" instead of updating it. Net effect: CI fails and the bump is a no-op even locally. Regenerate `bun.lock` (`bun install`) in this PR so the manifest and lockfile agree.
| "@radix-ui/react-visually-hidden": "^1.2.3", | ||
| "@tailwindcss/postcss": "^4.1.11", | ||
| "@tanstack/react-table": "^8.20.0", | ||
| "@tanstack/react-table": "^9.1.2", |
There was a problem hiding this comment.
🔴 Blocker · Blocker
bun.lock not regenerated — frozen-lockfile CI will fail
"@tanstack/react-table": "^9.1.2"
bun.lock was not updated in this PR: the workspace entry still declares "@tanstack/react-table": "^8.20.0" (bun.lock:88) and resolves @tanstack/react-table@8.21.3 / @tanstack/table-core@8.21.3 (bun.lock:683-685). Because the new range can't resolve to the pinned 8.21.3, Bun must rewrite the lockfile — and bun install --frozen-lockfile (.github/workflows/ci.yml:216, the "Web Brand Color" job, which is gated on apps/web/** and asserted as required at ci.yml:665) errors with "lockfile had changes, but lockfile is frozen" instead of updating it. Net effect: CI fails and the bump is a no-op even locally. Regenerate bun.lock (bun install) in this PR so the manifest and lockfile agree.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid concrete bugs, skip the
rest with a brief reason, keep changes minimal, and validate. Skip Decision required,
policy forks, and "consider X" alternatives. Do not add new features, refactors, or
architecture beyond the fix; prefer the smallest diff.
In `@apps/web/package.json` (line 27, Blocker):
`"@tanstack/react-table": "^9.1.2"`
`bun.lock` was not updated in this PR: the workspace entry still declares `"@tanstack/react-table": "^8.20.0"` (bun.lock:88) and resolves `@tanstack/react-table@8.21.3` / `@tanstack/table-core@8.21.3` (bun.lock:683-685). Because the new range can't resolve to the pinned 8.21.3, Bun must rewrite the lockfile — and `bun install --frozen-lockfile` (`.github/workflows/ci.yml:216`, the "Web Brand Color" job, which is gated on `apps/web/**` and asserted as required at `ci.yml:665`) errors with "lockfile had changes, but lockfile is frozen" instead of updating it. Net effect: CI fails and the bump is a no-op even locally. Regenerate `bun.lock` (`bun install`) in this PR so the manifest and lockfile agree.
1a20139 to
4dd45ff
Compare
Bumps [@tanstack/react-table](https://github.com/TanStack/table/tree/HEAD/packages/react-table) from 8.21.3 to 9.1.2. - [Release notes](https://github.com/TanStack/table/releases) - [Changelog](https://github.com/TanStack/table/blob/main/packages/react-table/CHANGELOG.md) - [Commits](https://github.com/TanStack/table/commits/@tanstack/react-table@9.1.2/packages/react-table) --- updated-dependencies: - dependency-name: "@tanstack/react-table" dependency-version: 9.1.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Dependabot bumps package.json but does not write bun.lock, so the web gate fails before it builds anything: error: lockfile had changes, but lockfile is frozen Regenerated against this branch rebased on main. 8.21.3 -> 9.1.2 crosses a major, but nothing imports @tanstack/react-table: the only references in the repo are apps/web/package.json and a .next build artifact. The upgrade is inert until something uses it, which also means the dependency is dead weight worth removing separately. Verified: `bun install --frozen-lockfile` exits 0.
4dd45ff to
dfbf663
Compare
1 participant
Bumps @tanstack/react-table from 8.21.3 to 9.1.2.
Release notes
Sourced from @tanstack/react-table's releases.
... (truncated)
Changelog
Sourced from @tanstack/react-table's changelog.
Commits
ff7653dci: Version Packages (#6533)ff43666refactor(table-core): centralize no-op state update guarding in setStateSlice...058a520ci: Version Packages (#6531)3af6abcci: Version Packages (#6527)896e998ci: Version Packages (#6525)10accb2fix(react-table): accept built-in fn names in legacy column helper (#6521)7ec3b90ci: Version Packages (#6513)2327f80release v9 (#6512)d0f2ef7release: version packages (#6510)82c32e0docs: regen docs and fix some typos repo wideMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@tanstack/react-tablesince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)