Conversation
📝 WalkthroughWalkthroughBumped Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
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 |
This comment has been minimized.
This comment has been minimized.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Deploying voltagent with
|
| Latest commit: |
5f007d6
|
| Status: | 🚫 Deploy failed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 11
🤖 Fix all issues with AI agents
In `@examples/with-amazon-bedrock/package.json`:
- Line 6: Revert the dependency version bump for "@voltagent/core" in
package.json to a published release; replace the non-existent "2.3.3" spec with
a valid tag such as "2.1.6" (or another existing release like "2.1.0") so
installs succeed, by updating the "@voltagent/core" entry in package.json
accordingly.
In `@examples/with-groq-ai/package.json`:
- Line 6: The package.json currently pins "@voltagent/core": "^2.3.3" which is
unpublished; update the dependency to the published 2.x release (e.g. change the
version string for "@voltagent/core" from "^2.3.3" to "^2.3.1") so npm installs
succeed and lockfiles remain consistent.
In `@examples/with-guardrails/package.json`:
- Line 6: The dependency entry for "@voltagent/core" in package.json references
a non-published version ("^2.3.3"); update the version string to a published
release (e.g., "^2.1.6") or replace it with the correct intended version, then
run an install to verify; edit the "@voltagent/core" dependency line in
package.json accordingly and ensure package-lock/yarn.lock is updated.
In `@examples/with-mcp-server/package.json`:
- Line 4: The package.json lists an unavailable dependency version for
"@voltagent/core" (currently "^2.3.3"); update that dependency entry to a
published version (for example "^2.1.6" or "^1.1.1") so npm can resolve it —
edit the "@voltagent/core" version string in package.json to a valid released
version and run npm install to verify.
In `@examples/with-ollama/package.json`:
- Line 5: Update the `@voltagent/core` dependency declaration in package.json:
change the version specifier for the "@voltagent/core" dependency from "^2.3.3"
to the published "^2.3.2" so the project references the actual released package
that includes the summarization metadata fix.
In `@examples/with-peaka-mcp/package.json`:
- Line 6: Dependency version for "@voltagent/core" in package.json is invalid
(2.3.3); update the dependency entry for "@voltagent/core" to a published
version such as "^2.3.2" so npm can resolve it, i.e., locate the
"@voltagent/core" dependency line and change the version string from "^2.3.3" to
"^2.3.2" (or another existing published version).
In `@examples/with-pinecone/package.json`:
- Line 7: Update the "@voltagent/core" dependency entry in package.json to a
published version (replace the non-existent "^2.3.3" with a valid release such
as "^2.3.1"); ensure the dependency string for "@voltagent/core" is corrected so
npm/yarn can resolve it.
In `@examples/with-retries-fallback/package.json`:
- Line 7: Update the package.json dependency entry for "@voltagent/core" to
reference an existing published version (replace "^2.3.3" with a valid version
such as "2.3.2" or "^2.3.2"); locate the dependency line containing
"@voltagent/core" and modify the version string, then run npm install (or yarn)
and verify package-lock.json / yarn.lock is updated to ensure the project uses
the published 2.3.2 package.
In `@examples/with-tavily-search/package.json`:
- Line 6: Update the dependency version for "@voltagent/core" in package.json
from "^2.3.3" to "^2.3.2" because 2.3.3 is not published; locate the entry with
the string "@voltagent/core" and replace the version specifier to "^2.3.2" so
installs succeed.
In `@examples/with-thinking-tool/package.json`:
- Line 6: The package.json specifies an invalid dependency version
"@voltagent/core": "^2.3.3"; change this to a published version (e.g., "^2.3.2")
to avoid npm install failures by updating the dependency entry for
"@voltagent/core" in package.json to a valid released version.
In `@examples/with-whatsapp/package.json`:
- Line 7: Update the dependency version for "@voltagent/core" in package.json:
replace the non-existent "^2.3.3" version with a valid released 1.x version
(e.g., "^1.1.1") so npm install can resolve the package; locate the dependency
entry "@voltagent/core" in package.json and change its version string
accordingly.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.3 latest release
💡 Result:
I couldn’t find any evidence that @voltagent/core v2.3.3 has been released (no npm/jsDelivr/NewReleases listing shows a 2.3.3 version).
- The npm package page shows v1.1.1 as the current version (published “11 hours ago” at the time it was crawled). [1]
- jsDelivr’s npm mirror shows the latest available package version as v2.1.6. [2]
- NewReleases lists recent
@voltagent/corereleases up to v2.1.0 (not 2.3.3). [3]
So: v2.3.3 is not the latest release based on available public indexes; the newest I can see is v2.1.6 (jsDelivr) and npm’s “current version” shows v1.1.1. [1][2]
Sources: [1] [2] [3]
Revert this change—@voltagent/core v2.3.3 does not exist on npm.
The npm package currently shows v1.1.1 as the published version, with v2.1.6 available on jsDelivr. Specifying a non-existent version will cause installation failures. Update to an existing release (e.g., v2.1.6 or v2.1.0) instead.
🤖 Prompt for AI Agents
In `@examples/with-amazon-bedrock/package.json` at line 6, Revert the dependency
version bump for "@voltagent/core" in package.json to a published release;
replace the non-existent "2.3.3" spec with a valid tag such as "2.1.6" (or
another existing release like "2.1.0") so installs succeed, by updating the
"@voltagent/core" entry in package.json accordingly.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package versions 2.3.3
💡 Result:
I couldn’t find any evidence that @voltagent/core has a published npm version 2.3.3.
The most recent 2.x versions I can confirm from VoltAgent’s release tracking are:
@voltagent/core@2.3.1(latest seen) [1]@voltagent/core@2.3.0[1]
For reference, jsDelivr’s package view currently shows @voltagent/core at 2.1.6 (which also suggests 2.3.3 isn’t available there either). [2]
Sources: [1] [2]
Revert to @voltagent/core@^2.3.1 — version 2.3.3 does not exist on npm.
The specified version 2.3.3 is unpublished. The latest available 2.x release is 2.3.1. Using 2.3.3 will break npm installations.
🤖 Prompt for AI Agents
In `@examples/with-groq-ai/package.json` at line 6, The package.json currently
pins "@voltagent/core": "^2.3.3" which is unpublished; update the dependency to
the published 2.x release (e.g. change the version string for "@voltagent/core"
from "^2.3.3" to "^2.3.1") so npm installs succeed and lockfiles remain
consistent.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.3 latest published
💡 Result:
@voltagent/core latest published version is 2.1.6 (so 2.3.3 is not the latest, and I don’t see evidence that 2.3.3 is published). [1]
Install: npm i @voltagent/core@2.1.6 [1]
Sources: [1] (jsdelivr.com)
Citations:
Do not approve: @voltagent/core 2.3.3 is not published.
The latest published version on npm is 2.1.6. Version 2.3.3 does not exist and will cause package installation failures. Update to ^2.1.6 or verify the correct target version.
🤖 Prompt for AI Agents
In `@examples/with-guardrails/package.json` at line 6, The dependency entry for
"@voltagent/core" in package.json references a non-published version ("^2.3.3");
update the version string to a published release (e.g., "^2.1.6") or replace it
with the correct intended version, then run an install to verify; edit the
"@voltagent/core" dependency line in package.json accordingly and ensure
package-lock/yarn.lock is updated.
| "name": "voltagent-example-with-mcp-server", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
python - <<'PY'
import json, urllib.request
try:
data = json.load(urllib.request.urlopen("https://registry.npmjs.org/@voltagent/core"))
has_2_3_3 = "2.3.3" in data.get("versions", {})
latest = data.get("dist-tags", {}).get("latest", "N/A")
print(f"has_2_3_3: {has_2_3_3}")
print(f"latest: {latest}")
if has_2_3_3:
print("Version 2.3.3 exists on npm")
else:
print("Version 2.3.3 NOT found on npm")
except Exception as e:
print(f"Error querying npm registry: {e}")
PYRepository: VoltAgent/voltagent
Length of output: 219
🌐 Web query:
@voltagent/core 2.3.3 npm package
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.3.3 exists on npm/CDN indexes.
- The jsDelivr npm index for
@voltagent/coreshows the package at version2.1.6(not2.3.3). [1] - The npm package page (as indexed) shows a
1.1.1release. [2] (npm blocks direct automated access here, so I couldn’t verify the live page contents directly.)
If you’re trying to install that exact version, confirm what versions npm sees from your machine:
npm view `@voltagent/core` versions --jsonSources: [1] [2]
Update @voltagent/core to an available version.
The version 2.3.3 does not exist on npm. Available versions include 2.1.6 and 1.1.1. Update the dependency to a published version.
🤖 Prompt for AI Agents
In `@examples/with-mcp-server/package.json` at line 4, The package.json lists an
unavailable dependency version for "@voltagent/core" (currently "^2.3.3");
update that dependency entry to a published version (for example "^2.1.6" or
"^1.1.1") so npm can resolve it — edit the "@voltagent/core" version string in
package.json to a valid released version and run npm install to verify.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.3 release information
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.3.3 has been published (no matching release entry showed up in the VoltAgent/voltagent release feed I checked).
The most recent published versions I can confirm are:
@voltagent/core@2.3.2(patch) — fixes preserving OpenAI reasoning/tool metadata during summarization to prevent errors withfunction_callitems. [1]@voltagent/core@2.3.1(patch) — adds separate workflow examples forcreateWorkflowandcreateWorkflowChain, includingworkflowStateusage. [2]@voltagent/core@2.3.0(minor) — replaces tool routers with system toolssearchTools+callTool; removescreateToolRouterandtoolRouting.routers(migration required). [3]
If you want, paste the output of npm view @voltagent/core@2.3.3 (or the install error/log) and I can pinpoint whether 2.3.3 exists in your registry or if it’s a typo/version mix-up.
Sources: [1] [2] [3]
Update dependency to the latest published version 2.3.2.
Version 2.3.3 does not exist on npm; the latest published release is @voltagent/core@2.3.2, which fixes preserving OpenAI reasoning/tool metadata during summarization. Update line 5 to "@voltagent/core": "^2.3.2".
🤖 Prompt for AI Agents
In `@examples/with-ollama/package.json` at line 5, Update the `@voltagent/core`
dependency declaration in package.json: change the version specifier for the
"@voltagent/core" dependency from "^2.3.3" to the published "^2.3.2" so the
project references the actual released package that includes the summarization
metadata fix.
| "@pinecone-database/pinecone": "^6.1.1", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify that `@voltagent/core`@2.3.3 exists on npm and check latest dist-tag.
python3 - <<'PY'
import json, urllib.request
try:
data = json.load(urllib.request.urlopen("https://registry.npmjs.org/@voltagent/core"))
has_2_3_3 = "2.3.3" in data.get("versions", {})
latest = data.get("dist-tags", {}).get("latest")
print(f"Version 2.3.3 exists: {has_2_3_3}")
print(f"Latest version: {latest}")
if has_2_3_3:
version_info = data["versions"].get("2.3.3", {})
published_time = version_info.get("_time", "unknown")
print(f"Published: {published_time}")
except Exception as e:
print(f"Error: {e}")
PYRepository: VoltAgent/voltagent
Length of output: 197
🌐 Web query:
@voltagent/core npm package version 2.3.3
💡 Result:
I couldn’t find @voltagent/core version 2.3.3 published on npm/CDN mirrors.
- jsDelivr’s npm mirror for
@voltagent/corecurrently lists versions up to2.3.1(no2.3.2/2.3.3). [1] - The jsDelivr package page also reports the current version as
2.3.1. [2]
If you meant the latest 2.3.x, install:
npm i `@voltagent/core`@2.3.1Sources: [1] [2]
Update @voltagent/core to an available version.
Version 2.3.3 does not exist on npm. The latest available version in the 2.3.x range is 2.3.1. Update the dependency to ^2.3.1 or confirm the intended target version.
🤖 Prompt for AI Agents
In `@examples/with-pinecone/package.json` at line 7, Update the "@voltagent/core"
dependency entry in package.json to a published version (replace the
non-existent "^2.3.3" with a valid release such as "^2.3.1"); ensure the
dependency string for "@voltagent/core" is corrected so npm/yarn can resolve it.
| "@ai-sdk/openai": "^3.0.0", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
python3 <<'PY'
import json
import urllib.request
import urllib.error
try:
response = urllib.request.urlopen("https://registry.npmjs.org/@voltagent/core", timeout=10)
data = json.loads(response.read().decode('utf-8'))
versions = data.get("versions", {})
dist_tags = data.get("dist-tags", {})
print(f"Version 2.3.3 exists: {'2.3.3' in versions}")
print(f"Latest dist-tag: {dist_tags.get('latest', 'N/A')}")
if '2.3.3' in versions:
v233 = versions['2.3.3']
print(f"Published: {v233.get('_published', 'N/A')}")
except urllib.error.HTTPError as e:
print(f"HTTP Error: {e.code}")
except urllib.error.URLError as e:
print(f"URL Error: {e.reason}")
except Exception as e:
print(f"Error: {e}")
PYRepository: VoltAgent/voltagent
Length of output: 185
🏁 Script executed:
#!/bin/bash
# Try to check npm package using npm CLI
npm view `@voltagent/core`@2.3.3 version 2>/dev/null && echo "Version exists" || echo "Version not found or npm error"
# Also check latest version
npm view `@voltagent/core` version 2>/dev/null || echo "Package lookup failed"Repository: VoltAgent/voltagent
Length of output: 99
@voltagent/core@2.3.3 does not exist on npm registry.
The latest published version is 2.3.2. Update the dependency to use an existing version (2.3.2 or earlier).
🤖 Prompt for AI Agents
In `@examples/with-retries-fallback/package.json` at line 7, Update the
package.json dependency entry for "@voltagent/core" to reference an existing
published version (replace "^2.3.3" with a valid version such as "2.3.2" or
"^2.3.2"); locate the dependency line containing "@voltagent/core" and modify
the version string, then run npm install (or yarn) and verify package-lock.json
/ yarn.lock is updated to ensure the project uses the published 2.3.2 package.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify that `@voltagent/core`@2.3.3 exists on npm and check latest dist-tag.
python3 <<'PY'
import json, urllib.request
try:
data = json.load(urllib.request.urlopen("https://registry.npmjs.org/@voltagent/core"))
print("has_2_3_3:", "2.3.3" in data.get("versions", {}))
print("latest:", data.get("dist-tags", {}).get("latest"))
except Exception as e:
print(f"Error: {e}")
PYRepository: VoltAgent/voltagent
Length of output: 197
🏁 Script executed:
#!/bin/bash
# Verify `@voltagent/core`@2.3.3 on npm using curl
curl -s https://registry.npmjs.org/@voltagent/core 2>&1 | jq '.versions | has("2.3.3"), .["dist-tags"].latest' 2>/dev/null || curl -s -k https://registry.npmjs.org/@voltagent/core 2>&1 | jq '.versions | has("2.3.3"), .["dist-tags"].latest' 2>/dev/null || echo "Cannot verify due to network/SSL constraints in sandbox"Repository: VoltAgent/voltagent
Length of output: 73
🏁 Script executed:
#!/bin/bash
# Get available versions of `@voltagent/core`
curl -s https://registry.npmjs.org/@voltagent/core 2>&1 | jq '.versions | keys[-5:], "latest_tag: " + (.["dist-tags"].latest // "unknown")' 2>/dev/null || curl -s -k https://registry.npmjs.org/@voltagent/core 2>&1 | jq -r '.versions | keys | .[-10:]' 2>/dev/null || echo "Cannot retrieve version list"Repository: VoltAgent/voltagent
Length of output: 142
Use @voltagent/core@2.3.2 instead; version 2.3.3 does not exist on npm.
The version 2.3.3 is not published on npm. The latest available version is 2.3.2. Update the dependency to "@voltagent/core": "^2.3.2" to resolve the installation failure.
🤖 Prompt for AI Agents
In `@examples/with-tavily-search/package.json` at line 6, Update the dependency
version for "@voltagent/core" in package.json from "^2.3.3" to "^2.3.2" because
2.3.3 is not published; locate the entry with the string "@voltagent/core" and
replace the version specifier to "^2.3.2" so installs succeed.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.3
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.3.3 has been published.
- The most recent release I can verify is
@voltagent/core@2.3.2, released on February 4, 2026. [1] - The prior release is
2.3.1. [2] - Some package indexes still show older “latest” values (e.g., npm page snapshot showing
1.1.1). [3]
To confirm from your environment, run:
npm view `@voltagent/core` version
npm view `@voltagent/core` versions --json | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).slice(-10)"🏁 Script executed:
# Check git history for this file to see the version change
cd examples/with-thinking-tool
git log --oneline -p package.json | head -100Repository: VoltAgent/voltagent
Length of output: 1234
Correct the dependency version: @voltagent/core version 2.3.3 does not exist on npm.
The latest published version of @voltagent/core is 2.3.2 (released February 4, 2026). Specifying ^2.3.3 will cause npm install failures. Update line 6 to use ^2.3.2 or another valid published version.
🤖 Prompt for AI Agents
In `@examples/with-thinking-tool/package.json` at line 6, The package.json
specifies an invalid dependency version "@voltagent/core": "^2.3.3"; change this
to a published version (e.g., "^2.3.2") to avoid npm install failures by
updating the dependency entry for "@voltagent/core" in package.json to a valid
released version.
| "@supabase/supabase-js": "^2.49.4", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify that `@voltagent/core`@2.3.3 exists on npm and check latest dist-tag.
python - <<'PY'
import json, urllib.request
data = json.load(urllib.request.urlopen("https://registry.npmjs.org/@voltagent/core"))
print("has_2_3_3:", "2.3.3" in data.get("versions", {}))
print("latest:", data.get("dist-tags", {}).get("latest"))
PYRepository: VoltAgent/voltagent
Length of output: 2644
🌐 Web query:
@voltagent/core 2.3.3 npm package
💡 Result:
There doesn’t appear to be an @voltagent/core version 2.3.3 published on npm. The npm package page for @voltagent/core shows the current release line as 1.x (e.g., 1.1.1) and provides the standard install command. [1]
Install (latest 1.x):
npm i `@voltagent/core`Or pin the version shown on npm:
npm i `@voltagent/core`@1.1.1[1]
If you were looking for a 2.x VoltAgent package, note that some related packages do have 2.x versions (for example, @voltagent/server-core shows 2.1.3 on jsDelivr). [2]
Sources: [1] [2]
@voltagent/core@2.3.3 does not exist on npm—correct to the latest available version.
The package currently only has 1.x releases published (e.g., 1.1.1). Change the dependency to "@voltagent/core": "^1.1.1" or the latest 1.x version to resolve the npm install failure.
🤖 Prompt for AI Agents
In `@examples/with-whatsapp/package.json` at line 7, Update the dependency version
for "@voltagent/core" in package.json: replace the non-existent "^2.3.3" version
with a valid released 1.x version (e.g., "^1.1.1") so npm install can resolve
the package; locate the dependency entry "@voltagent/core" in package.json and
change its version string accordingly.
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
9320d6c to
c1a546f
Compare
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In `@examples/with-chroma/package.json`:
- Around line 9-10: Update the dependency versions in package.json so they point
to published releases: change "@voltagent/core" from "2.3.3" to "2.3.2" and
change "@voltagent/libsql" from "2.1.0" to "2.0.3"; after updating these package
entries, run npm install (or yarn) to verify the install succeeds and adjust any
lockfile accordingly.
In `@examples/with-voice-openai/package.json`:
- Around line 6-7: The package.json currently references non-published versions;
change the dependency entries for "@voltagent/core" and "@voltagent/libsql" to
the published versions ("@voltagent/core": "2.3.2" and "@voltagent/libsql":
"2.0.3") so installs won't fail, then run a fresh install to verify; update any
lockfile if present.
In `@examples/with-workflow-chain/package.json`:
- Around line 6-7: The package.json lists non-existent versions
"@voltagent/core": "2.3.3" and "@voltagent/libsql": "2.1.0" which will break
installs; open the package.json dependency entries and replace those versions
with published versions (e.g., the latest published semver for `@voltagent/core`
and `@voltagent/libsql`) or change them to valid tags like "latest" or an existing
semver (confirm via npm info), or remove the entries until those packages are
released; ensure you update the dependency lines matching "@voltagent/core" and
"@voltagent/libsql" accordingly and run npm install to verify the fix.
In `@packages/libsql/package.json`:
- Around line 4-11: The devDependency for "@voltagent/core" in package.json is
pinned to a non-existent version "^2.3.3"; update the entry under
"devDependencies" for the symbol "@voltagent/core" to a published version (e.g.,
change to "^2.3.2") so npm install succeeds, or revert the change and wait for
2.3.3 to be released before updating.
| "@voltagent/core": "^2.3.3", | ||
| "@voltagent/libsql": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify published versions for `@voltagent/core` and `@voltagent/libsql`
for pkg in "@voltagent/core" "@voltagent/libsql"; do
echo "=== Checking $pkg ==="
curl -s "https://registry.npmjs.org/$pkg" | jq -r '.["dist-tags"] | "Latest: \(.latest // "N/A")" , .versions | keys[] | select(test("2.3.3|2.1.0"))'
doneRepository: VoltAgent/voltagent
Length of output: 271
🏁 Script executed:
#!/bin/bash
# Verify published versions more carefully
for pkg in "@voltagent/core" "@voltagent/libsql"; do
echo "=== Checking $pkg ==="
response=$(curl -s "https://registry.npmjs.org/$pkg")
# Check if we got a valid response
if echo "$response" | jq -e '.versions' > /dev/null 2>&1; then
# Check for specific versions
latest=$(echo "$response" | jq -r '.["dist-tags"].latest // "not found"')
echo "Latest version: $latest"
has_2_3_3=$(echo "$response" | jq 'has("versions") and (.versions | has("2.3.3")) // false')
has_2_1_0=$(echo "$response" | jq 'has("versions") and (.versions | has("2.1.0")) // false')
echo "Has 2.3.3: $has_2_3_3"
echo "Has 2.1.0: $has_2_1_0"
else
echo "Package not found or invalid response"
echo "Response: $response"
fi
echo ""
doneRepository: VoltAgent/voltagent
Length of output: 243
Update dependencies to published versions.
Both packages reference unpublished versions:
@voltagent/core@2.3.3does not exist (latest: 2.3.2)@voltagent/libsql@2.1.0does not exist (latest: 2.0.3)
Update to available versions to prevent npm install failures.
🤖 Prompt for AI Agents
In `@examples/with-chroma/package.json` around lines 9 - 10, Update the dependency
versions in package.json so they point to published releases: change
"@voltagent/core" from "2.3.3" to "2.3.2" and change "@voltagent/libsql" from
"2.1.0" to "2.0.3"; after updating these package entries, run npm install (or
yarn) to verify the install succeeds and adjust any lockfile accordingly.
| "@voltagent/core": "^2.3.3", | ||
| "@voltagent/libsql": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify published versions for `@voltagent/core` and `@voltagent/libsql`
echo "=== Checking `@voltagent/core` ==="
curl -s "https://registry.npmjs.org/@voltagent/core" | jq '.versions | keys[] | select(. == "2.3.3") | "Found: " + .' 2>/dev/null || echo "Version 2.3.3 not found or package unavailable"
echo ""
echo "=== Checking `@voltagent/libsql` ==="
curl -s "https://registry.npmjs.org/@voltagent/libsql" | jq '.versions | keys[] | select(. == "2.1.0") | "Found: " + .' 2>/dev/null || echo "Version 2.1.0 not found or package unavailable"
echo ""
echo "=== Summary ==="
curl -s "https://registry.npmjs.org/@voltagent/core" 2>/dev/null | jq -r '.["dist-tags"]' || echo "Could not fetch `@voltagent/core` dist-tags"
curl -s "https://registry.npmjs.org/@voltagent/libsql" 2>/dev/null | jq -r '.["dist-tags"]' || echo "Could not fetch `@voltagent/libsql` dist-tags"Repository: VoltAgent/voltagent
Length of output: 248
Correct the bumped package versions—they don't exist on npm yet.
The versions specified do not exist:
@voltagent/core@2.3.3doesn't exist (latest is2.3.2)@voltagent/libsql@2.1.0doesn't exist (latest is2.0.3)
Update to the actual published versions to prevent install failures.
🤖 Prompt for AI Agents
In `@examples/with-voice-openai/package.json` around lines 6 - 7, The package.json
currently references non-published versions; change the dependency entries for
"@voltagent/core" and "@voltagent/libsql" to the published versions
("@voltagent/core": "2.3.2" and "@voltagent/libsql": "2.0.3") so installs won't
fail, then run a fresh install to verify; update any lockfile if present.
| "@voltagent/core": "^2.3.3", | ||
| "@voltagent/libsql": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Function to check if a version exists for a package
check_npm_version() {
local pkg=$1
local version=$2
local encoded_pkg=$(echo "$pkg" | sed 's/@/%40/g' | sed 's/\//%2F/g')
response=$(curl -s "https://registry.npmjs.org/$encoded_pkg")
if echo "$response" | jq -e ".versions[\"$version\"]" > /dev/null 2>&1; then
echo "$pkg@$version: EXISTS"
else
echo "$pkg@$version: NOT FOUND"
fi
}
# Check both packages
check_npm_version "@voltagent/core" "2.3.3"
check_npm_version "@voltagent/libsql" "2.1.0"Repository: VoltAgent/voltagent
Length of output: 130
@voltagent/core@2.3.3 and @voltagent/libsql@2.1.0 do not exist on npm registry.
Installation will fail with these versions. Either update the dependencies to versions that are published on npm, or ensure these versions are released before merging.
🤖 Prompt for AI Agents
In `@examples/with-workflow-chain/package.json` around lines 6 - 7, The
package.json lists non-existent versions "@voltagent/core": "2.3.3" and
"@voltagent/libsql": "2.1.0" which will break installs; open the package.json
dependency entries and replace those versions with published versions (e.g., the
latest published semver for `@voltagent/core` and `@voltagent/libsql`) or change
them to valid tags like "latest" or an existing semver (confirm via npm info),
or remove the entries until those packages are released; ensure you update the
dependency lines matching "@voltagent/core" and "@voltagent/libsql" accordingly
and run npm install to verify the fix.
| "version": "2.1.0", | ||
| "dependencies": { | ||
| "@libsql/client": "^0.15.0", | ||
| "@voltagent/internal": "^1.0.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@vitest/coverage-v8": "^3.2.4", | ||
| "@voltagent/core": "^2.0.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Query npm registry for `@voltagent/core` version information
curl -s "https://registry.npmjs.org/@voltagent%2Fcore" | jq -r '.["dist-tags"] as $tags | .versions as $versions |
"Latest version: \($tags.latest)",
"Version 2.3.3 exists: \(if $versions["2.3.3"] then "YES" else "NO" end)",
"Available versions (last 5): \(($versions | keys | sort -V | reverse | .[0:5]) | join(", "))"'Repository: VoltAgent/voltagent
Length of output: 289
🏁 Script executed:
#!/bin/bash
# Query npm registry for `@voltagent/core` version information
curl -s "https://registry.npmjs.org/@voltagent%2Fcore" | jq -r '
"Latest version: " + .["dist-tags"].latest,
(if .versions["2.3.3"] then "Version 2.3.3 exists: YES" else "Version 2.3.3 exists: NO" end)
'Repository: VoltAgent/voltagent
Length of output: 109
@voltagent/core@2.3.3 does not exist on npm—latest published version is 2.3.2.
The devDependency specifies ^2.3.3, which will cause npm install to fail. Update the version to ^2.3.2 or wait for version 2.3.3 to be published before release.
🤖 Prompt for AI Agents
In `@packages/libsql/package.json` around lines 4 - 11, The devDependency for
"@voltagent/core" in package.json is pinned to a non-existent version "^2.3.3";
update the entry under "devDependencies" for the symbol "@voltagent/core" to a
published version (e.g., change to "^2.3.2") so npm install succeeds, or revert
the change and wait for 2.3.3 to be released before updating.
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
c1a546f to
5f007d6
Compare
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Fix all issues with AI agents
In `@examples/github-repo-analyzer/package.json`:
- Around line 7-8: The package.json references non-existent npm versions for
`@voltagent/core` and `@voltagent/libsql`; update the dependency entries for
"@voltagent/core" and "@voltagent/libsql" to published versions (e.g., bump
"@voltagent/core" to "2.1.6" and "@voltagent/libsql" to "2.0.3") or explicitly
switch them to valid prerelease tags if those are intended, then run npm install
to verify the lockfile builds successfully before merging.
In `@examples/with-nestjs/package.json`:
- Line 9: The package.json dependency for "@voltagent/core" pins to an
unpublished version "^2.3.3"; update that dependency entry to the latest
published version "^2.3.2" by changing the version string for "@voltagent/core"
in the dependencies block so the project installs a valid package.
In `@examples/with-offline-evals/package.json`:
- Line 6: Update the dependency version for `@voltagent/core` in package.json:
locate the dependency entry "@voltagent/core": "^2.3.3" and change it to
"@voltagent/core": "^2.3.2" so the project references the published 2.3.2
release.
In `@examples/with-voltagent-exporter/package.json`:
- Around line 6-7: Update the dependency versions in package.json so they point
to published releases: change "@voltagent/core" from "^2.3.3" to a valid
published version (e.g., "1.1.1") and "@voltagent/libsql" from "^2.1.0" to a
published 1.x version (e.g., "1.0.14"); ensure the package.json entries for
"@voltagent/core" and "@voltagent/libsql" use the corrected versions and run npm
install to verify resolution.
In `@examples/with-zapier-mcp/package.json`:
- Around line 7-8: Update the package.json dependency entries for
`@voltagent/core` and `@voltagent/libsql` to actual published versions: change
"@voltagent/core": "~2.3.3" to "~2.3.2" (or exact "2.3.2") and change
"@voltagent/libsql": "^2.1.0" to "^1.0.7" (or exact "1.0.7") so the listed
versions exist on npm; ensure you update the version strings in the package.json
dependencies block and run a quick npm install to verify no other transitive
constraints break.
| "@voltagent/core": "^2.3.3", | ||
| "@voltagent/libsql": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.3.3 npm package
💡 Result:
I couldn’t find any public evidence that @voltagent/core@2.3.3 exists on npm (or on jsDelivr’s npm mirror). The highest version I can see publicly via jsDelivr is 2.1.6 for @voltagent/core. [1] The npm package page itself is accessible via search results, but I can’t verify a 2.3.3 release from it. [2]
If you try to install 2.3.3 and it’s not published, npm will fail with “No matching version found”:
npm i `@voltagent/core`@2.3.3If you tell me where you saw 2.3.3 (link / screenshot / lockfile snippet), I can help confirm whether it’s a typo, a prerelease tag, or a different package name.
Sources: [1] [2]
🌐 Web query:
@voltagent/libsql 2.1.0 npm package
💡 Result:
@voltagent/libsql@2.1.0 does not appear to be published on npm (the available 2.x versions shown go up to 2.0.3). [1]
- Latest published version (per jsDelivr mirror):
2.0.3[1] - Package metadata for 2.0.3: peer deps include
@voltagent/core ^2.0.0,@voltagent/logger ^2.0.0, andai ^6.0.0. [2] - Install (latest):
Usage is via
npm i `@voltagent/libsql`LibSQLMemoryAdapterwithMemoryfrom@voltagent/core. [3]
If you were looking for 2.1.0, that version number shows up for @voltagent/core, not @voltagent/libsql. [4]
Sources: [1] [2] [3] [4]
Both specified versions do not exist on npm—this blocks installation.
The versions referenced in lines 7–8 are not published:
@voltagent/core@2.3.3does not exist (latest available:2.1.6)@voltagent/libsql@2.1.0does not exist (latest available:2.0.3)
Update to published versions before merge, or confirm these are prerelease tags.
🤖 Prompt for AI Agents
In `@examples/github-repo-analyzer/package.json` around lines 7 - 8, The
package.json references non-existent npm versions for `@voltagent/core` and
`@voltagent/libsql`; update the dependency entries for "@voltagent/core" and
"@voltagent/libsql" to published versions (e.g., bump "@voltagent/core" to
"2.1.6" and "@voltagent/libsql" to "2.0.3") or explicitly switch them to valid
prerelease tags if those are intended, then run npm install to verify the
lockfile builds successfully before merging.
| "@nestjs/core": "^11.0.0", | ||
| "@nestjs/platform-express": "^11.0.0", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.3
💡 Result:
I couldn’t find any evidence that @voltagent/core v2.3.3 has been published to the npm ecosystem yet. The latest version I can verify from a public npm mirror (jsDelivr) is v2.3.2. [1]
If you meant to install the latest verified version:
npm i `@voltagent/core`@2.3.2Update @voltagent/core to published version.
Line 9 specifies @voltagent/core@^2.3.3, but version 2.3.3 has not been published to npm. The latest available version is 2.3.2. Update the dependency to ^2.3.2:
Suggested change
- "@voltagent/core": "^2.3.3",
+ "@voltagent/core": "^2.3.2",
🤖 Prompt for AI Agents
In `@examples/with-nestjs/package.json` at line 9, The package.json dependency for
"@voltagent/core" pins to an unpublished version "^2.3.3"; update that
dependency entry to the latest published version "^2.3.2" by changing the
version string for "@voltagent/core" in the dependencies block so the project
installs a valid package.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.3.2", | ||
| "@voltagent/core": "^2.3.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.3.3
💡 Result:
@voltagent/core does not have a published npm release 2.3.3 (it isn’t present in the CDN/npm version listings). The latest available 2.3.x release shown is 2.3.2. [1][2]
To install the latest available version:
npm i `@voltagent/core`@2.3.2Update @voltagent/core to version 2.3.2.
Line 6 specifies @voltagent/core@^2.3.3, but version 2.3.3 is not published on npm. The latest available version is 2.3.2. Change the dependency to "@voltagent/core": "^2.3.2".
🤖 Prompt for AI Agents
In `@examples/with-offline-evals/package.json` at line 6, Update the dependency
version for `@voltagent/core` in package.json: locate the dependency entry
"@voltagent/core": "^2.3.3" and change it to "@voltagent/core": "^2.3.2" so the
project references the published 2.3.2 release.
| "@voltagent/core": "^2.3.3", | ||
| "@voltagent/libsql": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.3.3 npm package
💡 Result:
I couldn’t find any evidence that @voltagent/core@2.3.3 exists on npm (no npm version page or search result for that exact version).
What is clearly available:
@voltagent/core(VoltAgent core runtime) is published on npm; the npm package page shows the current published version as1.1.1and describes it as the core engine for the VoltAgent TypeScript agent framework. [1]- GitHub release tracking sites show
@voltagent/corehas 2.x releases (e.g.,2.1.0) on the repository side, which may explain why you expected a 2.x version—but that doesn’t confirm an npm2.3.3publish. [2] - VoltAgent docs discuss a 1.x → 2.x migration, reinforcing that 2.x exists as a concept/release line. [3]
Install (latest on npm):
npm i `@voltagent/core`(or pin whatever version npm actually offers, e.g. npm i @voltagent/core@1.1.1). [1]
If you tell me whether you saw “2.3.3” in an error log, lockfile, GitHub release, or another registry (npm mirror/private registry), I can pinpoint where that version reference is coming from.
Sources: [1] [2] [3]
🌐 Web query:
@voltagent/libsql 2.1.0 npm package
💡 Result:
@voltagent/libsql is VoltAgent’s LibSQL/Turso/SQLite memory adapter package (e.g., LibSQLMemoryAdapter, plus optional LibSQLVectorAdapter for semantic search). Install and use it like: npm install @voltagent/libsql``, then new Memory({ storage: new LibSQLMemoryAdapter({ url: "file:./.voltagent/memory.db" }) }). [1][2]
There does not appear to be an @voltagent/libsql@2.1.0 release: VoltAgent’s 2.x versioning applies to other packages (e.g., @voltagent/core, @voltagent/voice), while @voltagent/libsql is still on the 1.x line (recent releases reported as 1.0.13 / 1.0.14, and third-party npm tracking shows 1.0.7 as “latest”). [3][4][5]
If you specifically need to pin a version, use: npm i @voltagent/libsql@1.0.14 (or whichever 1.x version you target). [3]
Sources: [1] https://voltagent.dev/docs/agents/memory/libsql/ • [2] https://voltagent.dev/docs/agents/memory/semantic-search/ • [3] https://newreleases.io/project/github/VoltAgent/voltagent/release/%40voltagent%2Flibsql%401.0.14 • [4] https://github.com/VoltAgent/voltagent/releases • [5] https://socket.dev/npm/package/%40voltagent/libsql
Both dependency versions do not exist on npm—fix before merge.
The specified versions will cause installation failures:
@voltagent/core@2.3.3does not exist on npm (current published version is1.1.1)@voltagent/libsql@2.1.0does not exist on npm (package is on 1.x line, latest ~1.0.14)
Update to published versions: @voltagent/core@1.1.1 and @voltagent/libsql@1.0.14 (or later available versions).
🤖 Prompt for AI Agents
In `@examples/with-voltagent-exporter/package.json` around lines 6 - 7, Update the
dependency versions in package.json so they point to published releases: change
"@voltagent/core" from "^2.3.3" to a valid published version (e.g., "1.1.1") and
"@voltagent/libsql" from "^2.1.0" to a published 1.x version (e.g., "1.0.14");
ensure the package.json entries for "@voltagent/core" and "@voltagent/libsql"
use the corrected versions and run npm install to verify resolution.
| "@voltagent/core": "~2.3.3", | ||
| "@voltagent/libsql": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package versions published
💡 Result:
To list all published versions of @voltagent/core, use:
npm view `@voltagent/core` versions --jsonWhat I can confirm from public package aggregators right now:
- Latest version shown: 2.3.2 (jsDelivr package page) [1]
- Another tracker reports Latest 2.3.1, with last publish ~19 hours ago, and notes older vulnerable versions in the 0.0.1–0.1.76 range [2]
Sources: [1] [2]
🌐 Web query:
@voltagent/libsql npm package versions published
💡 Result:
Published versions of @voltagent/libsql on npm (oldest → newest):
0.1.01.0.0-next.0,1.0.0-next.1,1.0.0-next.21.0.0,1.0.1,1.0.21.0.3-next.01.0.3,1.0.4,1.0.5,1.0.6,1.0.7(latest) [1]
Dist-tags: latest = 1.0.7; next = 1.0.3-next.0. [1]
Sources: Socket’s npm package version index for @voltagent/libsql. [1]
Update dependencies to published versions.
Lines 7–8 reference versions that do not exist on npm:
@voltagent/core@2.3.3does not exist; latest published is 2.3.2@voltagent/libsql@2.1.0does not exist; latest published is 1.0.7
Update both to existing versions before merge.
🤖 Prompt for AI Agents
In `@examples/with-zapier-mcp/package.json` around lines 7 - 8, Update the
package.json dependency entries for `@voltagent/core` and `@voltagent/libsql` to
actual published versions: change "@voltagent/core": "~2.3.3" to "~2.3.2" (or
exact "2.3.2") and change "@voltagent/libsql": "^2.1.0" to "^1.0.7" (or exact
"1.0.7") so the listed versions exist on npm; ensure you update the version
strings in the package.json dependencies block and run a quick npm install to
verify no other transitive constraints break.
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/cloudflare-d1@2.1.0
Minor Changes
a35626aThanks @fengyun99! - The SQL statement has been modified. Previously, the query returned the earliest messages instead of the most recent ones.@voltagent/libsql@2.1.0
Minor Changes
a35626aThanks @fengyun99! - The SQL statement has been modified. Previously, the query returned the earliest messages instead of the most recent ones.@voltagent/postgres@2.1.0
Minor Changes
a35626aThanks @fengyun99! - The SQL statement has been modified. Previously, the query returned the earliest messages instead of the most recent ones.Patch Changes
238f87fThanks @omeraplak! - fix: validate UI/response messages and keep streaming response message IDs consistent across UI streams - [FEAT] Generate records in the voltagent_memory_messages table in advance before generating the chat history in streaming generation mode #1010fix(postgres/supabase): upsert conversation messages by (conversation_id, message_id) to avoid duplicate insert failures
@voltagent/supabase@2.1.0
Minor Changes
a35626aThanks @fengyun99! - The SQL statement has been modified. Previously, the query returned the earliest messages instead of the most recent ones.Patch Changes
238f87fThanks @omeraplak! - fix: validate UI/response messages and keep streaming response message IDs consistent across UI streams - [FEAT] Generate records in the voltagent_memory_messages table in advance before generating the chat history in streaming generation mode #1010fix(postgres/supabase): upsert conversation messages by (conversation_id, message_id) to avoid duplicate insert failures
@voltagent/core@2.3.3
Patch Changes
#1014
e121adcThanks @omeraplak! - fix: persist feedback metadata on assistant messages so history reloads keep feedback actions#1017
c706872Thanks @omeraplak! - fix: align OpenAI reasoning metadata handling with AI SDK#1016
238f87fThanks @omeraplak! - fix: validate UI/response messages and keep streaming response message IDs consistent across UI streams - [FEAT] Generate records in the voltagent_memory_messages table in advance before generating the chat history in streaming generation mode #1010fix(postgres/supabase): upsert conversation messages by (conversation_id, message_id) to avoid duplicate insert failures
Summary by CodeRabbit
Bug Fixes
Chores