ci(changesets): version packages#992
Conversation
Deploying voltagent with
|
| Latest commit: |
c524d9a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4fd06356.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughThis pull request releases version 2.2.2 of Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 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}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Fix all issues with AI agents
In `@examples/with-agent-tool/package.json`:
- Line 7: The package.json dependency "@voltagent/core": "2.2.2" references a
non-published version; update the dependency in package.json to a published
release (for example "@voltagent/core": "1.1.1") or correct the package name if
you intended a different `@voltagent` package using 2.x; ensure the change is made
where the dependency string "@voltagent/core" is defined so installs succeed.
In `@examples/with-chroma/package.json`:
- Line 9: The dependency entry "@voltagent/core": "^2.2.2" in package.json
references a non-published version and will break installs; update that
dependency to a published version (for example replace "^2.2.2" with a
known-published version like "1.1.1" or "0.1.46") in the package.json
dependencies so npm/yarn can resolve it.
In `@examples/with-mcp-server/package.json`:
- Line 4: The package.json dependency for `@voltagent/core` is pinned to a
non-existent version "^2.2.2"; update the dependency entry in package.json from
"@voltagent/core": "^2.2.2" to "@voltagent/core": "^2.2.1" so the project uses
the latest published 2.2.x release; then run your package manager
(npm/yarn/pnpm) to refresh lockfiles and ensure installation succeeds.
In `@examples/with-memory-rest-api/package.json`:
- Line 7: Update the dependency version for the `@voltagent/core` entry in
package.json: change the version string currently set to "^2.2.2" to the
published release "^2.2.1" so npm can resolve the package; locate the
"@voltagent/core" key in package.json and replace its version value accordingly,
then run npm install to verify the lockfile updates.
In `@examples/with-recipe-generator/package.json`:
- Line 6: The package.json dependency "@voltagent/core": "^2.2.2" references a
non-existent npm version; update that dependency entry to a published version
(for example "@voltagent/core": "1.1.1" or "@voltagent/core": "2.2.0") so the
package can be installed; edit the dependency string in package.json (the
"@voltagent/core" entry) to a valid published version and run install to verify.
In `@examples/with-voltagent-actions/package.json`:
- Line 6: Update the `@voltagent/core` dependency version in package.json from
"^2.2.2" to the published "^2.2.1"; locate the dependency entry
"@voltagent/core" and change its version specifier to "^2.2.1" so the project
uses the published package compatible with the other `@voltagent/`* packages.
| "author": "", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.2.1", | ||
| "@voltagent/core": "^2.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.2 npm package published
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.2.2 has been published to npm. The npm package listing shows @voltagent/core at version 1.1.1 (latest) rather than any 2.x release. [1]
If you meant a different VoltAgent package (several are on 2.x, e.g. @voltagent/server-core), that may be where you saw a 2.x version series. [2]
Sources: [1] [2]
@voltagent/core@2.2.2 is not published on npm and cannot be installed.
The latest published version of @voltagent/core is 1.1.1. Update the dependency to a published version, or verify the intended package name (other @voltagent/* packages may use 2.x versioning).
🤖 Prompt for AI Agents
In `@examples/with-agent-tool/package.json` at line 7, The package.json dependency
"@voltagent/core": "2.2.2" references a non-published version; update the
dependency in package.json to a published release (for example
"@voltagent/core": "1.1.1") or correct the package name if you intended a
different `@voltagent` package using 2.x; ensure the change is made where the
dependency string "@voltagent/core" is defined so installs succeed.
| "@chroma-core/openai": "^0.1.7", | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.2.1", | ||
| "@voltagent/core": "^2.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core 2.2.2 npm package published
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.2.2 has been published to npm. The package pages indexed for @voltagent/core show other versions (e.g., 1.1.1 on npm, and 0.1.46 on Libraries.io), but not 2.2.2. [1], [2]
@voltagent/core@2.2.2 is not published on npm and will fail dependency resolution.
The version 2.2.2 does not exist in the npm registry for this package. This will cause installation failures. Use a published version (e.g., 1.1.1 or 0.1.46) instead.
🤖 Prompt for AI Agents
In `@examples/with-chroma/package.json` at line 9, The dependency entry
"@voltagent/core": "^2.2.2" in package.json references a non-published version
and will break installs; update that dependency to a published version (for
example replace "^2.2.2" with a known-published version like "1.1.1" or
"0.1.46") in the package.json dependencies so npm/yarn can resolve it.
| "name": "voltagent-example-with-mcp-server", | ||
| "dependencies": { | ||
| "@voltagent/core": "^2.2.1", | ||
| "@voltagent/core": "^2.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.2.2 npm published breaking changes
💡 Result:
I couldn’t find any evidence that @voltagent/core@2.2.2 has been published (on GitHub releases, the latest visible 2.2.x release is 2.2.1 on January 25, 2026). (github.com)
So: breaking changes in 2.2.2
- None found, because
2.2.2itself doesn’t appear to exist publicly (at least in the project’s release history). (github.com)
Closest available: what changed in 2.2.1
2.2.1is a patch release and the notes don’t indicate breaking changes; it adds default span inheritance behavior for wrapped agent calls (opt-out supported). (github.com)
If you meant “2.x breaking changes” (more general)
- The official 1.x → 2.x migration guide states no breaking changes in VoltAgent APIs if you only use VoltAgent APIs, but it calls out at least one breaking type change: message helper utilities now use AI SDK
UIMessagetypes. (voltagent.dev)
Citations:
- 1: https://github.com/VoltAgent/voltagent/releases
- 2: https://github.com/VoltAgent/voltagent/releases
- 3: https://github.com/VoltAgent/voltagent/releases
- 4: https://voltagent.dev/docs/getting-started/migration-guide/?utm_source=openai
🏁 Script executed:
# Check the package.json file to see all `@voltagent/`* versions
find . -path "*/examples/with-mcp-server/package.json" -exec cat {} \;Repository: VoltAgent/voltagent
Length of output: 755
@voltagent/core@2.2.2 does not exist on npm. The latest 2.2.x release is @2.2.1 (published January 25, 2026). Update the version to "@voltagent/core": "^2.2.1" to resolve the dependency.
🤖 Prompt for AI Agents
In `@examples/with-mcp-server/package.json` at line 4, The package.json dependency
for `@voltagent/core` is pinned to a non-existent version "^2.2.2"; update the
dependency entry in package.json from "@voltagent/core": "^2.2.2" to
"@voltagent/core": "^2.2.1" so the project uses the latest published 2.2.x
release; then run your package manager (npm/yarn/pnpm) to refresh lockfiles and
ensure installation succeeds.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.2.1", | ||
| "@voltagent/core": "^2.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core version 2.2.2 npm release breaking changes
💡 Result:
There doesn’t appear to be an @voltagent/core@2.2.2 release on the upstream VoltAgent repo as of January 27, 2026. The latest published GitHub release shown is @voltagent/core@2.2.1 (Jan 25, 2026). [1]
So: no documented “breaking changes” exist for 2.2.2, because that release isn’t present in the upstream release list. [1]
If you meant the 2.2.x line generally, the upstream release notes show no breaking-change section for:
2.2.1: patch — auto-inherit VoltAgent spans for wrapped agent calls; opt out viainheritParentSpan: false. [1]2.2.0: minor/patch — tool-specific hooks;onToolEndcan override tool output; addsworkflowState/setWorkflowState; enhancesandForEachwithitemsselector + optionalmap. [1]
Source
- [1] GitHub releases list for VoltAgent/voltagent (shows
@voltagent/core@2.2.1latest and2.2.0, and no2.2.2).
@voltagent/core@2.2.2 does not exist on npm.
The latest published version is @voltagent/core@2.2.1 (Jan 25, 2026). Update line 7 to use "@voltagent/core": "^2.2.1" instead.
🤖 Prompt for AI Agents
In `@examples/with-memory-rest-api/package.json` at line 7, Update the dependency
version for the `@voltagent/core` entry in package.json: change the version string
currently set to "^2.2.2" to the published release "^2.2.1" so npm can resolve
the package; locate the "@voltagent/core" key in package.json and replace its
version value accordingly, then run npm install to verify the lockfile updates.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.2.1", | ||
| "@voltagent/core": "^2.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@voltagent/core npm package version 2.2.2 published
💡 Result:
I couldn’t find any evidence that @voltagent/core version 2.2.2 has been published to npm.
- The npm package page shows the latest published version as
1.1.1(not2.2.2). [1] - The most recent GitHub release I can find for
@voltagent/coreis2.2.0(again, not2.2.2). [2]
Sources: [1] [turn5search0], [2] [turn6search5]
@voltagent/core@2.2.2 does not exist on npm. The latest published version on npm is 1.1.1, and the latest GitHub release is 2.2.0. Update the dependency to a version that is actually published (1.1.1, 2.2.0, or another existing version), as the current reference cannot be installed.
🤖 Prompt for AI Agents
In `@examples/with-recipe-generator/package.json` at line 6, The package.json
dependency "@voltagent/core": "^2.2.2" references a non-existent npm version;
update that dependency entry to a published version (for example
"@voltagent/core": "1.1.1" or "@voltagent/core": "2.2.0") so the package can be
installed; edit the dependency string in package.json (the "@voltagent/core"
entry) to a valid published version and run install to verify.
| "dependencies": { | ||
| "@voltagent/cli": "^0.1.21", | ||
| "@voltagent/core": "^2.2.1", | ||
| "@voltagent/core": "^2.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat examples/with-voltagent-actions/package.jsonRepository: VoltAgent/voltagent
Length of output: 911
🌐 Web query:
@voltagent/core 2.2.2 npm package release notes breaking changes
💡 Result:
I couldn’t find any published @voltagent/core@2.2.2 release (no GitHub release entry for that tag/version). The latest 2.2.x releases shown are @voltagent/core@2.2.1 (Jan 25, 2026) and @voltagent/core@2.2.0 (Jan 23, 2026). [1]
Breaking changes in 2.2.2
- None found (because
2.2.2does not appear to be released/published in the project’s release feed). [1]
Breaking changes in 2.2.x (what is published)
- None indicated. Both
2.2.1(patch) and2.2.0(minor) are listed with feature/fix notes, but no “Breaking Changes” section. [1] - The official 1.x → 2.x migration guide explicitly states “There are no breaking changes in VoltAgent APIs” for the 2.x line (with caveats only if you directly use upstream AI SDK APIs). [2]
Relevant release notes (closest matches)
@voltagent/core@2.2.1: patch change—agent calls auto-inherit VoltAgent spans for wrapped agent calls (unlessinheritParentSpan: false). [1]@voltagent/core@2.2.0: minor + patch changes—tool-specific hooks;onToolEndcan override tool output; addedworkflowState/setWorkflowState; enhancedandForEach; plus other fixes/features. [1]
If you have a link to where you saw 2.2.2 (npm dist-tag, CI output, etc.), share it and I can verify against that specific source.
References: [1] [2]
@voltagent/core@2.2.2 is not published on npm. The latest published version is 2.2.1 (released Jan 25, 2026). Update the dependency to "@voltagent/core": "^2.2.1" to match the available releases. The other @voltagent/* packages (logger@2.0.2, sdk@2.0.2, server-hono@2.0.4) appear compatible with 2.2.1.
🤖 Prompt for AI Agents
In `@examples/with-voltagent-actions/package.json` at line 6, Update the
`@voltagent/core` dependency version in package.json from "^2.2.2" to the
published "^2.2.1"; locate the dependency entry "@voltagent/core" and change its
version specifier to "^2.2.1" so the project uses the published package
compatible with the other `@voltagent/`* packages.
2 participants
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@voltagent/core@2.2.2
Patch Changes
fd17a51Thanks @omeraplak! - feat: ship embedded docs inside @voltagent/core (packages/core/docs) and keep them synced during build/pack for offline, version-matched docs lookupSummary by cubic
Release @voltagent/core 2.2.2, which ships embedded, version-matched docs for offline lookup. Updated all example apps and the lockfile to use the new core version.
Written for commit c524d9a. Summary will update on new commits.
Summary by CodeRabbit
Chores
New Features
✏️ Tip: You can customize this high-level summary in your review settings.