ci(changesets): version packages#972
Conversation
Deploying voltagent with
|
| Latest commit: |
dc088e1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://beaf5837.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughBumps package versions and adds changelog entries: Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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}
7eb3ed4 to
fd67422
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@examples/with-offline-evals/package.json`:
- Around line 6-7: The package.json references non-existent versions of
`@voltagent/core` (2.1.6) and `@voltagent/evals` (2.0.3); verify the correct
published versions on the npm registry for the packages and update the
dependency entries in package.json (the "@voltagent/core" and "@voltagent/evals"
entries) to valid, published version strings (or use the latest tag) and then
run npm install to confirm the example builds; if you want to pin a known
working release, choose the specific published semver (e.g., replace the current
version tokens with the verified published versions) and commit that change.
fd67422 to
dc088e1
Compare
There was a problem hiding this comment.
Actionable comments posted: 8
🤖 Fix all issues with AI agents
In `@examples/with-a2a-server/package.json`:
- Around line 4-8: Update the invalid dependency versions in package.json:
change "@voltagent/core" from "^2.1.6" to "^2.1.0" and change
"@voltagent/server-hono" from "^2.0.4" to "^1.0.4" so the specified packages
match published npm versions.
In `@examples/with-auth/package.json`:
- Around line 7-10: Update the invalid dependency versions in package.json:
change the `@voltagent/core` entry from "^2.1.6" to "^2.1.5" and change the
`@voltagent/server-hono` entry from "^2.0.4" to "^2.0.3" so npm can resolve the
packages; ensure you update the version strings for the package keys
"@voltagent/core" and "@voltagent/server-hono" in the file and run npm install
to verify.
In `@examples/with-google-vertex-ai/package.json`:
- Around line 6-9: Update the invalid dependency versions in package.json:
replace "@voltagent/core":"^2.1.6" with a published version (e.g., "^2.1.0" or a
suitable 1.x), replace "@voltagent/libsql":"^2.0.2" with the published "1.0.5"
(e.g., "^1.0.5"), and replace "@voltagent/server-hono":"^2.0.4" with the
published "1.0.4" (e.g., "^1.0.4"); leave "@voltagent/logger":"^2.0.2" as-is,
then run npm install to verify resolution.
In `@examples/with-nestjs/package.json`:
- Around line 9-11: The package.json lists non-existent VoltAgent versions
causing npm install failures; update the dependency versions for
"@voltagent/core", "@voltagent/server-core", and "@voltagent/server-hono" to the
published releases (e.g., set "@voltagent/core" to 2.1.0,
"@voltagent/server-core" to 2.1.2, and "@voltagent/server-hono" to 1.0.4) and
run npm install to verify resolution; ensure the three entries in package.json
exactly match these published version strings.
In `@examples/with-playwright/package.json`:
- Around line 10-13: The package.json lists unpublished `@voltagent` versions;
update the dependency entries to published names/versions: change
"@voltagent/core" from 2.1.6 to 2.1.0, change "@voltagent/libsql" from 2.0.2 to
1.0.5, and either correct "@voltagent/server-hono" to the published 1.0.4 or
replace it with the intended package "@voltagent/serverless-hono@2.0.4"; verify
the registry for each package name/version before committing.
In `@examples/with-qdrant/package.json`:
- Around line 7-10: The dependencies in package.json reference unpublished
versions and will break installs: update the `@voltagent` packages to published
npm versions by changing the dependency entries for `@voltagent/core`,
`@voltagent/server-hono`, and `@voltagent/libsql` to known published versions (for
example `@voltagent/core` -> 0.1.1, `@voltagent/server-hono` -> 1.0.4, and an
existing `@voltagent/libsql` 1.0.x release), leave `@voltagent/logger` as-is, and
validate by running npm view <package>@<version> or a test npm install to ensure
the chosen versions exist before committing.
In `@examples/with-zapier-mcp/package.json`:
- Around line 7-10: The package versions listed are not published; update the
dependency entries for `@voltagent/core` and `@voltagent/server-hono` in
package.json: change "@voltagent/core": "~2.1.6" to "~2.1.5" and change
"@voltagent/server-hono": "^2.0.4" to "^2.0.3" so the project depends on the
published releases.
In `@packages/server-elysia/CHANGELOG.md`:
- Around line 43-44: Wrap the bare URLs in the curl examples in angle brackets
to satisfy markdownlint MD034: replace occurrences of the literal URL strings
(e.g., "http://localhost:3141/api/memory/save-messages" and the other curl
example around lines 69-70) with
"<http://localhost:3141/api/memory/save-messages>" (and the corresponding other
URL) so the markdown examples use angled brackets around the URLs.
♻️ Duplicate comments (1)
examples/with-offline-evals/package.json (1)
6-7: Dependency bumps align with release.Please re-confirm
@voltagent/core@2.1.6 and@voltagent/evals@2.0.3 are published before merge.
| "@voltagent/a2a-server": "^2.0.2", | ||
| "@voltagent/core": "^2.1.5", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/internal": "^1.0.3", | ||
| "@voltagent/logger": "^2.0.2", | ||
| "@voltagent/server-hono": "^2.0.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
python - <<'PY'
import json, urllib.request, urllib.parse
targets = {
"@voltagent/core": "2.1.6",
"@voltagent/server-hono": "2.0.4",
}
for pkg, ver in targets.items():
url = "https://registry.npmjs.org/" + urllib.parse.quote(pkg, safe='@/')
data = json.load(urllib.request.urlopen(url))
has_ver = ver in data.get("versions", {})
latest = data.get("dist-tags", {}).get("latest")
print(f"{pkg}: latest={latest}, has {ver}={has_ver}")
PYRepository: VoltAgent/voltagent
Length of output: 149
🌐 Web query:
npm @voltagent/core 2.1.6 package
💡 Result:
I couldn't find a published npm release for @voltagent/core version 2.1.6. The official npm listing and project release notes show other versions (e.g., 2.1.0 / 1.x series) — install the package using the published/latest version instead (npm info on the package and the project repo/releases linked below). [1][2][3]
Sources:
- npm package page for
@voltagent/core. [1] - VoltAgent docs / migration guide (1.x → 2.x). [2]
- VoltAgent GitHub releases / changelog (shows 2.1.0 as a released 2.x). [3]
🌐 Web query:
npm @voltagent/server-hono 2.0.4 package
💡 Result:
I couldn't find an npm release @voltagent/server-hono@2.0.4. The package on npm is published as version 1.0.4, and the VoltAgent docs reference the @voltagent/server-hono server provider (v2.0.x docs). (npmjs.com)
Citations:
Fix dependency versions—@voltagent/core@2.1.6 and @voltagent/server-hono@2.0.4 do not exist in the npm registry.
@voltagent/core@2.1.6is not published; the latest 2.x version available is 2.1.0. Use^2.1.0instead.@voltagent/server-hono@2.0.4is not published; the actual published version is 1.0.4. Use^1.0.4instead.
These changes are required before the code can be installed.
🤖 Prompt for AI Agents
In `@examples/with-a2a-server/package.json` around lines 4 - 8, Update the invalid
dependency versions in package.json: change "@voltagent/core" from "^2.1.6" to
"^2.1.0" and change "@voltagent/server-hono" from "^2.0.4" to "^1.0.4" so the
specified packages match published npm versions.
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/logger": "^2.0.2", | ||
| "@voltagent/server-hono": "^2.0.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Checking VoltAgent package versions on npm registry..."
# Check each package version
packages=(
"@voltagent/core:2.1.6"
"@voltagent/libsql:2.0.2"
"@voltagent/logger:2.0.2"
"@voltagent/server-hono:2.0.4"
)
for package_spec in "${packages[@]}"; do
IFS=':' read -r pkg_name version <<< "$package_spec"
pkg_encoded=$(echo "$pkg_name" | sed 's/@/%40/g; s/\//%2f/g')
echo "Checking $pkg_name@$version..."
if curl -fsSL "https://registry.npmjs.org/${pkg_encoded}/${version}" 2>/dev/null | jq -e '.version' > /dev/null 2>&1; then
echo "✓ $pkg_name@$version exists"
else
echo "✗ $pkg_name@$version NOT FOUND"
fi
doneRepository: VoltAgent/voltagent
Length of output: 405
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Checking available versions for missing packages..."
# Check available versions
for pkg in "@voltagent/core" "@voltagent/server-hono"; do
pkg_encoded=$(echo "$pkg" | sed 's/@/%40/g; s/\//%2f/g')
echo "Available versions for $pkg:"
curl -fsSL "https://registry.npmjs.org/${pkg_encoded}" 2>/dev/null | jq -r '.versions | keys[] | select(startswith("2."))' | tail -5
doneRepository: VoltAgent/voltagent
Length of output: 249
Fix invalid dependency versions in package.json.
@voltagent/core@2.1.6 and @voltagent/server-hono@2.0.4 do not exist in the npm registry. Update to available versions:
@voltagent/core: ^2.1.6 → ^2.1.5 (latest available)@voltagent/server-hono: ^2.0.4 → ^2.0.3 (latest available)
These missing versions will cause npm install to fail for this example.
🤖 Prompt for AI Agents
In `@examples/with-auth/package.json` around lines 7 - 10, Update the invalid
dependency versions in package.json: change the `@voltagent/core` entry from
"^2.1.6" to "^2.1.5" and change the `@voltagent/server-hono` entry from "^2.0.4"
to "^2.0.3" so npm can resolve the packages; ensure you update the version
strings for the package keys "@voltagent/core" and "@voltagent/server-hono" in
the file and run npm install to verify.
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/logger": "^2.0.2", | ||
| "@voltagent/server-hono": "^2.0.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check all four packages mentioned in the code snippet
echo "Checking `@voltagent/core`@2.1.6..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2fcore/2.1.6" | jq '.version' 2>/dev/null || echo "NOT FOUND"
echo "Checking `@voltagent/libsql`@2.0.2..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2flibsql/2.0.2" | jq '.version' 2>/dev/null || echo "NOT FOUND"
echo "Checking `@voltagent/logger`@2.0.2..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2flogger/2.0.2" | jq '.version' 2>/dev/null || echo "NOT FOUND"
echo "Checking `@voltagent/server-hono`@2.0.4..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2fserver-hono/2.0.4" | jq '.version' 2>/dev/null || echo "NOT FOUND"Repository: VoltAgent/voltagent
Length of output: 182
🌐 Web query:
@voltagent/core npm package version 2.1.6
💡 Result:
I couldn't find an @voltagent/core release for version 2.1.6. The package's npm page and registry listings show other versions (for example 1.x and 2.1.0), but not 2.1.6. See the npm package page and the project repo for published versions. [1][2][3]
If you want to check yourself or install a specific version:
- Check available versions: npm view
@voltagent/coreversions --json - Install a version: npm install
@voltagent/core@
Sources:
[1] npm package page for @voltagent/core.
[2] VoltAgent GitHub repository.
[3] Package info on Socket.dev showing v2.1.0.
🌐 Web query:
@voltagent/libsql npm package version 2.0.2
💡 Result:
I couldn't find a published @voltagent/libsql version 2.0.2. The npm package shows latest v1.0.5 (install with npm i @voltagent/libsql). [1][2]
Sources:
@voltagent/libsqlon npm (package page showing v1.0.5). [1]- VoltAgent docs referencing
@voltagent/libsql(v2.x docs/migration). [2]
🌐 Web query:
@voltagent/logger npm package version 2.0.2
💡 Result:
Yes — @voltagent/logger version 2.0.2 is released. See the release notes and migration guide referencing @voltagent/logger@2.0.2. [1][2]
Install:
npm install @voltagent/logger@2.0.2
Sources:
[1] Release entry for @voltagent/logger@2.0.2.
[2] VoltAgent migration/docs referencing @voltagent/logger (installation examples).
🌐 Web query:
@voltagent/server-hono npm package version 2.0.4
💡 Result:
I couldn't find an @voltagent/server-hono version 2.0.4 on npm. The npm registry shows version 1.0.4 as the published release (checked Jan 21, 2026). [1][2]
Sources:
- npm package page for
@voltagent/server-hono(shows v1.0.4). [1] - VoltAgent docs / server architecture (project uses
@voltagent/server-hono; docs current v2.0.x but not the package release). [2]
Fix package versions: @voltagent/core, @voltagent/libsql, and @voltagent/server-hono are not published at the specified versions.
The following versions do not exist on npm and will cause installation to fail:
@voltagent/core@2.1.6— only 1.x and 2.1.0 are published@voltagent/libsql@2.0.2— only v1.0.5 is available@voltagent/server-hono@2.0.4— only v1.0.4 is published
Only @voltagent/logger@2.0.2 is available. Update package.json to use valid published versions.
🤖 Prompt for AI Agents
In `@examples/with-google-vertex-ai/package.json` around lines 6 - 9, Update the
invalid dependency versions in package.json: replace "@voltagent/core":"^2.1.6"
with a published version (e.g., "^2.1.0" or a suitable 1.x), replace
"@voltagent/libsql":"^2.0.2" with the published "1.0.5" (e.g., "^1.0.5"), and
replace "@voltagent/server-hono":"^2.0.4" with the published "1.0.4" (e.g.,
"^1.0.4"); leave "@voltagent/logger":"^2.0.2" as-is, then run npm install to
verify resolution.
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/server-core": "^2.1.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
pkgs=("@voltagent/core@2.1.6" "@voltagent/server-core@2.1.3" "@voltagent/server-hono@2.0.4")
for p in "${pkgs[@]}"; do
echo "== $p =="
python - <<'PY' "$p"
import json, sys, urllib.request
p = sys.argv[1]
name, ver = p.rsplit("@", 1)
try:
data = json.load(urllib.request.urlopen(f"https://registry.npmjs.org/{name}"))
has_version = ver in data.get("versions", {})
print("has_version:", has_version)
if has_version:
pkg_data = data["versions"][ver]
print("peerDependencies:", pkg_data.get("peerDependencies", {}))
print("published_version_exists: true")
else:
available_versions = list(data.get("versions", {}).keys())
print("available_versions (recent):", available_versions[-5:] if available_versions else "none")
print("published_version_exists: false")
except Exception as e:
print(f"error: {e}")
PY
echo ""
doneRepository: VoltAgent/voltagent
Length of output: 149
🌐 Web query:
@voltagent/core npm registry version 2.1.6
💡 Result:
I couldn't find @voltagent/core@2.1.6 on the npm registry. The package page and recent release listings show other versions (e.g., 0.1.x on npm and releases up to 2.1.0). [1][2]
Sources:
- npm package page for
@voltagent/core. [1] - VoltAgent GitHub / release listing (shows
@voltagent/coreup to 2.1.0). [2]
🌐 Web query:
@voltagent/server-core npm registry version 2.1.3
💡 Result:
I couldn't find a published @voltagent/server-core v2.1.3 on the npm registry. The latest published version appears to be v2.1.2 (published Jan 8, 2026). [1][2]
Sources:
- Socket.dev package info showing v2.1.2 as latest. [1]
- Libraries.io/npm listing for
@voltagent/server-core. [2]
🌐 Web query:
@voltagent/server-hono npm registry version 2.0.4
💡 Result:
I couldn't find a published @voltagent/server-hono package at version 2.0.4 on the npm registry. The npm package page shows the latest published version as 1.0.4. [1][2]
If you want to confirm locally: run npm view @voltagent/server-hono versions --json. [1]
Sources:
- npm package page for
@voltagent/server-hono(version info). [1] - VoltAgent docs referencing the server-hono package (project v2.x docs). [2]
These VoltAgent package versions do not exist on the npm registry and will cause npm install to fail.
@voltagent/core@2.1.6→ Latest published is2.1.0@voltagent/server-core@2.1.3→ Latest published is2.1.2(Jan 8, 2026)@voltagent/server-hono@2.0.4→ Latest published is1.0.4
Update to the correct published versions.
🤖 Prompt for AI Agents
In `@examples/with-nestjs/package.json` around lines 9 - 11, The package.json
lists non-existent VoltAgent versions causing npm install failures; update the
dependency versions for "@voltagent/core", "@voltagent/server-core", and
"@voltagent/server-hono" to the published releases (e.g., set "@voltagent/core"
to 2.1.0, "@voltagent/server-core" to 2.1.2, and "@voltagent/server-hono" to
1.0.4) and run npm install to verify resolution; ensure the three entries in
package.json exactly match these published version strings.
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/logger": "^2.0.2", | ||
| "@voltagent/server-hono": "^2.0.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check all four dependencies mentioned in the snippet
versions=(
"@voltagent/core:2.1.6"
"@voltagent/libsql:2.0.2"
"@voltagent/logger:2.0.2"
"@voltagent/server-hono:2.0.4"
)
for dep in "${versions[@]}"; do
IFS=':' read -r pkg ver <<< "$dep"
echo "Checking $pkg@$ver..."
if curl -fsSL "https://registry.npmjs.org/$(echo "$pkg" | sed 's/@/%40/' | sed 's/\//%2f/')/json" 2>/dev/null | jq -e ".versions[\"$ver\"]" >/dev/null 2>&1; then
echo "✓ $pkg@$ver is published"
else
echo "✗ $pkg@$ver NOT found"
fi
doneRepository: VoltAgent/voltagent
Length of output: 182
🌐 Web query:
@voltagent/core npm package version 2.1.6
💡 Result:
I couldn't find an npm release for @voltagent/core at version 2.1.6. The npm registry pages show 0.1.x series releases, while the project's GitHub/new-releases listings show up through 2.1.0 (not 2.1.6). Sources: npm package page and the VoltAgent GitHub release listing. [1][2]
Sources
[1] npm @voltagent/core package page.
[2] VoltAgent (voltagent) GitHub / releases (shows @voltagent/core up to 2.1.0).
🌐 Web query:
@voltagent/server-hono npm package version 2.0.4
💡 Result:
I couldn't find an npm release of @voltagent/server-hono at version 2.0.4 — the npm page shows @voltagent/server-hono at 1.0.4. [1]
There is, however, a GitHub release entry for @voltagent/serverless-hono v2.0.4. [2]
Sources:
- npm package page for
@voltagent/server-hono(version listed: 1.0.4). [1] - GitHub release listing for
@voltagent/serverless-hono@ 2.0.4. [2]
🌐 Web query:
@voltagent/libsql npm package version 2.0.2
💡 Result:
I couldn't find an @voltagent/libsql package release 2.0.2 on npm. The npm package page shows current published version 1.0.5. [1] VoltAgent docs reference a v2.0.x docs line but do not show an @voltagent/libsql v2.0.2 release on npm. [2]
If you want, I can watch the package for updates or search the VoltAgent GitHub/releases for any unpublished or upcoming 2.0.x release.
Sources:
- npm:
@voltagent/libsql(shows version 1.0.5). [1] - VoltAgent docs (v2.0.x docs/migration guide). [2]
🌐 Web query:
@voltagent/logger npm package version 2.0.2
💡 Result:
@voltagent/logger version 2.0.2 is listed in the VoltAgent releases (part of the VoltAgent 2.x updates) and referenced in the VoltAgent documentation. [1][2]
Sources:
- VoltAgent docs (logging / createPinoLogger). [1]
- Release listing showing
@voltagent/logger@2.0.2. [2]
@VoltAgent dependencies specify unpublished versions that will cause npm install to fail.
The following versions in this package.json don't exist on npm registry:
@voltagent/core@2.1.6— only version 2.1.0 is published; 2.1.6 does not exist@voltagent/server-hono@2.0.4— npm has only 1.0.4; there is a separate@voltagent/serverless-hono@2.0.4@voltagent/libsql@2.0.2— only version 1.0.5 is published; 2.0.2 does not exist
Only @voltagent/logger@2.0.2 is available. Update these dependency versions to match published releases or verify the correct package names.
🤖 Prompt for AI Agents
In `@examples/with-playwright/package.json` around lines 10 - 13, The package.json
lists unpublished `@voltagent` versions; update the dependency entries to
published names/versions: change "@voltagent/core" from 2.1.6 to 2.1.0, change
"@voltagent/libsql" from 2.0.2 to 1.0.5, and either correct
"@voltagent/server-hono" to the published 1.0.4 or replace it with the intended
package "@voltagent/serverless-hono@2.0.4"; verify the registry for each package
name/version before committing.
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/logger": "^2.0.2", | ||
| "@voltagent/server-hono": "^2.0.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check if versions exist in npm registry
echo "Checking `@voltagent/core`@2.1.6..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2fcore/2.1.6" >/dev/null && echo "✓ Found" || echo "✗ Not found"
echo "Checking `@voltagent/server-hono`@2.0.4..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2fserver-hono/2.0.4" >/dev/null && echo "✓ Found" || echo "✗ Not found"
echo "Checking `@voltagent/libsql`@2.0.2..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2flibsql/2.0.2" >/dev/null && echo "✓ Found" || echo "✗ Not found"
echo "Checking `@voltagent/logger`@2.0.2..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2flogger/2.0.2" >/dev/null && echo "✓ Found" || echo "✗ Not found"Repository: VoltAgent/voltagent
Length of output: 182
🏁 Script executed:
# Check the full context of the package.json file
find . -path "*examples/with-qdrant/package.json" -type f -exec head -20 {} \;Repository: VoltAgent/voltagent
Length of output: 555
🌐 Web query:
@voltagent/core npm package version 2.1.6
💡 Result:
I could not find an @voltagent/core release at version 2.1.6. The public npm package page lists versions in the 0.x range (latest shown 0.1.1). [1][2] The VoltAgent docs and repo reference a v2.x migration but do not show an @voltagent/core@2.1.6 npm release. [3][4]
Sources:
- npm
@voltagent/core(package page). [1] - npm
@voltagent/core(versions/summary). [2] - VoltAgent docs (migration guide referencing v2.x). [3]
- VoltAgent GitHub repository. [4]
🌐 Web query:
@voltagent/server-hono npm package version 2.0.4
💡 Result:
I couldn't find an npm release @voltagent/server-hono@2.0.4. The npm package currently shows v1.0.4 (published ~16 hours ago). [1][2]
- npm package page (shows v1.0.4). [1]
- VoltAgent docs reference server-related v2.0.x docs, but that doesn't indicate an npm v2.0.4 release. [2]
If you want, I can watch for a 2.0.x release or check a specific registry/GitHub release for that tag.
🌐 Web query:
@voltagent/libsql npm package version 2.0.2
💡 Result:
I couldn't find a published @voltagent/libsql version 2.0.2 on npm. The npm package page shows versions in the 1.0.x line (e.g., 1.0.5 / 1.0.7) and the VoltAgent docs reference the 2.x migration for core but not a @voltagent/libsql 2.0.2 release. [1][2]
If you want to verify yourself, check the package page on npm (search for @voltagent/libsql) or run:
- npm view
@voltagent/libsqlversions --json
Sources:
[1] @voltagent/libsql npm package page.
[2] VoltAgent migration guide / docs referencing @voltagent/libsql.
🌐 Web query:
@voltagent/logger npm package version 2.0.2
💡 Result:
@voltagent/logger version 2.0.2 is published (used by VoltAgent v2.x). See the VoltAgent docs and release notes. [1][2]
Sources:
[1] VoltAgent docs — Logging (@voltagent/logger).
[2] VoltAgent repository release mentioning @voltagent/logger@2.0.2.
Critical: Package versions not published on npm — example will fail to install.
Three of the specified VoltAgent packages are not published at the versions in package.json:
@voltagent/core@2.1.6— not found (latest is 0.1.1)@voltagent/server-hono@2.0.4— not found (current is 1.0.4)@voltagent/libsql@2.0.2— not found (versions are 1.0.x)@voltagent/logger@2.0.2— ✓ found
Update the package.json to use published versions that exist on npm, or these dependencies will fail to resolve during installation.
🤖 Prompt for AI Agents
In `@examples/with-qdrant/package.json` around lines 7 - 10, The dependencies in
package.json reference unpublished versions and will break installs: update the
`@voltagent` packages to published npm versions by changing the dependency entries
for `@voltagent/core`, `@voltagent/server-hono`, and `@voltagent/libsql` to known
published versions (for example `@voltagent/core` -> 0.1.1, `@voltagent/server-hono`
-> 1.0.4, and an existing `@voltagent/libsql` 1.0.x release), leave
`@voltagent/logger` as-is, and validate by running npm view <package>@<version> or
a test npm install to ensure the chosen versions exist before committing.
| "@voltagent/core": "~2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/logger": "^2.0.2", | ||
| "@voltagent/server-hono": "^2.0.3", | ||
| "@voltagent/server-hono": "^2.0.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check `@voltagent/core` version 2.1.6
echo "Checking `@voltagent/core`@2.1.6..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2fcore/2.1.6" 2>&1 | jq -r '.version' || echo "NOT_FOUND"
# Check `@voltagent/server-hono` version 2.0.4
echo "Checking `@voltagent/server-hono`@2.0.4..."
curl -fsSL "https://registry.npmjs.org/@voltagent%2fserver-hono/2.0.4" 2>&1 | jq -r '.version' || echo "NOT_FOUND"
# Also check the latest versions available
echo ""
echo "Latest versions available:"
curl -fsSL "https://registry.npmjs.org/@voltagent%2fcore" 2>&1 | jq -r '.dist-tags.latest' || echo "Unable to fetch"
curl -fsSL "https://registry.npmjs.org/@voltagent%2fserver-hono" 2>&1 | jq -r '.dist-tags.latest' || echo "Unable to fetch"Repository: VoltAgent/voltagent
Length of output: 550
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check if packages exist at all with HTTP status codes
echo "Checking `@voltagent/core`@2.1.6:"
curl -w "\nHTTP Status: %{http_code}\n" -sL "https://registry.npmjs.org/@voltagent%2fcore/2.1.6" 2>&1 | head -20
echo ""
echo "Checking `@voltagent/server-hono`@2.0.4:"
curl -w "\nHTTP Status: %{http_code}\n" -sL "https://registry.npmjs.org/@voltagent%2fserver-hono/2.0.4" 2>&1 | head -20
# Check if `@voltagent` org exists
echo ""
echo "Checking `@voltagent/core` (any version):"
curl -w "\nHTTP Status: %{http_code}\n" -sL "https://registry.npmjs.org/@voltagent%2fcore" 2>&1 | grep -E '"name"|"version"|error" | head -10
# Check the actual package.json file
echo ""
echo "Full package.json from the example:"
cat examples/with-zapier-mcp/package.jsonRepository: VoltAgent/voltagent
Length of output: 350
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Read the package.json file
echo "=== Package.json content ==="
cat examples/with-zapier-mcp/package.json
echo ""
echo "=== Checking available versions for `@voltagent/core` ==="
curl -sL "https://registry.npmjs.org/@voltagent%2fcore" 2>&1 | jq '.versions | keys[-5:]' 2>/dev/null || echo "Unable to fetch versions"
echo ""
echo "=== Checking available versions for `@voltagent/server-hono` ==="
curl -sL "https://registry.npmjs.org/@voltagent%2fserver-hono" 2>&1 | jq '.versions | keys[-5:]' 2>/dev/null || echo "Unable to fetch versions"Repository: VoltAgent/voltagent
Length of output: 1116
Update dependency versions to published releases in npm registry.
The versions specified don't exist:
@voltagent/core@2.1.6→ latest available is2.1.5@voltagent/server-hono@2.0.4→ latest available is2.0.3
Update package.json to use:
"@voltagent/core": "~2.1.5",
"@voltagent/server-hono": "^2.0.3",🤖 Prompt for AI Agents
In `@examples/with-zapier-mcp/package.json` around lines 7 - 10, The package
versions listed are not published; update the dependency entries for
`@voltagent/core` and `@voltagent/server-hono` in package.json: change
"@voltagent/core": "~2.1.6" to "~2.1.5" and change "@voltagent/server-hono":
"^2.0.4" to "^2.0.3" so the project depends on the published releases.
| curl -X POST http://localhost:3141/api/memory/save-messages \ | ||
| -H "Content-Type: application/json" \ |
There was a problem hiding this comment.
Wrap bare URLs in angle brackets to satisfy markdownlint MD034.
markdownlint flags the bare URLs in the curl examples. Wrap them in <...> to comply.
✏️ Proposed fix
- curl -X POST http://localhost:3141/api/memory/save-messages \
+ curl -X POST <http://localhost:3141/api/memory/save-messages> \- curl "http://localhost:3141/api/memory/search?searchQuery=refund%20policy&limit=5"
+ curl "<http://localhost:3141/api/memory/search?searchQuery=refund%20policy&limit=5>"Also applies to: 69-70
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
44-44: Bare URL used
(MD034, no-bare-urls)
🤖 Prompt for AI Agents
In `@packages/server-elysia/CHANGELOG.md` around lines 43 - 44, Wrap the bare URLs
in the curl examples in angle brackets to satisfy markdownlint MD034: replace
occurrences of the literal URL strings (e.g.,
"http://localhost:3141/api/memory/save-messages" and the other curl example
around lines 69-70) with "<http://localhost:3141/api/memory/save-messages>" (and
the corresponding other URL) so the markdown examples use angled brackets around
the URLs.
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.1.6
Patch Changes
9221498Thanks @omeraplak! - fix: normalize Anthropic usage for finish events so totals reflect the last step in multi-step runs@voltagent/evals@2.0.3
Patch Changes
#970
ed6075aThanks @omeraplak! - feat: allowrunExperimentto accept aVoltOpsClientdirectly by adapting it for dataset resolution when needed.@voltagent/server-core@2.1.3
Patch Changes
#974
a5bc28dThanks @omeraplak! - feat: add memory HTTP endpoints for conversations, messages, working memory, and search across server-core, Hono, Elysia, and serverless runtimes.Endpoints
GET /api/memory/conversationsPOST /api/memory/conversationsGET /api/memory/conversations/:conversationIdPATCH /api/memory/conversations/:conversationIdDELETE /api/memory/conversations/:conversationIdPOST /api/memory/conversations/:conversationId/cloneGET /api/memory/conversations/:conversationId/messagesGET /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/save-messagesPOST /api/memory/messages/deleteGET /api/memory/searchNote: include
agentId(query/body) when multiple agents are registered or no global memory is configured.Examples
Create a conversation:
Save messages into the conversation:
Update working memory (append mode):
Search memory (requires embedding + vector adapters):
curl "http://localhost:3141/api/memory/search?searchQuery=refund%20policy&limit=5"Updated dependencies [
9221498]:@voltagent/server-elysia@2.0.1
Patch Changes
#974
a5bc28dThanks @omeraplak! - feat: add memory HTTP endpoints for conversations, messages, working memory, and search across server-core, Hono, Elysia, and serverless runtimes.Endpoints
GET /api/memory/conversationsPOST /api/memory/conversationsGET /api/memory/conversations/:conversationIdPATCH /api/memory/conversations/:conversationIdDELETE /api/memory/conversations/:conversationIdPOST /api/memory/conversations/:conversationId/cloneGET /api/memory/conversations/:conversationId/messagesGET /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/save-messagesPOST /api/memory/messages/deleteGET /api/memory/searchNote: include
agentId(query/body) when multiple agents are registered or no global memory is configured.Examples
Create a conversation:
Save messages into the conversation:
Update working memory (append mode):
Search memory (requires embedding + vector adapters):
curl "http://localhost:3141/api/memory/search?searchQuery=refund%20policy&limit=5"Updated dependencies [
9221498,a5bc28d]:@voltagent/server-hono@2.0.4
Patch Changes
#974
a5bc28dThanks @omeraplak! - feat: add memory HTTP endpoints for conversations, messages, working memory, and search across server-core, Hono, Elysia, and serverless runtimes.Endpoints
GET /api/memory/conversationsPOST /api/memory/conversationsGET /api/memory/conversations/:conversationIdPATCH /api/memory/conversations/:conversationIdDELETE /api/memory/conversations/:conversationIdPOST /api/memory/conversations/:conversationId/cloneGET /api/memory/conversations/:conversationId/messagesGET /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/save-messagesPOST /api/memory/messages/deleteGET /api/memory/searchNote: include
agentId(query/body) when multiple agents are registered or no global memory is configured.Examples
Create a conversation:
Save messages into the conversation:
Update working memory (append mode):
Search memory (requires embedding + vector adapters):
curl "http://localhost:3141/api/memory/search?searchQuery=refund%20policy&limit=5"Updated dependencies [
9221498,a5bc28d]:@voltagent/serverless-hono@2.0.6
Patch Changes
#974
a5bc28dThanks @omeraplak! - feat: add memory HTTP endpoints for conversations, messages, working memory, and search across server-core, Hono, Elysia, and serverless runtimes.Endpoints
GET /api/memory/conversationsPOST /api/memory/conversationsGET /api/memory/conversations/:conversationIdPATCH /api/memory/conversations/:conversationIdDELETE /api/memory/conversations/:conversationIdPOST /api/memory/conversations/:conversationId/cloneGET /api/memory/conversations/:conversationId/messagesGET /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/conversations/:conversationId/working-memoryPOST /api/memory/save-messagesPOST /api/memory/messages/deleteGET /api/memory/searchNote: include
agentId(query/body) when multiple agents are registered or no global memory is configured.Examples
Create a conversation:
Save messages into the conversation:
Update working memory (append mode):
Search memory (requires embedding + vector adapters):
curl "http://localhost:3141/api/memory/search?searchQuery=refund%20policy&limit=5"Updated dependencies [
a5bc28d]:Summary by CodeRabbit
New Features
Bug Fixes
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.