chore(deps): update all non-major dependencies - #290
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
⚠️ No Changeset foundLatest 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 changesetsWhen 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 |
Sorry, something went wrong.
Copy link
Copy Markdown
|
| Command | Status | Duration | Result |
|---|---|---|---|
| nx affected --targets=test:eslint,test:sherif,t... | ❌ Failed | 2m 56s | View ↗ |
| nx run-many --targets=build --exclude=examples/** | ✅ Succeeded | 39s | View ↗ |
☁️ Nx Cloud last updated this comment at 2026-05-11 20:36:30 UTC
Sorry, something went wrong.
Copy link
Copy Markdown
|
More templates
npm i https://pkg.pr.new/@tanstack/angular-devtools@290
npm i https://pkg.pr.new/@tanstack/devtools@290
npm i https://pkg.pr.new/@tanstack/devtools-a11y@290
npm i https://pkg.pr.new/@tanstack/devtools-client@290
npm i https://pkg.pr.new/@tanstack/devtools-ui@290
npm i https://pkg.pr.new/@tanstack/devtools-utils@290
npm i https://pkg.pr.new/@tanstack/devtools-vite@290
npm i https://pkg.pr.new/@tanstack/devtools-event-bus@290
npm i https://pkg.pr.new/@tanstack/devtools-event-client@290
npm i https://pkg.pr.new/@tanstack/preact-devtools@290
npm i https://pkg.pr.new/@tanstack/react-devtools@290
npm i https://pkg.pr.new/@tanstack/solid-devtools@290
npm i https://pkg.pr.new/@tanstack/vue-devtools@290 commit: 5aa3587 |
Sorry, something went wrong.
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
21 times, most recently
from
e861232 to
4b90eb1
Compare
December 30, 2025 21:54
Copy link
Copy Markdown
|
Important Review skippedBot user detected. To trigger a single review, invoke the @coderabbitai review command. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: b81b48db-9e74-465c-90ed-81ea1a3e3717 You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file. Use the checkbox below for a quick retry:
Note Reviews pausedIt 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:
Use the checkboxes below for quick actions:
WalkthroughUpdated 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
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem🚥 Pre-merge checks | ✅ 2 | ❌ 1 ❌ Failed checks (1 warning)
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. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
Copy link
Copy Markdown
There was a problem hiding this comment.
🧹 Nitpick comments (1)
ℹ️ Review info ⚙️ Run configuration
examples/react/bundling-repro/package.json (1)🤖 Prompt for all review comments with AI agents18-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 AgentsVerify 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.
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
📥 CommitsReviewing 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
- .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
Sorry, something went wrong.
Copy link
Copy Markdown
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agentsVerify 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
📥 CommitsReviewing 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
- .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
- 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
Sorry, something went wrong.
Comment thread
.github/workflows/release.yml
Outdated
Comment thread
package.json
Outdated
Comment on lines
+62
to
+65
| "@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", |
Copy link
Copy Markdown
There was a problem hiding this comment.
⚠️ 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 AgentsVerify 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.
Sorry, something went wrong.
Copy link
Copy Markdown
There was a problem hiding this comment.
♻️ Duplicate comments (2)
ℹ️ Review info ⚙️ Run configuration
.github/workflows/release.yml (1)🧹 Nitpick comments (1)package.json (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.
🤖 Prompt for AI Agents#!/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" doneVerify 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.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.
🤖 Prompt for AI Agents#!/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'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.
examples/react/bundling-repro/package.json (1)🤖 Prompt for all review comments with AI agents50-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 AgentsVerify 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.
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
📥 CommitsReviewing 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
- .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
- 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
Sorry, something went wrong.
Copy link
Copy Markdown
There was a problem hiding this comment.
♻️ Duplicate comments (1)
ℹ️ Review info ⚙️ Run configuration
package.json (1)🤖 Prompt for all review comments with AI agents62-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 AgentsVerify 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.
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
📥 CommitsReviewing 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
- .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
- 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
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
🚀 Changeset Version Preview3 package(s) bumped directly, 11 bumped as dependents. 🟨 Minor bumps
🟩 Patch bumps
|
Sorry, something went wrong.
Copy link
Copy Markdown
|
Only repository collaborators, contributors, or members can run CodeRabbit commands. |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
⚠️ Artifact update problemRenovate failed to update artifacts 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:
The artifact failure details are included below: File name: pnpm-lock.yamlScope: all 49 workspace projects ? Verifying lockfile against supply-chain policies (2234 entries)... [WARN] Request took 10293ms: https://registry.npmjs.org/@eslint-react%2Fast [WARN] Request took 10324ms: https://registry.npmjs.org/@eslint-react%2Fvar [WARN] Request took 10739ms: https://registry.npmjs.org/@eslint-react%2Fshared [WARN] Request took 11027ms: https://registry.npmjs.org/@eslint-react%2Fcore [WARN] Request took 13933ms: https://registry.npmjs.org/@eslint-react%2Feslint-plugin [WARN] Request took 11089ms: https://registry.npmjs.org/@typescript-eslint%2Fvisitor-keys [WARN] Request took 11956ms: https://registry.npmjs.org/@typescript-eslint%2Fscope-manager [WARN] Request took 15693ms: https://registry.npmjs.org/@playwright%2Ftest [WARN] Request took 15365ms: https://registry.npmjs.org/@typescript-eslint%2Fparser [WARN] Request took 16591ms: https://registry.npmjs.org/@typescript-eslint%2Ftypescript-estree [WARN] Request took 18329ms: https://registry.npmjs.org/@typescript-eslint%2Feslint-plugin [WARN] Request took 10560ms: https://registry.npmjs.org/eslint-plugin-react-web-api [WARN] Request took 18184ms: https://registry.npmjs.org/@types%2Fnode [WARN] Request took 11238ms: https://registry.npmjs.org/eslint-plugin-react-hooks-extra [WARN] Request took 11980ms: https://registry.npmjs.org/eslint-plugin-react-x [WARN] Request took 12609ms: https://registry.npmjs.org/eslint-plugin-react-dom [WARN] Request took 16449ms: https://registry.npmjs.org/@typescript-eslint%2Ftype-utils [WARN] Request took 13059ms: https://registry.npmjs.org/eslint-plugin-react-debug [WARN] Request took 13840ms: https://registry.npmjs.org/eslint-plugin-react-naming-convention [WARN] Request took 16501ms: https://registry.npmjs.org/axe-core [WARN] Request took 18409ms: https://registry.npmjs.org/@typescript-eslint%2Futils [WARN] Request took 13443ms: https://registry.npmjs.org/eslint-plugin-react-hooks [WARN] Request took 10292ms: https://registry.npmjs.org/miniflare [WARN] Request took 14146ms: https://registry.npmjs.org/playwright [WARN] Request took 14434ms: https://registry.npmjs.org/playwright-core [WARN] Request took 20220ms: https://registry.npmjs.org/@typescript-eslint%2Ftypes [WARN] Request took 19769ms: https://registry.npmjs.org/@typescript-eslint%2Fvisitor-keys [WARN] Request took 19711ms: https://registry.npmjs.org/@typescript-eslint%2Fscope-manager [WARN] Request took 11351ms: https://registry.npmjs.org/typescript [WARN] Request took 10970ms: https://registry.npmjs.org/react-dom [WARN] Request took 18019ms: https://registry.npmjs.org/@typescript-eslint%2Fparser [WARN] Request took 17621ms: https://registry.npmjs.org/@typescript-eslint%2Ftypescript-estree [WARN] Request took 10506ms: https://registry.npmjs.org/nx [WARN] Request took 17423ms: https://registry.npmjs.org/@typescript-eslint%2Feslint-plugin [WARN] Request took 10973ms: https://registry.npmjs.org/wrangler [WARN] Request took 11641ms: https://registry.npmjs.org/vite [WARN] Request took 32985ms: https://registry.npmjs.org/drizzle-orm ✗ Lockfile failed supply-chain policy check (2234 entries in 1m 3.4s) [ERR_PNPM_TRUST_DOWNGRADE] 5 lockfile entries failed verification: chokidar@4.0.3 High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover) semver@5.7.2 High-risk trust downgrade for "semver@5.7.2" (possible package takeover) semver@6.3.1 High-risk trust downgrade for "semver@6.3.1" (possible package takeover) undici-types@6.21.0 High-risk trust downgrade for "undici-types@6.21.0" (possible package takeover) vite@6.4.1 High-risk trust downgrade for "vite@6.4.1" (possible package takeover) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them. File name: examples/solid/start/pnpm-lock.yamlScope: all 49 workspace projects ? Verifying lockfile against supply-chain policies (2234 entries)... [WARN] Request took 17114ms: https://registry.npmjs.org/drizzle-orm ✗ Lockfile failed supply-chain policy check (2234 entries in 35.3s) [ERR_PNPM_TRUST_DOWNGRADE] 5 lockfile entries failed verification: chokidar@4.0.3 High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover) semver@5.7.2 High-risk trust downgrade for "semver@5.7.2" (possible package takeover) semver@6.3.1 High-risk trust downgrade for "semver@6.3.1" (possible package takeover) undici-types@6.21.0 High-risk trust downgrade for "undici-types@6.21.0" (possible package takeover) vite@6.4.1 High-risk trust downgrade for "vite@6.4.1" (possible package takeover) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them. File name: examples/react/a11y-devtools/pnpm-lock.yamlScope: all 49 workspace projects ? Verifying lockfile against supply-chain policies (2234 entries)... [WARN] Request took 17460ms: https://registry.npmjs.org/drizzle-orm ✗ Lockfile failed supply-chain policy check (2234 entries in 39.2s) [ERR_PNPM_TRUST_DOWNGRADE] 5 lockfile entries failed verification: chokidar@4.0.3 High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover) semver@5.7.2 High-risk trust downgrade for "semver@5.7.2" (possible package takeover) semver@6.3.1 High-risk trust downgrade for "semver@6.3.1" (possible package takeover) undici-types@6.21.0 High-risk trust downgrade for "undici-types@6.21.0" (possible package takeover) vite@6.4.1 High-risk trust downgrade for "vite@6.4.1" (possible package takeover) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them. |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
At least 0 approving reviews are required to merge this pull request.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
Release Notes
angular/angular-cli (@angular/build)v21.2.21
Compare Source
@angular/cli
@angular/build
| Commit
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.