ci(changesets): version packages#977
Conversation
Deploying voltagent with
|
| Latest commit: |
f87b54e
|
| Status: | ⚡️ Build in progress... |
📝 WalkthroughWalkthroughThis PR bumps patch versions across four core packages (libsql, postgres, supabase, voltagent-memory) and updates all corresponding example dependencies to use the new versions. CHANGELOG files are updated for each package, and a previous changeset entry is removed. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 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 |
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}
![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/base/package.json`:
- Line 8: The package.json dependency entry for "@voltagent/libsql": "^2.0.3"
references a non-existent npm version; update that dependency to a published
version such as "@voltagent/libsql": "^1.0.5" (or another valid existing
version) so installs succeed, i.e., locate the "@voltagent/libsql" entry in
package.json and replace "^2.0.3" with a valid version string like "^1.0.5".
In `@examples/with-custom-endpoints/package.json`:
- Line 7: The package.json dependency for "@voltagent/libsql" specifies a
non-existent version "^2.0.3"; update the dependency declaration for
"@voltagent/libsql" to a published release (for example change the version
string to "^1.0.5" or the intended valid semver) so the project installs
correctly.
In `@examples/with-nuxt/package.json`:
- Line 7: The package.json currently depends on a non-existent version
"@voltagent/libsql": "^2.0.3"; update that dependency to a published version
(for example change the version string to "^1.1.0" or the latest published
release) so npm install can succeed, then run npm install or yarn to verify
dependency resolution and update lockfile if present.
In `@examples/with-tavily-search/package.json`:
- Line 7: Update the dependency entry for "@voltagent/libsql" in package.json to
a valid published version (e.g., change the version string from "^2.0.3" to
"^1.0.5") so installs won't fail; locate the "@voltagent/libsql" dependency in
the file and replace the version specifier accordingly, and if you intended to
upgrade from a prior v1 release, verify/adjust any code using LibSQLStorage →
Memory V2 with LibSQLMemoryAdapter for breaking-change compatibility.
In `@examples/with-voice-elevenlabs/package.json`:
- Line 7: The package.json dependency "@voltagent/libsql" is pinned to a
non-existent version "2.0.3"; update the version string for "@voltagent/libsql"
to a valid published version (e.g., a 1.x release such as "^1.0.7" or the latest
1.x available) in package.json and then reinstall dependencies (npm install /
yarn install) so the project uses a valid published package.
In `@examples/with-voice-openai/package.json`:
- Line 7: The dependency entry for "@voltagent/libsql" in package.json
references a non-existent version 2.0.3; update the version string for the
"@voltagent/libsql" dependency to a valid 1.x release (for example "^1.0.5" or
"^1.0.0") so the package resolves successfully during install/build.
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/libsql 2.0.3 npm release notes breaking changes
💡 Result:
I couldn't find an @voltagent/libsql v2.0.3 release. The package on npm and the VoltAgent GitHub releases show 1.x releases (examples: npm listing and GitHub releases/changelog). If you meant a different package or version, tell me and I’ll search again.
Sources:
- npm package page for
@voltagent/libsql. [1] - VoltAgent GitHub releases (release notes / changelog for
@voltagent/libsql1.x). [2]
🌐 Web query:
@voltagent/libsql npm package version 2.0.3
💡 Result:
There is no published @voltagent/libsql version 2.0.3. The npm package's latest published version is 1.0.5. [1][2]
Sources:
- npm package page for
@voltagent/libsql(shows version 1.0.5). [1] - VoltAgent docs / release notes referencing the libsql adapter (project pages). [2]
References:
[1] https://www.npmjs.com/package/%40voltagent%2Flibsql
[2] https://voltagent.dev/docs/agents/memory/libsql/
Version 2.0.3 does not exist on npm.
@voltagent/libsql has no published v2.0.3 release. The latest published version is 1.0.5. This will cause npm install to fail. Update the dependency to an existing version (e.g., ^1.0.5).
🤖 Prompt for AI Agents
In `@examples/base/package.json` at line 8, The package.json dependency entry for
"@voltagent/libsql": "^2.0.3" references a non-existent npm version; update that
dependency to a published version such as "@voltagent/libsql": "^1.0.5" (or
another valid existing version) so installs succeed, i.e., locate the
"@voltagent/libsql" entry in package.json and replace "^2.0.3" with a valid
version string like "^1.0.5".
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/libsql 2.0.3 npm release notes breaking changes
💡 Result:
I couldn’t find an npm release @voltagent/libsql@2.0.3. The npm package shows current versions in the 1.x range (latest listed ~1.0.5 / recent publishes) and the project releases pages list 1.x tags—no 2.0.3 release or 2.x changelog entries were found. See the package page and releases index for details. [1][2]
If you want, I can:
- Search the VoltAgent GitHub releases/changelog more deeply, or
- Watch for a 2.0.x release and report breaking changes when it appears.
Sources:
[1] @voltagent/libsql — npm package page.
[2] VoltAgent/voltagent release listings (examples of 1.x releases).
@voltagent/libsql 2.0.3 does not exist on npm.
The npm package shows versions in the 1.x range (latest ~1.0.5). Correct the version in package.json to an actual published release (e.g., ^1.0.5 or the intended version if available).
🤖 Prompt for AI Agents
In `@examples/with-custom-endpoints/package.json` at line 7, The package.json
dependency for "@voltagent/libsql" specifies a non-existent version "^2.0.3";
update the dependency declaration for "@voltagent/libsql" to a published release
(for example change the version string to "^1.0.5" or the intended valid semver)
so the project installs correctly.
| "@nuxt/ui": "^4.0.0", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/libsql npm package 2.0.3 release notes
💡 Result:
I couldn't find any release notes for @voltagent/libsql v2.0.3 — the package's published versions and release notes appear to be in the 1.x series (examples: npm package page and recent 1.1.0 / 1.0.x release notes). See the npm package page and recent release entries. [1][2]
Sources:
- npm package page for
@voltagent/libsql(current listed versions/info). [1] - Release entries for
@voltagent/libsql(e.g., 1.1.0, 1.0.x) on release aggregators. [2]
🌐 Web query:
@voltagent/libsql version 2.0.3 breaking changes
💡 Result:
I couldn't find an @voltagent/libsql 2.0.3 release. The library appears to be on 1.x (latest released noted: 1.1.0) and the major 1.x breaking change was the 1.0.0 migration that replaced the old LibSQLStorage with the new Memory V2 adapter (migration guide). See VoltAgent releases/docs for details. [1][2][3]
Sources:
- VoltAgent releases (GitHub releases listing). [1]
@voltagent/libsql1.1.0 release notes (Edge/Cloudflare Workers support). [2]- LibSQL/SQLite Memory docs (usage and migration examples). [3]
🌐 Web query:
site:npmjs.com @voltagent/libsql 2.0.3
💡 Result:
I couldn't find an npm release of @voltagent/libsql at version 2.0.3. The package page on npm shows @voltagent/libsql (current shown version 1.0.5) and the VoltAgent docs reference the libsql adapter. See the npm package and VoltAgent docs. [1][2]
Sources:
[1] npm — @voltagent/libsql package page.
[2] VoltAgent docs — LibSQL / SQLite Memory (mentions @voltagent/libsql).
@voltagent/libsql 2.0.3 does not exist on npm.
Version 2.0.3 is not published. The highest published version is 1.1.0. Update the dependency to use an available version.
🤖 Prompt for AI Agents
In `@examples/with-nuxt/package.json` at line 7, The package.json currently
depends on a non-existent version "@voltagent/libsql": "^2.0.3"; update that
dependency to a published version (for example change the version string to
"^1.1.0" or the latest published release) so npm install can succeed, then run
npm install or yarn to verify dependency resolution and update lockfile if
present.
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/libsql 2.0.3 npm package published
💡 Result:
I couldn't find a published @voltagent/libsql v2.0.3. The npm registry shows the package at v1.x (latest listed ~1.0.5 / 1.0.7), not 2.0.3. [1][2]
If you want, I can monitor npm and let you know if/when v2.0.3 appears.
Sources:
- npm package page for
@voltagent/libsql. [1] - Package metadata mirror (Socket). [2]
🌐 Web query:
@voltagent/libsql release notes breaking changes changelog
💡 Result:
Short summary — where to find the release notes / changelog and the main breaking change:
- Releases page (full release notes for
@voltagent/libsqlon GitHub). [1] - 1.0.0 release (notes call out a breaking migration: LibSQLStorage → Memory V2 with LibSQLMemoryAdapter; see migration guide). [2]
- Docs for LibSQLMemoryAdapter (usage and migration examples). [3]
Main breaking change to watch for
- v1.0.0 replaces the old LibSQLStorage API with the new Memory V2 pattern: you must switch from importing LibSQLStorage to using Memory + LibSQLMemoryAdapter (plus optional LibSQLVectorAdapter). See the migration snippet in the 1.0.0 release notes and the LibSQL docs. [2][3]
If you want, I can fetch the exact migration guide steps and paste the code changes from the releases/migration doc.
🌐 Web query:
site:npmjs.com @voltagent/libsql``
💡 Result:
Found the npm package @voltagent/libsql:
- Package:
@voltagent/libsql. - Latest version: 1.0.5.
- Weekly downloads: ~1,077.
- Last published: “a day ago” (per npm).
- Install: npm i
@voltagent/libsql. [1]
Sources: [1] @voltagent/libsql npm page.
@voltagent/libsql version 2.0.3 does not exist on npm. The latest published version is 1.0.5. The version constraint ^2.0.3 will fail during installation. Correct to a valid version (e.g., ^1.0.5) or wait until version 2.0.3 is released. If upgrading from an older version, note that v1.0.0 introduced breaking changes (LibSQLStorage → Memory V2 with LibSQLMemoryAdapter).
🤖 Prompt for AI Agents
In `@examples/with-tavily-search/package.json` at line 7, Update the dependency
entry for "@voltagent/libsql" in package.json to a valid published version
(e.g., change the version string from "^2.0.3" to "^1.0.5") so installs won't
fail; locate the "@voltagent/libsql" dependency in the file and replace the
version specifier accordingly, and if you intended to upgrade from a prior v1
release, verify/adjust any code using LibSQLStorage → Memory V2 with
LibSQLMemoryAdapter for breaking-change compatibility.
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/libsql 2.0.3 npm package release notes breaking changes
💡 Result:
I can't find any @voltagent/libsql release v2.0.3. The npm package shows 1.x (latest ~1.0.5/1.0.7 on registry pages) and GitHub release listings for the package are in the 1.0–1.1 range. Sources: npm package page and release listings. [1][2]
Do you mean a different package or version (e.g., @voltagent/core v2.0.3 or another package)? If you want, I can search for a specific repo/release tag (please confirm exact package name and version).
Sources:
- npm:
@voltagent/libsqlpackage page. [1] - VoltAgent release listings (voltagent/@voltagent/libsql releases). [2]
@voltagent/libsql 2.0.3 does not exist on npm.
The package only has versions in the 1.x range (latest ~1.0.5/1.0.7). Update the dependency to a valid version.
🤖 Prompt for AI Agents
In `@examples/with-voice-elevenlabs/package.json` at line 7, The package.json
dependency "@voltagent/libsql" is pinned to a non-existent version "2.0.3";
update the version string for "@voltagent/libsql" to a valid published version
(e.g., a 1.x release such as "^1.0.7" or the latest 1.x available) in
package.json and then reinstall dependencies (npm install / yarn install) so the
project uses a valid published package.
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.6", | ||
| "@voltagent/libsql": "^2.0.2", | ||
| "@voltagent/libsql": "^2.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/libsql 2.0.3 npm release notes breaking changes
💡 Result:
I couldn't find any @voltagent/libsql release v2.0.3. The npm package shows versions in the 1.x series (latest listed v1.0.5 on the package page), and the VoltAgent GitHub releases also show @voltagent/libsql releases in the 1.x range. Please confirm the version number or check the package/release pages directly. [1][2]
Sources:
[1] npm: @voltagent/libsql package page. (npmjs.com)
[2] VoltAgent releases on GitHub. (github.com)
Citations:
- 1: https://www.npmjs.com/package/%40voltagent%2Flibsql?utm_source=openai
- 2: https://github.com/VoltAgent/voltagent/releases?utm_source=openai
@voltagent/libsql 2.0.3 does not exist on npm. The package is only available in the 1.x series, with the latest version being 1.0.5. Update the dependency to use a valid version from the 1.x range (e.g., ^1.0.5 or ^1.0.0) to avoid build failures.
🤖 Prompt for AI Agents
In `@examples/with-voice-openai/package.json` at line 7, The dependency entry for
"@voltagent/libsql" in package.json references a non-existent version 2.0.3;
update the version string for the "@voltagent/libsql" dependency to a valid 1.x
release (for example "^1.0.5" or "^1.0.0") so the package resolves successfully
during install/build.
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/libsql@2.0.3
Patch Changes
b0fae14Thanks @omeraplak! - chore: bump version@voltagent/postgres@2.0.3
Patch Changes
b0fae14Thanks @omeraplak! - chore: bump version@voltagent/supabase@2.0.3
Patch Changes
b0fae14Thanks @omeraplak! - chore: bump version@voltagent/voltagent-memory@1.0.3
Patch Changes
b0fae14Thanks @omeraplak! - chore: bump versionSummary by cubic
Prepare patch releases and update examples to use the new versions of our memory adapters. This aligns the monorepo for publishing via Changesets.
@voltagent/libsql 2.0.3
@voltagent/postgres 2.0.3
@voltagent/supabase 2.0.3
@voltagent/voltagent-memory 1.0.3
Dependencies
Written for commit f87b54e. Summary will update on new commits.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.