ci(changesets): version packages#996
Conversation
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughThe PR bumps Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 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}
Deploying voltagent with
|
| Latest commit: |
2f1d882
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://01f67516.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In `@examples/with-copilotkit/server/CHANGELOG.md`:
- Around line 3-11: Update the 0.0.4 CHANGELOG.md entry to mention the breaking
changes in `@voltagent/core`@3.0.0 by adding a brief migration note or link to the
migration guide: reference that createToolRouter has been replaced by the new
system tools searchTools and callTool and either summarize the required change
or add a URL/section pointing to the full migration steps; ensure the entry
mentions the package (`@voltagent/core`@3.0.0) and the removed/added symbols
(createToolRouter → searchTools, callTool) so users know what to update when
upgrading.
In `@examples/with-google-vertex-ai/package.json`:
- Line 8: Update the "@voltagent/logger" dependency in package.json from a caret
range to the exact version required by core@^3.0.0 by changing
"@voltagent/logger": "^2.0.2" to "@voltagent/logger": "2.0.2" so the example
matches the peer dependency constraint declared by core; locate the dependency
entry for "@voltagent/logger" in the examples/with-google-vertex-ai package.json
and replace the version specifier accordingly.
In `@packages/ag-ui/package.json`:
- Line 13: The peerDependency entry for "@voltagent/core" in package.json is
inconsistent (currently ">=1.0.0"); update the peerDependencies object to use
the same semver as devDependencies and the rest of the monorepo by changing the
"@voltagent/core" value to "^3.0.0" so the package's peer dependency aligns with
the new major version; locate the "@voltagent/core" key in package.json's
"peerDependencies" and replace its value accordingly.
In `@packages/cli/CHANGELOG.md`:
- Around line 3-9: The changelog header "Updated dependencies []:" is malformed;
open CHANGELOG.md and either remove the empty brackets or replace them with the
appropriate changeset/commit reference so the header reads e.g. "Updated
dependencies:" or "Updated dependencies [<changeset>]:", updating the exact line
containing "Updated dependencies []:" to maintain consistent changelog
formatting.
🧹 Nitpick comments (3)
packages/supabase/CHANGELOG.md (1)
3-9: Consider clarifying the major version bump and its impact.The version 3.0.0 (major bump) is listed with only "Patch Changes," which creates ambiguity about whether this release contains breaking changes for
@voltagent/supabaseusers. While the dependency update to@voltagent/core@3.0.0is documented, it's unclear whether the breaking changes in core (tool routing modifications) affect this package's API surface.Historical major releases (2.0.0, 1.0.0) included "Major Changes" sections with migration guidance. Consider either:
- Adding a "Major Changes" section if users are impacted by the core@3.0.0 breaking changes
- Adding a note explaining this is a version alignment bump with no breaking changes to the supabase package API itself
This would help users understand what to expect when upgrading.
examples/with-live-evals/CHANGELOG.md (1)
3-11: Consider adding a note about the major version bump in dependencies.While the changelog entry is accurate, users may not immediately recognize that the dependency updates from 2.x to 3.0.0 include breaking changes in
@voltagent/core. The previous major version bump (0.0.5) included a detailed migration summary and guide link.Consider adding a brief note referencing the core package's breaking changes or linking to migration documentation, similar to the pattern used in version 0.0.5 (lines 16-31).
📝 Example enhancement
## 0.0.6 ### Patch Changes -- Updated dependencies [[`e0b6693`](https://github.com/VoltAgent/voltagent/commit/e0b6693dcdd18821735607cbd10ac1fa250c552e)]: +- Updated dependencies to VoltAgent 3.0.0. Note: `@voltagent/core`@3.0.0 introduces breaking changes to tool routing APIs. See the [migration guide](https://voltagent.dev/docs/getting-started/migration-guide/) for details. [[`e0b6693`](https://github.com/VoltAgent/voltagent/commit/e0b6693dcdd18821735607cbd10ac1fa250c552e)]: - `@voltagent/core`@3.0.0 - `@voltagent/scorers`@3.0.0 - `@voltagent/server-hono`@3.0.0packages/core/CHANGELOG.md (1)
9-55: Clarify whethersearchTools/callToolare auto-injected or require explicit registration.The migration example no longer lists
tools, which may leave users unsure if they must add these system tools manually. A one-line clarification in the changelog would prevent misconfiguration.✍️ Suggested clarification
- Tool routing now exposes two system tools instead of router tools. The model must search first, then call the selected tool with schema-compliant args. `createToolRouter` and `toolRouting.routers` are removed. + Tool routing now exposes two system tools instead of router tools. The model must search first, then call the selected tool with schema-compliant args. `createToolRouter` and `toolRouting.routers` are removed. (Clarify whether `searchTools` / `callTool` are auto-injected or need to be registered explicitly.)
| ## 0.0.4 | ||
|
|
||
| ### Patch Changes | ||
|
|
||
| - Updated dependencies [[`e0b6693`](https://github.com/VoltAgent/voltagent/commit/e0b6693dcdd18821735607cbd10ac1fa250c552e)]: | ||
| - @voltagent/core@3.0.0 | ||
| - @voltagent/server-hono@3.0.0 | ||
| - @voltagent/cli@0.1.22 | ||
|
|
There was a problem hiding this comment.
Consider adding migration context or reference for the 3.0.0 breaking changes.
The 0.0.4 entry documents dependency updates to @voltagent/core@3.0.0, which introduces breaking changes to tool routing (replacing createToolRouter with searchTools and callTool system tools). Unlike the detailed migration guide provided in the 0.0.3 entry for the 2.x upgrade, this entry lacks context about the breaking changes.
Consider adding a brief note about the breaking changes or a reference to the migration guide to help users upgrading this example.
📝 Suggested enhancement
## 0.0.4
### Patch Changes
- Updated dependencies [[`e0b6693`](https://github.com/VoltAgent/voltagent/commit/e0b6693dcdd18821735607cbd10ac1fa250c552e)]:
- `@voltagent/core`@3.0.0
- `@voltagent/server-hono`@3.0.0
- `@voltagent/cli`@0.1.22
+
+ VoltAgent 3.0.0 introduces breaking changes to tool routing. See the [`@voltagent/core` changelog](../../packages/voltagent/CHANGELOG.md) for migration details.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## 0.0.4 | |
| ### Patch Changes | |
| - Updated dependencies [[`e0b6693`](https://github.com/VoltAgent/voltagent/commit/e0b6693dcdd18821735607cbd10ac1fa250c552e)]: | |
| - @voltagent/core@3.0.0 | |
| - @voltagent/server-hono@3.0.0 | |
| - @voltagent/cli@0.1.22 | |
| ## 0.0.4 | |
| ### Patch Changes | |
| - Updated dependencies [[`e0b6693`](https://github.com/VoltAgent/voltagent/commit/e0b6693dcdd18821735607cbd10ac1fa250c552e)]: | |
| - `@voltagent/core`@3.0.0 | |
| - `@voltagent/server-hono`@3.0.0 | |
| - `@voltagent/cli`@0.1.22 | |
| VoltAgent 3.0.0 introduces breaking changes to tool routing. See the [`@voltagent/core` changelog](../../packages/voltagent/CHANGELOG.md) for migration details. |
🤖 Prompt for AI Agents
In `@examples/with-copilotkit/server/CHANGELOG.md` around lines 3 - 11, Update the
0.0.4 CHANGELOG.md entry to mention the breaking changes in
`@voltagent/core`@3.0.0 by adding a brief migration note or link to the migration
guide: reference that createToolRouter has been replaced by the new system tools
searchTools and callTool and either summarize the required change or add a
URL/section pointing to the full migration steps; ensure the entry mentions the
package (`@voltagent/core`@3.0.0) and the removed/added symbols (createToolRouter
→ searchTools, callTool) so users know what to update when upgrading.
| "@voltagent/cli": "^0.1.22", | ||
| "@voltagent/core": "^3.0.0", | ||
| "@voltagent/libsql": "^3.0.0", | ||
| "@voltagent/logger": "^2.0.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Find all package.json files and filter for the relevant packages
echo "=== Finding `@voltagent/core` package ==="
fd 'package.json' -x cat {} + | grep -B5 -A5 '"name"\s*:\s*"@voltagent/core"' | head -50
echo ""
echo "=== Finding `@voltagent/logger` package ==="
fd 'package.json' -x cat {} + | grep -B5 -A5 '"name"\s*:\s*"@voltagent/logger"' | head -50Repository: VoltAgent/voltagent
Length of output: 9068
🏁 Script executed:
#!/bin/bash
# More targeted search - find package.json files with `@voltagent` packages
echo "=== Searching for `@voltagent` packages ==="
rg '"@voltagent/(core|logger)"' --files-with-matchesRepository: VoltAgent/voltagent
Length of output: 30559
🏁 Script executed:
#!/bin/bash
# List all package.json files in the repo to understand structure
echo "=== All package.json files ==="
fd -H 'package.json$' | sortRepository: VoltAgent/voltagent
Length of output: 4658
🏁 Script executed:
#!/bin/bash
# Read the logger package.json to check peer dependencies
echo "=== packages/logger/package.json ==="
cat packages/logger/package.jsonRepository: VoltAgent/voltagent
Length of output: 1351
🏁 Script executed:
#!/bin/bash
# Read the core package.json to check version and peer dependencies
echo "=== packages/core/package.json ==="
cat packages/core/package.jsonRepository: VoltAgent/voltagent
Length of output: 3628
Use exact version @voltagent/logger@2.0.2 to match core@^3.0.0 peer dependency constraint.
Core v3.0.0 declares "@voltagent/logger": "2.0.2" as an exact peer dependency (not a range), but the example specifies ^2.0.2. If logger publishes patch or minor releases (2.0.3, 2.1.0), they won't be declared compatible by core@3.0.0. Change to "@voltagent/logger": "2.0.2" to match the peer dependency requirement.
🤖 Prompt for AI Agents
In `@examples/with-google-vertex-ai/package.json` at line 8, Update the
"@voltagent/logger" dependency in package.json from a caret range to the exact
version required by core@^3.0.0 by changing "@voltagent/logger": "^2.0.2" to
"@voltagent/logger": "2.0.2" so the example matches the peer dependency
constraint declared by core; locate the dependency entry for "@voltagent/logger"
in the examples/with-google-vertex-ai package.json and replace the version
specifier accordingly.
| ## 0.1.22 | ||
|
|
||
| ### Patch Changes | ||
|
|
||
| - Updated dependencies []: | ||
| - @voltagent/sdk@2.0.3 | ||
| - @voltagent/evals@3.0.0 |
There was a problem hiding this comment.
Fix malformed dependency update header.
The empty brackets in “Updated dependencies []:” look like a missing changeset/commit reference. Please populate or remove the brackets for consistent changelog formatting.
🛠️ Suggested fix
-- Updated dependencies []:
+- Updated dependencies:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## 0.1.22 | |
| ### Patch Changes | |
| - Updated dependencies []: | |
| - @voltagent/sdk@2.0.3 | |
| - @voltagent/evals@3.0.0 | |
| ## 0.1.22 | |
| ### Patch Changes | |
| - Updated dependencies: | |
| - `@voltagent/sdk`@2.0.3 | |
| - `@voltagent/evals`@3.0.0 |
🤖 Prompt for AI Agents
In `@packages/cli/CHANGELOG.md` around lines 3 - 9, The changelog header "Updated
dependencies []:" is malformed; open CHANGELOG.md and either remove the empty
brackets or replace them with the appropriate changeset/commit reference so the
header reads e.g. "Updated dependencies:" or "Updated dependencies
[<changeset>]:", updating the exact line containing "Updated dependencies []:"
to maintain consistent changelog formatting.
47a8fd7 to
e85664b
Compare
e85664b to
2f1d882
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.3.0
Minor Changes
#991
e0b6693Thanks @omeraplak! - feat: replace tool routers withsearchTools+callTooltool routingTool routing now exposes two system tools instead of router tools. The model must search first, then call the selected tool with schema-compliant args.
createToolRouterandtoolRouting.routersare removed.Migration guide
toolRouting.routersBefore:
After:
Summary by CodeRabbit
Release Notes
New Features
Breaking Changes
✏️ Tip: You can customize this high-level summary in your review settings.