Uh oh!
There was an error while loading. Please reload this page.
chore(deps): update all non-major dependencies - #719
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
ContributorAuthor
|
Contributor
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 Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR re-pins GitHub Actions uses (notably actions/checkout) and upgrades many dependency/devDependency versions across root, examples, packages, workflows, and testing manifests. ChangesMonorepo dependency and workflow action updates
Estimated code review effort 🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related issues
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@examples/ts-vue-chat/package.json`:
- Line 28: Replace Tailwind v3's focus:outline-none usages with the v4
equivalent focus:outline-hidden in the listed Vue components: update the class
strings in VueUIView.vue (around the element at ~line 91), ChatView.vue (around
~line 111), and ChatInput.vue (around ~lines 64 and 72) to use
focus:outline-hidden; search those files for any remaining "outline-none"
occurrences and update them, and run the dev build to verify no other Tailwind
v3-specific utilities remain.
In `@package.json`:
- Line 8: The packageManager value ("packageManager": "pnpm@11.5.2") and
engines.pnpm (currently ">=11.5.2") are inconsistent with the repo guideline
requiring pnpm@10.17.0; update them to match the chosen source of truth: either
change packageManager to "pnpm@10.17.0" and set engines.pnpm to ">=10.17.0", or
update the CLAUDE.md/AGENTS.md docs to require pnpm 11.5.x so both
packageManager and engines.pnpm reflect pnpm@11.5.2 consistently; ensure you
update both packageManager and engines.pnpm together so they stay aligned.
In `@packages/ai-anthropic/live-tests/package.json`:
- Line 14: The live-tests package incorrectly depends on zod "^3.25.76" which
conflicts with the parent `@tanstack/ai-anthropic`'s zod ^4.x peer dependency;
update the "zod" entry in the live-tests package.json (the dependency in
packages/ai-anthropic/live-tests/package.json) to a compatible ^4.x version
(e.g., "^4.4.3" or "^4.0.0") so it matches the parent package's declared peer,
then reinstall/update lockfile to ensure a single Zod major version is used
across the workspace.
In `@packages/ai-isolate-node/package.json`:
- Line 52: Extend probeIsolatedVm to perform not only construction/disposal of
an ivm.Isolate but also createContext() on the isolate, create and use a new
ivm.Reference (including exercising applySyncPromise), and compile+run a trivial
script via isolate.compileScript(...).run(..., { promise: true }) inside the
subprocess; update the lightweight smoke/integration test invoked by
probeIsolatedVm to spawn the subprocess that exercises these calls under
isolated-vm@^6.1.2 and surface any runtime/return-shape changes so failures are
detected at execution-time rather than init-time.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 804973d0-b104-4cbe-a640-92f2007dc569
📒 Files selected for processing (57)
.github/workflows/autofix.yml.github/workflows/e2e.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/sync-models.yml.github/workflows/zizmor.ymlcodemods/package.jsonexamples/ts-code-mode-web/package.jsonexamples/ts-group-chat/package.jsonexamples/ts-react-chat/package.jsonexamples/ts-react-media/package.jsonexamples/ts-react-native-chat/package.jsonexamples/ts-react-search/package.jsonexamples/ts-solid-chat/package.jsonexamples/ts-svelte-chat/package.jsonexamples/ts-vue-chat/package.jsonexamples/vanilla-chat/package.jsonpackage.jsonpackages/ai-anthropic/live-tests/package.jsonpackages/ai-anthropic/package.jsonpackages/ai-client/package.jsonpackages/ai-code-mode-skills/package.jsonpackages/ai-code-mode/models-eval/package.jsonpackages/ai-code-mode/package.jsonpackages/ai-devtools/package.jsonpackages/ai-elevenlabs/package.jsonpackages/ai-event-client/package.jsonpackages/ai-fal/package.jsonpackages/ai-gemini/package.jsonpackages/ai-grok/package.jsonpackages/ai-groq/package.jsonpackages/ai-isolate-cloudflare/package.jsonpackages/ai-isolate-node/package.jsonpackages/ai-isolate-quickjs/package.jsonpackages/ai-mcp/package.jsonpackages/ai-ollama/package.jsonpackages/ai-openai/live-tests/package.jsonpackages/ai-openai/package.jsonpackages/ai-openrouter/package.jsonpackages/ai-preact/package.jsonpackages/ai-react-ui/package.jsonpackages/ai-react/package.jsonpackages/ai-solid-ui/package.jsonpackages/ai-solid/package.jsonpackages/ai-svelte/package.jsonpackages/ai-utils/package.jsonpackages/ai-vue-ui/package.jsonpackages/ai-vue/package.jsonpackages/ai/package.jsonpackages/openai-base/package.jsonpackages/preact-ai-devtools/package.jsonpackages/react-ai-devtools/package.jsonpackages/solid-ai-devtools/package.jsonpnpm-workspace.yamltesting/e2e/package.jsontesting/panel/package.jsontesting/react-native-smoke/package.json
| }, | ||
| "devDependencies": { | ||
| "@tailwindcss/vite": "^4.1.18", | ||
| "@tailwindcss/vite": "^4.3.0", |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash# Description: Check for Tailwind v3 patterns incompatible with v4echo"=== Checking for old important modifier syntax (v3: !text-*) ==="
rg -n --type=vue --type=ts -C1 'className=.*!text-|class=.*!text-|className=.*!bg-|class=.*!bg-' examples/ts-vue-chat/src/
echo -e "\n=== Checking for removed opacity utilities (bg-opacity-*, text-opacity-*) ==="
rg -n --type=vue --type=ts -C1 'bg-opacity-|text-opacity-|border-opacity-|ring-opacity-' examples/ts-vue-chat/src/
echo -e "\n=== Checking for old CSS variable syntax with brackets ==="
rg -n --type=vue --type=ts -C1 'bg-\[--.*\]|text-\[--.*\]' examples/ts-vue-chat/src/
echo -e "\n=== Checking for outline-none (behavior changed in v4) ==="
rg -n --type=vue --type=ts -C1 'outline-none' examples/ts-vue-chat/src/Repository: TanStack/ai
Length of output: 449
🏁 Script executed:
#!/bin/bashset -euo pipefail
echo"=== package.json (tailwind/tailwind plugin versions) ==="
nl -ba examples/ts-vue-chat/package.json | sed -n '1,120p'echoecho"=== Search Tailwind v3 patterns in examples/ts-vue-chat/src (important modifier, opacity, bracketed CSS vars) ==="cd examples/ts-vue-chat/src
# Important modifier (v3-style prefix: !text-*, !bg-*, etc.)echo -e "\n--- v3 important prefix (!text- / !bg- / !border- / !ring-) ---"
rg -n --glob '*.{ts,tsx,js,jsx,vue,html}''!((text|bg|border|ring|stroke|fill)-)'.||true# Opacity utilities removed (v3-style)echo -e "\n--- v3 opacity utilities (bg-opacity-*, text-opacity-*, border-opacity-*, ring-opacity-*) ---"
rg -n --glob '*.{ts,tsx,js,jsx,vue,html}''(bg|text|border|ring)-opacity-'.||true# Bracketed CSS variable syntax (v3/old style)echo -e "\n--- bracketed CSS vars: [--*] (e.g., bg-[--color]) ---"
rg -n --glob '*.{ts,tsx,js,jsx,vue,html}''(bg|text|border|ring)-\[\-\-[^]]+\]|\[\-\-[^]]+\]'.||trueecho -e "\n--- generic bracketed CSS vars: [- -] style in class-like strings ---"
rg -n --glob '*.{ts,tsx,js,jsx,vue,html}''\[\-\-'.||trueechoecho"=== outline-none occurrences ==="
rg -n --glob '*.{ts,tsx,js,jsx,vue,html}''outline-none'.||trueRepository: TanStack/ai
Length of output: 173
🌐 Web query:
Tailwind CSS v4 outline-none behavior changed
💡 Result:
In Tailwind CSS v4, the behavior of outline-none was changed to resolve inconsistencies and improve accessibility [1][2]. Key changes: - New outline-none behavior: The outline-none utility now strictly applies outline-style: none [1][3]. In Tailwind v3, this utility used a "clever" implementation that created a 2px invisible outline to ensure focus states remained visible in forced-colors mode [1][2]. - Introduction of outline-hidden: To replicate the v3 behavior—where an outline is removed in standard rendering but remains visible for accessibility in forced-colors mode—Tailwind v4 introduced the outline-hidden utility [1][4]. - Upgrade recommendation: Projects migrating from v3 to v4 should generally replace instances of outline-none with outline-hidden to maintain accessibility for users relying on forced-colors modes [1][4]. The outline-none utility should only be used if you explicitly intend to remove the outline entirely without any fallback [1][3]. Additionally, the outline utility itself was updated in v4 to set outline-width: 1px by default for better consistency with other border and ring utilities [1][5]. Top results: [1], [2], [3], [4]
Citations:
- 1: https://tailwindcss.com/docs/upgrade-guide
- 2: Replace
outline-nonewithoutline-hidden, add newoutline-nonetailwindlabs/tailwindcss#14926 - 3: [v4] :focus-visible no longer overrides default outline for some reason tailwindlabs/tailwindcss#15152
- 4: [bug]: v4 registry incomplete outline-none to outline-hidden migration (19 components) shadcn-ui/ui#10101
- 5: v3 -> v4 upgrade tool should replace
outlinewithoutline-solidtailwindlabs/tailwindcss#15861
🌐 Web query:
Tailwind CSS v4 important modifier syntax text-xl! instead of !text-xl
💡 Result:
In Tailwind CSS v4, the important modifier syntax has officially changed to place the exclamation mark (!) at the end of the utility class (e.g., text-xl!) rather than at the beginning (e.g., !text-xl) [1][2][3]. Key details regarding this change include: * Standard Syntax: The new convention is to append the ! suffix to the class name, which mimics the behavior of native CSS where !important follows the rule [1][3][4]. * Backward Compatibility: While the new syntax is the recommended approach, the previous prefix syntax (e.g., !text-xl) remains supported for backward compatibility, though it is considered deprecated [2][3]. * Design Reasoning: Placing the modifier at the end makes it easier to read and reason about, particularly when combining utilities with variants [5]. * Global Important: If you need to make all utility classes !important globally, Tailwind CSS v4 uses an import-level flag instead of the old tailwind.config.js setting [6][7]. You can achieve this by adding important to your CSS import [6][4]: @import "tailwindcss" important; This syntax change applies to standard utility classes used in HTML as well as utility classes used within @apply directives in your CSS files [5][8].
Citations:
- 1: https://stackoverflow.com/questions/75664539/tailwind-css-class-precedence-is-not-respected
- 2: https://combray.prose.sh/2025-11-30-tailwind-best-practices
- 3: https://tailwindcss.com/docs/upgrade-guide
- 4: https://tailwindcss.com/docs/styling-with-utility-classes
- 5: Add initial codemod tooling tailwindlabs/tailwindcss#14434
- 6: Add support for
importantin v4 tailwindlabs/tailwindcss#14448 - 7: How to make all the classes important by default tailwindlabs/tailwindcss#17994
- 8: PostCSS + TailwindCSS 4 throws error on important! and ! modifiers tailwindlabs/tailwindcss#18570
🌐 Web query:
Tailwind CSS v4 CSS variable syntax parentheses bg-(--color) instead of brackets bg-[--color]
💡 Result:
In Tailwind CSS v4, you can use parentheses syntax, such as bg-(--color), as a shorthand for referencing CSS variables as arbitrary values [1][2]. This syntax automatically wraps the value in a var function, serving as a more concise alternative to the traditional square bracket syntax (bg-[var(--color)]) used in previous versions [2][3]. Key aspects of this syntax include: - Convenience: It functions as a shorthand for bg-[var(--my-color)], automatically adding the required var wrapper for you [2]. - Ambiguity Resolution: If a variable name is ambiguous or requires specific type handling, you can use a type hint prefix within the parentheses [2]. For example, to ensure the utility is treated as a length or color, you can use: - text-(length:--my-var) [2] - text-(color:--my-var) [2] - Technical Change: The introduction of this syntax in v4 is part of a broader engine change, where tokenization now treats parentheses differently than in Tailwind CSS v3 [4]. This shorthand is specifically designed for CSS variables and simplifies the process of applying custom design tokens that are defined via the @theme directive or as standard CSS custom properties [2][5].
Citations:
- 1: https://github.com/tailwindlabs/tailwindcss/blob/14b13378cb9966af11dce6e37a22c1fc5cead16a/CHANGELOG.md
- 2: https://tailwindcss.com/docs/adding-custom-styles
- 3: https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.0.0-alpha.35
- 4: Tailwind 4 doesn't detect classes in parenthesis tailwindlabs/tailwindcss#18431
- 5: https://tailwindcss.com/docs/theme
🌐 Web query:
Tailwind CSS v4 opacity utilities removed bg-opacity- use slash syntax bg-blue-500/20
💡 Result:
In Tailwind CSS v4, the standalone opacity utility classes—such as bg-opacity-, text-opacity-, and border-opacity-—have been removed [1][2]. To control the opacity of specific properties, you must now use the slash-based opacity modifier syntax directly on the color utility [1][3]. How to use the new syntax: * Background colors: Use bg-blue-500/20 instead of bg-blue-500 bg-opacity-20 [1][4][2]. * Text colors: Use text-blue-500/20 instead of text-blue-500 text-opacity-20 [1][2]. * Border colors: Use border-blue-500/20 instead of border-blue-500 border-opacity-20 [1][2]. This syntax works by using the CSS color-mix function under the hood, which applies the opacity only to the specific color rather than the entire element [5][3][6]. If you need to adjust opacity based on state or dynamic conditions (a common use case for the old classes), you can use arbitrary CSS variables [7][8]. For example:
Note that the standalone opacity- classes (e.g., opacity-50) still exist in Tailwind CSS v4, but they are used to control the opacity of an entire element (including its children) rather than just a specific color property [9][10].Citations:
- 1: https://tailwindcss.com/docs/upgrade-guide
- 2: https://wowhow.cloud/blogs/tailwind-css-v4-everything-changed-migration-guide-2026
- 3: https://learn.bemorex.com/en/cursos/tailwind-css-v4/colors-and-theming
- 4: https://tailwindcss.com/docs/background-color
- 5: https://tailwindcss.com/docs/colors
- 6: https://tailwindcss.com/blog/tailwindcss-v4
- 7: Use CSS variables for color opacity instead of hard coding it! tailwindlabs/tailwindcss#9942
- 8: [v4] What's the v4 way to do bg-opacity? tailwindlabs/tailwindcss#15097
- 9: https://tailwindcss.com/docs/opacity
- 10: https://frontend-hero.com/tailwind-opacity-scale
🏁 Script executed:
#!/bin/bashset -euo pipefail
echo"=== examples/ts-vue-chat/package.json tailwind-related deps ==="# show relevant lines without relying on `nl`
sed -n '1,120p' examples/ts-vue-chat/package.json | sed -n '/tailwind/p;/@tailwindcss/p;/postcss/p;/autoprefixer/p'echoecho"=== Tailwind v3-era patterns in examples/ts-vue-chat/src ==="
ROOT="examples/ts-vue-chat/src"# important modifier prefix syntax (!text-*, !bg-*, etc.)echo -e "\n--- prefix important (!text- / !bg- / !border- / !ring-) ---"
rg -n -S -g'*.{ts,tsx,js,jsx,vue,html}''!(text|bg|border|ring|stroke|fill)-'"$ROOT"||true# old standalone opacity utilitiesecho -e "\n--- standalone opacity utilities (bg-opacity-, text-opacity-, border-opacity-, ring-opacity-) ---"
rg -n -S -g'*.{ts,tsx,js,jsx,vue,html}''(bg|text|border|ring)-(opacity)-'"$ROOT"||true# bracketed CSS variable arbitrary values: bg-[--...] or text-[--...]echo -e "\n--- bracketed CSS variable arbitrary values: (bg|text|border|ring)-[--...] ---"
rg -n -S -g'*.{ts,tsx,js,jsx,vue,html}''(bg|text|border|ring|stroke|fill)-\[\s*--[^]]+\]'"$ROOT"||trueecho -e "\n--- generic bracketed CSS vars: \\[--... ---"
rg -n -S -g'*.{ts,tsx,js,jsx,vue,html}''\[\s*--[^]]+\]'"$ROOT"||true# outline-noneecho -e "\n--- outline-none occurrences ---"
rg -n -S -g'*.{ts,tsx,js,jsx,vue,html}''outline-none'"$ROOT"||trueechoecho"=== Optional: check for v4 parentheses variable syntax bg-(--...) / text-(--...) ==="
rg -n -S -g'*.{ts,tsx,js,jsx,vue,html}''(bg|text|border|ring|stroke|fill)-\(\s*--[^)]+\s*\)'"$ROOT"||trueRepository: TanStack/ai
Length of output: 1712
Tailwind v4.3: migrate focus:outline-none to focus:outline-hidden
outline-none has a behavior change in Tailwind v4; the example still uses focus:outline-none in:
examples/ts-vue-chat/src/views/VueUIView.vue:91examples/ts-vue-chat/src/views/ChatView.vue:111examples/ts-vue-chat/src/components/ChatInput.vue:64and72
Other v3→v4 breaking syntax patterns from the comment (!text-*/!bg-* important prefix, bg-opacity-*/etc, and bracketed CSS vars like bg-[--...]) don’t appear in examples/ts-vue-chat/src.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/ts-vue-chat/package.json` at line 28, Replace Tailwind v3's
focus:outline-none usages with the v4 equivalent focus:outline-hidden in the
listed Vue components: update the class strings in VueUIView.vue (around the
element at ~line 91), ChatView.vue (around ~line 111), and ChatInput.vue (around
~lines 64 and 72) to use focus:outline-hidden; search those files for any
remaining "outline-none" occurrences and update them, and run the dev build to
verify no other Tailwind v3-specific utilities remain.
Uh oh!
There was an error while loading. Please reload this page.
| "@tanstack/ai": "workspace:*", | ||
| "@tanstack/ai-anthropic": "workspace:*", | ||
| "zod": "^3.24.1" | ||
| "zod": "^3.25.76" |
Contributor
There was a problem hiding this comment.
Critical: Zod version mismatch with parent package.
This live-tests package uses zod ^3.25.76, but the parent @tanstack/ai-anthropic package (line 63) uses zod ^4.4.3 and declares a peer dependency of ^4.0.0. If this test package imports any schemas or validators from @tanstack/ai-anthropic, runtime errors will occur due to incompatible zod instances across major versions.
🔧 Proposed fix
- "zod": "^3.25.76"+ "zod": "^4.4.3"📝 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
| "zod": "^3.25.76" | |
| "zod": "^4.4.3" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/ai-anthropic/live-tests/package.json` at line 14, The live-tests
package incorrectly depends on zod "^3.25.76" which conflicts with the parent
`@tanstack/ai-anthropic`'s zod ^4.x peer dependency; update the "zod" entry in the
live-tests package.json (the dependency in
packages/ai-anthropic/live-tests/package.json) to a compatible ^4.x version
(e.g., "^4.4.3" or "^4.0.0") so it matches the parent package's declared peer,
then reinstall/update lockfile to ensure a single Zod major version is used
across the workspace.
| ], | ||
| "dependencies": { | ||
| "isolated-vm": "^6.0.2" | ||
| "isolated-vm": "^6.1.2" |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash# Description: Check for isolated-vm API usage# Find isolated-vm API calls in the implementation
rg -n --type ts -C3 "from ['\"]isolated-vm['\"]" packages/ai-isolate-node/src/
# Look for specific isolated-vm API patterns
rg -nP --type ts '(Isolate|Context|Reference|ExternalCopy|\.create|\.compile|\.run)' packages/ai-isolate-node/src/Repository: TanStack/ai
Length of output: 4630
Isolated-vm bump: broaden compatibility checks from init-time to execution-time.
probeIsolatedVm only exercises native-addon loading by constructing/dispose-ing an ivm.Isolate in a subprocess, but the runtime path used by the driver also calls isolate.createContext(), new ivm.Reference(...) + applySyncPromise, and isolate.compileScript(...).run(..., { promise: true }). Add/extend a lightweight smoke/integration test for these execution steps under isolated-vm@^6.1.2 so any behavior/return-shape changes are caught.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/ai-isolate-node/package.json` at line 52, Extend probeIsolatedVm to
perform not only construction/disposal of an ivm.Isolate but also
createContext() on the isolate, create and use a new ivm.Reference (including
exercising applySyncPromise), and compile+run a trivial script via
isolate.compileScript(...).run(..., { promise: true }) inside the subprocess;
update the lightweight smoke/integration test invoked by probeIsolatedVm to
spawn the subprocess that exercises these calls under isolated-vm@^6.1.2 and
surface any runtime/return-shape changes so failures are detected at
execution-time rather than init-time.
renovateBotforce-pushed
the
renovate/all-minor-patch
branch
from
June 8, 2026 03:22
69d6799 to
0930f35CompareContributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/sync-models.yml:
- Line 22: The pinned actions/checkout commit SHA in the workflow step "uses:
actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3" is
incorrect; update the pinned SHA to the real v6.0.3 tag commit SHA
(9f698171ed81b15d1823a05fc7211befd50c8ae0) or change the trailing comment to
match the current pinned SHA so the "uses: actions/checkout@..." line and its
comment are consistent and supply-chain-safe.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: bbed66ef-28c9-4cf6-bdf3-cc58624d53a6
📒 Files selected for processing (57)
.github/workflows/autofix.yml.github/workflows/e2e.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/sync-models.yml.github/workflows/zizmor.ymlcodemods/package.jsonexamples/ts-code-mode-web/package.jsonexamples/ts-group-chat/package.jsonexamples/ts-react-chat/package.jsonexamples/ts-react-media/package.jsonexamples/ts-react-native-chat/package.jsonexamples/ts-react-search/package.jsonexamples/ts-solid-chat/package.jsonexamples/ts-svelte-chat/package.jsonexamples/ts-vue-chat/package.jsonexamples/vanilla-chat/package.jsonpackage.jsonpackages/ai-anthropic/live-tests/package.jsonpackages/ai-anthropic/package.jsonpackages/ai-client/package.jsonpackages/ai-code-mode-skills/package.jsonpackages/ai-code-mode/models-eval/package.jsonpackages/ai-code-mode/package.jsonpackages/ai-devtools/package.jsonpackages/ai-elevenlabs/package.jsonpackages/ai-event-client/package.jsonpackages/ai-fal/package.jsonpackages/ai-gemini/package.jsonpackages/ai-grok/package.jsonpackages/ai-groq/package.jsonpackages/ai-isolate-cloudflare/package.jsonpackages/ai-isolate-node/package.jsonpackages/ai-isolate-quickjs/package.jsonpackages/ai-mcp/package.jsonpackages/ai-ollama/package.jsonpackages/ai-openai/live-tests/package.jsonpackages/ai-openai/package.jsonpackages/ai-openrouter/package.jsonpackages/ai-preact/package.jsonpackages/ai-react-ui/package.jsonpackages/ai-react/package.jsonpackages/ai-solid-ui/package.jsonpackages/ai-solid/package.jsonpackages/ai-svelte/package.jsonpackages/ai-utils/package.jsonpackages/ai-vue-ui/package.jsonpackages/ai-vue/package.jsonpackages/ai/package.jsonpackages/openai-base/package.jsonpackages/preact-ai-devtools/package.jsonpackages/react-ai-devtools/package.jsonpackages/solid-ai-devtools/package.jsonpnpm-workspace.yamltesting/e2e/package.jsontesting/panel/package.jsontesting/react-native-smoke/package.json
✅ Files skipped from review due to trivial changes (32)
- pnpm-workspace.yaml
- examples/vanilla-chat/package.json
- packages/ai-ollama/package.json
- packages/ai-preact/package.json
- packages/ai-openai/package.json
- packages/ai-anthropic/package.json
- packages/preact-ai-devtools/package.json
- packages/openai-base/package.json
- packages/ai-isolate-node/package.json
- packages/ai-grok/package.json
- packages/ai-isolate-cloudflare/package.json
- packages/ai-devtools/package.json
- .github/workflows/zizmor.yml
- packages/ai-code-mode/package.json
- packages/ai-openai/live-tests/package.json
- packages/react-ai-devtools/package.json
- packages/ai-fal/package.json
- packages/ai-gemini/package.json
- .github/workflows/release.yml
- packages/ai-client/package.json
- .github/workflows/pr.yml
- packages/solid-ai-devtools/package.json
- packages/ai-code-mode/models-eval/package.json
- examples/ts-react-media/package.json
- packages/ai-solid/package.json
- packages/ai-svelte/package.json
- packages/ai-elevenlabs/package.json
- packages/ai-anthropic/live-tests/package.json
- examples/ts-group-chat/package.json
- examples/ts-svelte-chat/package.json
- packages/ai-openrouter/package.json
- examples/ts-react-chat/package.json
🚧 Files skipped from review as they are similar to previous changes (21)
- packages/ai-event-client/package.json
- packages/ai-solid-ui/package.json
- packages/ai-utils/package.json
- packages/ai-code-mode-skills/package.json
- examples/ts-react-native-chat/package.json
- packages/ai-isolate-quickjs/package.json
- packages/ai-react-ui/package.json
- packages/ai-vue/package.json
- .github/workflows/e2e.yml
- packages/ai-react/package.json
- packages/ai-vue-ui/package.json
- packages/ai/package.json
- .github/workflows/autofix.yml
- testing/react-native-smoke/package.json
- examples/ts-vue-chat/package.json
- codemods/package.json
- testing/e2e/package.json
- package.json
- examples/ts-code-mode-web/package.json
- examples/ts-react-search/package.json
- examples/ts-solid-chat/package.json
Uh oh!
There was an error while loading. Please reload this page.
renovateBotforce-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
June 8, 2026 13:39
cb952ac to
fbdcf75CompareContributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@codemods/package.json`:
- Around line 17-20: The package bumps in codemods/package.json aren’t reflected
in pnpm-lock.yaml’s codemods block (prettier still resolves to 3.7.4 and vitest
to 4.1.4); regenerate the lockfile so the codemods section resolves to the
declared versions (jscodeshift ^17.3.0, prettier ^3.8.3, vitest ^4.1.8) by
reinstalling/updating pnpm dependencies for the codemods workspace (or run a
repo-level pnpm install / update filtered to the codemods workspace), commit the
updated pnpm-lock.yaml, and then run the codemod test suite (pnpm test:pr) to
verify everything passes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 02b6b29c-9e01-4494-9def-f8e788c9cb65
📒 Files selected for processing (57)
.github/workflows/autofix.yml.github/workflows/e2e.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/sync-models.yml.github/workflows/zizmor.ymlcodemods/package.jsonexamples/ts-code-mode-web/package.jsonexamples/ts-group-chat/package.jsonexamples/ts-react-chat/package.jsonexamples/ts-react-media/package.jsonexamples/ts-react-native-chat/package.jsonexamples/ts-react-search/package.jsonexamples/ts-solid-chat/package.jsonexamples/ts-svelte-chat/package.jsonexamples/ts-vue-chat/package.jsonexamples/vanilla-chat/package.jsonpackage.jsonpackages/ai-anthropic/live-tests/package.jsonpackages/ai-anthropic/package.jsonpackages/ai-client/package.jsonpackages/ai-code-mode-skills/package.jsonpackages/ai-code-mode/models-eval/package.jsonpackages/ai-code-mode/package.jsonpackages/ai-devtools/package.jsonpackages/ai-elevenlabs/package.jsonpackages/ai-event-client/package.jsonpackages/ai-fal/package.jsonpackages/ai-gemini/package.jsonpackages/ai-grok/package.jsonpackages/ai-groq/package.jsonpackages/ai-isolate-cloudflare/package.jsonpackages/ai-isolate-node/package.jsonpackages/ai-isolate-quickjs/package.jsonpackages/ai-mcp/package.jsonpackages/ai-ollama/package.jsonpackages/ai-openai/live-tests/package.jsonpackages/ai-openai/package.jsonpackages/ai-openrouter/package.jsonpackages/ai-preact/package.jsonpackages/ai-react-ui/package.jsonpackages/ai-react/package.jsonpackages/ai-solid-ui/package.jsonpackages/ai-solid/package.jsonpackages/ai-svelte/package.jsonpackages/ai-utils/package.jsonpackages/ai-vue-ui/package.jsonpackages/ai-vue/package.jsonpackages/ai/package.jsonpackages/openai-base/package.jsonpackages/preact-ai-devtools/package.jsonpackages/react-ai-devtools/package.jsonpackages/solid-ai-devtools/package.jsonpnpm-workspace.yamltesting/e2e/package.jsontesting/panel/package.jsontesting/react-native-smoke/package.json
✅ Files skipped from review due to trivial changes (29)
- packages/preact-ai-devtools/package.json
- packages/react-ai-devtools/package.json
- packages/openai-base/package.json
- packages/ai-anthropic/package.json
- examples/vanilla-chat/package.json
- packages/ai-utils/package.json
- packages/ai-openai/live-tests/package.json
- pnpm-workspace.yaml
- packages/ai-openrouter/package.json
- .github/workflows/autofix.yml
- packages/ai-solid/package.json
- examples/ts-react-media/package.json
- packages/ai-gemini/package.json
- packages/ai-grok/package.json
- .github/workflows/sync-models.yml
- packages/ai-openai/package.json
- packages/ai-solid-ui/package.json
- packages/ai-event-client/package.json
- packages/ai-preact/package.json
- packages/ai-client/package.json
- packages/ai-fal/package.json
- testing/react-native-smoke/package.json
- packages/ai-vue/package.json
- packages/ai-anthropic/live-tests/package.json
- packages/ai-code-mode/models-eval/package.json
- packages/ai-isolate-node/package.json
- examples/ts-vue-chat/package.json
- testing/panel/package.json
- packages/ai-svelte/package.json
🚧 Files skipped from review as they are similar to previous changes (24)
- packages/ai-mcp/package.json
- .github/workflows/release.yml
- .github/workflows/e2e.yml
- packages/ai-vue-ui/package.json
- packages/ai-elevenlabs/package.json
- packages/ai-react/package.json
- packages/ai-code-mode/package.json
- packages/ai-groq/package.json
- packages/ai-isolate-cloudflare/package.json
- packages/ai-isolate-quickjs/package.json
- testing/e2e/package.json
- packages/ai-react-ui/package.json
- packages/ai-ollama/package.json
- examples/ts-group-chat/package.json
- packages/solid-ai-devtools/package.json
- .github/workflows/zizmor.yml
- packages/ai-code-mode-skills/package.json
- .github/workflows/pr.yml
- examples/ts-code-mode-web/package.json
- package.json
- examples/ts-solid-chat/package.json
- packages/ai-devtools/package.json
- examples/ts-react-search/package.json
- examples/ts-react-chat/package.json
Uh oh!
There was an error while loading. Please reload this page.
renovateBotforce-pushed
the
renovate/all-minor-patch
branch
20 times, most recently
from
June 12, 2026 02:00
ab1273b to
da42d13ComparerenovateBotforce-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
June 17, 2026 17:21
b04b6f6 to
0664591CompareContributor
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 Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR re-pins GitHub Actions uses (notably actions/checkout) and upgrades many dependency/devDependency versions across root, examples, packages, workflows, and testing manifests. ChangesMonorepo dependency and workflow action updates
Estimated code review effort 🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related issues
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
renovateBotforce-pushed
the
renovate/all-minor-patch
branch
19 times, most recently
from
June 22, 2026 11:32
b21edbd to
fd1815cCompare
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
^0.25.0→^0.29.0^2.6.2→^2.6.3^2.30.0→^2.31.1^0.12.1→^0.12.4^1.42.1→^1.46.0^4.20260317.1→^4.20260702.1^1.34.0→^1.37.4^0.191.0→^0.200.00.200.1^1.3.1→^1.15.2^2.44.0→^2.59.0^10.1.0→^10.5.0^1.19.6→^1.19.14^0.31.0→^0.32.0^0.31.0→^0.32.0^0.31.0→^0.32.0^0.31.0→^0.32.0^1.17.4→^1.18.4^1.57.0→^1.61.1^1.1.2→^1.1.171.1.18^1.2.4→^1.3.01.3.1^5.4.5→^5.6.8^4.14.2→^4.16.1^0.4.1→^0.4.2^0.4.1→^0.5.0^0.4.1→^0.5.0^0.5.1→^0.6.0^0.4.0→^0.6.0^0.5.3→^0.8.10.8.3(+1)^1.0.6→^1.1.01.2.0^0.1.55→^0.1.94^0.9.10→^0.10.80.10.9^5.90.12→^5.101.4^1.158.4→^1.170.18^1.158.4→^1.167.0^1.158.4→^1.167.1^1.159.0→^1.168.32^0.8.0→^0.11.0^1.158.4→^1.168.23^1.158.4→^1.168.23^0.7.15→^0.8.80.8.9^1.139.10→^1.170.18^1.139.10→^1.167.0^1.139.10→^1.167.1^1.139.10→^1.168.32^0.8.0→^0.11.0^0.8.0→^0.11.0^1.140.1→^1.167.0^2.2.1→^2.8.0190f659→bfa1648^3.0.0→^3.0.1v6.0.2→v6.1.0^2.1.28→^2.2.3^2.1.28→^2.2.30.3→0.3.6^10.4.21→^10.5.40.8→0.8.9v1.7.0→v1.9.0^9.1.2→^9.2.4^9.1.2→^9.2.40.12.1→0.12.4^4.0.2→^4.0.12^17.2.3→^17.4.2^17.2.3→^17.4.2^0.25.12→^0.28.1~56.0.5→~56.0.1656.0.17^5.1.0→^5.2.1^11.15.0→^11.18.20.3→0.3.331.22→1.26.5^2.1.18→^2.1.19^4.10.6→^4.12.31^6.0.2→^6.1.2^2.4.2→^2.7.0^17.1.1→^17.4.0^4.20260609.0→^4.20260721.0^21.2.0→^21.2.5^0.59.0→^0.60.0^1.74.0→^1.75.0^1.74.0→^1.75.0^0.24.0→^0.25.011.9.0→11.15.111.16.0>=11.9.0→>=11.15.111.16.0^10.26.9→^10.29.7^24.34.0→^24.43.1^0.31.0→^0.32.0^0.31.0→^0.32.0^1.4.3→^1.6.41.6.5^2.15.0→^2.15.40.12→0.13.4^7.8.0→^7.8.21→1.0.2291→1.0.151^3.35.0→^3.35.1^3.4.0→^3.6.01→1.53.10.1→0.1.19^0.17.0-beta.6→^0.22.13^5.1.0→^5.3.0^4.103.0→^4.113.0^8.18.3→^8.21.1v0.5.3→v0.6.0^4.2.0→^4.4.3^4.2.0→^4.4.3^4.2.0→^4.4.3^4.2.0→^4.4.3^3.24.1→^3.25.76^0.15.0→^0.16.2^0.15.0→^0.16.2Release Notes
agentclientprotocol/typescript-sdk (@agentclientprotocol/sdk)
v0.29.0Compare Source
Features
v0.28.1Compare Source
Bug Fixes
v0.28.0Compare Source
Features
v0.27.1Compare Source
Bug Fixes
v0.27.0Compare Source
This is a big release! We have rewritten the SDK to have a more ergonomic design for creating new agents and clients. You can read more in the Migration Guide for how to migrate.
For now, you will still have the old interfaces available to ease the migration, but they are deprecated and will be removed in a future release.
Features
v0.26.0Compare Source
Features
changesets/changesets (@changesets/cli)
v2.31.1Compare Source
Patch Changes
15cf592Thanks @ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successfulnpm info --jsonoutput in an array. The unwrapped output madechangeset publishtreat every package as unpublished and fail attempting to republish existing versions.v2.31.0Compare Source
Minor Changes
#1889
96ca062Thanks @mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.#1873
42943b7Thanks @mixelburg! - Respond to--helpon all subcommands. Previously,--helpwas only handled when it was the sole argument; passing it alongside a subcommand (e.g.changeset version --help) would silently execute the command instead. Now--helpalways exits early and prints per-command usage when a known subcommand is provided, or the general help text otherwise.Patch Changes
d2121dcThanks @Andarist! - Fix npm auth for path-based registries during publish by preserving configured registry URLs instead of normalizing them.#1888
036fdd4Thanks @mixelburg! - Fix severalchangeset versionissues with workspace protocol dependencies. Valid explicitworkspace:ranges and aliases are no longer rewritten unnecessarily, and workspace path references are handled correctly during versioning.#1903
5c4731fThanks @Andarist! - Gracefully handle stalenpm infodata leading to duplicate publish attempts.#1867
f61e716Thanks @Andarist! - Improved detection forpublishedstate of prerelease-only packages withoutlatestdist-tag on GitHub Packages registry.Updated dependencies [
036fdd4,036fdd4,036fdd4]:cloudflare/sandbox-sdk (@cloudflare/sandbox)
v0.12.4Compare Source
Patch Changes
33ac27bThanks @aron-cf! - AddlabelstoSandboxOptionssogetSandbox()can attach Cloudflare Container labels for analytics and observability. Labels are applied on container start; updates while running apply on the next start.v0.12.3Compare Source
Patch Changes
#781
56b4f78Thanks @ghostwriternr! - Restoring a backup now survives a durable object restart.#780
2fec714Thanks [@ghostwriternr](https://redirect.github.com/ghostConfiguration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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.