Conversation
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughRemoved documentation/changeset entries about tool hooks, onToolEnd overrides, and tool routing; bumped Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant Agent
participant Router
participant Registry
participant Tool
Client->>Agent: request that may require tool
Agent->>Router: determine target tool (with arguments)
Router->>Registry: resolve provider-qualified embedding/model IDs
Registry-->>Router: model/provider info
Router-->>Agent: selected tool + routing metadata
Agent->>Tool: invoke tool (may call embedding/model)
Tool-->>Agent: tool result
Agent->>Client: final response (may be overridden/truncated via agent hooks)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 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. 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}
Deploying voltagent with
|
| Latest commit: |
6d90547
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://848c9250.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Fix all issues with AI agents
In `@examples/with-custom-endpoints/package.json`:
- Line 6: The package.json dependency "@voltagent/core": "^2.2.0" is invalid on
npm; update it to a published version such as "@voltagent/core": "^2.1.6" (or
the correct intended version) and verify the example code is compatible with the
2.x breaking changes (AI SDK v6 alignment, telemetry removal, structured output
API deprecations) referenced in the review; locate the dependency entry in
package.json and replace the version string accordingly, then run npm install
and smoke-test the example to ensure compatibility.
In `@examples/with-groq-ai/package.json`:
- Line 6: The package.json dependency for "@voltagent/core" is pinned to a
non-published version "^2.2.0"; update that dependency entry (the
"@voltagent/core" line in package.json) to a published 2.1.x release such as
"^2.1.2" (or the latest 2.1.x) so installations succeed, then run npm install /
yarn install to verify.
In `@examples/with-netlify-functions/package.json`:
- Line 6: The package.json lists a non-existent dependency version
"@voltagent/core": "^2.2.0"; update that dependency entry to a published version
such as "@voltagent/core": "^2.1.6" so installs succeed—edit the dependency line
in package.json replacing the "^2.2.0" specifier with "^2.1.6".
In `@examples/with-postgres/package.json`:
- Line 7: The package.json dependency "@voltagent/core": "^2.2.0" refers to a
non-existent npm release and prevents installs; update that dependency entry to
"@voltagent/core": "^2.1.6" so the example can be installed successfully, and
run npm install to verify; also scan for any code relying on 2.2.0-only features
(telemetry/AI SDK changes) and adjust usage if you encounter missing APIs.
In `@examples/with-thinking-tool/package.json`:
- Line 6: The package.json dependency entry for "@voltagent/core" references a
non-existent version "2.2.0"; update the dependency value for "@voltagent/core"
in package.json to a published version (for example "2.1.6" or another available
release) so installations succeed, then run npm install to verify the change.
In `@examples/with-vercel-ai/package.json`:
- Line 6: Update the dependency declaration for "@voltagent/core" in
package.json to use a published version (e.g., change "^2.2.0" to "^2.1.0") or
document that 2.2.0 is a private/dist-tag; then run npm install to verify
resolution. If you are moving from VoltAgent 1.x to 2.x, refactor any uses of
generateObject / streamObject to use generateText / streamText combined with
Output.object(), and remove or migrate any telemetry and server configuration
options from core as those were removed in 2.x.
🧹 Nitpick comments (2)
packages/core/CHANGELOG.md (1)
9-29: Align example with output-schema validation claim.The text mentions output validation when an output schema exists, but the example doesn’t show
outputSchema. Consider adding it (or a brief note) to make the behavior tangible.examples/with-zapier-mcp/package.json (1)
7-7: Consider using caret (^) for consistency.This example uses tilde (
~2.2.0) while all other examples in this PR use caret (^2.2.0). The tilde restricts updates to patch versions only, which may cause this example to drift behind other examples during minor updates.Suggested fix for consistency
- "@voltagent/core": "~2.2.0", + "@voltagent/core": "^2.2.0",
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.2.0 npm package release notes breaking changes
💡 Result:
As of January 23, 2026, I can’t find any published @voltagent/core@2.2.0 release (no npm/CDN listing and no GitHub release tag for that version). The newest published version I can verify is 2.1.6. [1][2]
Release notes (closest available: 2.1.x line)
Recent @voltagent/core release notes are posted as GitHub “Releases” entries per version tag (e.g., @voltagent/core@2.1.6, 2.1.5, 2.1.4, etc.). [2]
Breaking changes
- No evidence of breaking changes specifically for “2.2.0” because that version does not appear to exist/published. [1][2]
- The major breaking-ish shift is the 1.x → 2.x upgrade, which aligns VoltAgent with AI SDK v6 and includes notable platform changes such as removal of legacy telemetry/exporter from core (moved to OpenTelemetry-based observability) and deprecations around structured output APIs (
generateObject/streamObjectdeprecated in favor ofgenerateText/streamText+Output.object(...)). [3][4]
Sources: jsDelivr package page (version), GitHub releases, VoltAgent migration guide, and VoltAgent 2.x release notes text. [1][2][3][4]
Update @voltagent/core to an available version.
@voltagent/core@2.2.0 does not exist on npm. The latest published version is 2.1.6. Update the dependency to "@voltagent/core": "^2.1.6" or verify the intended version.
Note: The 2.x major version includes breaking changes (AI SDK v6 alignment, legacy telemetry removal, structured output API deprecations). Ensure the example code is compatible.
🤖 Prompt for AI Agents
In `@examples/with-custom-endpoints/package.json` at line 6, The package.json
dependency "@voltagent/core": "^2.2.0" is invalid on npm; update it to a
published version such as "@voltagent/core": "^2.1.6" (or the correct intended
version) and verify the example code is compatible with the 2.x breaking changes
(AI SDK v6 alignment, telemetry removal, structured output API deprecations)
referenced in the review; locate the dependency entry in package.json and
replace the version string accordingly, then run npm install and smoke-test the
example to ensure compatibility.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.2.0 npm package
💡 Result:
I couldn’t find any public record of an npm release @voltagent/core@2.2.0 (no matching release/changelog pages turned up in search).
What is visible publicly is that @voltagent/core has 2.x releases (e.g., 2.1.x on the project’s GitHub release feed), so 2.2.0 likely hasn’t been published (or isn’t indexed publicly) as of now. [1]
How to verify from your machine (authoritative):
npm view `@voltagent/core` version
npm view `@voltagent/core` versions --json | node -p 'JSON.parse(fs.readFileSync(0,"utf8")).slice(-20)'If you meant “latest 2.x”, check the project’s release feed and install that exact version (example shown in the feed: 2.1.x). [1]
Sources:
[1] VoltAgent GitHub release feed showing recent @voltagent/core 2.1.x releases (e.g., 2.1.2/2.1.1 listed as latest) https://newreleases.io/project/github/VoltAgent/voltagent/release/%40voltagent%2Fcore%402.0.11
@voltagent/core 2.2.0 is not published on npm and must be updated.
Version 2.2.0 does not appear in npm registry; latest available versions are 2.1.x. Update the dependency to an actual published version (e.g., ^2.1.2 or the latest 2.1.x release) to avoid installation failures.
🤖 Prompt for AI Agents
In `@examples/with-groq-ai/package.json` at line 6, The package.json dependency
for "@voltagent/core" is pinned to a non-published version "^2.2.0"; update that
dependency entry (the "@voltagent/core" line in package.json) to a published
2.1.x release such as "^2.1.2" (or the latest 2.1.x) so installations succeed,
then run npm install / yarn install to verify.
| "version": "1.0.0", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.2.0
💡 Result:
@voltagent/core does not have an npm release 2.2.0 (it isn’t in the published version list). The latest published version is 2.1.6 as of Jan 23, 2026. [1]
If you tried npm i @voltagent/core@2.2.0, it will fail because that version isn’t published. [1]
Sources
[1] (socket.dev)
Citations:
🌐 Web query:
@voltagent/core 2.2.0 release notes breaking changes
💡 Result:
I couldn’t find any @voltagent/core 2.2.0 release/tag or release notes in the official VoltAgent GitHub releases feed; the newest @voltagent/core release I can see there is 2.1.6 (Jan 21, 2026). [1]
If you’re upgrading within the 2.x line, the VoltAgent docs’ 1.x → 2.x migration guide highlights the notable breaking change in @voltagent/core as:
- Message helper utilities now accept/return
UIMessageinstead ofBaseMessage(type-level breaking change). [2]
Other important 2.x upgrade notes called out there (not necessarily “breaking” at the VoltAgent API level, but potentially impactful) include:
- Legacy
telemetry/*+ telemetry exporter removed from core in favor of OpenTelemetry-based observability. [2] - If you used VoltAgent structured-output helpers:
generateObject/streamObjectare deprecated in 2.x (migration guide recommendsgenerateText/streamTextwithOutput.object(...)). [2]
If you have a link to 2.2.0 (npm dist-tag, GitHub tag, or changelog entry), paste it and I’ll extract the exact breaking changes from that specific release.
References: [1] [2]
@voltagent/core version 2.2.0 does not exist on npm. The latest published version is 2.1.6 (Jan 23, 2026). Update the dependency to "@voltagent/core": "^2.1.6" or the dependency installation will fail.
🤖 Prompt for AI Agents
In `@examples/with-netlify-functions/package.json` at line 6, The package.json
lists a non-existent dependency version "@voltagent/core": "^2.2.0"; update that
dependency entry to a published version such as "@voltagent/core": "^2.1.6" so
installs succeed—edit the dependency line in package.json replacing the "^2.2.0"
specifier with "^2.1.6".
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 npm release notes breaking changes
💡 Result:
As of Jan 23, 2026, there is no @voltagent/core 2.2.0 release published (latest shown is 2.1.6), so there are no 2.2.0 release notes or breaking changes to report. [1][2]
If you were expecting “2.2.0” because you’re upgrading from 1.x → 2.x: VoltAgent’s docs state no breaking changes in VoltAgent APIs, but note ecosystem changes like removal of legacy telemetry/* from core (moved to OpenTelemetry-based observability) and upstream AI SDK v6 alignment. [3]
Sources: [1] [2] [3]
Update @voltagent/core to an available version.
@voltagent/core version 2.2.0 does not exist on npm—only 2.1.6 is currently published. Update the dependency to "@voltagent/core": "^2.1.6" to ensure the example installs successfully. Note that ecosystem changes between versions (telemetry moved to OpenTelemetry-based observability, AI SDK v6 alignment) should be reviewed if upgrading from 1.x.
🤖 Prompt for AI Agents
In `@examples/with-postgres/package.json` at line 7, The package.json dependency
"@voltagent/core": "^2.2.0" refers to a non-existent npm release and prevents
installs; update that dependency entry to "@voltagent/core": "^2.1.6" so the
example can be installed successfully, and run npm install to verify; also scan
for any code relying on 2.2.0-only features (telemetry/AI SDK changes) and
adjust usage if you encounter missing APIs.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 npm package
💡 Result:
@voltagent/core@2.2.0 does not appear to be published on the public npm registry/CDN mirrors (no listing for 2.2.0). The latest version showing on package mirrors is 2.1.6 (jsDelivr) and 2.1.0 (Socket’s analysis snapshot). [1], [2]
- Package:
@voltagent/core(VoltAgent’s core runtime for building AI agents in TypeScript/JavaScript) [3] - Install (latest available):
npm i `@voltagent/core` - To verify from your machine (authoritative):
npm view `@voltagent/core` version npm view `@voltagent/core` versions --json
Sources: jsDelivr package page [1], Socket package analysis [2], VoltAgent GitHub repo [3].
@voltagent/core 2.2.0 does not exist on npm and will cause installation failures.
Update to an available version such as 2.1.6 or earlier, as the specified version is not published on the public registry.
🤖 Prompt for AI Agents
In `@examples/with-thinking-tool/package.json` at line 6, The package.json
dependency entry for "@voltagent/core" references a non-existent version
"2.2.0"; update the dependency value for "@voltagent/core" in package.json to a
published version (for example "2.1.6" or another available release) so
installations succeed, then run npm install to verify the change.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.2.0 npm package release notes breaking changes
💡 Result:
I couldn’t find any public release/tag/changelog entry for @voltagent/core@2.2.0 (it doesn’t show up in the VoltAgent GitHub release feeds; the highest version shown there is @voltagent/core@2.1.0). [2]
Closest available “breaking-change” guidance (for the 1.x → 2.x line):
- VoltAgent says there are no breaking changes in VoltAgent APIs for 2.x if you only use VoltAgent APIs, but you may need changes if you call Vercel AI SDK directly because VoltAgent 2.x aligns with AI SDK v6. [1][3]
- Structured output:
generateObject/streamObjectare deprecated in VoltAgent 2.x; usegenerateText/streamTextwithOutput.object(...). [3] - Observability: legacy
telemetry/*and the telemetry exporter were removed from core; observability moved to OpenTelemetry. [1] - Server config: core options like
port,enableSwaggerUI,autoStart, and custom endpoint registration were removed from core; you now pass a server provider (e.g.honoServer()) and useconfigureAppfor custom routes. [1]
If you can share where you saw “2.2.0” (link/screenshot or package-lock.json snippet), I can reconcile whether it’s a private/dist-tag build, a fork, or a different package name.
Sources: [1] [2] [3]
Use a published version of @voltagent/core—2.2.0 is not available on npm.
The highest released version is 2.1.0. Update the dependency to a version that exists (e.g., "^2.1.0") or clarify if 2.2.0 is a private/dist-tag build. If upgrading from 1.x, note that VoltAgent 2.x removes generateObject / streamObject (use generateText / streamText with Output.object() instead) and removes telemetry and server configuration options from core.
🤖 Prompt for AI Agents
In `@examples/with-vercel-ai/package.json` at line 6, Update the dependency
declaration for "@voltagent/core" in package.json to use a published version
(e.g., change "^2.2.0" to "^2.1.0") or document that 2.2.0 is a
private/dist-tag; then run npm install to verify resolution. If you are moving
from VoltAgent 1.x to 2.x, refactor any uses of generateObject / streamObject to
use generateText / streamText combined with Output.object(), and remove or
migrate any telemetry and server configuration options from core as those were
removed in 2.x.
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
5ea8146 to
47336eb
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@examples/with-a2a-server/package.json`:
- Line 5: The package.json currently pins the dependency "@voltagent/core" to a
non-existent version "2.2.0"; update the dependency entry for "@voltagent/core"
to the published version "2.1.6" and regenerate your lockfile (npm install /
yarn install) so installs succeed and the lockfile matches the new version.
♻️ Duplicate comments (1)
examples/with-thinking-tool/package.json (1)
6-6: Duplicate: verify@voltagent/core@^2.2.0 availability.
Same dependency version check applies to this example.#!/bin/bash npm view `@voltagent/core` version npm view `@voltagent/core` versions --json
| "dependencies": { | ||
| "@voltagent/a2a-server": "^2.0.2", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core` version
npm view `@voltagent/core` versions --jsonRepository: VoltAgent/voltagent
Length of output: 2225
Change @voltagent/core version to 2.1.6 (latest available).
Version 2.2.0 does not exist on npm registry. The latest published version is 2.1.6. Update the dependency version to match an available release to prevent install failures.
🤖 Prompt for AI Agents
In `@examples/with-a2a-server/package.json` at line 5, The package.json currently
pins the dependency "@voltagent/core" to a non-existent version "2.2.0"; update
the dependency entry for "@voltagent/core" to the published version "2.1.6" and
regenerate your lockfile (npm install / yarn install) so installs succeed and
the lockfile matches the new version.
47336eb to
e7645fb
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@examples/with-google-ai/package.json`:
- Line 6: Update the dependency entry for `@voltagent/core` in package.json where
it currently reads "@voltagent/core": "^2.2.0" to use the published version
"@voltagent/core": "^2.1.6" so installs succeed; locate the dependency line in
examples/with-google-ai's package.json and change the version string
accordingly.
♻️ Duplicate comments (10)
examples/with-retrieval/package.json (1)
6-6: Same verification as above for the@voltagent/corebump.examples/with-voltagent-actions/package.json (1)
6-6: Same verification as above for the@voltagent/corebump.examples/with-hooks/package.json (1)
6-6: Same verification as above for the@voltagent/corebump.examples/next-js-chatbot-starter-template/package.json (1)
19-19: Same verification as above for the@voltagent/corebump.examples/with-mcp-server/package.json (1)
4-4: Same verification as above for the@voltagent/corebump.examples/with-client-side-tools/package.json (1)
7-7: Same dependency-bump verification as other examples.Please confirm this example still builds/runs with
@voltagent/core2.2.0.examples/with-middleware/package.json (1)
7-7: Same dependency-bump verification as other examples.Please confirm this example still builds/runs with
@voltagent/core2.2.0.examples/with-retries-fallback/package.json (1)
7-7: Same dependency-bump verification as other examples.Please confirm this example still builds/runs with
@voltagent/core2.2.0.examples/with-rag-chatbot/package.json (1)
7-7: Same dependency-bump verification as other examples.Please confirm this example still builds/runs with
@voltagent/core2.2.0.examples/with-supabase/package.json (1)
7-7: Same dependency-bump verification as other examples.Please confirm this example still builds/runs with
@voltagent/core2.2.0.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Verify lockfile resolutions for `@voltagent/core`
fd -H -t f 'pnpm-lock.yaml|package-lock.json|yarn.lock' -x rg -n "@voltagent/core" {}Repository: VoltAgent/voltagent
Length of output: 182
🏁 Script executed:
# Check the structure of the example and if it has dependencies resolved
ls -la examples/with-google-ai/Repository: VoltAgent/voltagent
Length of output: 182
🏁 Script executed:
# Check if there's a lockfile in the example directory specifically
cd examples/with-google-ai && ls -la | grep -E 'lock|package.json'Repository: VoltAgent/voltagent
Length of output: 125
🌐 Web query:
@voltagent/core 2.2.0 release notes breaking changes
💡 Result:
I couldn’t find any published @voltagent/core 2.2.0 release (and therefore no 2.2.0 release notes or breaking-changes list). The GitHub Releases feed for the repo shows @voltagent/core in the 2.1.x line (e.g. 2.1.6 on Jan 21, 2026), not 2.2.0 [1]. Third‑party package/version trackers likewise don’t show a 2.2.0 version for @voltagent/core [2].
If you meant a different package (e.g. @voltagent/server-core) or a prerelease tag, tell me the link/tag name and I’ll extract the breaking changes.
Sources: [1], [2]
🌐 Web query:
@voltagent/core npm package version 2.2.0
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.2.0 has been published to npm.
The most recent published version I can verify from public package mirrors is 2.1.6 (jsDelivr). [1] Recent release trackers also list latest @voltagent/core releases in the 2.0.x–2.1.x range (e.g., 2.1.0 shown by Socket; older 2.0.x releases on NewReleases). [2][3]
If you try to install 2.2.0 and it fails, install the latest known version instead:
npm i `@voltagent/core`@2.1.6Sources: [1] [2] [3]
@voltagent/core 2.2.0 does not exist — downgrade to 2.1.6.
The latest published version of @voltagent/core is 2.1.6 (as of Jan 21, 2026). Version 2.2.0 is not available on npm, so package installation will fail. Update the dependency to "@voltagent/core": "^2.1.6".
🤖 Prompt for AI Agents
In `@examples/with-google-ai/package.json` at line 6, Update the dependency entry
for `@voltagent/core` in package.json where it currently reads "@voltagent/core":
"^2.2.0" to use the published version "@voltagent/core": "^2.1.6" so installs
succeed; locate the dependency line in examples/with-google-ai's package.json
and change the version string accordingly.
e7645fb to
c94ad9a
Compare
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In `@examples/with-composio-mcp/package.json`:
- Line 7: The dependency entry "@voltagent/core": "^2.2.0" in package.json is
pointing to a version that doesn't exist; update the dependency to a published
version or correct package name so the example can install. Locate the
dependency line for "@voltagent/core" in package.json and replace the version
string with a valid published version (or change the package name if it was
mistyped), then run npm/yarn to verify installation succeeds.
In `@examples/with-mcp-server/package.json`:
- Line 4: Update the package.json dependency for `@voltagent/core` to a published
version: replace the nonexistent version specifier "^2.2.0" with a valid
published version such as "^2.1.6" so installations succeed; edit the dependency
entry for "@voltagent/core" in package.json to the new version string.
In `@examples/with-research-assistant/package.json`:
- Around line 5-7: The package.json dependency for "@voltagent/core" is set to a
non-existent version ("^2.2.0"); update the dependency string to the latest
published version by changing "@voltagent/core": "^2.2.0" to "@voltagent/core":
"^2.1.6" in package.json (the dependency line in the diff) and then run your
install/test step to verify the install succeeds.
In `@examples/with-zapier-mcp/package.json`:
- Line 7: Update the `@voltagent/core` dependency specifier in package.json from
"~2.2.0" to "^2.2.0" so it matches the project's versioning pattern; locate the
dependency entry for "@voltagent/core" in examples/with-zapier-mcp/package.json
and change the tilde-prefixed version to a caret-prefixed one.
| "name": "voltagent-example-with-mcp-server", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Query npm registry for `@voltagent/core` package info
curl -s https://registry.npmjs.org/@voltagent/core | jq -r '.versions["2.2.0"] | if . then {version: .version, peerDependencies: .peerDependencies} else "VERSION_NOT_FOUND" end'Repository: VoltAgent/voltagent
Length of output: 80
🏁 Script executed:
#!/bin/bash
# Get all available versions of `@voltagent/core`
curl -s https://registry.npmjs.org/@voltagent/core | jq -r '.versions | keys | sort -V | tail -20'Repository: VoltAgent/voltagent
Length of output: 324
🏁 Script executed:
#!/bin/bash
# Get available versions of `@voltagent/core`
curl -s https://registry.npmjs.org/@voltagent/core | jq -r '.versions | keys[]' | sort -rV | head -20Repository: VoltAgent/voltagent
Length of output: 187
@voltagent/core@2.2.0 does not exist on npm—update to an available version.
The specified version is not published. The latest available version is 2.1.6. Update the dependency to a published version, such as "@voltagent/core": "^2.1.6", to prevent installation failures.
🤖 Prompt for AI Agents
In `@examples/with-mcp-server/package.json` at line 4, Update the package.json
dependency for `@voltagent/core` to a published version: replace the nonexistent
version specifier "^2.2.0" with a valid published version such as "^2.1.6" so
installations succeed; edit the dependency entry for "@voltagent/core" in
package.json to the new version string.
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check `@voltagent/core` version metadata from npm registry
curl -s https://registry.npmjs.org/@voltagent/core | jq '.versions["2.2.0"] | {version, peerDependencies, engines, dependencies}' 2>/dev/null || echo "Query failed or version not found"Repository: VoltAgent/voltagent
Length of output: 155
🏁 Script executed:
# Also check the full package.json context
cat examples/with-research-assistant/package.jsonRepository: VoltAgent/voltagent
Length of output: 871
🏁 Script executed:
# Check what versions exist for `@voltagent/core`
curl -s https://registry.npmjs.org/@voltagent/core | jq '.versions | keys | sort' 2>/dev/null | head -50Repository: VoltAgent/voltagent
Length of output: 646
🏁 Script executed:
# Also check if the package exists and get release info
curl -s https://registry.npmjs.org/@voltagent/core | jq '{name, "dist-tags": .["dist-tags"], latest_release: .time.modified}' 2>/dev/nullRepository: VoltAgent/voltagent
Length of output: 214
🏁 Script executed:
# Check all versions in the 2.x range
curl -s https://registry.npmjs.org/@voltagent/core | jq '.versions | keys | map(select(startswith("2."))) | sort' 2>/dev/nullRepository: VoltAgent/voltagent
Length of output: 312
@voltagent/core 2.2.0 is not published; downgrade to latest available 2.1.6.
Version 2.2.0 does not exist in the npm registry. The latest available version is 2.1.6. Update the dependency to "@voltagent/core": "^2.1.6" to resolve installation failures.
🤖 Prompt for AI Agents
In `@examples/with-research-assistant/package.json` around lines 5 - 7, The
package.json dependency for "@voltagent/core" is set to a non-existent version
("^2.2.0"); update the dependency string to the latest published version by
changing "@voltagent/core": "^2.2.0" to "@voltagent/core": "^2.1.6" in
package.json (the dependency line in the diff) and then run your install/test
step to verify the install succeeds.
| "author": "", | ||
| "dependencies": { | ||
| "@voltagent/core": "~2.1.6", | ||
| "@voltagent/core": "~2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Explore repo structure to understand context
find . -name "package.json" -type f | head -20Repository: VoltAgent/voltagent
Length of output: 946
🏁 Script executed:
# Check if `@voltagent/core` is an internal package
find . -name "package.json" -type f -exec grep -l "@voltagent/core" {} \;Repository: VoltAgent/voltagent
Length of output: 4488
🏁 Script executed:
# Look for CHANGELOG or release notes files
find . -type f \( -name "CHANGELOG*" -o -name "HISTORY*" -o -name "RELEASE*" -o -name "NEWS*" \) | head -20Repository: VoltAgent/voltagent
Length of output: 889
🏁 Script executed:
# Check the specific file mentioned in the review
cat examples/with-zapier-mcp/package.jsonRepository: VoltAgent/voltagent
Length of output: 850
🏁 Script executed:
# Check core package.json to see current version
cat packages/core/package.json | head -30Repository: VoltAgent/voltagent
Length of output: 1140
🏁 Script executed:
# Check CHANGELOG for core package to understand 2.2.0 changes
head -100 packages/core/CHANGELOG.mdRepository: VoltAgent/voltagent
Length of output: 3203
🏁 Script executed:
# Check what version other examples use for `@voltagent/core`
grep -r "@voltagent/core" examples/*/package.json | grep -v node_modulesRepository: VoltAgent/voltagent
Length of output: 5789
Align version specifier with project pattern.
The @voltagent/core 2.2.0 is stable and compatible (includes additive tool routing and hook features, no breaking changes). However, use ^2.2.0 instead of ~2.2.0 to match the versioning strategy across other examples in the project.
- "@voltagent/core": "~2.2.0",
+ "@voltagent/core": "^2.2.0",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@voltagent/core": "~2.2.0", | |
| "@voltagent/core": "^2.2.0", |
🤖 Prompt for AI Agents
In `@examples/with-zapier-mcp/package.json` at line 7, Update the `@voltagent/core`
dependency specifier in package.json from "~2.2.0" to "^2.2.0" so it matches the
project's versioning pattern; locate the dependency entry for "@voltagent/core"
in examples/with-zapier-mcp/package.json and change the tilde-prefixed version
to a caret-prefixed one.
c94ad9a to
d846ccb
Compare
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In `@examples/with-rag-chatbot/package.json`:
- Around line 6-8: The package.json dependency for "@voltagent/core" is pinned
to a non-existent release ("^2.2.0"); update the dependency declaration for
"@voltagent/core" in package.json to a published version (e.g., "^2.1.6") or
explicitly use a prerelease tag if that was intended, then run npm/yarn install
to verify resolution; look for the "@voltagent/core" entry in the dependencies
block to make this change.
In `@examples/with-resumable-streams/package.json`:
- Line 7: The package.json dependency for "@voltagent/core" is pinned to a
non-existent version "^2.2.0"; update the dependency entry for "@voltagent/core"
to the published version "2.1.6" (replace "^2.2.0" with "2.1.6") so installs
succeed.
In `@examples/with-supabase/package.json`:
- Line 7: The dependency entry "@voltagent/core": "^2.2.0" in package.json is
referencing a non-published version; update that dependency to the latest
published version by changing "@voltagent/core": "^2.2.0" to "@voltagent/core":
"^2.1.6" so npm install succeeds; ensure package.json's dependencies object only
contains the corrected version string and run npm install to verify.
In `@examples/with-workflow/package.json`:
- Line 6: The package.json dependency "@voltagent/core": "^2.2.0" references a
non-existent release; update the dependency to a valid published version or
switch to a local workspace/pre-release setup: either change the version string
to the latest released version "@voltagent/core": "^1.2.14" (or the intended
released tag) or document/implement a workspace/local link (e.g., via npm/yarn
workspaces or file: path) if this example requires a development build; update
all example package.json files that follow the same pattern to avoid install
failures.
♻️ Duplicate comments (3)
examples/with-research-assistant/package.json (1)
6-6: Re-check@voltagent/core@^2.2.0 availability.Same as earlier: confirm 2.2.0 is published in npm at merge time so this example remains installable.
examples/with-composio-mcp/package.json (1)
7-7: Verify@voltagent/core@2.2.0 is published before merging.Public package indexes currently list versions below 2.2.0 (jsDelivr shows 2.1.6; npm’s package page snapshot shows 1.1.1), so this range may not resolve until 2.2.0 is published. (jsdelivr.com)
If 2.2.0 isn’t live yet, keep the previous range until the publish completes.
📌 Suggested fallback (if publish isn’t complete)
- "@voltagent/core": "^2.2.0", + "@voltagent/core": "^2.1.6",examples/with-postgres/package.json (1)
7-7: Verify@voltagent/core@2.2.0 is published before merging.Public package indexes currently list versions below 2.2.0 (jsDelivr shows 2.1.6; npm’s package page snapshot shows 1.1.1), so this range may not resolve until 2.2.0 is published. (jsdelivr.com)
If 2.2.0 isn’t live yet, keep the previous range until the publish completes.
📌 Suggested fallback (if publish isn’t complete)
- "@voltagent/core": "^2.2.0", + "@voltagent/core": "^2.1.6",
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 release notes breaking changes
💡 Result:
No @voltagent/core@2.2.0 release notes exist as of January 23, 2026—the highest published 2.x version I can find is 2.1.6. [1][2]
So: breaking changes in @voltagent/core@2.2.0
- None published (because 2.2.0 isn’t released). [1][2]
Closest relevant “breaking changes” (in the 2.x line overall)
From the official 1.x → 2.x migration guide, notable breaking/behavioral changes include:
- Message helper utilities now use
UIMessage(ai-sdk UI message type) instead ofBaseMessage. [3] - Legacy
telemetry/*and the old telemetry exporter were removed from core (replaced by OpenTelemetry-based observability). [3] - If you were using VoltAgent’s old server options:
port,enableSwaggerUI,autoStart, and custom endpoint registration were removed from core in favor of aserverprovider approach. [3]
Sources: Socket package versions (shows latest as 2.1.6, no 2.2.0) [1]; GitHub releases (shows @voltagent/core@2.1.6) [2]; VoltAgent migration guide 1.x → 2.x [3].
@voltagent/core@2.2.0 does not exist yet. As of January 23, 2026, the highest published version in the 2.x line is 2.1.6. The ^2.2.0 specifier will fail at install time. Revert to a released version (e.g., ^2.1.6) or clarify if a prerelease is intended.
🤖 Prompt for AI Agents
In `@examples/with-rag-chatbot/package.json` around lines 6 - 8, The package.json
dependency for "@voltagent/core" is pinned to a non-existent release ("^2.2.0");
update the dependency declaration for "@voltagent/core" in package.json to a
published version (e.g., "^2.1.6") or explicitly use a prerelease tag if that
was intended, then run npm/yarn install to verify resolution; look for the
"@voltagent/core" entry in the dependencies block to make this change.
| "author": "", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package latest version
💡 Result:
The latest published version of the @voltagent/core npm package is 2.1.0. [1] [2]
🌐 Web query:
@voltagent/core 2.2.0 published
💡 Result:
@voltagent/core 2.2.0 does not appear to be published (not listed among available versions / latest). The latest published version shown is 2.1.0. [1][2]
🏁 Script executed:
#!/bin/bash
# Query npm API for `@voltagent/core` package info
curl -s "https://registry.npmjs.org/@voltagent/core" | jq '.versions | keys' 2>/dev/null || echo "Could not fetch npm registry data"Repository: VoltAgent/voltagent
Length of output: 2219
@voltagent/core@2.2.0 is not published; update to 2.1.6 before merging.
Version 2.2.0 does not exist in the npm registry. The latest published version is 2.1.6. Using ^2.2.0 will cause installation to fail.
📌 Required change
- "@voltagent/core": "^2.2.0",
+ "@voltagent/core": "^2.1.6",📝 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.
| "@voltagent/core": "^2.2.0", | |
| "@voltagent/core": "^2.1.6", |
🤖 Prompt for AI Agents
In `@examples/with-resumable-streams/package.json` at line 7, The package.json
dependency for "@voltagent/core" is pinned to a non-existent version "^2.2.0";
update the dependency entry for "@voltagent/core" to the published version
"2.1.6" (replace "^2.2.0" with "2.1.6") so installs succeed.
| "@supabase/supabase-js": "^2.49.4", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>/dev/null | head -50Repository: VoltAgent/voltagent
Length of output: 642
🏁 Script executed:
npm view `@voltagent/core`@latest version 2>/dev/nullRepository: VoltAgent/voltagent
Length of output: 68
🏁 Script executed:
npm view `@voltagent/core` 2>/dev/null | grep -A 20 "versions:"Repository: VoltAgent/voltagent
Length of output: 741
Revert @voltagent/core to ^2.1.6 — version 2.2.0 is not published.
The bumped version 2.2.0 does not exist on npm. The latest published version is 2.1.6. The npm install command will fail with this unresolved version constraint.
Fix
- "@voltagent/core": "^2.2.0",
+ "@voltagent/core": "^2.1.6",📝 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.
| "@voltagent/core": "^2.2.0", | |
| "@voltagent/core": "^2.1.6", |
🤖 Prompt for AI Agents
In `@examples/with-supabase/package.json` at line 7, The dependency entry
"@voltagent/core": "^2.2.0" in package.json is referencing a non-published
version; update that dependency to the latest published version by changing
"@voltagent/core": "^2.2.0" to "@voltagent/core": "^2.1.6" so npm install
succeeds; ensure package.json's dependencies object only contains the corrected
version string and run npm install to verify.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 release notes changelog breaking changes
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.2.0 exists (no GitHub release/tag for it, and the project’s published releases don’t list it). The latest @voltagent/core release shown in the official VoltAgent GitHub Releases page is @voltagent/core@1.2.14 (Dec 3, 2025). [1]
If you were expecting “2.x” breaking changes, VoltAgent’s docs state that 2.x aligns with AI SDK v6 and provides a migration guide (it includes breaking changes such as message helper types moving to UIMessage, plus removals around legacy telemetry/exporter wiring). [2]
Where to check changelogs/release notes:
- VoltAgent GitHub Releases (authoritative per-package release notes): [1]
- VoltAgent 1.x → 2.x migration guide (breaking-change style notes): [2]
Sources: [1] [2]
🏁 Script executed:
# Search for other package.json files in examples to understand existing patterns
find examples -name "package.json" -type fRepository: VoltAgent/voltagent
Length of output: 3369
🏁 Script executed:
# Check the current package.json file to understand its full structure
cat examples/with-workflow/package.jsonRepository: VoltAgent/voltagent
Length of output: 892
🏁 Script executed:
# Search for `@voltagent/core` versions in other example package.json files
grep -r '"@voltagent/core"' examples --include="package.json" | head -20Repository: VoltAgent/voltagent
Length of output: 1524
Resolve version mismatch: @voltagent/core 2.2.0 does not exist.
The version @voltagent/core@2.2.0 is not published. The latest released version is @voltagent/core@1.2.14 (Dec 3, 2025). This constraint will cause npm install to fail. Verify whether this example should pin ^1.2.14 or if it requires a pre-release/development setup with local workspace linking. Note that this pattern appears across most examples in the repository, suggesting a systemic issue.
🤖 Prompt for AI Agents
In `@examples/with-workflow/package.json` at line 6, The package.json dependency
"@voltagent/core": "^2.2.0" references a non-existent release; update the
dependency to a valid published version or switch to a local
workspace/pre-release setup: either change the version string to the latest
released version "@voltagent/core": "^1.2.14" (or the intended released tag) or
document/implement a workspace/local link (e.g., via npm/yarn workspaces or
file: path) if this example requires a development build; update all example
package.json files that follow the same pattern to avoid install failures.
d846ccb to
18ad1d1
Compare
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Fix all issues with AI agents
In `@examples/with-hooks/package.json`:
- Line 6: The package.json dependency for "@voltagent/core" references a
non-existent version "2.2.0"; update that dependency entry in
examples/with-hooks package.json to a published version (e.g., "1.1.1") so
installations succeed—edit the "@voltagent/core" version string in package.json
to a valid semver (such as "1.1.1") and run npm install to verify.
In `@examples/with-subagents/package.json`:
- Line 7: Update the dependency version for `@voltagent/core` in package.json:
replace the current caret version ^2.2.0 with ^2.1.0 so the example installs
against the published npm "latest" dist-tag; locate the "@voltagent/core" entry
in the dependencies object and change its version string accordingly.
In `@examples/with-tool-routing/package.json`:
- Line 7: The dependency entry for "@voltagent/core" in package.json uses a
non-existent version "2.2.0"; update that dependency string to a published
version (e.g., "^2.1.6") so installs succeed, then run your package manager
(npm/yarn/pnpm) to refresh lockfiles; specifically change the "@voltagent/core":
"^2.2.0" line to "@voltagent/core": "^2.1.6" and regenerate
node_modules/lockfile.
In `@examples/with-turso/package.json`:
- Line 7: Replace the non-existent dependency version for "@voltagent/core" in
package.json: change the version specifier "^2.2.0" to the published release
"2.1.6" (e.g., replace the string "^2.2.0" with "2.1.6") so installs succeed;
look for the "@voltagent/core" entry in package.json to make this edit.
In `@packages/core/package.json`:
- Line 4: The package.json "version" field for `@voltagent/core` is set to 2.2.0
but that release is not published or tagged; either change the "version" value
in packages/core/package.json to a published release (e.g., match the npm/GitHub
latest like 2.1.0 or 2.1.6) or publish and create a GitHub release/tag for
`@voltagent/core`@2.2.0 before merging so the package version matches an actual
published release.
♻️ Duplicate comments (5)
examples/with-netlify-functions/package.json (1)
6-6: Already flagged in a prior review.
Please follow the earlier verification about the@voltagent/core2.2.0 publish status.examples/with-resumable-streams/package.json (1)
7-7: Duplicate: verify@voltagent/core@^2.2.0 is published.Same concern as prior review—please confirm availability to avoid failed installs.
Check the npm registry for `@voltagent/core` and confirm whether 2.2.0 is published.examples/with-postgres/package.json (1)
7-7: Duplicate: verify@voltagent/core@^2.2.0 is published.Same as earlier feedback—please confirm availability to avoid install failures.
Confirm on npm whether `@voltagent/core` version 2.2.0 is published.examples/with-workflow/package.json (1)
6-6: Version bump is correct for Changesets release workflow.This is a Changesets release PR—version bumps occur before the npm publish step, which triggers automatically when this PR merges. The
@voltagent/core@2.2.0package will be published at that point. Since this example is marked"private": trueand uses workspace linking during development, the dependency will resolve correctly both locally and after the release.examples/with-research-assistant/package.json (1)
6-6: Version bump aligns with Changesets release workflow.Same context as other examples: the version will be published when this PR merges. The private example package uses workspace linking locally, and the npm-published version will be available post-merge.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package latest version published
💡 Result:
The npm package @voltagent/core shows latest version 1.1.1, with “Last publish: 11 hours ago” on its npm page. [1]
Update @voltagent/core to an existing published version.
Version 2.2.0 does not exist on npm. The latest published version is 1.1.1. Using the non-existent version will cause installation to fail. Update to 1.1.1 or another available version.
🤖 Prompt for AI Agents
In `@examples/with-hooks/package.json` at line 6, The package.json dependency for
"@voltagent/core" references a non-existent version "2.2.0"; update that
dependency entry in examples/with-hooks package.json to a published version
(e.g., "1.1.1") so installations succeed—edit the "@voltagent/core" version
string in package.json to a valid semver (such as "1.1.1") and run npm install
to verify.
| "@ai-sdk/openai": "^3.0.0", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package latest version 2.2.0
💡 Result:
I can’t confirm 2.2.0 as the latest for @voltagent/core from the sources I can access right now.
- Socket reports the npm latest dist-tag as
2.1.0. [1] - NewReleases also lists recent
@voltagent/corereleases with the latest shown as2.1.0. [2]
To verify directly against npm from your machine, run:
npm view `@voltagent/core` version
npm view `@voltagent/core` dist-tagsUse @voltagent/core@^2.1.0 instead of ^2.2.0.
The npm latest dist-tag for @voltagent/core is 2.1.0, not 2.2.0. Specifying ^2.2.0 will cause installation to fail, making the example uninstallable. Update the dependency version to ^2.1.0.
🤖 Prompt for AI Agents
In `@examples/with-subagents/package.json` at line 7, Update the dependency
version for `@voltagent/core` in package.json: replace the current caret version
^2.2.0 with ^2.1.0 so the example installs against the published npm "latest"
dist-tag; locate the "@voltagent/core" entry in the dependencies object and
change its version string accordingly.
| "@ai-sdk/openai": "^3.0.0", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.2.0
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.2.0 exists/published on npm.
The most recent versions I can verify from third-party package indexes are in the 2.1.x range (e.g., 2.1.6 shown by jsDelivr, and 2.1.0 shown by Socket/NewReleases). [1] [2] [3]
If you’re seeing 2.2.0 in a lockfile or install log, paste the exact command output (or the relevant package-lock.json/pnpm-lock.yaml snippet) and I’ll help reconcile where it’s coming from.
Sources: [1] [2] [3]
Update @voltagent/core to an available version.
Version 2.2.0 is not published on npm. The latest available version is 2.1.6. Update the dependency to use an existing version to prevent install failures.
🤖 Prompt for AI Agents
In `@examples/with-tool-routing/package.json` at line 7, The dependency entry for
"@voltagent/core" in package.json uses a non-existent version "2.2.0"; update
that dependency string to a published version (e.g., "^2.1.6") so installs
succeed, then run your package manager (npm/yarn/pnpm) to refresh lockfiles;
specifically change the "@voltagent/core": "^2.2.0" line to "@voltagent/core":
"^2.1.6" and regenerate node_modules/lockfile.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.2.0
💡 Result:
I couldn’t find any evidence that @voltagent/core has an npm release 2.2.0.
The latest version I can verify via public package mirrors is 2.1.6 (jsDelivr’s npm mirror shows @voltagent/core at 2.1.6). [1] NewReleases’ GitHub release tracking also shows the most recent @voltagent/core releases in the 2.0.x–2.1.x range (e.g., @voltagent/core@2.1.0), with no 2.2.0 listed. [2]
Install (latest known):
npm i `@voltagent/core`@2.1.6If you specifically need 2.2.0: it may be unpublished, mis-typed, or from a different package—share where you saw “2.2.0” (link/screenshot/log) and I’ll verify that exact reference.
Sources: [1] [2]
Downgrade @voltagent/core to 2.1.6 — version 2.2.0 is not published on npm.
The caret constraint ^2.2.0 will cause install failures since 2.2.0 does not exist. The latest available version is 2.1.6.
🤖 Prompt for AI Agents
In `@examples/with-turso/package.json` at line 7, Replace the non-existent
dependency version for "@voltagent/core" in package.json: change the version
specifier "^2.2.0" to the published release "2.1.6" (e.g., replace the string
"^2.2.0" with "2.1.6") so installs succeed; look for the "@voltagent/core" entry
in package.json to make this edit.
| "name": "@voltagent/core", | ||
| "description": "VoltAgent Core - AI agent framework for JavaScript", | ||
| "version": "2.1.6", | ||
| "version": "2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 npm registry published
💡 Result:
As of January 23, 2026, I can’t find any evidence that @voltagent/core@2.2.0 has been published to the npm registry. Public version indexes list 2.1.0 as the latest for @voltagent/core, with no 2.2.0 present. [1], [2]
Sources: [1] [2]
🌐 Web query:
voltagent/core 2.2.0 GitHub release tag
💡 Result:
In the VoltAgent/voltagent GitHub repo, @voltagent/core is tagged using the format @voltagent/core@<version>. The tags list currently includes @voltagent/core@2.1.6 (Jan 21, 2026), and there is no @voltagent/core@2.2.0 release/tag present. [1]
So, a “voltagent/core 2.2.0” GitHub release tag does not exist (yet) in this repository. [1]
Sources: [1] https://github.com/VoltAgent/voltagent/tags
Do not merge: @voltagent/core 2.2.0 is not published and has no GitHub release tag.
As of January 23, 2026, version 2.2.0 does not exist on the npm registry (latest is 2.1.0) and no corresponding GitHub release tag exists (latest tag is @voltagent/core@2.1.6 from Jan 21, 2026). Update the version to match an actual published release or create and publish the 2.2.0 release before merging.
🤖 Prompt for AI Agents
In `@packages/core/package.json` at line 4, The package.json "version" field for
`@voltagent/core` is set to 2.2.0 but that release is not published or tagged;
either change the "version" value in packages/core/package.json to a published
release (e.g., match the npm/GitHub latest like 2.1.0 or 2.1.6) or publish and
create a GitHub release/tag for `@voltagent/core`@2.2.0 before merging so the
package version matches an actual published release.
18ad1d1 to
bb1910a
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@examples/with-retries-fallback/package.json`:
- Line 7: The dependency entry "@voltagent/core": "^2.2.0" is invalid; update
the package.json dependency to a published version such as "@voltagent/core":
"^2.1.0" so installs succeed—locate the dependency string ("@voltagent/core":
"^2.2.0") in package.json and replace the version specifier with "^2.1.0".
In `@packages/core/CHANGELOG.md`:
- Around line 101-111: The changelog example references getStatus in the Agent
toolRouting snippet without defining it, which can confuse readers; add a
one-line stub or a brief comment declaring getStatus (or note it's predeclared)
near the example so readers know it’s a function used in
toolRouting.pool/expose, and ensure the sample still shows Agent, toolRouting,
pool and expose to make the example self-contained and clear.
♻️ Duplicate comments (1)
examples/with-rag-chatbot/package.json (1)
7-7: Verify@voltagent/core@2.2.0 is actually published before merge.Public package indexes still list 2.1.x as the latest (jsDelivr shows 2.1.6; Socket shows 2.1.0), so if the publish step hasn’t run yet this example will fail to install. Please confirm the release workflow will publish 2.2.0 on merge or keep a published version until it’s live. (jsdelivr.com)
🧹 Nitpick comments (2)
packages/core/CHANGELOG.md (2)
71-95: Align embedding example with provider‑qualified IDs.The text highlights
openai/text-embedding-3-small, but the example usesopenai.embedding("text-embedding-3-small"). Consider switching to the provider‑qualified string to reinforce the new capability.
119-121: Resolver fallback returns empty args.For tools with required parameters,
return {}will fail schema validation. Consider adding a short note that the resolver must supply required args or throw for unsupported tools.
| "@ai-sdk/openai": "^3.0.0", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 release notes changelog
💡 Result:
I couldn’t find any published @voltagent/core 2.2.0 release notes/changelog entry: the available version lists for @voltagent/core currently go up to 2.1.0 (no 2.2.0 shown). [1]
If you meant a different package (or a prerelease/tag), tell me the exact registry (npm vs GitHub tag) and I’ll pull the right changelog. [2]
Sources: [1] [2]
🏁 Script executed:
cat examples/with-retries-fallback/package.jsonRepository: VoltAgent/voltagent
Length of output: 924
🌐 Web query:
@voltagent/core 2.2.0 prerelease npm beta alpha
💡 Result:
I can’t find any published prerelease of @voltagent/core in the 2.2.0-* range (alpha/beta/etc.) in public release feeds right now. The npm package page shows the current published version as 1.1.1. [1] Release trackers show 2.x exists (e.g., @voltagent/core@2.1.0, 2.0.14, etc.), but still nothing labeled 2.2.0-alpha/beta. [2]
To check/install prereleases on npm, use dist-tags and/or explicit prerelease versions:
npm dist-tag ls `@voltagent/core`
npm view `@voltagent/core` versions --json
npm i `@voltagent/core`@next # if they publish prereleases under "next"
npm i `@voltagent/core`@2.2.0-alpha.1 # if/when that exact version existsnpm dist-tags are just aliases (commonly latest, next, beta, etc.). [3]
Sources: [1] [2] [3]
@voltagent/core 2.2.0 does not exist—correct the version.
The version @voltagent/core@2.2.0 is not published on npm. The latest available release is 2.1.0. Update the dependency to an existing version (e.g., ^2.1.0) to ensure the example can install and run.
🤖 Prompt for AI Agents
In `@examples/with-retries-fallback/package.json` at line 7, The dependency entry
"@voltagent/core": "^2.2.0" is invalid; update the package.json dependency to a
published version such as "@voltagent/core": "^2.1.0" so installs succeed—locate
the dependency string ("@voltagent/core": "^2.2.0") in package.json and replace
the version specifier with "^2.1.0".
| ```ts | ||
| const agent = new Agent({ | ||
| name: "Support Agent", | ||
| instructions: "Use tool_router for tools.", | ||
| model: "openai/gpt-4o-mini", | ||
| toolRouting: { | ||
| embedding: "text-embedding-3-small", | ||
| pool: [getWeather], | ||
| expose: [getStatus], | ||
| }, | ||
| }); |
There was a problem hiding this comment.
Define getStatus (or note it’s predeclared).
The pool/expose snippet references getStatus without prior definition in the changelog entry, which may confuse readers. A one‑line stub or comment would help.
🤖 Prompt for AI Agents
In `@packages/core/CHANGELOG.md` around lines 101 - 111, The changelog example
references getStatus in the Agent toolRouting snippet without defining it, which
can confuse readers; add a one-line stub or a brief comment declaring getStatus
(or note it's predeclared) near the example so readers know it’s a function used
in toolRouting.pool/expose, and ensure the sample still shows Agent,
toolRouting, pool and expose to make the example self-contained and clear.
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
bb1910a to
6d90547
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@examples/with-nextjs-resumable-stream/package.json`:
- Line 20: The package.json dependency "@voltagent/core": "^2.2.0" references a
non-existent npm version; change that dependency entry to use the latest
published version (e.g. "@voltagent/core": "^2.1.6") or revert the bump and wait
until 2.2.0 is published so installs won't fail.
In `@examples/with-voltops-retrieval/package.json`:
- Around line 5-7: The package.json dependency entry for "@voltagent/core"
references a non-existent version "2.2.0"; update the dependency in package.json
to a valid released version (e.g., change the "@voltagent/core" value to
"^2.1.6") or confirm and switch to the correct prerelease tag if that was
intended; ensure the modified dependency string is consistent with the existing
entries for "@voltagent/cli" and "@voltagent/libsql" so npm/yarn install
resolves successfully.
♻️ Duplicate comments (3)
examples/with-vercel-ai/package.json (1)
6-6: LGTM — version bump is correct for this Changesets release PR.The previous review flagged that
@voltagent/core@2.2.0doesn't exist on npm, but that's expected: this PR is the Changesets release that will publish version 2.2.0 when merged. The example dependency update is part of the standard release workflow.examples/with-google-ai/package.json (1)
6-6: Confirm@voltagent/core@^2.2.0is published before release.If
2.2.0isn’t on npm yet, installs for this example will fail. Please verify availability before merging. Line 6.#!/bin/bash # Verify that `@voltagent/core` 2.2.0 exists on npm curl -s https://registry.npmjs.org/@voltagent/core | jq -r '.versions | keys[]' | grep -Fx '2.2.0'packages/core/CHANGELOG.md (1)
159-170: DefinegetStatus(or note it’s predeclared).The pool/expose snippet references
getStatuswithout defining it, which may confuse readers. Consider adding a one‑line stub or a brief comment that it’s predeclared.
| "@tavily/core": "^0.6.3", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify `@voltagent/core` 2.2.0 publication status
echo "Checking `@voltagent/core` dist-tags..."
curl -s https://registry.npmjs.org/@voltagent/core | jq -r '.["dist-tags"] // empty'
echo ""
echo "Checking if version 2.2.0 exists..."
curl -s https://registry.npmjs.org/@voltagent/core | jq -e '.versions["2.2.0"]' >/dev/null 2>&1 && echo "✓ Version 2.2.0 is published" || echo "✗ Version 2.2.0 is NOT found"
echo ""
echo "Latest versions available:"
curl -s https://registry.npmjs.org/@voltagent/core | jq -r '.versions | keys | .[-5:] | .[]' 2>/dev/null || echo "Could not retrieve version list"Repository: VoltAgent/voltagent
Length of output: 274
@voltagent/core@2.2.0 does not exist on npm registry; the change will fail during installation.
The highest available version is 2.1.6 (current latest dist-tag). Either downgrade the dependency to ^2.1.6 or defer this change until version 2.2.0 is actually published.
🤖 Prompt for AI Agents
In `@examples/with-nextjs-resumable-stream/package.json` at line 20, The
package.json dependency "@voltagent/core": "^2.2.0" references a non-existent
npm version; change that dependency entry to use the latest published version
(e.g. "@voltagent/core": "^2.1.6") or revert the bump and wait until 2.2.0 is
published so installs won't fail.
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/core": "^2.2.0", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.0 release notes breaking changes
💡 Result:
I couldn’t find any published release notes for @voltagent/core v2.2.0 (and it does not appear in the project’s GitHub Releases list). The most recent @voltagent/core release shown there is v2.1.6 (Jan 21, 2026). [1]
If you’re looking for breaking changes in the 2.x line, VoltAgent’s 1.x → 2.x migration guide calls out these notable breaks/required updates (even though many VoltAgent APIs are intended to remain compatible):
- Message helper utils changed to use
UIMessageinstead ofBaseMessage(breaking type/API change for those helpers). [2] - Legacy telemetry APIs/exporter removed from core; observability moved to OpenTelemetry-based approach. [2]
- If your app calls AI SDK directly, you must follow the upstream AI SDK v6 migration (VoltAgent 2.x aligns to AI SDK v6). [2]
If you can share a link to where you saw “2.2.0” referenced (PR, tag, announcement), I can pinpoint the exact breaking changes for that version.
Sources:
[1] GitHub Releases (VoltAgent/voltagent) – shows latest @voltagent/core@2.1.6 and recent history: (github.com)
[2] VoltAgent “Migration guide: 1.x → 2.x” (breaking changes/removed APIs notes): (voltagent.dev)
Citations:
- 1: https://github.com/VoltAgent/voltagent/releases
- 2: https://voltagent.dev/docs/getting-started/migration-guide/?utm_source=openai
🏁 Script executed:
# Check the example code to see how `@voltagent/core` is used
find examples/with-voltops-retrieval -type f -name "*.ts" -o -name "*.js" -o -name "*.json" | head -20Repository: VoltAgent/voltagent
Length of output: 253
🏁 Script executed:
# Check the package.json to see the exact dependency version
cat -n examples/with-voltops-retrieval/package.jsonRepository: VoltAgent/voltagent
Length of output: 1032
🏁 Script executed:
# Check the example code to see how `@voltagent/core` APIs are used
head -50 examples/with-voltops-retrieval/src/index.tsRepository: VoltAgent/voltagent
Length of output: 1142
🏁 Script executed:
# Also check the retriever code
head -40 examples/with-voltops-retrieval/src/retriever/index.tsRepository: VoltAgent/voltagent
Length of output: 268
Update @voltagent/core to an existing version.
Version 2.2.0 does not exist in the official @voltagent/core releases; the latest is v2.1.6 (Jan 21, 2026). Update the dependency to ^2.1.6 or verify if a prerelease/unreleased version was intended.
🤖 Prompt for AI Agents
In `@examples/with-voltops-retrieval/package.json` around lines 5 - 7, The
package.json dependency entry for "@voltagent/core" references a non-existent
version "2.2.0"; update the dependency in package.json to a valid released
version (e.g., change the "@voltagent/core" value to "^2.1.6") or confirm and
switch to the correct prerelease tag if that was intended; ensure the modified
dependency string is consistent with the existing entries for "@voltagent/cli"
and "@voltagent/libsql" so npm/yarn install resolves successfully.
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.2.0
Minor Changes
#978
db394ceThanks @omeraplak! - feat: allow tool-specific hooks and letonToolEndoverride tool output [FEAT] Middleware Interception & Truncation for Tool Results #975Tool hooks run alongside agent hooks.
onToolEndcan now return{ output }to replace the tool result (validated again if an output schema exists).Patch Changes
#985
85f8611Thanks @omeraplak! - feat: workflowState + andForEach selector/mapWhat's New
workflowStateandsetWorkflowStateadd shared state across steps (preserved after suspend/resume).andForEachnow supports anitemsselector and optionalmap(iterate without losing parent data).Workflow State Usage
andForEach Selector + Map
#983
96ebba3Thanks @omeraplak! - fix: allow custom workflow stream event types while preserving IntelliSense for built-in names#986
850b5bbThanks @omeraplak! - feat: add optional conversation title generation on conversation creation. Titles are derived from the first user message, respect a max length, and can use the agent model or a configured override. Make use of the title field of the conversation. #981#980
b65715eThanks @omeraplak! - feat: add tool routing for agents with router tools, pool/expose controls, and embedding routing.Embedding model strings also accept provider-qualified IDs like
openai/text-embedding-3-smallusing the same model registry as agent model strings.Basic embedding router:
Pool and expose:
Custom router strategy + resolver mode:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.