ci(changesets): version packages#962
Conversation
Deploying voltagent with
|
| Latest commit: |
f9377c9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5e45a176.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
📝 WalkthroughWalkthroughBumps package versions to publish Changes
Sequence Diagram(s)(omitted — changes are version/changelog and dependency updates without new multi-component control flow) 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. 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: 13
🤖 Fix all issues with AI agents
In `@examples/with-amazon-bedrock/package.json`:
- Line 6: The package.json dependency entry uses a non-existent version
"@voltagent/core": "^2.1.3"; change that dependency string to the published
version by updating the entry to "@voltagent/core": "^2.1.2" so npm install
succeeds—locate and edit the dependency line containing "@voltagent/core" in
package.json and replace 2.1.3 with 2.1.2.
In `@examples/with-client-side-tools/package.json`:
- Line 7: Update the published dependency version: replace the dependency entry
"@voltagent/core": "^2.1.3" with an available release such as "@voltagent/core":
"^2.1.0" in package.json, then regenerate your lockfile (npm install or yarn
install) so the lockfile reflects the updated version; ensure any CI or build
scripts that reference `@voltagent/core` use the updated version string.
In `@examples/with-cloudflare-workers/package.json`:
- Line 6: Update the dependency entry in package.json that references
"@voltagent/core": change the version string from "^2.1.3" to the published
version "^2.1.2" so npm install can resolve the package; locate the dependency
line for "@voltagent/core" and replace the version token accordingly.
In `@examples/with-google-vertex-ai/package.json`:
- Line 6: Update the dependency entry for "@voltagent/core" to a valid published
version (replace "^2.1.3" with an available version such as "^2.1.2") in the
package.json so npm can resolve the package; ensure any lockfile is regenerated
(npm install or yarn install) after updating.
In `@examples/with-guardrails/package.json`:
- Line 6: The package.json entry for the dependency "@voltagent/core" references
a non-existent version (^2.1.3); update that dependency string to the published
latest version (^2.1.2) so npm can install it—find the "@voltagent/core" line in
package.json and change the version token accordingly.
In `@examples/with-hooks/package.json`:
- Line 6: The package.json references a non-existent dependency version
"@voltagent/core": "^2.1.3"; update that entry to the latest published version
by changing the dependency string to "@voltagent/core": "^2.1.2" so installs
succeed (edit the package.json dependency line that currently contains
"@voltagent/core": "^2.1.3" and replace the version).
In `@examples/with-mcp-server/package.json`:
- Line 4: The dependency entry for "@voltagent/core" in examples/with-mcp-server
is referencing a non-existent version 2.1.3; update the package.json dependency
value for "@voltagent/core" to the published version "^2.1.2" (replace the
version string for the "@voltagent/core" dependency) so npm install can succeed.
In `@examples/with-nuxt/package.json`:
- Line 6: Update the dependency entry for "@voltagent/core" which currently
references a non-existent version "^2.1.3" by changing it to the published
latest "^2.1.2"; locate the dependency line with the key "@voltagent/core" in
package.json and replace the version specifier so the project installs the
actual released package.
In `@examples/with-postgres/package.json`:
- Line 7: The package.json references a non-existent version "@voltagent/core":
"^2.1.3"; update that dependency to the latest published version by changing the
dependency entry for "@voltagent/core" to "^2.1.2" so installs succeed.
In `@examples/with-slack/package.json`:
- Line 6: The dependency version for `@voltagent/core` in package.json is
incorrect (refs the non-existent 2.1.3); update the version string in
package.json (the "@voltagent/core" entry) to "^2.1.2" so npm can resolve the
package successfully.
In `@examples/with-viteval/package.json`:
- Line 6: The package.json currently depends on an unpublished version
"@voltagent/core": "^2.1.3" which will break installs; update the dependency
entry in package.json to a published version (for example "@voltagent/core":
"^1.1.0") or coordinate to publish 2.1.3 before merging so the install succeeds
— edit the "@voltagent/core" line accordingly and run npm install to verify.
In `@examples/with-voltagent-actions/package.json`:
- Line 6: Replace the non-existent dependency version in package.json for
"@voltagent/core"; change the current version spec "^2.1.3" to the published
version "^2.1.2" so package installation uses the available release (update the
version string in the dependencies block where "@voltagent/core" is declared).
In `@examples/with-whatsapp/package.json`:
- Line 7: Replace the non-existent dependency version by updating the
package.json dependency for "@voltagent/core" from "^2.1.3" to the published
version "^2.1.2" so the project uses the correct, available package version.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core`@2.1.3 version 2>&1Repository: VoltAgent/voltagent
Length of output: 443
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | head -50Repository: VoltAgent/voltagent
Length of output: 642
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | tail -20Repository: VoltAgent/voltagent
Length of output: 277
@voltagent/core 2.1.3 does not exist—downgrade to 2.1.2.
The specified version is not published on npm. The latest available version is 2.1.2. Update the dependency to "@voltagent/core": "^2.1.2" to resolve npm install failures.
🤖 Prompt for AI Agents
In `@examples/with-amazon-bedrock/package.json` at line 6, The package.json
dependency entry uses a non-existent version "@voltagent/core": "^2.1.3"; change
that dependency string to the published version by updating the entry to
"@voltagent/core": "^2.1.2" so npm install succeeds—locate and edit the
dependency line containing "@voltagent/core" in package.json and replace 2.1.3
with 2.1.2.
| "@ai-sdk/react": "^3.0.0", | ||
| "@libsql/client": "^0.15.0", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core@2.1.3 npm package
💡 Result:
I couldn't find a published @voltagent/core version 2.1.3. The project’s releases and package info show 2.1.0 as a recent published release (and many 1.x releases). See the project site and releases for details: [VoltAgent website] [1], GitHub releases summary showing 2.1.0 [2].
If you want to check locally or install the latest available version, run:
- npm view
@voltagent/coreversions - npm install
@voltagent/core@latest
Sources:
[1] https://voltagent.dev/ (project site).
[2] GitHub releases / repo summary (VoltAgent/voltagent).
Update dependency to an available version.
Version @voltagent/core@2.1.3 is not published on npm. The latest available version is 2.1.0. Update the dependency to "@voltagent/core": "^2.1.0" or a version that exists in the published releases.
🤖 Prompt for AI Agents
In `@examples/with-client-side-tools/package.json` at line 7, Update the published
dependency version: replace the dependency entry "@voltagent/core": "^2.1.3"
with an available release such as "@voltagent/core": "^2.1.0" in package.json,
then regenerate your lockfile (npm install or yarn install) so the lockfile
reflects the updated version; ensure any CI or build scripts that reference
`@voltagent/core` use the updated version string.
| "version": "1.0.0", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify that `@voltagent/core`@2.1.3 exists on npm
curl -s https://registry.npmjs.org/@voltagent%2Fcore \
| jq -r '.versions["2.1.3"].version // empty'
# Check the latest dist-tag to ensure expected release alignment
curl -s https://registry.npmjs.org/@voltagent%2Fcore \
| jq -r '.["dist-tags"]'Repository: VoltAgent/voltagent
Length of output: 112
Downgrade @voltagent/core to 2.1.2 — version 2.1.3 does not exist on npm.
The latest published version is 2.1.2 (dist-tags show latest: 2.1.2). Version 2.1.3 has not been released. The package.json references a non-existent version, which will cause npm install to fail.
🤖 Prompt for AI Agents
In `@examples/with-cloudflare-workers/package.json` at line 6, Update the
dependency entry in package.json that references "@voltagent/core": change the
version string from "^2.1.3" to the published version "^2.1.2" so npm install
can resolve the package; locate the dependency line for "@voltagent/core" and
replace the version token accordingly.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core` versions --json | tail -20Repository: VoltAgent/voltagent
Length of output: 277
🏁 Script executed:
npm view `@voltagent/core`@2.1.3Repository: VoltAgent/voltagent
Length of output: 443
Version 2.1.3 does not exist on npm. The latest available version of @voltagent/core is 2.1.2. Update the dependency to use an available version.
Available versions: 2.1.2, 2.1.1, 2.1.0, 2.0.14, and earlier.
🤖 Prompt for AI Agents
In `@examples/with-google-vertex-ai/package.json` at line 6, Update the dependency
entry for "@voltagent/core" to a valid published version (replace "^2.1.3" with
an available version such as "^2.1.2") in the package.json so npm can resolve
the package; ensure any lockfile is regenerated (npm install or yarn install)
after updating.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core`@2.1.3 version 2>&1Repository: VoltAgent/voltagent
Length of output: 443
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | head -50Repository: VoltAgent/voltagent
Length of output: 642
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | tail -20Repository: VoltAgent/voltagent
Length of output: 277
Update @voltagent/core to 2.1.2—version 2.1.3 does not exist on npm.
The specified version 2.1.3 is not published. The latest available version is 2.1.2. Update the dependency to "@voltagent/core": "^2.1.2" to resolve the package.
🤖 Prompt for AI Agents
In `@examples/with-guardrails/package.json` at line 6, The package.json entry for
the dependency "@voltagent/core" references a non-existent version (^2.1.3);
update that dependency string to the published latest version (^2.1.2) so npm
can install it—find the "@voltagent/core" line in package.json and change the
version token accordingly.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core`@2.1.3 version 2>&1Repository: VoltAgent/voltagent
Length of output: 443
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | head -50Repository: VoltAgent/voltagent
Length of output: 642
🏁 Script executed:
npm view `@voltagent/core` versionRepository: VoltAgent/voltagent
Length of output: 68
@voltagent/core@2.1.3 does not exist on npm; update to 2.1.2 (latest available version).
Version 2.1.3 is not published in the npm registry. The package.json will fail to install. Downgrade to "@voltagent/core": "^2.1.2", which is the latest available version.
🤖 Prompt for AI Agents
In `@examples/with-postgres/package.json` at line 7, The package.json references a
non-existent version "@voltagent/core": "^2.1.3"; update that dependency to the
latest published version by changing the dependency entry for "@voltagent/core"
to "^2.1.2" so installs succeed.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core` versionRepository: VoltAgent/voltagent
Length of output: 68
🏁 Script executed:
# Also check the full package.json for context
cat -n examples/with-slack/package.json | head -20Repository: VoltAgent/voltagent
Length of output: 673
Correct @voltagent/core version to 2.1.2—version 2.1.3 does not exist in npm registry.
The package.json specifies @voltagent/core@2.1.3, but the npm registry only has version 2.1.2 available. This will cause dependency resolution failures during installation. Change line 6 to:
"@voltagent/core": "^2.1.2",
🤖 Prompt for AI Agents
In `@examples/with-slack/package.json` at line 6, The dependency version for
`@voltagent/core` in package.json is incorrect (refs the non-existent 2.1.3);
update the version string in package.json (the "@voltagent/core" entry) to
"^2.1.2" so npm can resolve the package successfully.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core`@2.1.3 versionRepository: VoltAgent/voltagent
Length of output: 182
🌐 Web query:
@voltagent/core 2.1.3 npm package
💡 Result:
I couldn't find a published @voltagent/core version 2.1.3 on the npm registry. npm shows the package (current npm listing/last-published info) but lists versions in the 0.1.x–1.1.x range, while the project repo shows 2.x releases on GitHub—indicating a registry/release mismatch. [1][2]
What you can do:
- Check the registry yourself: npm view
@voltagent/coreversions. [npm listing]. [1] - If you need a 2.1.x release, check the repo releases/tags on GitHub and the project docs for publish notes. [2]
References
- npm package page for
@voltagent/core. [1] - VoltAgent GitHub repository / releases and official site. [2]
@voltagent/core@2.1.3 is not published on npm—this will cause installation failures.
The npm registry only has versions 0.1.x–1.1.x available. While the GitHub repository shows 2.x releases, version 2.1.3 has not been published to npm. Revert to an available version (e.g., from the 1.1.x range) or ensure 2.1.3 is published before merging.
🤖 Prompt for AI Agents
In `@examples/with-viteval/package.json` at line 6, The package.json currently
depends on an unpublished version "@voltagent/core": "^2.1.3" which will break
installs; update the dependency entry in package.json to a published version
(for example "@voltagent/core": "^1.1.0") or coordinate to publish 2.1.3 before
merging so the install succeeds — edit the "@voltagent/core" line accordingly
and run npm install to verify.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core`@2.1.3 version 2>&1Repository: VoltAgent/voltagent
Length of output: 443
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | head -50Repository: VoltAgent/voltagent
Length of output: 642
🏁 Script executed:
npm view `@voltagent/core`@latest versionRepository: VoltAgent/voltagent
Length of output: 68
Update @voltagent/core to 2.1.2—version 2.1.3 does not exist on npm.
The specified version is not published. The latest available version is 2.1.2.
"@voltagent/core": "^2.1.2",
🤖 Prompt for AI Agents
In `@examples/with-voltagent-actions/package.json` at line 6, Replace the
non-existent dependency version in package.json for "@voltagent/core"; change
the current version spec "^2.1.3" to the published version "^2.1.2" so package
installation uses the available release (update the version string in the
dependencies block where "@voltagent/core" is declared).
| "@supabase/supabase-js": "^2.49.4", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
npm view `@voltagent/core`@2.1.3 version 2>&1Repository: VoltAgent/voltagent
Length of output: 443
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | head -100Repository: VoltAgent/voltagent
Length of output: 1251
🏁 Script executed:
npm view `@voltagent/core` versions --json 2>&1 | tail -20Repository: VoltAgent/voltagent
Length of output: 277
@voltagent/core@2.1.3 does not exist—use 2.1.2 instead.
The version 2.1.3 is not published on npm. The latest available version is 2.1.2. Update the dependency to "@voltagent/core": "^2.1.2" to resolve correctly.
🤖 Prompt for AI Agents
In `@examples/with-whatsapp/package.json` at line 7, Replace the non-existent
dependency version by updating the package.json dependency for "@voltagent/core"
from "^2.1.3" to the published version "^2.1.2" so the project uses the correct,
available package version.
92ce4c5 to
135f376
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@examples/with-resumable-streams/package.json`:
- Line 7: The package dependency for `@voltagent/core` is set to an unavailable
version "^2.1.3"; update the package.json dependency entry for "@voltagent/core"
to use the published version "^2.1.2" so installations succeed (replace the
version string in the existing dependency line).
♻️ Duplicate comments (3)
examples/with-viteval/package.json (1)
6-6: LGTM — this is a Changesets release PR.The previous review comment flagging version 2.1.3 as unpublished is not applicable here. As stated in the PR description: "Merging will publish the updated packages to npm automatically." This is the expected Changesets workflow where version bumps are committed first, then packages are published to npm upon merge.
examples/with-nuxt/package.json (1)
6-6: LGTM — Changesets will publish upon merge.The previous review flagging 2.1.3 as unavailable doesn't apply to Changesets release PRs. The package will be published to npm when this PR is merged.
examples/with-mcp-server/package.json (1)
4-4: Re-verify@voltagent/core@2.1.3 is published.Same concern as earlier: ensure the version is on npm before merging so installs don’t fail.
#!/bin/bash # Verify published version exists on npm npm view `@voltagent/core`@2.1.3 version npm view `@voltagent/core` versions --json | tail -20
| "author": "", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.1.2", | ||
| "@voltagent/core": "^2.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify published version exists on npm
npm view `@voltagent/core`@2.1.3 version 2>&1
echo "---"
npm view `@voltagent/core` versions --json 2>&1 | tail -30Repository: VoltAgent/voltagent
Length of output: 778
Update dependency to use available version 2.1.2.
@voltagent/core@2.1.3 is not published on npm. The latest available version is 2.1.2. Change the dependency from "@voltagent/core": "^2.1.3" to "@voltagent/core": "^2.1.2" to allow the example to install successfully.
🤖 Prompt for AI Agents
In `@examples/with-resumable-streams/package.json` at line 7, The package
dependency for `@voltagent/core` is set to an unavailable version "^2.1.3"; update
the package.json dependency entry for "@voltagent/core" to use the published
version "^2.1.2" so installations succeed (replace the version string in the
existing dependency line).
135f376 to
f9377c9
Compare
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.3
Patch Changes
#959
99ba28cThanks @omeraplak! - feat: allow PlanAgent task tool to forward subagent stream events via supervisorConfigExample:
#963
ee1ad19Thanks @omeraplak! - feat: add retry/fallback hooks and middleware retry feedbackModel Retry and Fallback
Configure ordered model candidates with per-model retry limits.
maxRetriesis per model (total attempts =maxRetries + 1).Middleware Retry Feedback
Middleware can request a retry. The retry reason and metadata are added as a system
message for the next attempt.
Input Middleware Example
Input middleware can rewrite user input before guardrails and hooks.
Retry and Fallback Hooks
Track retries and fallbacks in hooks.
onRetryruns for LLM and middleware retries.Updated dependencies [
c39fedd]:@voltagent/internal@1.0.3
Patch Changes
c39feddThanks @rallu! - fix(internal): improve safeStringify function to handle circular references more effectivelySummary by CodeRabbit
Release Notes
New Features
Bug Fixes
Chores
✏️ Tip: You can customize this high-level summary in your review settings.