ci(changesets): version packages#1012
Conversation
Deploying voltagent with
|
| Latest commit: |
efe2785
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0f2279a8.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughThis PR releases version 2.3.2 of Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 15
🤖 Fix all issues with AI agents
In `@examples/with-chroma/package.json`:
- Line 9: The package.json dependency declaration for "@voltagent/core":
"^2.3.2" references a non-existent publish; update the dependency string to a
published version (e.g. "@voltagent/core": "^2.3.1") or the intended released
tag so installation succeeds; locate the "@voltagent/core" entry in package.json
and replace "^2.3.2" with the correct published version.
In `@examples/with-hooks/package.json`:
- Line 6: The dependency entry for "@voltagent/core" in package.json references
a non-existent version (2.3.2); update the "@voltagent/core" dependency to a
valid published version (for example "^2.1.6" or "^1.1.1"), or if you intend to
use 2.3.2 publish that release first and then update the package.json
accordingly; locate the "@voltagent/core" key in package.json and change its
version string to a confirmed registry release before merging.
In `@examples/with-nextjs-resumable-stream/package.json`:
- Line 20: The package.json dependency for "@voltagent/core" is pinned to a
non-existent 2.3.2; update the dependency entry that currently reads
"@voltagent/core": "^2.3.2" to use the published 2.3.1 release by changing it to
"@voltagent/core": "^2.3.1" and then run npm/yarn install to update lockfiles.
In `@examples/with-playwright/package.json`:
- Line 10: The package.json dependency entry "@voltagent/core": "^2.3.2" is
incorrect because 2.3.2 isn't published; update that dependency string to
"@voltagent/core": "^2.3.1" in the examples/with-playwright package.json so
npm/yarn can resolve the package (locate the dependency line containing
"@voltagent/core" and replace the version).
In `@examples/with-rag-chatbot/package.json`:
- Line 7: Update the dependency version for "@voltagent/core" in package.json:
change the version string from "^2.3.2" to "^2.3.1" so the project references
the published release; locate the dependency entry line containing
"@voltagent/core" and replace the version token accordingly, then run npm
install / yarn install to refresh lockfile.
In `@examples/with-research-assistant/package.json`:
- Line 6: The dependency "@voltagent/core": "^2.3.2" is invalid on npm; change
the version to a published release (use "^2.3.1" or "^2.3.0") in package.json,
and if you choose "^2.3.0" verify and update any usage of removed APIs (e.g.,
createToolRouter, toolRouting.routers) to the new system tools (searchTools,
callTool) so the example remains compatible.
In `@examples/with-retries-fallback/package.json`:
- Line 7: Update the dependency version for `@voltagent/core` in package.json:
replace the nonexistent "2.3.2" entry with the published version "^2.3.1" so
installation succeeds (locate the "@voltagent/core" dependency line in
package.json and change its version string).
In `@examples/with-slack/package.json`:
- Line 6: The package.json dependency entry for "@voltagent/core" references a
non-existent version ^2.3.2 causing installs to fail; update the dependency in
package.json to a published version (e.g., "2.1.6" or "1.1.1") or the intended
correct release, then run npm install to verify; locate the dependency line for
"@voltagent/core" in package.json and replace the version string accordingly and
commit the change.
In `@examples/with-tool-routing/package.json`:
- Line 7: The dependency entry for "@voltagent/core" currently points to "2.3.2"
which is not published; either change the version string in package.json to
"^2.3.1" (or the exact "2.3.1") or coordinate/publish the "2.3.2" release before
merging so that the dependency resolves correctly.
In `@examples/with-vector-search/package.json`:
- Line 7: The package.json dependency for "@voltagent/core" references a
non-existent version "^2.3.2"; update that dependency entry (the
"@voltagent/core" line in package.json) to an existing published version such as
"^2.1.6" so npm install can resolve the package.
In `@examples/with-vercel-ai/package.json`:
- Line 6: The package.json currently references a non-existent dependency
version "@voltagent/core": "^2.3.2"; update this dependency string to a valid
published version (e.g. change "@voltagent/core": "^2.3.2" to "@voltagent/core":
"^2.3.1") or confirm and set the intended published version, then run npm
install to verify resolution.
In `@examples/with-voice-xsai/package.json`:
- Line 6: The package.json lists an unpublished dependency version for
"@voltagent/core" (currently "^2.3.2"); update the dependency to a published
version such as "^2.3.1" (or another valid published tag) so npm installs
succeed—modify the "@voltagent/core" entry in package.json accordingly and
ensure package-lock or yarn.lock is regenerated after the change.
In `@examples/with-voltagent-exporter/package.json`:
- Line 6: The package.json in the examples references an unpublished dependency
"@voltagent/core": "^2.3.2" which will break installs; update the dependency
entry in this package.json (and any other example package.json files) to use the
published version "^2.3.1" or change to a published tag, ensuring the dependency
string is replaced wherever "@voltagent/core": "^2.3.2" appears; if you intend
to publish 2.3.2 instead, hold merging until that release is available.
In `@examples/with-voltagent-managed-memory/package.json`:
- Line 6: The package.json currently references the non-existent dependency
string "@voltagent/core": "^2.3.2"; update this dependency to a published
version (e.g. change the version specifier to "@voltagent/core": "^2.3.1") or
confirm and wait for the 2.3.2 release to be published before keeping the
"^2.3.2" specifier.
In `@examples/with-workflow-chain/package.json`:
- Line 6: Update the dependency string for "@voltagent/core" in package.json
from "^2.3.2" to "^2.3.1" (or "2.3.1") so the package resolver can find the
published version; after updating, run the example and, if the example code uses
the removed API createToolRouter, replace usages with the new routing approach
using searchTools and callTool (refactor any createToolRouter calls to use
searchTools to find tools and callTool to invoke them).
| "@chroma-core/openai": "^0.1.7", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.2 release notes
💡 Result:
I couldn’t find any public release notes (or even a published tag/release) for @voltagent/core version 2.3.2 in the usual places (npm or the VoltAgent/voltagent GitHub release trackers).
What I can verify:
- The npm package page currently shows
@voltagent/corelatest =1.1.1(published ~11 hours before the crawl that indexed it), and it does not surface any2.3.2release notes. [1] - A GitHub-release tracker for the VoltAgent monorepo lists recent
@voltagent/corereleases like2.3.1and2.3.0, but not2.3.2. [2] - VoltAgent’s docs include a 1.x → 2.x migration guide, indicating 2.x exists conceptually, but it does not provide specific
2.3.2notes. [3]
If you meant a different package name or scope (or you have a link to the 2.3.2 tag/commit), paste it and I’ll extract the exact release notes from that source.
Sources:
[1] (npmjs.com)
[2] (newreleases.io)
[3] (voltagent.dev)
Citations:
- 1: https://www.npmjs.com/package/%40voltagent/core?utm_source=openai
- 2: https://newreleases.io/project/github/VoltAgent/voltagent/release/create-voltagent-app%400.2.17?utm_source=openai
- 3: https://voltagent.dev/docs/getting-started/migration-guide/?utm_source=openai
@voltagent/core version 2.3.2 does not exist. According to npm and GitHub release records, the latest published versions are 2.3.1 and 2.3.0. The current specification will fail during installation. Update to a published version like ^2.3.1 or verify the intended version.
🤖 Prompt for AI Agents
In `@examples/with-chroma/package.json` at line 9, The package.json dependency
declaration for "@voltagent/core": "^2.3.2" references a non-existent publish;
update the dependency string to a published version (e.g. "@voltagent/core":
"^2.3.1") or the intended released tag so installation succeeds; locate the
"@voltagent/core" entry in package.json and replace "^2.3.2" with the correct
published version.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm version 2.3.2
💡 Result:
I couldn’t find any public npm record for @voltagent/core v2.3.2.
- The npm package page currently shows v1.1.1 as the published version. [1]
- jsDelivr (npm CDN index) shows v2.1.6 as the package version it knows about. [2]
- A GitHub release tracker for the VoltAgent repo shows releases up to @voltagent/core@2.1.0 (and others like 2.0.14), but nothing for 2.3.2. [3]
To verify from your environment, run:
npm view `@voltagent/core` version
npm view `@voltagent/core` versions --jsonSources: [1] [2] [3]
@voltagent/core v2.3.2 is not published on npm—this dependency bump is invalid.
The version 2.3.2 does not exist on the npm registry. Published versions include v1.1.1 (npm), v2.1.6 (jsDelivr), and up to v2.1.0 on GitHub releases. Either correct the version to an existing release or publish v2.3.2 before merging.
🤖 Prompt for AI Agents
In `@examples/with-hooks/package.json` at line 6, The dependency entry for
"@voltagent/core" in package.json references a non-existent version (2.3.2);
update the "@voltagent/core" dependency to a valid published version (for
example "^2.1.6" or "^1.1.1"), or if you intend to use 2.3.2 publish that
release first and then update the package.json accordingly; locate the
"@voltagent/core" key in package.json and change its version string to a
confirmed registry release before merging.
| "@tavily/core": "^0.6.3", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.3.2 npm package release notes
💡 Result:
I couldn’t find any published release (or release notes) for @voltagent/core@2.3.2 in the VoltAgent repo’s tagged/package releases aggregator (NewReleases). The most recent 2.3.x entry I can verify is:
@voltagent/core@2.3.1— Adds two separate workflow examples:with-workflow(functionalcreateWorkflow) andwith-workflow-chain(fluentcreateWorkflowChain), and both demonstrateworkflowState/setWorkflowStatefor persisting data across steps. [1]
If you meant a nearby version, another recent patch I can verify is:
@voltagent/core@2.2.2— Ships embedded docs inside@voltagent/core(packages/core/docs) and keeps them synced during build/pack for offline, version-matched docs lookup. [2]
Sources: [1] [2]
Correct @voltagent/core version to 2.3.1 (published; 2.3.2 does not exist).
Version 2.3.2 is not published on npm. The latest available 2.3.x release is 2.3.1, which adds workflow examples (createWorkflow, createWorkflowChain) and introduces workflowState/setWorkflowState for persisting data across steps. Update the dependency to "^2.3.1".
🤖 Prompt for AI Agents
In `@examples/with-nextjs-resumable-stream/package.json` at line 20, The
package.json dependency for "@voltagent/core" is pinned to a non-existent 2.3.2;
update the dependency entry that currently reads "@voltagent/core": "^2.3.2" to
use the published 2.3.1 release by changing it to "@voltagent/core": "^2.3.1"
and then run npm/yarn install to update lockfiles.
| "@playwright/test": "^1.51.1", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.3.2 npm package release notes breaking changes
💡 Result:
I couldn’t find any evidence that @voltagent/core v2.3.2 has been released (no tag / release entry / changelog page turned up for that version). The public release trackers I can access show 2.0.x and mention “latest releases” like @voltagent/core@2.1.0 and @voltagent/core@2.0.14, but not 2.3.2. [1], [2]
Closest available “2.x” release notes & breaking-change signals
For the 2.0.2 release notes (the start of VoltAgent 2.x), the project states:
- VoltAgent 2.x aligns with AI SDK v6
- VoltAgent APIs are compatible (i.e., no framework-level breaking changes if you only use VoltAgent APIs)
- But if your app calls the AI SDK directly, you must follow the AI SDK v6 migration guide
- Also:
generateObject/streamObjectare deprecated in VoltAgent 2.x in favor ofgenerateText/streamTextwithOutput.object(...). [1]
If you can share where you saw “2.3.2” (link, git tag, npm dist-tag, etc.), I can verify it and extract the exact breaking changes for that specific version.
Sources:
[1] https://newreleases.io/project/github/VoltAgent/voltagent/release/%40voltagent%2Fcore%402.0.2
[2] https://newreleases.io/project/github/VoltAgent/voltagent/release/%40voltagent%2Fcore%400.1.64
🌐 Web query:
site:npmjs.com @voltagent/core version 2.3.2
💡 Result:
I couldn’t find any evidence that @voltagent/core@2.3.2 exists on npm (no npm page/version entry showed up for 2.3.2 via search).
The latest visible 2.x release I can confirm from public package indexes is 2.3.1 (jsDelivr shows @voltagent/core at Version 2.3.1) [1]. NewReleases also lists recent @voltagent/core releases including 2.3.1 and 2.3.0, with no 2.3.2 mentioned [2].
Sources: [1] (jsdelivr.com) [2] (newreleases.io)
Citations:
- 1: https://www.jsdelivr.com/package/npm/%40voltagent/core
- 2: https://newreleases.io/project/github/VoltAgent/voltagent/release/create-voltagent-app%400.2.17?utm_source=openai
Update @voltagent/core to 2.3.1 (2.3.2 does not exist on npm).
The specified version @voltagent/core@2.3.2 is not published on npm. The latest available version in the 2.3.x series is 2.3.1. Update the dependency to "@voltagent/core": "^2.3.1" to resolve the package installation failure.
🤖 Prompt for AI Agents
In `@examples/with-playwright/package.json` at line 10, The package.json
dependency entry "@voltagent/core": "^2.3.2" is incorrect because 2.3.2 isn't
published; update that dependency string to "@voltagent/core": "^2.3.1" in the
examples/with-playwright package.json so npm/yarn can resolve the package
(locate the dependency line containing "@voltagent/core" and replace the
version).
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.3.2 npm package release notes breaking changes
💡 Result:
I couldn’t find any GitHub tag/release for @voltagent/core@2.3.2 (the tags jump from 2.3.1 to 2.3.0), so there are no official 2.3.2 release notes / breaking-change notes available from the upstream repo. [1]
Closest available release notes
-
@voltagent/core@2.3.1(Jan 28, 2026) — Patch release; adds separate workflow examples demonstrating both workflow APIs, includingworkflowState/setWorkflowState. No breaking changes mentioned. [2] -
@voltagent/core@2.3.0(Jan 28, 2026) — Breaking change in tool routing:- Tool routers were replaced with system tools
searchTools+callTool createToolRouterandtoolRouting.routerswere removed [3]
- Tool routers were replaced with system tools
Sources: [1] [2] [3]
Use @voltagent/core@2.3.1 instead — version 2.3.2 does not exist on npm.
The specified version 2.3.2 is not published; available versions are 2.3.1 (current patch) and 2.3.0. Update the dependency to ^2.3.1, which introduces no breaking changes and is the latest stable release.
🤖 Prompt for AI Agents
In `@examples/with-rag-chatbot/package.json` at line 7, Update the dependency
version for "@voltagent/core" in package.json: change the version string from
"^2.3.2" to "^2.3.1" so the project references the published release; locate the
dependency entry line containing "@voltagent/core" and replace the version token
accordingly, then run npm install / yarn install to refresh lockfile.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify that `@voltagent/core`@2.3.2 exists on npm and inspect dist-tags.
curl -s https://registry.npmjs.org/@voltagent/core | jq '.["dist-tags"], .versions["2.3.2"].version' 2>/dev/nullRepository: VoltAgent/voltagent
Length of output: 117
@voltagent/core@2.3.2 does not exist on npm. The latest published version is 2.3.1. Update the dependency to "@voltagent/core": "^2.3.1" or verify the intended version exists before release.
🤖 Prompt for AI Agents
In `@examples/with-vercel-ai/package.json` at line 6, The package.json currently
references a non-existent dependency version "@voltagent/core": "^2.3.2"; update
this dependency string to a valid published version (e.g. change
"@voltagent/core": "^2.3.2" to "@voltagent/core": "^2.3.1") or confirm and set
the intended published version, then run npm install to verify resolution.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.2 release notes
💡 Result:
I couldn’t find any published release notes (or even a release entry) for @voltagent/core@2.3.2 in the VoltAgent repo’s release feed; the most recent @voltagent/core patch release I can locate is 2.3.1, which adds two new workflow examples (with-workflow and with-workflow-chain) and demonstrates workflowState / setWorkflowState for persisting state across steps. [1]
If you meant the closest prior patch, 2.2.2 includes “ship embedded docs inside @voltagent/core (packages/core/docs) … for offline, version-matched docs lookup.” [2]
Sources:
[1] @voltagent/core@2.3.1 release notes (NewReleases / GitHub feed)
[2] @voltagent/core@2.2.2 release notes (NewReleases / GitHub feed)
🌐 Web query:
site:npmjs.com @voltagent/core 2.3.2
💡 Result:
I couldn’t find any evidence that @voltagent/core@2.3.2 exists on npmjs.com (no npm page for that version shows up in search results). A release-tracking page for the repo lists latest releases up to @voltagent/core@2.1.0, but not 2.3.2. [1]
What I can see indexed on npmjs.com includes older version pages like @voltagent/core@0.1.1. [2] General package search snippets also don’t surface a 2.3.2 tag/version. [3]
If you want to confirm from your machine, run:
npm view `@voltagent/core` versions --json | grep 2.3.2Sources: [1] [2] [3]
@voltagent/core version 2.3.2 does not appear to be published on npm.
The latest available patch release is 2.3.1 (which adds workflow examples and demonstrates workflowState/setWorkflowState). Update the dependency to a published version—either ^2.3.1 if you want the latest patch, or clarify if this version was intended for a future release.
🤖 Prompt for AI Agents
In `@examples/with-voice-xsai/package.json` at line 6, The package.json lists an
unpublished dependency version for "@voltagent/core" (currently "^2.3.2");
update the dependency to a published version such as "^2.3.1" (or another valid
published tag) so npm installs succeed—modify the "@voltagent/core" entry in
package.json accordingly and ensure package-lock or yarn.lock is regenerated
after the change.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.3.2 npm release notes
💡 Result:
I couldn’t find any published release notes (or even evidence of a published version) for @voltagent/core@2.3.2.
The most recent @voltagent/core release notes I can find are for @voltagent/core@2.2.2, which lists this patch change: “ship embedded docs inside @voltagent/core (packages/core/docs) and keep them synced during build/pack for offline, version-matched docs lookup”. [1]
Also note: the npm package page snapshot I can access shows a latest version of 1.1.1, not 2.3.2. [2]
Sources: [1], [2]
🌐 Web query:
@voltagent/core version 2.3.2 breaking changes
💡 Result:
I can’t find any published @voltagent/core@2.3.2 tag/release—GitHub shows @voltagent/core@2.3.1 (Jan 28, 2026) as the latest in the 2.3.x line. (github.com)
Closest breaking change (in 2.3.0)
@voltagent/core@2.3.0 includes a breaking change to tool routing:
- Replaces “tool router” tools with two system tools:
searchTools+callTool - Removes
createToolRouterandtoolRouting.routers - Default behavior expects the model to search first, then call the selected tool with schema-compliant args (with an option to relax enforcement) (github.com)
What changed in 2.3.1
2.3.1 is a patch release and (per release notes) does not list breaking changes. (github.com)
Broader 1.x → 2.x notes (if you’re upgrading across majors)
The official migration guide states VoltAgent 2.x aligns with AI SDK v6 and calls out several changes (including some “breaking” type-level changes like message helpers moving to UIMessage, server decoupling, observability changes). (voltagent.dev)
Citations:
- 1: https://github.com/VoltAgent/voltagent/tags
- 2: https://github.com/VoltAgent/voltagent/releases
- 3: https://github.com/VoltAgent/voltagent/releases
- 4: https://voltagent.dev/docs/getting-started/migration-guide/?utm_source=openai
🏁 Script executed:
# Check if there's a package-lock.json or yarn.lock to see actual resolved version
find . -name "package-lock.json" -o -name "yarn.lock" | head -5Repository: VoltAgent/voltagent
Length of output: 90
🏁 Script executed:
# Check other package.json files in the repo to see what versions of `@voltagent/core` are used elsewhere
find . -name "package.json" -type f -exec grep -l "@voltagent/core" {} \;Repository: VoltAgent/voltagent
Length of output: 4575
🏁 Script executed:
cat examples/with-voltagent-exporter/package.jsonRepository: VoltAgent/voltagent
Length of output: 896
🏁 Script executed:
# Search for any references to 2.3.2 in the repository
rg "2\.3\.2" --type jsonRepository: VoltAgent/voltagent
Length of output: 5980
🏁 Script executed:
# Check what `@voltagent/core` version is specified in other examples
rg "@voltagent/core" --type json -A 1 | head -50Repository: VoltAgent/voltagent
Length of output: 2319
@voltagent/core@2.3.2 is not published on npm. Only version 2.3.1 is available; the latest published release (Jan 28, 2026). This will cause installation failures. Either publish version 2.3.2 before merging, or update all example package.json files to use ^2.3.1.
No breaking changes were introduced in 2.3.2; the breaking tool routing changes occurred in 2.3.0 and are not present in 2.3.1.
🤖 Prompt for AI Agents
In `@examples/with-voltagent-exporter/package.json` at line 6, The package.json in
the examples references an unpublished dependency "@voltagent/core": "^2.3.2"
which will break installs; update the dependency entry in this package.json (and
any other example package.json files) to use the published version "^2.3.1" or
change to a published tag, ensuring the dependency string is replaced wherever
"@voltagent/core": "^2.3.2" appears; if you intend to publish 2.3.2 instead,
hold merging until that release is available.
| "dependencies": { | ||
| "@ai-sdk/openai": "^3.0.0", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.3.2 npm package release notes breaking changes
💡 Result:
I couldn’t find any public release/tag/changelog entry for @voltagent/core@2.3.2. The most recent 2.3.x release I can locate is @voltagent/core@2.3.1. [1]
@voltagent/core@2.3.1 (what changed)
Patch changes
- Added separate workflow examples demonstrating both workflow APIs:
with-workflow(functionalcreateWorkflow)with-workflow-chain(fluentcreateWorkflowChain)
- Examples also demonstrate
workflowState/setWorkflowStatefor persisting data across steps. [1]
Breaking changes for 2.3.2
- Since I can’t find a
2.3.2release, I can’t confirm any2.3.2-specific breaking changes. - In general, patch releases (like 2.3.x) typically should not introduce breaking changes; the notable breaking/migration items are around the 1.x → 2.x jump (AI SDK v6 alignment, structured output approach changes, etc.). [2][3]
If you paste a link to where you’re seeing 2.3.2 (npm version page, Git tag, or internal registry), I can extract the exact release notes and call out any breaking changes precisely.
Sources: [1] [2] [3]
Update @voltagent/core to a published version.
@voltagent/core@2.3.2 does not exist on npm. The most recent 2.3.x release is 2.3.1. Update the dependency to "^2.3.1" or confirm when 2.3.2 will be published.
🤖 Prompt for AI Agents
In `@examples/with-voltagent-managed-memory/package.json` at line 6, The
package.json currently references the non-existent dependency string
"@voltagent/core": "^2.3.2"; update this dependency to a published version (e.g.
change the version specifier to "@voltagent/core": "^2.3.1") or confirm and wait
for the 2.3.2 release to be published before keeping the "^2.3.2" specifier.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.1", | ||
| "@voltagent/core": "^2.3.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.3.2 npm package
💡 Result:
@voltagent/core@2.3.2 does not appear to exist on npm.
- The npm package
@voltagent/corecurrently shows version 1.1.1 as the latest published release. [1] - VoltAgent’s docs UI shows “v2.0.x” (documentation/version track), which is likely what you’re seeing—not an npm
@voltagent/core2.x release, and not2.3.2. [2]
If you want to double-check from your machine, run:
npm view `@voltagent/core` versions --jsonSources: [1] [2]
🌐 Web query:
@voltagent/core 2.3.2 release notes breaking changes
💡 Result:
@voltagent/core@2.3.2 does not appear to be released (the latest tag/release shown is @voltagent/core@2.3.1, dated Jan 28, 2026). [1]
Breaking changes (closest relevant release: @voltagent/core@2.3.0)
In @voltagent/core@2.3.0 (Jan 28, 2026), tool routing changed in a breaking way: [2]
- Tool routing now uses two system tools:
searchTools+callTool(search first, then call). createToolRouterwas removed.toolRouting.routerswas removed.
@voltagent/core@2.3.1
2.3.1 is a patch release and the notes shown are example additions (no breaking change mentioned). [2]
Sources: [1] [2]
Update @voltagent/core to version 2.3.1 (2.3.2 does not exist on npm).
The package version 2.3.2 is not published on npm. The latest available release is 2.3.1 (Jan 28, 2026). The caret constraint ^2.3.2 will fail to resolve. Update the dependency to "@voltagent/core": "^2.3.1" or "2.3.1".
Note: Version 2.3.0 introduced breaking changes to tool routing (removed createToolRouter, changed routing to use searchTools + callTool). Verify the example works with these changes.
🤖 Prompt for AI Agents
In `@examples/with-workflow-chain/package.json` at line 6, Update the dependency
string for "@voltagent/core" in package.json from "^2.3.2" to "^2.3.1" (or
"2.3.1") so the package resolver can find the published version; after updating,
run the example and, if the example code uses the removed API createToolRouter,
replace usages with the new routing approach using searchTools and callTool
(refactor any createToolRouter calls to use searchTools to find tools and
callTool to invoke them).
2 participants
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@voltagent/core@2.3.2
Patch Changes
38a80bcThanks @omeraplak! - fix: preserve OpenAI reasoning/tool metadata during summarization so function_call items keep their required reasoning references and no longer errorSummary by cubic
Publish @voltagent/core 2.3.2 and update all example packages to use it. This patch preserves OpenAI reasoning/tool metadata during summarization, preventing errors in function_call items.
Written for commit efe2785. Summary will update on new commits.
Summary by CodeRabbit
Bug Fixes
Chores