Conversation
Deploying voltagent with
|
| Latest commit: |
7302061
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3df56569.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughRemoved three changeset files and bumped package versions and changelogs: 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 |
![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}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
packages/server-core/package.json (1)
18-18: Add Zod v4 to devDependencies or create a test matrix for v4 compatibility validation.The devDependency pins to
"zod": "^3.25.76"(v3 only), so CI validates the schema fix exclusively under Zod v3. While the peerDependency range already includes^4.0.0and the fix (explicit key types inz.record()) is syntactically valid in both versions, the v4 code path is never exercised in automated tests despite being a supported peer dependency.Consider either upgrading the devDependency to Zod v4 or adding a separate test matrix entry to validate v4 compatibility alongside v3 coverage.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/server-core/package.json` at line 18, The package.json devDependency pins "zod" to v3 only, so CI never tests the v4 peer path; update package.json devDependencies to include a compatible Zod v4 (e.g., add or bump "zod" to a ^4.x version) or update the CI/test matrix to run tests against both Zod v3 and v4; locate the package.json entry for "zod" in devDependencies and either change its version string to a ^4.x range or add a separate CI matrix job that installs/uses Zod v4 to validate compatibility with the code paths using z.record() and other Zod symbols.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@packages/server-core/package.json`:
- Line 18: The package.json devDependency pins "zod" to v3 only, so CI never
tests the v4 peer path; update package.json devDependencies to include a
compatible Zod v4 (e.g., add or bump "zod" to a ^4.x version) or update the
CI/test matrix to run tests against both Zod v3 and v4; locate the package.json
entry for "zod" in devDependencies and either change its version string to a
^4.x range or add a separate CI matrix job that installs/uses Zod v4 to validate
compatibility with the code paths using z.record() and other Zod symbols.
voltagent-bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
3051eea to
e885397
Compare
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
examples/with-groq-ai/package.json (1)
1-36:⚠️ Potential issue | 🟡 MinorPre-existing: missing
"type": "module"Every other example in this PR includes
"type": "module", but this file does not. If any source files use ES moduleimport/exportsyntax, Node.js will fail to resolve them correctly without this field.Not introduced by this PR, but worth tracking.
🔧 Suggested addition
"scripts": { "build": "tsc", "dev": "tsx watch --env-file=.env ./src ", "start": "node dist/index.js", "volt": "volt" - } + }, + "type": "module" }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@examples/with-groq-ai/package.json` around lines 1 - 36, The package.json for the example is missing the top-level "type": "module" field, which causes Node to treat files as CommonJS and will break ES module import/export; open the package.json in the example (file shown in the diff) and add a top-level "type": "module" property (e.g., alongside "name" and "author") so Node resolves ES modules correctly for this example.examples/with-nextjs-resumable-stream/package.json (1)
63-63:⚠️ Potential issue | 🟡 MinorStale
repository.directory— points to the wrong example folder.The
directoryfield is"examples/with-nextjs-ai-elements"but this package lives atexamples/with-nextjs-resumable-stream. This causes incorrect source-link metadata on npm.🛠️ Proposed fix
- "directory": "examples/with-nextjs-ai-elements" + "directory": "examples/with-nextjs-resumable-stream"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@examples/with-nextjs-resumable-stream/package.json` at line 63, The repository metadata in package.json has a stale "directory" field; update the "directory" value from "examples/with-nextjs-ai-elements" to the correct path "examples/with-nextjs-resumable-stream" so npm source-link metadata points to this package's actual folder; locate and edit the "directory" property in the package.json for this package to make the change.
🧹 Nitpick comments (1)
examples/with-zapier-mcp/package.json (1)
7-7: Inconsistent range specifier:~vs^used across sibling examples.This example uses
~2.5.0(patch-range only,>=2.5.0 <2.6.0), while every other example in the monorepo pins@voltagent/corewith^(minor+patch range,>=2.5.0 <3.0.0). This is a pre-existing inconsistency but carries forward with each automated release. Aligning to^would keep examples consistent and allow receiving future minor updates without manual edits.🔧 Proposed fix
- "@voltagent/core": "~2.5.0", + "@voltagent/core": "^2.5.0",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@examples/with-zapier-mcp/package.json` at line 7, Update the dependency specifier for `@voltagent/core` in the examples/with-zapier-mcp package.json to use a caret range instead of a tilde; locate the line containing the string "@voltagent/core": "~2.5.0" and change it to use "^2.5.0" so it matches the other examples and allows minor+patch updates.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@examples/with-groq-ai/package.json`:
- Around line 1-36: The package.json for the example is missing the top-level
"type": "module" field, which causes Node to treat files as CommonJS and will
break ES module import/export; open the package.json in the example (file shown
in the diff) and add a top-level "type": "module" property (e.g., alongside
"name" and "author") so Node resolves ES modules correctly for this example.
In `@examples/with-nextjs-resumable-stream/package.json`:
- Line 63: The repository metadata in package.json has a stale "directory"
field; update the "directory" value from "examples/with-nextjs-ai-elements" to
the correct path "examples/with-nextjs-resumable-stream" so npm source-link
metadata points to this package's actual folder; locate and edit the "directory"
property in the package.json for this package to make the change.
---
Nitpick comments:
In `@examples/with-zapier-mcp/package.json`:
- Line 7: Update the dependency specifier for `@voltagent/core` in the
examples/with-zapier-mcp package.json to use a caret range instead of a tilde;
locate the line containing the string "@voltagent/core": "~2.5.0" and change it
to use "^2.5.0" so it matches the other examples and allows minor+patch updates.
e885397 to
57dd961
Compare
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
examples/with-playwright/package.json (1)
18-18:⚠️ Potential issue | 🔴 CriticalFix example dependency on non-existent
@voltagent/core@2.5.0.The example specifies
"@voltagent/core": "^2.5.0"in devDependencies, but this version does not exist on npm. The latest available version is2.4.4. Update the constraint to"^2.4.4"or the intended version if 2.5.0 is planned for release.Note:
@voltagent/core@2.4.4declares"zod": "^3.25.0 || ^4.0.0"as a peer dependency, so the example's"zod": "^3.25.76"is compatible and no peer-conflict warning will occur.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@examples/with-playwright/package.json` at line 18, The package.json devDependency for `@voltagent/core` references a non-existent 2.5.0 release; update the version constraint for "@voltagent/core" to "^2.4.4" (or the correct intended release) so the example depends on the published version, keeping the existing "zod": "^3.25.76" which is compatible with `@voltagent/core`@2.4.4.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@examples/with-playwright/package.json`:
- Line 18: The package.json devDependency for `@voltagent/core` references a
non-existent 2.5.0 release; update the version constraint for "@voltagent/core"
to "^2.4.4" (or the correct intended release) so the example depends on the
published version, keeping the existing "zod": "^3.25.76" which is compatible
with `@voltagent/core`@2.4.4.
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
57dd961 to
7302061
Compare
There was a problem hiding this comment.
🧹 Nitpick comments (1)
examples/with-rag-chatbot/package.json (1)
12-12: Consider migratingzoddependency to^4.0.0.
zod@^3.25.76is a valid, published version. However, it's worth noting that starting in v3.25.0, the package contains copies of both Zod 3 and Zod 4 at their respective subpaths, meaning the installed package is effectively twice the size. Zod v4.0.0 has been published to npm, and the package root ("zod") now exports Zod 4. Since@voltagent/server-core@2.1.8in this PR has already been updated for Zod v4 compatibility, migrating this example tozod@^4.0.0would be the natural next step to avoid carrying the dual-bundle overhead of3.25.x.♻️ Proposed update
- "zod": "^3.25.76" + "zod": "^4.0.0"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@examples/with-rag-chatbot/package.json` at line 12, Update the zod dependency in the examples/with-rag-chatbot package.json from "zod": "^3.25.76" to "zod": "^4.0.0" to avoid the dual-bundle overhead; after changing the "zod" semver, run your package manager (npm/yarn/pnpm) to reinstall and then rebuild/test the example to ensure `@voltagent/server-core` and any code that imports Zod types still compile against Zod v4.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@examples/with-rag-chatbot/package.json`:
- Line 12: Update the zod dependency in the examples/with-rag-chatbot
package.json from "zod": "^3.25.76" to "zod": "^4.0.0" to avoid the dual-bundle
overhead; after changing the "zod" semver, run your package manager
(npm/yarn/pnpm) to reinstall and then rebuild/test the example to ensure
`@voltagent/server-core` and any code that imports Zod types still compile against
Zod v4.
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.5.0
Minor Changes
#1097
e15bb6eThanks @omeraplak! - AddstartAsync()to workflow and workflow chain APIs for fire-and-forget execution.startAsync()starts a workflow run in the background and returns{ executionId, workflowId, startAt }immediately. The run keeps existing execution semantics, respects providedexecutionId, and persists terminal states in memory for later inspection.Also adds workflow documentation updates with
startAsync()usage examples in the workflow overview and streaming docs.#1099
160e60bThanks @omeraplak! - Add workflow time-travel and deterministic replay APIs.New APIs:
workflow.timeTravel(options)workflow.timeTravelStream(options)workflowChain.timeTravel(options)workflowChain.timeTravelStream(options)timeTravelreplays a historical execution from a selected step with a new execution ID, preserving the original execution history. Replay runs can optionally override selected-step input (inputData), resume payload (resumeData), and shared workflow state (workflowStateOverride).Replay lineage metadata is now persisted on workflow state records:
replayedFromExecutionIdreplayFromStepIdNew public type exports from
@voltagent/coreincludeWorkflowTimeTravelOptions.Also adds workflow documentation and usage examples for deterministic replay in overview, suspend/resume, and streaming docs.
Adds REST API documentation for replay endpoint
POST /workflows/:id/executions/:executionId/replay, including request/response details and both cURL and JavaScript (fetch) code examples for default replay and replay with overrides (inputData,resumeData,workflowStateOverride).#1098
b610ec6Thanks @omeraplak! - Add workflow restart and crash-recovery APIs.New APIs:
workflow.restart(executionId, options?)workflow.restartAllActive()workflowChain.restart(executionId, options?)workflowChain.restartAllActive()WorkflowRegistry.restartWorkflowExecution(workflowId, executionId, options?)WorkflowRegistry.restartAllActiveWorkflowRuns(options?)The workflow runtime now persists running checkpoints during execution, including step progress, shared workflow state, context, and usage snapshots, so interrupted runs in
runningstate can be recovered deterministically.New public types are now exported from
@voltagent/corefor consumer annotations, includingWorkflowRestartAllResultandWorkflowRestartCheckpoint.Also adds docs for restart/crash-recovery usage under workflow overview and suspend/resume docs.
@voltagent/server-core@2.1.8
Patch Changes
#1089
c007b3eThanks @chrisisagile! - Fix workflow execution request schema to use explicit record key types for Zod v4 compatibility.Updated dependencies [
e15bb6e,160e60b,b610ec6]:Summary by CodeRabbit
New Features
Bug Fixes