ci(changesets): version packages #953
Conversation
📝 WalkthroughWalkthroughThis PR version-bumps the core package to 2.1.0 and cascades the dependency update across all 69 example projects. A changelog entry documents new eval feedback helper functionality for onResult callbacks and VoltOps feedback client support. A temporary changeset file is removed. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 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}
There was a problem hiding this comment.
1 issue found across 76 files
Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="packages/core/CHANGELOG.md">
<violation number="1" location="packages/core/CHANGELOG.md:7">
P3: The release note still contains the unresolved template placeholder `@${payload.input}`, which renders a broken GitHub attribution link. Replace it with a real username or remove the placeholder so the changelog doesn’t ship invalid markdown.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
|
|
||
| ### Minor Changes | ||
|
|
||
| - [#952](https://github.com/VoltAgent/voltagent/pull/952) [`79d636b`](https://github.com/VoltAgent/voltagent/commit/79d636bc93e9f6733d95c65e2258f14d33932d30) Thanks [@${payload.input}](https://github.com/${payload.input})! - feat: add eval feedback helper for onResult callbacks and VoltOps feedback client support |
There was a problem hiding this comment.
P3: The release note still contains the unresolved template placeholder @${payload.input}, which renders a broken GitHub attribution link. Replace it with a real username or remove the placeholder so the changelog doesn’t ship invalid markdown.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/core/CHANGELOG.md, line 7:
<comment>The release note still contains the unresolved template placeholder `@${payload.input}`, which renders a broken GitHub attribution link. Replace it with a real username or remove the placeholder so the changelog doesn’t ship invalid markdown.</comment>
<file context>
@@ -1,5 +1,113 @@
+
+### Minor Changes
+
+- [#952](https://github.com/VoltAgent/voltagent/pull/952) [`79d636b`](https://github.com/VoltAgent/voltagent/commit/79d636bc93e9f6733d95c65e2258f14d33932d30) Thanks [@${payload.input}](https://github.com/${payload.input})! - feat: add eval feedback helper for onResult callbacks and VoltOps feedback client support
+
+ Example usage:
</file context>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@examples/github-repo-analyzer/package.json`:
- Line 7: The package.json dependency "@voltagent/core" is pinned to a
non-published version "2.1.0"; change it to a published 2.x release (e.g.,
"2.0.13") to match the other `@voltagent` packages or verify and replace with the
correct published version; update the "@voltagent/core" version string in
package.json accordingly and run a quick npm install to confirm the dependency
resolves.
In `@packages/core/CHANGELOG.md`:
- Line 7: The changelog entry contains an unresolved template `${payload.input}`
in the contributor link (the line with PR `#952` and commit `79d636b`); update
that line in CHANGELOG.md to replace `${payload.input}` with the actual GitHub
handle used in the PR (or remove the "Thanks ..." portion entirely if the handle
is not known), ensuring the displayed markdown link to the contributor becomes a
valid URL and the text no longer contains the literal template.
♻️ Duplicate comments (8)
examples/with-google-vertex-ai/package.json (1)
7-7: Same@voltagent/corebump as other examples.
Line 7 mirrors the repo-wide update; no extra concerns beyond confirming 2.1.0 is published and compatible.examples/with-planagents/package.json (1)
9-9: Same@voltagent/corebump as other examples.
Line 9 follows the repo-wide update; no extra concerns beyond verifying 2.1.0 availability and compatibility.examples/with-turso/package.json (1)
8-8: Same@voltagent/corebump as other examples.
Line 8 matches the repo-wide update; no extra concerns beyond confirming 2.1.0 availability and compatibility.examples/with-ollama/package.json (1)
5-5: Same@voltagent/corebump as other examples.
Line 5 aligns with the repo-wide update; no extra concerns beyond verifying 2.1.0 availability and compatibility.examples/with-supabase/package.json (1)
8-8: Same@voltagent/corebump as prior example.examples/with-rag-chatbot/package.json (1)
8-8: Same@voltagent/corebump as prior example.examples/with-resumable-streams/package.json (1)
8-8: Same@voltagent/corebump as prior example.examples/with-anthropic/package.json (1)
7-7: Same@voltagent/corebump as prior example.
📜 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 (75)
.changeset/native-feedback-helper.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-feedback/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/native-feedback-helper.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-01-07T05:09:23.227Z
Learnt from: CR
Repo: VoltAgent/voltagent PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-07T05:09:23.227Z
Learning: Follow the monorepo structure - changes may impact multiple packages
Applied to files:
examples/with-airtable/package.jsonexamples/with-composio-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). (18)
- GitHub Check: cubic · AI code reviewer
- GitHub Check: Test internal
- GitHub Check: Test supabase
- GitHub Check: Test logger
- GitHub Check: Test libsql
- GitHub Check: Test voice
- GitHub Check: Test core
- GitHub Check: Test server-core
- GitHub Check: Test create-voltagent-app
- GitHub Check: Test postgres
- GitHub Check: Test cli
- GitHub Check: Test docs-mcp
- GitHub Check: Lint (Node 22)
- GitHub Check: Lint (Node 24)
- GitHub Check: Build (Node 24)
- GitHub Check: Build (Node 20)
- GitHub Check: Build (Node 22)
- GitHub Check: Lint (Node 20)
🔇 Additional comments (64)
examples/with-netlify-functions/package.json (1)
7-7: LGTM!Routine minor version bump for
@voltagent/core(^2.0.14 → ^2.1.0) as part of the coordinated Changesets release. The caret range specifier is appropriate for accepting compatible updates.examples/with-playwright/package.json (1)
11-11: LGTM!The dependency version bump for
@voltagent/corefrom^2.0.14to^2.1.0is consistent with the Changesets release. This minor version update introduces the new eval feedback helper functionality while maintaining backward compatibility.examples/with-memory-rest-api/package.json (1)
8-8: Verify@voltagent/core2.1.0 compatibility for this example.Since this is a runtime dependency bump, please confirm the example still runs end-to-end and that peer/version expectations for related
@voltagent/* packages remain compatible.examples/with-slack/package.json (1)
7-7: LGTM! Standard dependency version bump.The minor version bump from ^2.0.14 to ^2.1.0 is correct and follows semver. This aligns with the new eval feedback features being released in
@voltagent/core@2.1.0.examples/with-postgres/package.json (1)
8-8: Version bump looks consistent.Aligns this example with the new core release.
examples/with-langfuse/package.json (1)
7-7: Version bump looks consistent.Keeps this example aligned with core 2.1.0.
packages/core/package.json (1)
4-4: Release version bump is consistent.Looks good for the 2.1.0 release.
examples/with-thinking-tool/package.json (1)
7-7: Version bump looks consistent.Matches the updated core release.
examples/with-retrieval/package.json (1)
7-7: Version bump looks consistent.Keeps this example aligned with core 2.1.0.
examples/with-voltops-resumable-streams/package.json (1)
8-8: LGTM!Version bump to
^2.1.0is consistent with the core package release and aligns with the Changesets release process.examples/with-voice-elevenlabs/package.json (1)
7-7: LGTM!Version bump aligns with the coordinated 2.1.0 release across example packages.
examples/with-tools/package.json (1)
7-7: LGTM!Version bump is consistent with the monorepo-wide core package release.
examples/with-pinecone/package.json (1)
8-8: LGTM!Version bump aligns with the 2.1.0 core release introducing eval feedback helper functionality.
examples/with-nextjs-resumable-stream/package.json (1)
21-21: LGTM!Version bump is consistent with the Changesets release for
@voltagent/[email protected].examples/with-zapier-mcp/package.json (1)
9-9: Version bump aligns with core release.Looks consistent with the repo-wide update to 2.1.0.
examples/with-research-assistant/package.json (1)
7-7: Dependency update looks good.No concerns with the 2.1.0 alignment here.
examples/with-whatsapp/package.json (1)
8-8: Version alignment is fine.This matches the core 2.1.0 rollout.
examples/with-voltops-retrieval/package.json (1)
7-7: Bump looks consistent.No concerns with the 2.1.0 update.
examples/with-recipe-generator/package.json (1)
7-7: LGTM for the version bump.Matches the core release version.
examples/with-hooks/package.json (1)
7-7: @voltagent/core 2.1.0 is published and widely used across examples.Version 2.1.0 is documented in CHANGELOG.md and already adopted consistently across 10+ examples in the repository (base, github-repo-analyzer, github-star-stories, next-js-chatbot-starter-template, with-a2a-server, with-agent-tool, with-airtable, with-amazon-bedrock, with-anthropic, and others), indicating stability and compatibility. The change aligns with the project's dependency versions.
examples/with-nestjs/package.json (1)
10-10: Dependency bump looks good.
Simple version update; no issues in this file.examples/with-subagents/package.json (1)
7-7: Dependency bump looks good.
No local concerns with this version update.examples/with-vercel-ai/package.json (1)
7-7: Dependency bump looks good.
No additional changes needed in this file.examples/with-groq-ai/package.json (1)
7-7: Dependency bump looks good.
This update is fine as-is.examples/with-voltagent-managed-memory/package.json (1)
6-6: Dependency bump looks good.
No issues identified in this file.examples/with-viteval/package.json (1)
7-7: LGTM!The dependency bump to
@voltagent/core@^2.1.0is correct and aligns with the release. This example is particularly well-suited to leverage the new eval feedback helper functionality introduced in 2.1.0.examples/with-tavily-search/package.json (1)
7-7: LGTM!Dependency version bump to
@voltagent/core@^2.1.0is consistent with the release.examples/with-voltagent-exporter/package.json (1)
7-7: LGTM!Dependency version bump to
@voltagent/core@^2.1.0is consistent with the release.examples/with-nextjs/package.json (1)
10-10: LGTM!Dependency version bump to
@voltagent/core@^2.1.0is consistent with the release.examples/with-voice-openai/package.json (1)
7-7: LGTM!Dependency version bump to
@voltagent/core@^2.1.0is consistent with the release.examples/with-hugging-face-mcp/package.json (1)
7-7: LGTM for the version bump; please verify compatibility.Please confirm this example still installs/runs cleanly with
@voltagent/core^2.1.0 (no peer/version conflicts).examples/with-cerbos/package.json (1)
9-9: LGTM for the version bump; please verify compatibility.Please confirm this example still installs/runs cleanly with
@voltagent/core^2.1.0 (no peer/version conflicts).examples/with-dynamic-parameters/package.json (1)
7-7: LGTM for the version bump; please verify compatibility.Please confirm this example still installs/runs cleanly with
@voltagent/core^2.1.0 (no peer/version conflicts).examples/next-js-chatbot-starter-template/package.json (1)
23-23: LGTM for the version bump; please verify compatibility.Please confirm this example still installs/runs cleanly with
@voltagent/core^2.1.0 (no peer/version conflicts).examples/with-google-ai/package.json (1)
7-7: LGTM for the version bump; please verify compatibility.Please confirm this example still installs/runs cleanly with
@voltagent/core^2.1.0 (no peer/version conflicts).examples/with-custom-endpoints/package.json (1)
7-7: LGTM!Version bump to
@voltagent/core@^2.1.0aligns with the core package release containing the new eval feedback helper and VoltOps feedback client support.examples/with-chroma/package.json (1)
10-10: LGTM!Version bump to
@voltagent/core@^2.1.0is consistent with the core package release.examples/with-amazon-bedrock/package.json (1)
8-8: LGTM!Version bump to
@voltagent/core@^2.1.0is consistent with the core package release.examples/with-cloudflare-workers/package.json (1)
7-7: LGTM!Version bump to
@voltagent/core@^2.1.0is consistent with the core package release.examples/github-star-stories/package.json (1)
7-7: LGTM!Version bump to
@voltagent/core@^2.1.0is consistent with the core package release.examples/with-composio-mcp/package.json (1)
8-8: LGTM!Dependency version bump to
@voltagent/core^2.1.0 aligns with the core package release.examples/with-mcp-elicitation/package.json (1)
8-8: LGTM!Standard dependency bump consistent with the monorepo-wide core release.
examples/with-agent-tool/package.json (1)
8-8: LGTM!Core dependency updated to ^2.1.0 as part of the release.
examples/with-peaka-mcp/package.json (1)
7-7: LGTM!Core dependency updated to ^2.1.0 as expected.
examples/with-client-side-tools/package.json (1)
8-8: LGTM!Core dependency version bump aligns with the 2.1.0 release. Based on learnings, this follows the expected monorepo pattern where changes cascade across multiple packages.
examples/with-qdrant/package.json (1)
8-8: Version bump looks good; please verify example still runs.Line 8 updates the core dependency; please confirm the example still builds and runs with
@voltagent/core2.1.0 (e.g., install + build/run).examples/with-voice-xsai/package.json (1)
7-7: Version bump looks good; please verify example still runs.Line 7 updates the core dependency; please confirm the example still builds and runs with
@voltagent/core2.1.0.examples/with-feedback/package.json (1)
7-7: Version bump looks good; please verify example still runs.Line 7 updates the core dependency; please confirm the example still builds and runs with
@voltagent/core2.1.0.examples/with-offline-evals/package.json (1)
7-7: Version bump looks good; please verify example still runs.Line 7 updates the core dependency; please confirm the example still builds and runs with
@voltagent/core2.1.0.examples/with-mcp/package.json (1)
8-8: Version bump looks good; please verify example still runs.Line 8 updates the core dependency; please confirm the example still builds and runs with
@voltagent/core2.1.0.examples/with-mcp-server/package.json (1)
5-5: Dependency bump looks good.Straightforward version alignment for the example.
examples/with-working-memory/package.json (1)
7-7: Dependency bump looks good.Consistent with the repo-wide upgrade.
examples/with-airtable/package.json (1)
7-7: Dependency bump looks good.No concerns for this example package.
examples/base/package.json (1)
7-7: Dependency bump looks good.Aligned with the rest of the examples.
examples/with-auth/package.json (1)
7-7: Dependency bump looks good.Simple version alignment; nothing else to flag.
examples/with-a2a-server/package.json (1)
6-6: No changes needed. Version 2.1.0 is a documented minor release (eval feedback helper addition) with no breaking changes. All examples in the repository consistently use this version, and this change aligns with the existing upgrade pattern across the monorepo.examples/with-guardrails/package.json (1)
7-7: LGTM—please confirm@voltagent/core@2.1.0 availability/compatibility.Same verification applies here: ensure the 2.1.0 release is published and peer deps remain compatible.
examples/with-dynamic-prompts/package.json (1)
7-7: LGTM—please verify@voltagent/core@2.1.0 is published and compatible.Ensure the 2.1.0 release is available on npm and its peer deps don’t conflict with this example.
examples/with-nuxt/package.json (1)
7-7: LGTM—please verify@voltagent/core@2.1.0 is published and fits the Nuxt example.Confirm 2.1.0 exists on npm and peer dependencies remain compatible here.
examples/with-workflow/package.json (1)
7-7: LGTM—please verify@voltagent/core@2.1.0 availability/compatibility.Ensure the 2.1.0 release is published and peer deps align with this example’s stack.
examples/with-google-drive-mcp/server/package.json (1)
9-9: LGTM!The
@voltagent/coreversion bump to^2.1.0aligns with the core package release. The caret range is appropriate for receiving compatible minor and patch updates.examples/with-youtube-to-blog/package.json (1)
7-7: LGTM!Version bump to
^2.1.0is consistent with the core package release.examples/with-voltagent-actions/package.json (1)
7-7: LGTM!Version bump to
^2.1.0is consistent with the core package release.examples/with-vector-search/package.json (1)
7-7: LGTM! Clean dependency update.The minor version bump to
@voltagent/core@^2.1.0is appropriate for the new eval feedback features being added. The changesets workflow ensures this update is consistent with the core package release.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
| "@ai-sdk/openai": "^3.0.0", | ||
| "@octokit/rest": "^21.0.0", | ||
| "@voltagent/core": "^2.0.14", | ||
| "@voltagent/core": "^2.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify `@voltagent/core`@2.1.0 is published and inspect peers
curl -s https://registry.npmjs.org/@voltagent%2fcore > /tmp/voltagent-core.json
python3 <<'PY'
import json
try:
data = json.load(open("/tmp/voltagent-core.json"))
print("latest:", data.get("dist-tags", {}).get("latest"))
print("has 2.1.0:", "2.1.0" in data.get("versions", {}))
if "2.1.0" in data.get("versions", {}):
pkg_info = data["versions"]["2.1.0"]
print("peerDependencies:", pkg_info.get("peerDependencies", "none"))
print("version found successfully")
else:
print("2.1.0 not found in versions")
except Exception as e:
print(f"Error: {e}")
PYRepository: VoltAgent/voltagent
Length of output: 149
🏁 Script executed:
# Check if there's a lock file with version info
find . -name "package-lock.json" -o -name "yarn.lock" -o -name "pnpm-lock.yaml" | head -10Repository: VoltAgent/voltagent
Length of output: 155
🌐 Web query:
@voltagent/core version 2.1.0 npm package release
💡 Result:
I couldn't find a published npm package for @voltagent/core version 2.1.0. The VoltAgent project is on 2.x releases, and the latest 2.0.x release listed in release feeds is 2.0.13. [1][2]
Sources:
- Release feed listing
@voltagent/coreversions (shows 2.0.13 as a recent 2.x release). [1] - Official VoltAgent site / docs (VoltAgent 2.x migration and package info). [2]
If you want, I can check the npm registry or the GitHub releases/tags again for a specific publish date — which would let me confirm whether 2.1.0 was published after these sources.
🏁 Script executed:
# Check what version is in the example's lock file
if [ -f "./examples/github-repo-analyzer/pnpm-lock.yaml" ]; then
grep -A 2 "@voltagent/core" ./examples/github-repo-analyzer/pnpm-lock.yaml | head -20
elif [ -f "./examples/github-repo-analyzer/package-lock.json" ]; then
cat ./examples/github-repo-analyzer/package-lock.json | grep -A 3 "voltagent/core" | head -20
fi
# Also check the package.json to confirm the requested version
cat ./examples/github-repo-analyzer/package.json | grep -A 1 -B 1 "voltagent"Repository: VoltAgent/voltagent
Length of output: 552
@voltagent/[email protected] does not exist on npm—revert to 2.0.13 or later verified release.
The version 2.1.0 has not been published to the npm registry. Web search shows the latest 2.x release is 2.0.13. The other @voltagent packages in this file are pinned to 2.0.x versions (2.0.2, 2.0.3). Update this to an existing version or confirm 2.1.0 is published before merging.
🤖 Prompt for AI Agents
In `@examples/github-repo-analyzer/package.json` at line 7, The package.json
dependency "@voltagent/core" is pinned to a non-published version "2.1.0";
change it to a published 2.x release (e.g., "2.0.13") to match the other
`@voltagent` packages or verify and replace with the correct published version;
update the "@voltagent/core" version string in package.json accordingly and run
a quick npm install to confirm the dependency resolves.
|
|
||
| ### Minor Changes | ||
|
|
||
| - [#952](https://github.com/VoltAgent/voltagent/pull/952) [`79d636b`](https://github.com/VoltAgent/voltagent/commit/79d636bc93e9f6733d95c65e2258f14d33932d30) Thanks [@${payload.input}](https://github.com/${payload.input})! - feat: add eval feedback helper for onResult callbacks and VoltOps feedback client support |
There was a problem hiding this comment.
Replace the templated GitHub handle before release.
The changelog still contains ${payload.input} which will render literally in published docs. Please replace with the actual GitHub handle or omit the thanks line if unknown.
🤖 Prompt for AI Agents
In `@packages/core/CHANGELOG.md` at line 7, The changelog entry contains an
unresolved template `${payload.input}` in the contributor link (the line with PR
`#952` and commit `79d636b`); update that line in CHANGELOG.md to replace
`${payload.input}` with the actual GitHub handle used in the PR (or remove the
"Thanks ..." portion entirely if the handle is not known), ensuring the
displayed markdown link to the contributor becomes a valid URL and the text no
longer contains the literal template.
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]
Minor Changes
#952
79d636bThanks @${payload.input}! - feat: add eval feedback helper for onResult callbacks and VoltOps feedback client supportExample usage:
LLM judge example:
Summary by cubic
Release @voltagent/core 2.1.0 with an eval feedback helper for onResult callbacks and native VoltOps feedback client support. Example apps are updated to use ^2.1.0.
Written for commit 499b24c. Summary will update on new commits.
Summary by CodeRabbit
Release Notes
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.