ci(changesets): version packages#1109
Merged
Merged
Conversation
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
February 25, 2026 02:23
bd8137e to
b66afa0
Compare
Deploying voltagent with
|
| Latest commit: |
b66afa0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1b173de5.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
Contributor
📝 WalkthroughWalkthroughA patch version release for Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
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 |
![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}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/evals/CHANGELOG.md`:
- Around line 19-40: The example in the CHANGELOG references voltOpsClient in
runExperiment but never declares or imports it; update the example to import
VoltOpsClient from "@voltagent/core" and construct a voltOpsClient instance
(e.g., new VoltOpsClient({...}) using VOLTAGENT_PUBLIC_KEY and
VOLTAGENT_SECRET_KEY environment vars) before calling runExperiment so the
example is copy-paste runnable; ensure the snippet shows the import, the const
voltOpsClient = new VoltOpsClient(...) and then passes { voltOpsClient } to
runExperiment alongside the existing createExperiment/runExperiment usage.
ℹ️ Review info
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 (4)
.changeset/soft-dots-bow.mdexamples/with-offline-evals/package.jsonpackages/evals/CHANGELOG.mdpackages/evals/package.json
💤 Files with no reviewable changes (1)
- .changeset/soft-dots-bow.md
Comment on lines
+19
to
+40
| ### Example | ||
|
|
||
| ```ts | ||
| import { createExperiment, runExperiment } from "@voltagent/evals"; | ||
|
|
||
| const experiment = createExperiment({ | ||
| dataset: { | ||
| name: "inline-smoke", | ||
| items: [ | ||
| { | ||
| id: "item-1", // non-UUID is supported | ||
| input: "What is VoltAgent?", | ||
| expected: "An open-source TypeScript framework for AI agents.", | ||
| }, | ||
| ], | ||
| }, | ||
| runner: async ({ item }) => ({ output: String(item.input) }), | ||
| }); | ||
|
|
||
| const result = await runExperiment(experiment, { voltOpsClient }); | ||
| console.log(result.runId); // now created and persisted | ||
| ``` |
Contributor
There was a problem hiding this comment.
voltOpsClient is referenced in the example but never declared or imported.
The snippet uses { voltOpsClient } on line 38 without showing how to construct it. Readers copy-pasting the example will get a ReferenceError. The 2.0.3 entry below shows the required setup — it should be included here too.
📝 Proposed fix — add the missing client setup
### Example
```ts
+ import { VoltOpsClient } from "@voltagent/core";
import { createExperiment, runExperiment } from "@voltagent/evals";
+ const voltOpsClient = new VoltOpsClient({
+ publicKey: process.env.VOLTAGENT_PUBLIC_KEY,
+ secretKey: process.env.VOLTAGENT_SECRET_KEY,
+ });
+
const experiment = createExperiment({📝 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.
Suggested change
| ### Example | |
| ```ts | |
| import { createExperiment, runExperiment } from "@voltagent/evals"; | |
| const experiment = createExperiment({ | |
| dataset: { | |
| name: "inline-smoke", | |
| items: [ | |
| { | |
| id: "item-1", // non-UUID is supported | |
| input: "What is VoltAgent?", | |
| expected: "An open-source TypeScript framework for AI agents.", | |
| }, | |
| ], | |
| }, | |
| runner: async ({ item }) => ({ output: String(item.input) }), | |
| }); | |
| const result = await runExperiment(experiment, { voltOpsClient }); | |
| console.log(result.runId); // now created and persisted | |
| ``` | |
| ### Example |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/evals/CHANGELOG.md` around lines 19 - 40, The example in the
CHANGELOG references voltOpsClient in runExperiment but never declares or
imports it; update the example to import VoltOpsClient from "@voltagent/core"
and construct a voltOpsClient instance (e.g., new VoltOpsClient({...}) using
VOLTAGENT_PUBLIC_KEY and VOLTAGENT_SECRET_KEY environment vars) before calling
runExperiment so the example is copy-paste runnable; ensure the snippet shows
the import, the const voltOpsClient = new VoltOpsClient(...) and then passes {
voltOpsClient } to runExperiment alongside the existing
createExperiment/runExperiment usage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/evals@2.0.4
Patch Changes
#1108
c1df46fThanks @omeraplak! - fix: persist offline eval runs when using inline datasets (dataset.items)Offline experiment runs now create and sync run results even when the dataset is provided inline without a managed
datasetVersionId.What changed
VoltOpsRunManagernow allows run creation whendataset.versionIdis missing.datasetItemId:datasetItemId.nulland still tracked viadatasetItemHash.This avoids API failures when inline dataset items use string IDs like
"item-1".Example
Summary by cubic
Release @voltagent/evals 2.0.4. It fixes offline eval runs with inline datasets so runs are created and synced even without a datasetVersionId.
Bug Fixes
Dependencies
Written for commit b66afa0. Summary will update on new commits.
Summary by CodeRabbit
Release Notes