Conversation
Deploying voltagent with
|
| Latest commit: |
4f2eb46
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a9c5f01a.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (84)
💤 Files with no reviewable changes (1)
✅ Files skipped from review due to trivial changes (83)
📝 WalkthroughWalkthroughRemoved a changeset file and published 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
eafac43 to
15e348a
Compare
15e348a to
4f2eb46
Compare
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.6.11
Patch Changes
#1168
2075bd9Thanks @omeraplak! - fix: emit LLM judge token and provider cost telemetry on eval scorer spansVoltAgent now records LLM judge model, token usage, cached tokens, reasoning tokens,
and provider-reported cost details on live eval scorer spans.
This makes scorer-side usage visible in observability backends and enables downstream
cost aggregation to distinguish agent costs from eval scorer costs.
#1163
6f14c4dThanks @omeraplak! - fix: preserve usage and provider cost metadata on structured output failuresWhen
generateTextreceives a successful model response but structured output is not produced,VoltAgent now keeps the resolved usage, finish reason, and provider metadata on the resulting
error path.
This preserves provider-reported cost data for observability spans and makes the same metadata
available to error hooks through
VoltAgentError.metadata.Summary by CodeRabbit
Release Notes
Bug Fixes
New Features