ci(changesets): version packages #928
Conversation
📝 WalkthroughWalkthroughRemoved temporary changeset file and bumped Changes
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}
Deploying voltagent with
|
| Latest commit: |
5e50cbd
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c795ff68.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: 1
🤖 Fix all issues with AI agents
In @examples/with-recipe-generator/package.json:
- Line 7: Update the @voltagent/core dependency to ^2.0.8 in the remaining
example package.json files; locate the dependency entry "@voltagent/core" in
each example folder (example-with-live-evals, with-jwt-auth,
voltagent-with-copilotkit-server, assistant-ui-starter, ai-ad-generator) and
change their versions from ^2.0.2 or ^2.0.0 to ^2.0.8 so all examples are
consistent.
🧹 Nitpick comments (1)
examples/with-voltops-resumable-streams/package.json (1)
8-8: Informational: Consider semantic versioning alignment.The PR description indicates this release includes a new feature ("feat: enable andAgent tool usage"), but it's released as a patch version (2.0.7 → 2.0.8). According to semantic versioning conventions, new features typically warrant a minor version bump, while patches are reserved for backward-compatible bug fixes.
If the change is actually fixing or properly enabling existing functionality rather than adding net-new capabilities, the patch version is appropriate. Otherwise, you may want to align the versioning strategy with semver conventions for future releases.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (74)
.changeset/crazy-eagles-float.mdexamples/base/package.jsonexamples/github-repo-analyzer/package.jsonexamples/github-star-stories/package.jsonexamples/next-js-chatbot-starter-template/package.jsonexamples/with-a2a-server/package.jsonexamples/with-agent-tool/package.jsonexamples/with-airtable/package.jsonexamples/with-amazon-bedrock/package.jsonexamples/with-anthropic/package.jsonexamples/with-auth/package.jsonexamples/with-cerbos/package.jsonexamples/with-chroma/package.jsonexamples/with-client-side-tools/package.jsonexamples/with-cloudflare-workers/package.jsonexamples/with-composio-mcp/package.jsonexamples/with-custom-endpoints/package.jsonexamples/with-dynamic-parameters/package.jsonexamples/with-dynamic-prompts/package.jsonexamples/with-google-ai/package.jsonexamples/with-google-drive-mcp/server/package.jsonexamples/with-google-vertex-ai/package.jsonexamples/with-groq-ai/package.jsonexamples/with-guardrails/package.jsonexamples/with-hooks/package.jsonexamples/with-hugging-face-mcp/package.jsonexamples/with-langfuse/package.jsonexamples/with-mcp-elicitation/package.jsonexamples/with-mcp-server/package.jsonexamples/with-mcp/package.jsonexamples/with-memory-rest-api/package.jsonexamples/with-nestjs/package.jsonexamples/with-netlify-functions/package.jsonexamples/with-nextjs-resumable-stream/package.jsonexamples/with-nextjs/package.jsonexamples/with-nuxt/package.jsonexamples/with-offline-evals/package.jsonexamples/with-ollama/package.jsonexamples/with-peaka-mcp/package.jsonexamples/with-pinecone/package.jsonexamples/with-planagents/package.jsonexamples/with-playwright/package.jsonexamples/with-postgres/package.jsonexamples/with-qdrant/package.jsonexamples/with-rag-chatbot/package.jsonexamples/with-recipe-generator/package.jsonexamples/with-research-assistant/package.jsonexamples/with-resumable-streams/package.jsonexamples/with-retrieval/package.jsonexamples/with-slack/package.jsonexamples/with-subagents/package.jsonexamples/with-supabase/package.jsonexamples/with-tavily-search/package.jsonexamples/with-thinking-tool/package.jsonexamples/with-tools/package.jsonexamples/with-turso/package.jsonexamples/with-vector-search/package.jsonexamples/with-vercel-ai/package.jsonexamples/with-viteval/package.jsonexamples/with-voice-elevenlabs/package.jsonexamples/with-voice-openai/package.jsonexamples/with-voice-xsai/package.jsonexamples/with-voltagent-actions/package.jsonexamples/with-voltagent-exporter/package.jsonexamples/with-voltagent-managed-memory/package.jsonexamples/with-voltops-resumable-streams/package.jsonexamples/with-voltops-retrieval/package.jsonexamples/with-whatsapp/package.jsonexamples/with-workflow/package.jsonexamples/with-working-memory/package.jsonexamples/with-youtube-to-blog/package.jsonexamples/with-zapier-mcp/package.jsonpackages/core/CHANGELOG.mdpackages/core/package.json
💤 Files with no reviewable changes (1)
- .changeset/crazy-eagles-float.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-01-07T05:09:23.217Z
Learnt from: CR
Repo: VoltAgent/voltagent PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-07T05:09:23.217Z
Learning: Follow the monorepo structure - changes may impact multiple packages
Applied to files:
examples/with-supabase/package.jsonexamples/with-mcp/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (16)
- GitHub Check: cubic · AI code reviewer
- GitHub Check: Test core
- GitHub Check: Test server-core
- GitHub Check: Test libsql
- GitHub Check: Test cli
- GitHub Check: Test supabase
- GitHub Check: Test internal
- GitHub Check: Test docs-mcp
- GitHub Check: Test postgres
- GitHub Check: Test create-voltagent-app
- GitHub Check: Test logger
- GitHub Check: Test voice
- GitHub Check: Build (Node 22)
- GitHub Check: Build (Node 24)
- GitHub Check: Lint (Node 20)
- GitHub Check: Build (Node 20)
🔇 Additional comments (68)
packages/core/package.json (1)
4-4: Verify semver classification: should this be a minor version bump instead of a patch?The version bump from 2.0.7 to 2.0.8 is technically valid. However, the changeset description uses the "feat:" prefix ("feat: enable andAgent tool usage..."), which typically indicates a new feature addition. According to semantic versioning conventions, new features should increment the minor version (e.g., 2.1.0) rather than the patch version (2.0.8), which is reserved for bug fixes and backward-compatible internal improvements.
If "enable andAgent tool usage" means fixing existing broken functionality, a patch is appropriate. If it adds new API surface or capabilities, consider whether this should have been a minor version bump.
Since Changesets uses the type specified in the changeset file, please verify that the original changeset in PR #927 used the correct type ("patch" vs "minor") based on the nature of the changes.
packages/core/CHANGELOG.md (1)
3-35: Changelog entry and example look consistent and accurateThe 2.0.8 note and the TypeScript example are aligned with existing changelog style and prior
andAgentusage patterns; nothing to fix here.examples/with-slack/package.json (1)
7-7: LGTM! Standard version bump.The patch version update to @voltagent/core ^2.0.8 is correct and aligns with the changeset release process.
examples/with-tools/package.json (1)
7-7: LGTM! Version bump is consistent.The dependency update to @voltagent/core ^2.0.8 is correct and matches the release version.
examples/with-custom-endpoints/package.json (1)
7-7: LGTM! Dependency update is correct.The version bump to @voltagent/core ^2.0.8 aligns with the changeset release.
examples/with-workflow/package.json (1)
7-7: LGTM! Version update is correct.The patch bump to @voltagent/core ^2.0.8 is consistent with the release process.
examples/with-whatsapp/package.json (1)
8-8: LGTM! Dependency version is correct.The update to @voltagent/core ^2.0.8 is consistent with the changeset release.
examples/with-voice-elevenlabs/package.json (1)
7-7: Dependency version bump looks good.The update to
@voltagent/core^2.0.8 is properly formatted and consistent with the coordinated release. The caret range ensures compatibility with future patch versions.examples/with-youtube-to-blog/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update from ^2.0.7 to ^2.0.8 is consistent with the automated changesets release for the patch version that enables andAgent tool usage.
examples/with-retrieval/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update from ^2.0.7 to ^2.0.8 is consistent with the automated changesets release.
examples/with-guardrails/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update from ^2.0.7 to ^2.0.8 is consistent with the automated changesets release.
examples/with-groq-ai/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update from ^2.0.7 to ^2.0.8 is consistent with the automated changesets release.
examples/with-nuxt/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update from ^2.0.7 to ^2.0.8 is consistent with the automated changesets release.
examples/with-peaka-mcp/package.json (1)
7-7: LGTM! Dependency version bump is consistent with the core package update.The patch version update to
@voltagent/core@^2.0.8correctly maintains alignment with the core package release.examples/with-viteval/package.json (1)
7-7: LGTM! Version bump maintains monorepo consistency.examples/with-vector-search/package.json (1)
7-7: LGTM! Dependency update is consistent.examples/with-netlify-functions/package.json (1)
7-7: LGTM! Version bump aligns with the release.examples/with-hooks/package.json (1)
7-7: LGTM! Dependency version update is correct.examples/with-nextjs/package.json (1)
10-10: LGTM! Dependency version bump is correct.The patch version bump from ^2.0.7 to ^2.0.8 is consistent with the Changesets release workflow and aligns with the core package update.
examples/with-voice-openai/package.json (1)
7-7: LGTM! Version bump is correct.examples/with-a2a-server/package.json (1)
6-6: LGTM! Version bump is correct.examples/with-airtable/package.json (1)
7-7: LGTM! Version bump is correct.examples/with-langfuse/package.json (1)
7-7: LGTM! Version bump is correct.examples/github-repo-analyzer/package.json (1)
7-7: LGTM! Consistent patch version bump.The dependency update from
^2.0.7to^2.0.8is consistent with the changeset release and aligns with the new andAgent tool usage feature.examples/with-hugging-face-mcp/package.json (1)
7-7: LGTM! Version bump applied correctly.The
@voltagent/coredependency update is consistent with the broader release across all example projects.examples/with-voltops-retrieval/package.json (1)
7-7: LGTM! Dependency updated correctly.The version bump to
^2.0.8is consistent with the changeset release pattern across all examples.examples/with-qdrant/package.json (1)
8-8: LGTM! Core dependency updated.The patch version bump to
^2.0.8is consistent with the automated release process.examples/with-research-assistant/package.json (1)
7-7: LGTM! Version bump completed.The dependency update to
^2.0.8correctly reflects the changeset release for the core package.examples/with-mcp-server/package.json (1)
5-5: LGTM - Routine patch version bump.The dependency update to
@voltagent/core@^2.0.8is consistent with the changeset release for the new andAgent tool usage feature.examples/with-nextjs-resumable-stream/package.json (1)
21-21: LGTM - Routine patch version bump.The dependency update to
@voltagent/core@^2.0.8is consistent with the changeset release for the new andAgent tool usage feature.examples/with-voltagent-exporter/package.json (1)
7-7: LGTM - Routine patch version bump.The dependency update to
@voltagent/core@^2.0.8is consistent with the changeset release for the new andAgent tool usage feature.examples/base/package.json (1)
7-7: LGTM - Routine patch version bump.The dependency update to
@voltagent/core@^2.0.8is consistent with the changeset release for the new andAgent tool usage feature.examples/with-zapier-mcp/package.json (1)
9-9: LGTM - Routine patch version bump.The dependency update to
@voltagent/core@~2.0.8is consistent with the changeset release for the new andAgent tool usage feature. The tilde range restricts updates to patch-level changes only.examples/with-cloudflare-workers/package.json (1)
7-7: Version bump looks correct.The dependency update to
^2.0.8is consistent with the patch release and appropriate for this example project.examples/with-dynamic-prompts/package.json (1)
7-7: Version bump looks correct.The dependency update to
^2.0.8aligns with the coordinated release across example projects.examples/with-memory-rest-api/package.json (1)
8-8: Version bump looks correct.The dependency update to
^2.0.8is consistent with the patch release.examples/with-google-vertex-ai/package.json (1)
7-7: Version bump looks correct.The dependency update to
^2.0.8is appropriate for this example project.examples/with-google-ai/package.json (1)
7-7: LGTM! Dependency version bump looks correct.The patch version bump to
@voltagent/core@^2.0.8is consistent with the release workflow and will enable the new andAgent tool usage features.examples/github-star-stories/package.json (1)
7-7: LGTM! Dependency version bump looks correct.The version update aligns with the automated release process and maintains consistency across example projects.
examples/with-google-drive-mcp/server/package.json (1)
9-9: LGTM! Dependency version bump looks correct.The patch version bump is properly applied and consistent with the release workflow.
examples/with-voice-xsai/package.json (1)
7-7: LGTM! Dependency version bump looks correct.The version update is properly applied and maintains dependency consistency across the repository.
examples/with-auth/package.json (1)
7-7: LGTM! Dependency version bump looks correct.The version update completes the consistent upgrade across example projects. This automated release PR is ready for merge.
examples/with-nestjs/package.json (1)
10-10: LGTM! Dependency version bump looks good.The @voltagent/core dependency update from ^2.0.7 to ^2.0.8 is consistent with the patch release described in the PR objectives. The caret range is appropriate for this patch version update.
examples/with-mcp-elicitation/package.json (1)
8-8: LGTM! Version bump is consistent.The @voltagent/core dependency update to ^2.0.8 aligns with the patch release for the andAgent tool usage feature.
examples/with-thinking-tool/package.json (1)
7-7: LGTM! Dependency update is correct.The @voltagent/core version bump to ^2.0.8 is part of the coordinated patch release across all example projects.
examples/with-rag-chatbot/package.json (1)
8-8: LGTM! Version synchronized correctly.The @voltagent/core dependency has been properly updated to ^2.0.8 in sync with the changesets release workflow.
examples/with-subagents/package.json (1)
7-7: LGTM! Dependency version bump is consistent.The @voltagent/core update to ^2.0.8 completes the coordinated patch release across all example projects in this changesets PR.
examples/with-client-side-tools/package.json (1)
8-8: LGTM! Version bump is consistent with the changeset release.The dependency update from ^2.0.7 to ^2.0.8 aligns with the patch release for @voltagent/core that enables andAgent tool usage.
examples/with-ollama/package.json (1)
5-5: LGTM! Dependency version updated correctly.The @voltagent/core version bump to ^2.0.8 is consistent with the automated changeset release.
examples/with-playwright/package.json (1)
11-11: LGTM! Version bump applied correctly.The patch version update to ^2.0.8 is consistent with the changeset release workflow.
examples/with-tavily-search/package.json (1)
7-7: LGTM! Dependency update is correct.The @voltagent/core version bump to ^2.0.8 follows the standard changeset release pattern.
examples/with-voltagent-managed-memory/package.json (1)
6-6: LGTM! Version bump is consistent.The dependency update to ^2.0.8 aligns with the automated changeset release for @voltagent/core.
examples/with-cerbos/package.json (1)
9-9: LGTM! Dependency version bump is correct.The @voltagent/core package version bump from ^2.0.7 to ^2.0.8 aligns with the core package release for this PR. The caret range is appropriate for example projects.
examples/with-dynamic-parameters/package.json (1)
7-7: LGTM! Version bump is consistent.examples/with-amazon-bedrock/package.json (1)
8-8: LGTM! Version bump is consistent.examples/with-vercel-ai/package.json (1)
7-7: LGTM! Version bump is consistent.examples/with-postgres/package.json (1)
8-8: LGTM! Version bump is consistent.examples/with-pinecone/package.json (1)
8-8: LGTM! Version bump looks correct.The dependency update from
^2.0.7to^2.0.8is consistent with the patch release described in the PR objectives.examples/with-chroma/package.json (1)
10-10: LGTM! Dependency update is correct.The version bump aligns with the monorepo-wide update to
@voltagent/core2.0.8.examples/with-planagents/package.json (1)
9-9: LGTM! Version update is consistent.The dependency bump to
^2.0.8matches the coordinated release across all example projects.examples/next-js-chatbot-starter-template/package.json (1)
23-23: LGTM! Dependency version updated correctly.The patch version bump to
^2.0.8is part of the coordinated monorepo release.examples/with-supabase/package.json (1)
8-8: LGTM! Coordinated monorepo update looks good.The version bump to
^2.0.8is consistent across all example packages. The patch release should maintain backward compatibility.Based on learnings, this follows the monorepo structure with coordinated changes across multiple packages.
examples/with-mcp/package.json (1)
8-8: LGTM: Version bump aligns with core package release.The dependency update to
@voltagent/core@^2.0.8is consistent with the core package's patch release for andAgent tool usage improvements.examples/with-composio-mcp/package.json (1)
8-8: LGTM: Dependency version update is correct.The
@voltagent/coreversion bump to^2.0.8is consistent with the monorepo-wide dependency update.examples/with-working-memory/package.json (1)
7-7: LGTM: Version bump is consistent with the release.The dependency update to
@voltagent/core@^2.0.8correctly reflects the new patch release.examples/with-resumable-streams/package.json (1)
8-8: LGTM: Dependency version correctly updated.The
@voltagent/coreversion bump to^2.0.8is appropriate for this patch release.examples/with-agent-tool/package.json (1)
8-8: LGTM: Version update aligns with new andAgent feature.The dependency update to
@voltagent/core@^2.0.8is correct and particularly relevant for this example, which demonstrates agent-as-tool patterns enhanced by the new release.examples/with-voltagent-actions/package.json (1)
7-7: LGTM! Dependency version bump is correct.The update to
@voltagent/core@^2.0.8is appropriate and follows standard package.json conventions. The caret versioning allows for compatible updates as expected.
| "@ai-sdk/openai": "^3.0.0", | ||
| "@voltagent/cli": "^0.1.20", | ||
| "@voltagent/core": "^2.0.7", | ||
| "@voltagent/core": "^2.0.8", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify all example package.json files have been updated to @voltagent/core@^2.0.8
# Find all package.json files in examples directory
echo "=== Checking @voltagent/core versions in example package.json files ==="
fd -t f '^package\.json$' examples/ --exec jq -r 'select(.dependencies."@voltagent/core" != null) | "\(.name): \(.dependencies."@voltagent/core")"'
# Check for any remaining references to 2.0.7
echo ""
echo "=== Checking for any remaining 2.0.7 references in example package.json files ==="
rg '"@voltagent/core":\s*"\^2\.0\.7"' examples/ -g 'package.json'Repository: VoltAgent/voltagent
Length of output: 3415
Update remaining examples to use @voltagent/core@^2.0.8 for consistency.
The version bump to ^2.0.8 is mostly complete, but 5 examples still have older versions and should be updated:
- example-with-live-evals: ^2.0.2
- with-jwt-auth: ^2.0.2
- voltagent-with-copilotkit-server: ^2.0.2
- assistant-ui-starter: ^2.0.2
- ai-ad-generator: ^2.0.0
🤖 Prompt for AI Agents
In @examples/with-recipe-generator/package.json at line 7, Update the
@voltagent/core dependency to ^2.0.8 in the remaining example package.json
files; locate the dependency entry "@voltagent/core" in each example folder
(example-with-live-evals, with-jwt-auth, voltagent-with-copilotkit-server,
assistant-ui-starter, ai-ad-generator) and change their versions from ^2.0.2 or
^2.0.0 to ^2.0.8 so all examples are consistent.
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/[email protected]
Patch Changes
#927
2712078Thanks @omeraplak! - feat: enableandAgenttool usage by switching togenerateTextwithOutput.objectwhile keeping structured outputExample:
Summary by cubic
Publish @voltagent/core 2.0.8 and update all example apps to use it. This patch enables tool usage in andAgent by switching to generateText with Output.object while keeping structured output.
New Features
Dependencies
Written for commit 5e50cbd. Summary will update on new commits.
Summary by CodeRabbit
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.