chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #290 · TanStack/devtools

renovate · 2025-12-15T00:53:46Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@babel/core (source)	`^7.28.4` → `^7.29.0`
@babel/generator (source)	`^7.28.3` → `^7.29.1`
@babel/parser (source)	`^7.28.4` → `^7.29.2`
@babel/traverse (source)	`^7.28.4` → `^7.29.0`
@babel/types (source)	`^7.28.4` → `^7.29.0`
@biomejs/biome (source)	`2.2.4` → `2.4.11`
@cloudflare/vite-plugin (source)	`^1.13.8` → `^1.31.2`
@preact/preset-vite	`^2.10.3` → `^2.10.5`
@solid-primitives/event-listener (source)	`^2.4.3` → `^2.4.5`
@solid-primitives/keyboard (source)	`^1.3.3` → `^1.3.5`
@solid-primitives/resize-observer (source)	`^2.1.3` → `^2.1.5`
@solidjs/start (source)	`^1.2.0` → `^1.3.2`
@tailwindcss/vite (source)	`^4.0.6` → `^4.2.2`
@tanstack/eslint-config (source)	`0.3.2` → `0.4.0`
@tanstack/intent	`^0.0.14` → `^0.0.29`
@tanstack/react-form (source)	`^1.23.7` → `^1.29.0`
@tanstack/react-form-devtools (source)	`^0.1.7` → `^0.2.21`
@tanstack/react-query (source)	`^5.90.1` → `^5.97.0`
@tanstack/react-query-devtools (source)	`^5.90.1` → `^5.97.0`
@tanstack/react-router (source)	`^1.132.0` → `^1.168.13`
@tanstack/react-router-devtools (source)	`^1.132.0` → `^1.166.11`
@tanstack/react-router-ssr-query (source)	`^1.131.7` → `^1.166.10`
@tanstack/react-start (source)	`^1.132.0` → `^1.167.20`
@tanstack/react-store (source)	`^0.9.0` → `^0.10.0`
@tanstack/router-plugin (source)	`^1.132.0` → `^1.167.12`
@tanstack/solid-query (source)	`^5.90.1` → `^5.97.0`
@tanstack/solid-query-devtools (source)	`^5.90.1` → `^5.97.0`
@tanstack/solid-router (source)	`^1.131.50` → `^1.168.12`
@tanstack/solid-router-devtools (source)	`^1.131.50` → `^1.166.11`
@tanstack/store (source)	`^0.9.0` → `^0.10.0`
@tanstack/vite-config (source)	`0.4.3` → `0.5.2`
@tanstack/vue-query (source)	`^5.90.5` → `^5.97.0`
@tanstack/vue-query-devtools (source)	`^6.1.0` → `^6.1.14`
@testing-library/dom	`^10.4.0` → `^10.4.1`
@testing-library/jest-dom	`^6.8.0` → `^6.9.1`
@testing-library/react	`^16.2.0` → `^16.3.2`
@types/picomatch (source)	`^4.0.2` → `^4.0.3`
@types/react (source)	`^19.2.0` → `^19.2.14`
@types/react (source)	`^19.2.0` → `^19.2.14`
@types/react-dom (source)	`^19.2.0` → `^19.2.3`
@vitejs/plugin-vue (source)	`^6.0.1` → `^6.0.5`
axe-core (source)	`^4.10.0` → `^4.11.2`
dayjs (source)	`^1.11.19` → `^1.11.20`
drizzle-kit (source)	`^0.31.4` → `^0.31.10`
drizzle-orm (source)	`^0.44.5` → `^0.45.2`
eslint (source)	`^9.36.0` → `^9.39.4`
eslint-plugin-unused-imports	`^4.2.0` → `^4.4.1`
eslint-plugin-vue (source)	`^10.5.1` → `^10.8.0`
goober	`^2.1.16` → `^2.1.18`
jsdom	`^27.0.0` → `^27.4.0`
knip (source)	`^5.64.0` → `^5.88.1`
launch-editor	`^2.11.1` → `^2.13.2`
lucide-react (source)	`^0.561.0` → `^0.577.0`
markdown-link-extractor	`^4.0.2` → `^4.0.3`
nx (source)	`22.1.3` → `22.6.5`
pg (source)	`^8.16.3` → `^8.20.0`
picomatch	`^4.0.3` → `^4.0.4`
pnpm (source)	`10.24.0` → `10.33.0`
preact (source)	`^10.28.0` → `^10.29.1`
prettier (source)	`^3.8.1` → `^3.8.2`
prettier-plugin-svelte	`^3.4.1` → `^3.5.1`
publint (source)	`^0.3.13` → `^0.3.18`
react (source)	`^19.2.0` → `^19.2.5`
react (source)	`^19.2.0` → `^19.2.5`
react-dom (source)	`^19.2.0` → `^19.2.5`
react-dom (source)	`^19.2.0` → `^19.2.5`
sherif	`^1.7.0` → `^1.11.1`
solid-js (source)	`^1.9.9` → `^1.9.12`
solid-js (source)	`^1.9.9` → `^1.9.12`
sonda (source)	`0.9.0` → `0.11.1`
streamdown (source)	`^1.6.5` → `^1.6.11`
tailwind-merge	`^3.0.2` → `^3.5.0`
tailwindcss (source)	`^4.0.6` → `^4.2.2`
tinyglobby (source)	`^0.2.15` → `^0.2.16`
tsup (source)	`^8.5.0` → `^8.5.1`
tw-animate-css	`^1.3.6` → `^1.4.0`
typescript (source)	`~5.9.2` → `~5.9.3`
vinxi (source)	`^0.5.8` → `^0.5.11`
vite (source)	`^8.0.0` → `^8.0.8`
vite-plugin-mkcert	`^1.17.8` → `^1.17.12`
vite-plugin-solid	`^2.11.11` → `^2.11.12`
vite-tsconfig-paths	`^6.0.2` → `^6.1.1`
vue (source)	`^3.5.22` → `^3.5.32`
web-vitals	`^5.1.0` → `^5.2.0`
wrangler (source)	`^4.40.3` → `^4.81.1`
ws	`^8.18.3` → `^8.20.0`
zod (source)	`^4.3.5` → `^4.3.6`
zustand	`^5.0.8` → `^5.0.12`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.4.11`

Compare Source

Patch Changes

#9350 4af4a3a Thanks @dyc3! - Added the new nursery rule useConsistentTestIt in the test domain. The rule enforces consistent use of either it or test for test functions in Jest/Vitest suites, with separate control for top-level tests and tests inside describe blocks.

Invalid:
```
test("should fly", () => {}); // Top-level test using 'test' flagged, convert to 'it'

describe("pig", () => {
  test("should fly", () => {}); // Test inside 'describe' using 'test' flagged, convert to 'it'
});
```
#9429 a2f3f7e Thanks @ematipico! - Added the new nursery lint rule useExplicitReturnType. It reports TypeScript functions and methods that omit an explicit return type.
```
function toString(x: any) {
  // rule triggered, it doesn't declare a return type
  return x.toString();
}
```
#9828 9e40844 Thanks @ematipico! - Fixed #9484: the formatter no longer panics when formatting files that contain graphql tagged template literals combined with parenthesized expressions.
#9886 e7c681e Thanks @ematipico! - Fixed an issue where, occasionally, some bindings and references were not properly tracked, causing false positives from noUnusedVariables and noUndeclaredVariables in Svelte, Vue, and Astro files.
#9760 5b16d18 Thanks @myx0m0p! - Fixed #4093: the noDelete rule no longer triggers for delete process.env.FOO, since delete is the documented way to remove environment variables in Node.js.
#9799 2af8efd Thanks @minseong0324! - Added the rule noMisleadingReturnType. The rule detects when a function's return type annotation is wider than what the implementation actually returns.
```
// Flagged: `: string` is wider than `"loading" | "idle"`
function getStatus(b: boolean): string {
  if (b) return "loading";
  return "idle";
}
```
#9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useFind to better explain the problem, why it matters, and how to fix it.
#9755 bff7bdb Thanks @ematipico! - Improved performance of fix-all operations (--write). Biome is now smarter when it runs lint rules and assist actions. First, it runs only rules that have code fixes, and then runs the rest of the rules.
#8651 aafca2d Thanks @siketyan! - Add a new lint rule useDisposables for JavaScript, which detects disposable objects assigned to variables without using or await using syntax. Disposable objects that implement the Disposable or AsyncDisposable interface are intended to be disposed of after use. Not disposing them can lead to resource or memory leaks, depending on the implementation.

Invalid:
```
function createDisposable(): Disposable {
  return {
    [Symbol.dispose]() {
      // do something
    },
  };
}

const disposable = createDisposable();
```
Valid:
```
function createDisposable(): Disposable {
  return {
    [Symbol.dispose]() {
      // do something
    },
  };
}

using disposable = createDisposable();
```
#9788 53b8e57 Thanks @MeGaNeKoS! - Fixed #7760: Added support for CSS scroll-driven animation timeline-range-name keyframe selectors (cover, contain, entry, exit, entry-crossing, exit-crossing). Biome no longer reports parse errors on keyframes like entry 0% { ... } or exit 100% { ... }.
#9728 5085424 Thanks @mkosei! - Fixed #9696: Astro frontmatter now correctly parses regular expression literals like /\d{4}/.
#9261 16b6c49 Thanks @ematipico! - Fixed #8409: CSS formatter now correctly places comments after the colon in property declarations.

Previously, comments that appeared after the colon in CSS property values were incorrectly moved before the property name:
```
[lang]:lang(ja) {
-  /* system-ui,*/ font-family:
+  font-family: /* system-ui,*/
    Hiragino Sans,
    sans-serif;
}
```
#9441 957ea4c Thanks @soconnor-seeq! - Fixed #1630: LSP project selection now prefers the most specific project root in nested workspaces.
#9878 de6210f Thanks @ematipico! - Fixed #9118: noUnusedImports no longer reports false positives for default imports used inside Svelte, Vue and Astro components.
#9879 ce7e2b7 Thanks @dyc3! - Fixed a parser diagnostic's message when vue syntax is disabled so that it no longer references the non-existant html.parser.vue option. This option will become available in 2.5.
#9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useRegexpExec to better explain the problem, why it matters, and how to fix it.
#9846 b7134d9 Thanks @ematipico! - Fixed #9140: Biome now parses Astro's attribute shorthand inside .astro files. The following snippet no longer reports a parse error:
```
---
const items = ['a', 'b'];
---
<ul>
  {items.map((item) => <li {item}>row</li>)}
</ul>
```
#9790 67df09d Thanks @dyc3! - Fixed #9781: Trailing comments after a top-level biome-ignore-all format suppression are now preserved instead of being dropped. This applies to JavaScript, CSS, HTML, JSONC, GraphQL, and Grit files.
#9745 d87073e Thanks @ematipico! - Fixed #9741: the LSP server now correctly returns the organizeImports code action when the client requests it via source.organizeImports.biome in the only filter. Previously, editors with codeAction/resolve support (e.g. Zed) received an empty response because the action was serialized with the wrong kind (source.biome.organizeImports instead of source.organizeImports.biome).
#9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useArraySome to better explain the problem, why it matters, and how to fix it.
#9795 1d09f0f Thanks @dyc3! - Relaxed useExplicitType for trivially inferrable types.

Type annotations can now be omitted when types are trivially inferrable from:
- Binary expressions (const sum = 1 + 1)
- Comparison expressions (const isEqual = 'a' === 'b', const isTest = process.env.NODE_ENV === 'test')
- Logical expressions (const and = true && false)
- Class instantiation (const date = new Date())
- Array literals (const arr = [1, 2, 3])
- Conditional expressions (const val = true ? 'yes' : 'no')
- Function calls (const num = Math.random())
- Parameter defaults - any expression is now allowed (const fn = (max = MAX_ATTEMPTS) => ...)
Comparison expressions always return boolean, so any operands are now allowed
(including property access like process.env.NODE_ENV).

Parameters with default values no longer require type annotations, as TypeScript
can infer the type from the default value (even when referencing variables).

Also removed the redundant any type validation from this rule. The any type
is now only validated by the dedicated noExplicitAny rule, following the
Single Responsibility Principle.
#9809 e8cad58 Thanks @Netail! - Added the new nursery rule useQwikLoaderLocation, which enforces that Qwik loader functions are declared in the correct location.
#9877 fc9d715 Thanks @ematipico! - Fixed #9136 and #9653: noUndeclaredVariables and noUnusedVariables no longer report false positives on several Svelte template constructs that declare or reference bindings in the host grammar:
- {#snippet name(params)} — the snippet name and its parameters (including object, array, rest, and nested destructuring) are now tracked.
- {@render name(args)} — the snippet name used at the render site is now resolved against the snippet declaration.
- {#each items as item, index (key)} — the item binding (plain identifier or destructured), the optional index, and the optional key expression are now tracked.
- {@const name = value} — the declared name is now tracked as a binding and the initializer is analyzed for undeclared references.
- {@debug a, b, c} — each debugged identifier is now analyzed and reported if undeclared.
- Shorthand attributes <img {src} /> — the curly-shorthand attribute is now analyzed as an expression, so undeclared references inside it are reported.
For example, the following template no longer triggers either rule:
```
<script>
let items = [];
let total = 0;
</script>

{#snippet figure(image)}
    <figure>
        <img src={image.src} alt={image.caption} />
        <figcaption>{image.caption}</figcaption>
    </figure>
{/snippet}

{#each items as item}
    {@&#8203;const price = item.price}
    {@&#8203;render figure(item)}
    <span>{price}</span>
{/each}

{@&#8203;debug items, total}
```
#9869 78bce77 Thanks @Netail! - Updated noDuplicateFieldDefinitionNames to also flag duplicate fields within type extensions, interface extensions & input extensions.
#9739 0bc2198 Thanks @dyc3! - Fixed Grit queries that use native Biome AST node names with the native field names that are in our .ungram grammar files. Queries such as JsConditionalExpression(consequent = $cons, alternate = $alt) now compile successfully in biome search and grit plugins.
#9811 2dddca3 Thanks @dyc3! - Updated noImpliedEval to flag new Function() usages, as its a form of indirect eval, and to include no-new-func as a rule source.
#9870 ccf9770 Thanks @Netail! - Marked eslint-qwik-plugin's unused-server as redundant since it was covered by noUnusedVariables.
#9701 1417c3b Thanks @dyc3! - Added the new nursery rule noUselessTypeConversion, which reports redundant primitive conversion patterns such as String(value) when value is already a string.
#9248 49f00a3 Thanks @pkallos! - useNullishCoalescing now also detects ternary expressions that check for null or undefined and suggests rewriting them with ??. A new ignoreTernaryTests option allows disabling this behavior.
#9863 6a44619 Thanks @ematipico! - Fixed #9690: biome check --write is now idempotent on HTML files that contain embedded <style> or <script> blocks. Previously, each run reported "Fixed 1 file" even when the file content did not actually change, because the embedded language formatter's output was not re-indented to match the surrounding HTML block.

`v2.4.10`

Compare Source

Patch Changes

#8838 f3a6a6b Thanks @baeseokjae! - Added new lint nursery rule noImpliedEval.

The rule detects implied eval() usage through functions like setTimeout, setInterval, and setImmediate when called with string arguments.
```
// Invalid
setTimeout("alert('Hello');", 100);

// Valid
setTimeout(() => alert("Hello"), 100);
```
#9320 93c3b6c Thanks @taberoajorge! - Fixed #7664: noUnusedVariables no longer reports false positives for TypeScript namespace declarations that participate in declaration merging with an exported or used value declaration (const, function, or class) of the same name. The reverse direction is also handled: a value declaration merged with an exported namespace is no longer flagged.
#9630 [1dd4a56](https://redir

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

changeset-bot · 2025-12-15T00:53:50Z

⚠️ No Changeset found

Latest commit: 346d88c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

nx-cloud · 2025-12-15T00:54:52Z

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

_{To disable these notifications, a workspace admin can disable them in workspace settings.}

View your CI Pipeline Execution ↗ for commit fbd770a

Command	Status	Duration	Result
`nx affected --targets=test:eslint,test:sherif,t...`	❌ Failed	2m 24s	View ↗
`nx run-many --targets=build --exclude=examples/**`	✅ Succeeded	36s	View ↗

☁️ Nx Cloud last updated this comment at 2026-04-10 21:47:12 UTC

pkg-pr-new · 2025-12-15T00:55:04Z

More templates

@tanstack/devtools

npm i https://pkg.pr.new/@tanstack/devtools@290

@tanstack/devtools-a11y

npm i https://pkg.pr.new/@tanstack/devtools-a11y@290

@tanstack/devtools-client

npm i https://pkg.pr.new/@tanstack/devtools-client@290

@tanstack/devtools-ui

npm i https://pkg.pr.new/@tanstack/devtools-ui@290

@tanstack/devtools-utils

npm i https://pkg.pr.new/@tanstack/devtools-utils@290

@tanstack/devtools-vite

npm i https://pkg.pr.new/@tanstack/devtools-vite@290

@tanstack/devtools-event-bus

npm i https://pkg.pr.new/@tanstack/devtools-event-bus@290

@tanstack/devtools-event-client

npm i https://pkg.pr.new/@tanstack/devtools-event-client@290

@tanstack/preact-devtools

npm i https://pkg.pr.new/@tanstack/preact-devtools@290

@tanstack/react-devtools

npm i https://pkg.pr.new/@tanstack/react-devtools@290

@tanstack/solid-devtools

npm i https://pkg.pr.new/@tanstack/solid-devtools@290

@tanstack/vue-devtools

npm i https://pkg.pr.new/@tanstack/vue-devtools@290

commit: fbd770a

coderabbitai · 2026-03-13T02:05:18Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

📝 Walkthrough

Walkthrough

Updated GitHub Actions workflows and bumped dependency/devDependency versions across root, packages, and example projects; no source code logic or exported API signatures were changed.

Changes

Cohort / File(s)	Summary
GitHub Actions workflows `\.github/workflows/autofix.yml`, `\.github/workflows/pr.yml`, `\.github/workflows/release.yml`	Bumped `actions/checkout` from `v6.0.1` → `v6.0.2`. `release.yml` also updated `changesets/action` to `v1.7.0` and added commit/title and `GITHUB_TOKEN` to the Run Changesets step.
Root workspace `package.json`	Updated `packageManager` to `pnpm@10.32.1` and bumped numerous devDependencies (changesets CLI, eslint, nx, typescript, vite, tooling configs, testing and linting tools).
Core devtools packages `packages/devtools/package.json`, `packages/devtools-ui/package.json`, `packages/devtools-utils/package.json`, `packages/devtools-vite/package.json`, `packages/event-bus/package.json`	Runtime and tooling dependency bumps (solid-js, goober, dayjs, ws, tsup, vite-plugin-solid, Babel libs, launch-editor, etc.).
Framework-specific devtools `packages/preact-devtools/package.json`, `packages/react-devtools/package.json`, `packages/solid-devtools/package.json`, `packages/vue-devtools/package.json`	Updated framework/runtime and tooling versions (preact, react, solid-js, vue, typings, Vite plugins, eslint plugin for Vue).
Examples — React `examples/react/.../package.json`	Wide dependency upgrades across TanStack packages, React, react-dom, typings, Vite plugins and other tooling; consistent version bumps across many React examples (including specialized examples like drizzle, start, bundling-repro).
Examples — Solid / Preact / Vue `examples/solid/.../package.json`, `examples/preact/.../package.json`, `examples/vue/basic/package.json`	Framework and tooling version bumps (solid-js, `@solidjs/start`, preact, vite, vite-plugin-solid, `@vitejs/plugin-vue`, `@tanstack/vue-query`, etc.).
Misc examples & smaller bumps `examples/preact/.../package.json`, `examples/.../*`	Smaller dependency/devDependency increments in other example projects (zod, sonda, vite, vite plugins, sonda, tailwind-related, zustand, drizzle tooling).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped through versions, bright and quick,
nudged checkout, bumped a patch or tick.
Examples polished, workflows tuned,
tiny hops and changes pruned. 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is a Renovate-generated dependency update report with a comprehensive table of package changes, but it lacks clear context about the motivation, testing, or release impact.	Add a brief explanation of why these updates are being made (e.g., security, performance, features) and confirm that 'pnpm test:pr' has been run locally as specified in the repository template.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title accurately describes the PR's primary objective: updating all non-major dependencies across the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch renovate/all-minor-patch

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

🧹 Nitpick comments (1)

examples/react/bundling-repro/package.json (1)
18-26: Consider pinning @tanstack/ai-* packages to specific versions.

Using "latest" for these AI packages means builds are non-reproducible and could break unexpectedly when new versions are published. While acceptable for a repro/debugging example, consider pinning to specific versions if this example is used for CI or regression testing.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@examples/react/bundling-repro/package.json` around lines 18 - 26, The
package.json currently pins multiple `@tanstack/ai` packages to "latest" which
makes builds unreproducible; replace the "latest" specifiers for "@tanstack/ai",
"@tanstack/ai-anthropic", "@tanstack/ai-client", "@tanstack/ai-gemini",
"@tanstack/ai-ollama", "@tanstack/ai-openai", "@tanstack/ai-react",
"@tanstack/react-ai-devtools", and "@tanstack/react-devtools" with concrete
version numbers (choose a specific semver like "^X.Y.Z" or an exact "X.Y.Z") to
lock dependencies for CI/regression tests and update the lockfile accordingly.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@examples/react/bundling-repro/package.json`:
- Around line 18-26: The package.json currently pins multiple `@tanstack/ai`
packages to "latest" which makes builds unreproducible; replace the "latest"
specifiers for "@tanstack/ai", "@tanstack/ai-anthropic", "@tanstack/ai-client",
"@tanstack/ai-gemini", "@tanstack/ai-ollama", "@tanstack/ai-openai",
"@tanstack/ai-react", "@tanstack/react-ai-devtools", and
"@tanstack/react-devtools" with concrete version numbers (choose a specific
semver like "^X.Y.Z" or an exact "X.Y.Z") to lock dependencies for CI/regression
tests and update the lockfile accordingly.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de66d22c-d3cb-4f54-a7b2-387035694052

📥 Commits

Reviewing files that changed from the base of the PR and between a120650 and 11e75ba.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (26)

.github/workflows/autofix.yml
.github/workflows/pr.yml
.github/workflows/release.yml
examples/preact/basic/package.json
examples/preact/custom-devtools/package.json
examples/react/basic/package.json
examples/react/bundling-repro/package.json
examples/react/custom-devtools/package.json
examples/react/drizzle/package.json
examples/react/https/package.json
examples/react/start/package.json
examples/react/time-travel/package.json
examples/solid/basic/package.json
examples/solid/devtools-ui/package.json
examples/solid/start/package.json
examples/vue/basic/package.json
package.json
packages/devtools-ui/package.json
packages/devtools-utils/package.json
packages/devtools-vite/package.json
packages/devtools/package.json
packages/event-bus/package.json
packages/preact-devtools/package.json
packages/react-devtools/package.json
packages/solid-devtools/package.json
packages/vue-devtools/package.json

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release.yml:
- Line 26: Replace mutable action references like uses: actions/checkout@v6.0.2
with the immutable commit SHA form (e.g., uses:
actions/checkout@<FULL_COMMIT_SHA>) while preserving the human-friendly tag as a
trailing comment (e.g., # v6.0.2) to maintain readability; update the checkout
usages in the release workflow (the uses: actions/checkout entries) and apply
the same SHA-pinning pattern to the checkout actions referenced in pr.yml (the
uses: actions/checkout entries on the other specified lines).

In `@package.json`:
- Around line 62-65: The `@tanstack` package upgrades introduce breaking changes:
update our build/docs configs accordingly by (1) in typedoc-related code/configs
(search for any Typedoc config files or usages that expect lower-cased output)
remove or adjust any post-processing that lower-cases Typedoc output and ensure
templates/consumers accept the new casing produced by `@tanstack/typedoc-config`
v0.3.3, and (2) in vite.config.ts (look for references to viteConfig or imports
from `@tanstack/vite-config`) migrate the old viteConfig usage to the new shape:
upgrade to Vite 8+ if not already and replace viteConfig options with
rolldownOptions and use the new native resolve.tsconfigPaths behavior (update
imports, option names, and any tsconfig path resolution code). Make these
changes where viteConfig and Typedoc config objects are defined so the project
builds and docs generate correctly with the new `@tanstack` versions.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3e3729bd-9872-4d23-b9a5-164d848e5c26

📥 Commits

Reviewing files that changed from the base of the PR and between 11e75ba and b24a560.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (26)

.github/workflows/autofix.yml
.github/workflows/pr.yml
.github/workflows/release.yml
examples/preact/basic/package.json
examples/preact/custom-devtools/package.json
examples/react/basic/package.json
examples/react/bundling-repro/package.json
examples/react/custom-devtools/package.json
examples/react/drizzle/package.json
examples/react/https/package.json
examples/react/start/package.json
examples/react/time-travel/package.json
examples/solid/basic/package.json
examples/solid/devtools-ui/package.json
examples/solid/start/package.json
examples/vue/basic/package.json
package.json
packages/devtools-ui/package.json
packages/devtools-utils/package.json
packages/devtools-vite/package.json
packages/devtools/package.json
packages/event-bus/package.json
packages/preact-devtools/package.json
packages/react-devtools/package.json
packages/solid-devtools/package.json
packages/vue-devtools/package.json

🚧 Files skipped from review as they are similar to previous changes (17)

examples/react/time-travel/package.json
packages/preact-devtools/package.json
packages/devtools/package.json
packages/devtools-ui/package.json
packages/devtools-utils/package.json
packages/react-devtools/package.json
examples/solid/devtools-ui/package.json
packages/solid-devtools/package.json
.github/workflows/autofix.yml
examples/solid/basic/package.json
packages/vue-devtools/package.json
examples/react/basic/package.json
examples/vue/basic/package.json
examples/preact/basic/package.json
packages/devtools-vite/package.json
examples/preact/custom-devtools/package.json
examples/react/start/package.json

coderabbitai · 2026-03-13T11:08:27Z

.github/workflows/release.yml

    steps:
      - name: Checkout
-        uses: actions/checkout@v6.0.1
+        uses: actions/checkout@v6.0.2


⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash set -euo pipefail echo "Unpinned GitHub Actions references in workflows:" rg -nP '^\s*uses:\s*[^@]+@(?![0-9a-f]{40}\b)\S+' .github/workflows echo echo "Resolve immutable SHAs for tags touched in this PR:" for item in "actions/checkout v6.0.2" "changesets/action v1.7.0"; do repo=$(awk '{print $1}' <<<"$item") tag=$(awk '{print $2}' <<<"$item") sha=$(git ls-remote --refs --tags "https://github.com/${repo}.git" \ "refs/tags/${tag}" "refs/tags/${tag}^{}" | awk 'END{print $1}') printf "%s@%s -> %s\n" "$repo" "$tag" "$sha" done

Repository: TanStack/devtools

Length of output: 1721

Pin GitHub Actions to immutable commit SHAs.

Lines 26 and 34 use mutable version tags. Pinning to full commit SHAs improves CI integrity and provenance; keep the tag as a trailing comment for readability. Apply the same pattern to all checkout actions in .github/workflows/pr.yml (lines 26, 42, and 56).

Suggested changes

- uses: actions/checkout@v6.0.2 + uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2 ... - uses: changesets/action@v1.7.0 + uses: changesets/action@e87c8ed249971350e47fab7515075f44eb134e5b # v1.7.0

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

uses: actions/checkout@v6.0.2

uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In @.github/workflows/release.yml at line 26, Replace mutable action references like uses: actions/checkout@v6.0.2 with the immutable commit SHA form (e.g., uses: actions/checkout@<FULL_COMMIT_SHA>) while preserving the human-friendly tag as a trailing comment (e.g., # v6.0.2) to maintain readability; update the checkout usages in the release workflow (the uses: actions/checkout entries) and apply the same SHA-pinning pattern to the checkout actions referenced in pr.yml (the uses: actions/checkout entries on the other specified lines).

coderabbitai · 2026-03-13T11:08:28Z

package.json

+    "@tanstack/eslint-config": "0.4.0",
    "@tanstack/intent": "^0.0.14",
-    "@tanstack/typedoc-config": "0.2.1",
-    "@tanstack/vite-config": "0.2.1",
-    "@testing-library/jest-dom": "^6.8.0",
+    "@tanstack/typedoc-config": "0.3.3",
+    "@tanstack/vite-config": "0.5.0",


⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

`What are the breaking changes (if any) between:

@tanstack/eslint-config 0.3.2 -> 0.4.0

@tanstack/typedoc-config 0.2.1 -> 0.3.3

@tanstack/vite-config 0.2.1 -> 0.5.0
Please cite official release notes/changelogs.`

💡 Result:

1) @tanstack/eslint-config 0.3.2 → 0.4.0

No explicit BREAKING change is called out in the release notes; the only noted change is: “update to @eslint/js v10”. [1]

However, the official docs for this config state you must have ESLint v9+ installed, which may be a practical breaking requirement if you were on ESLint 8. [2]

2) @tanstack/typedoc-config 0.2.1 → 0.3.3

Breaking change introduced in 0.3.0: upgrade to TypeDoc v0.28, and “typedoc output is no longer lower-cased” (marked BREAKING in the release notes). [3]

0.3.3 is a patch release (“migrate to tsdown”) and does not list breaking changes. [4]

3) @tanstack/vite-config 0.2.1 → 0.5.0

0.3.0: update to Vite v7 (major Vite bump; not labeled breaking in the release note, but it is a major underlying dependency change). [5]

0.4.0: “support for bundling dependencies” (not labeled breaking). [6]

Breaking change in 0.5.0: “Bump to Vite 8 with Rolldown. Drops Vite 6/7 support. Switches to rolldownOptions and native resolve.tsconfigPaths.” [7]

Sources (official release notes/docs): GitHub Releases for TanStack/config and TanStack Config docs. [1][2][3][4][5][6][7]

Address breaking changes in upgraded @tanstack config packages before merge.

Lines 62–65 upgrade three @tanstack config packages with 0.x minor bumps that introduce breaking changes:

@tanstack/typedoc-config (0.2.1 → 0.3.3): Breaking change in 0.3.0 — "typedoc output is no longer lower-cased" (output format changed).

@tanstack/vite-config (0.2.1 → 0.5.0): Breaking change in 0.5.0 — drops support for Vite 6/7, requires Vite 8+, and switches configuration from viteConfig to rolldownOptions with native resolve.tsconfigPaths.

These upgrades require corresponding changes to the codebase configuration (especially vite.config.ts). Verify and apply necessary config adjustments before merging.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@package.json` around lines 62 - 65, The `@tanstack` package upgrades introduce breaking changes: update our build/docs configs accordingly by (1) in typedoc-related code/configs (search for any Typedoc config files or usages that expect lower-cased output) remove or adjust any post-processing that lower-cases Typedoc output and ensure templates/consumers accept the new casing produced by `@tanstack/typedoc-config` v0.3.3, and (2) in vite.config.ts (look for references to viteConfig or imports from `@tanstack/vite-config`) migrate the old viteConfig usage to the new shape: upgrade to Vite 8+ if not already and replace viteConfig options with rolldownOptions and use the new native resolve.tsconfigPaths behavior (update imports, option names, and any tsconfig path resolution code). Make these changes where viteConfig and Typedoc config objects are defined so the project builds and docs generate correctly with the new `@tanstack` versions.

coderabbitai

♻️ Duplicate comments (2)

.github/workflows/release.yml (1)

26-34: ⚠️ Potential issue | 🟠 Major

Pin GitHub Actions to immutable SHAs instead of mutable tags.

Line 26 and Line 34 still use mutable tags (v6.0.2, v1.7.0). Please pin to full commit SHAs (keep tag as inline comment) to reduce supply-chain risk. This also applies to matching checkout entries in .github/workflows/pr.yml.

#!/bin/bash
set -euo pipefail

echo "Mutable action refs in workflows:"
rg -nP '^\s*uses:\s*[^@]+@(?![0-9a-f]{40}\b)\S+' .github/workflows

echo
echo "Resolve immutable SHAs for tags touched here:"
for item in "actions/checkout v6.0.2" "changesets/action v1.7.0"; do
  repo=$(awk '{print $1}' <<<"$item")
  tag=$(awk '{print $2}' <<<"$item")
  sha=$(git ls-remote --refs --tags "https://github.com/${repo}.git" \
    "refs/tags/${tag}" "refs/tags/${tag}^{}" | awk 'END{print $1}')
  printf "%s@%s -> %s\n" "$repo" "$tag" "$sha"
done

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/release.yml around lines 26 - 34, Replace mutable action
refs with immutable commit SHAs: for each uses entry shown
(actions/checkout@v6.0.2 and changesets/action@v1.7.0, and any other mutable
refs like tanstack/config/.github/setup@main), resolve the tag to its full
40-char commit SHA (e.g., via git ls-remote or the repo's tags API) and update
the uses value to repo@<full-sha>, keeping the original tag as an inline comment
for readability; also mirror these exact SHA-pinned changes for the matching
checkout/uses entries in the pr.yml workflow so all workflow invocations use
immutable SHAs.

package.json (1)

62-65: ⚠️ Potential issue | 🟠 Major

Re-verify breaking config implications for upgraded @tanstack config packages.

Line 65 (@tanstack/vite-config@0.5.0) alongside Line 82 (vite@^7.3.1) may be incompatible depending on current config usage. Line 64 (@tanstack/typedoc-config@0.3.3) can also require doc pipeline adjustments. Please confirm required migrations are already applied before merge.

#!/bin/bash
set -euo pipefail

echo "1) Find usages of `@tanstack/vite-config` and old/new option names:"
rg -nP --type=ts --type=js --type=json \
  '@tanstack/vite-config|viteConfig|rolldownOptions|resolve\.tsconfigPaths'

echo
echo "2) Find typedoc config usage and possible output-casing assumptions:"
rg -nP --type=ts --type=js --type=json \
  '@tanstack/typedoc-config|typedoc|toLowerCase\(|lower-?case'

echo
echo "3) Show vite versions pinned across manifests:"
rg -nP '"vite"\s*:\s*"[^"]+"' --glob '**/package.json'

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 62 - 65, Upgrade of `@tanstack` packages may
introduce breaking config/name changes; re-verify and apply migrations for
`@tanstack/vite-config` (0.5.0) vs vite@^7.3.1 and `@tanstack/typedoc-config`
(0.3.3). Search the repo for usages of '@tanstack/vite-config', 'viteConfig',
'rollupOptions', and 'resolve.tsconfigPaths' and update any renamed options or
import paths in your Vite config (e.g., viteConfig-related exports), verify vite
plugin/api compatibility or pin/bump vite accordingly, and search for
'@tanstack/typedoc-config', 'typedoc' and any case-transforming assumptions
(toLowerCase / lower-case) to update the typedoc pipeline or output casing.
After making changes, run the project build/tests and lockfile update to ensure
no runtime errors and include migration notes in the PR.

🧹 Nitpick comments (1)

examples/react/bundling-repro/package.json (1)
50-65: Consider adding a engines.node field to improve tooling compatibility.

The repository and all example packages lack Node version constraints. With Vite ^7.3.1 and Wrangler ^4.73.0 in bundling-repro, and no explicit Node version pinning in CI workflows (pr.yml, release.yml), adding engines.node to the root or example package.json files would make local and CI behavior more deterministic.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@examples/react/bundling-repro/package.json` around lines 50 - 65, Add an
engines.node field to the package.json (root or this example) to pin a supported
Node range for Vite and Wrangler; for example target the current LTS used by
those tools (e.g., Node 18.x — something like ">=18.16.0 <21") so local/dev/CI
environments are deterministic. Update the package.json containing Vite and
Wrangler (the file shown in the diff) to include that engines.node range, and
mirror that constraint in CI workflows (pr.yml, release.yml) or GitHub Actions
matrix so pipelines use a matching Node version; run the install/test matrix
locally or in CI to verify compatibility.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In @.github/workflows/release.yml:
- Around line 26-34: Replace mutable action refs with immutable commit SHAs: for
each uses entry shown (actions/checkout@v6.0.2 and changesets/action@v1.7.0, and
any other mutable refs like tanstack/config/.github/setup@main), resolve the tag
to its full 40-char commit SHA (e.g., via git ls-remote or the repo's tags API)
and update the uses value to repo@<full-sha>, keeping the original tag as an
inline comment for readability; also mirror these exact SHA-pinned changes for
the matching checkout/uses entries in the pr.yml workflow so all workflow
invocations use immutable SHAs.

In `@package.json`:
- Around line 62-65: Upgrade of `@tanstack` packages may introduce breaking
config/name changes; re-verify and apply migrations for `@tanstack/vite-config`
(0.5.0) vs vite@^7.3.1 and `@tanstack/typedoc-config` (0.3.3). Search the repo for
usages of '@tanstack/vite-config', 'viteConfig', 'rollupOptions', and
'resolve.tsconfigPaths' and update any renamed options or import paths in your
Vite config (e.g., viteConfig-related exports), verify vite plugin/api
compatibility or pin/bump vite accordingly, and search for
'@tanstack/typedoc-config', 'typedoc' and any case-transforming assumptions
(toLowerCase / lower-case) to update the typedoc pipeline or output casing.
After making changes, run the project build/tests and lockfile update to ensure
no runtime errors and include migration notes in the PR.

---

Nitpick comments:
In `@examples/react/bundling-repro/package.json`:
- Around line 50-65: Add an engines.node field to the package.json (root or this
example) to pin a supported Node range for Vite and Wrangler; for example target
the current LTS used by those tools (e.g., Node 18.x — something like ">=18.16.0
<21") so local/dev/CI environments are deterministic. Update the package.json
containing Vite and Wrangler (the file shown in the diff) to include that
engines.node range, and mirror that constraint in CI workflows (pr.yml,
release.yml) or GitHub Actions matrix so pipelines use a matching Node version;
run the install/test matrix locally or in CI to verify compatibility.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e678879d-8d9a-43d3-ba5e-e0fa5aebf4bb

📥 Commits

Reviewing files that changed from the base of the PR and between b24a560 and d2763b0.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (26)

.github/workflows/autofix.yml
.github/workflows/pr.yml
.github/workflows/release.yml
examples/preact/basic/package.json
examples/preact/custom-devtools/package.json
examples/react/basic/package.json
examples/react/bundling-repro/package.json
examples/react/custom-devtools/package.json
examples/react/drizzle/package.json
examples/react/https/package.json
examples/react/start/package.json
examples/react/time-travel/package.json
examples/solid/basic/package.json
examples/solid/devtools-ui/package.json
examples/solid/start/package.json
examples/vue/basic/package.json
package.json
packages/devtools-ui/package.json
packages/devtools-utils/package.json
packages/devtools-vite/package.json
packages/devtools/package.json
packages/event-bus/package.json
packages/preact-devtools/package.json
packages/react-devtools/package.json
packages/solid-devtools/package.json
packages/vue-devtools/package.json

🚧 Files skipped from review as they are similar to previous changes (14)

examples/react/drizzle/package.json
examples/solid/start/package.json
packages/devtools-ui/package.json
packages/solid-devtools/package.json
examples/solid/basic/package.json
examples/vue/basic/package.json
packages/preact-devtools/package.json
packages/devtools/package.json
examples/react/https/package.json
examples/preact/custom-devtools/package.json
packages/event-bus/package.json
packages/devtools-vite/package.json
.github/workflows/autofix.yml
examples/react/custom-devtools/package.json

coderabbitai

♻️ Duplicate comments (1)

package.json (1)
62-65: ⚠️ Potential issue | 🟠 Major

Verify Vite version compatibility with @tanstack/vite-config 0.5.0.

The past review correctly identified that @tanstack/vite-config 0.5.0 requires Vite 8+ and drops support for Vite 6/7. However, this PR updates vite to ^7.3.1 (Line 82), which would be incompatible with @tanstack/vite-config 0.5.0.

Either:

Upgrade vite to ^8.x to match the requirements of @tanstack/vite-config 0.5.0, or

Pin @tanstack/vite-config to a version compatible with Vite 7 (e.g., 0.4.x)

Also applies to: 82-82
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 62 - 65, The package version mismatch:
"@tanstack/vite-config"@0.5.0 requires Vite 8+, but this PR sets "vite" to
"^7.3.1"; update package.json so versions are compatible by either (A) bumping
"vite" to a 8.x version (e.g., "^8.0.0") to match "@tanstack/vite-config"@0.5.0,
or (B) pinning "@tanstack/vite-config" to a Vite-7-compatible release (e.g.,
"0.4.x"); pick one approach and make the corresponding change to the dependency
entry for "vite" or "@tanstack/vite-config" so the two packages are aligned.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@package.json`:
- Around line 62-65: The package version mismatch: "@tanstack/vite-config"@0.5.0
requires Vite 8+, but this PR sets "vite" to "^7.3.1"; update package.json so
versions are compatible by either (A) bumping "vite" to a 8.x version (e.g.,
"^8.0.0") to match "@tanstack/vite-config"@0.5.0, or (B) pinning
"@tanstack/vite-config" to a Vite-7-compatible release (e.g., "0.4.x"); pick one
approach and make the corresponding change to the dependency entry for "vite" or
"@tanstack/vite-config" so the two packages are aligned.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 03c422c2-f992-4780-bceb-2f7fb298b00e

📥 Commits

Reviewing files that changed from the base of the PR and between d2763b0 and 7f1f126.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (29)

.github/workflows/autofix.yml
.github/workflows/pr.yml
.github/workflows/release.yml
examples/preact/basic/package.json
examples/preact/custom-devtools/package.json
examples/react/a11y-devtools/package.json
examples/react/basic/package.json
examples/react/bundling-repro/package.json
examples/react/custom-devtools/package.json
examples/react/drizzle/package.json
examples/react/https/package.json
examples/react/start/package.json
examples/react/time-travel/package.json
examples/solid/a11y-devtools/package.json
examples/solid/basic/package.json
examples/solid/devtools-ui/package.json
examples/solid/start/package.json
examples/vue/basic/package.json
package.json
packages/devtools-a11y/package.json
packages/devtools-ui/package.json
packages/devtools-utils/package.json
packages/devtools-vite/package.json
packages/devtools/package.json
packages/event-bus/package.json
packages/preact-devtools/package.json
packages/react-devtools/package.json
packages/solid-devtools/package.json
packages/vue-devtools/package.json

🚧 Files skipped from review as they are similar to previous changes (13)

packages/devtools-vite/package.json
packages/event-bus/package.json
packages/devtools-utils/package.json
packages/vue-devtools/package.json
examples/react/start/package.json
examples/solid/devtools-ui/package.json
examples/solid/start/package.json
examples/react/https/package.json
packages/devtools/package.json
examples/react/drizzle/package.json
examples/solid/basic/package.json
examples/preact/basic/package.json
packages/devtools-ui/package.json

github-actions · 2026-03-17T13:58:45Z

🚀 Changeset Version Preview

No changeset entries found. Merging this PR will not cause a version bump for any packages.

renovate bot added the dependencies label Dec 15, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 26 times, most recently from 8f5167e to 09c56be Compare December 20, 2025 17:05

renovate bot force-pushed the renovate/all-minor-patch branch 23 times, most recently from e861232 to 4b90eb1 Compare December 30, 2025 21:54

coderabbitai bot reviewed Mar 13, 2026

View reviewed changes

chore(deps): update all non-major dependencies

fbd770a

	uses: actions/checkout@v6.0.2
	uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2

Uh oh!

Conversation

renovate bot commented Dec 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.4.11

Patch Changes

v2.4.10

Patch Changes

Configuration

Uh oh!

changeset-bot bot commented Dec 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

nx-cloud bot commented Dec 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 Nx Cloud AI Fix Eligible

Uh oh!

pkg-pr-new bot commented Dec 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai bot commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Estimated code review effort

Poem

❌ Failed checks (1 inconclusive)

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Mar 13, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Mar 13, 2026

Choose a reason for hiding this comment

1) @tanstack/eslint-config 0.3.2 → 0.4.0

2) @tanstack/typedoc-config 0.2.1 → 0.3.3

3) @tanstack/vite-config 0.2.1 → 0.5.0

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 Changeset Version Preview

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Dec 15, 2025 •

edited

Loading

`v2.4.11`

`v2.4.10`

changeset-bot bot commented Dec 15, 2025 •

edited

Loading

nx-cloud bot commented Dec 15, 2025 •

edited

Loading

pkg-pr-new bot commented Dec 15, 2025 •

edited

Loading

coderabbitai bot commented Mar 13, 2026 •

edited

Loading

1) `@tanstack/eslint-config` 0.3.2 → 0.4.0

2) `@tanstack/typedoc-config` 0.2.1 → 0.3.3

3) `@tanstack/vite-config` 0.2.1 → 0.5.0

github-actions bot commented Mar 17, 2026 •

edited

Loading