ci(changesets): version packages #930
Conversation
voltagent-bot
force-pushed
the
changeset-release/main
branch
from
5e50cbd to
9fe4531
Compare
Deploying voltagent with
|
| Latest commit: |
9fe4531
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e949a915.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
📝 WalkthroughWalkthroughThis diff represents a patch release (2.0.9) of Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
examples/with-hooks/package.json (1)
4-13: Lockfile not updated; pnpm-lock.yaml missing @voltagent/[email protected] entry.All example packages correctly reference
^2.0.9and the core package version is confirmed as2.0.9, but the mainpnpm-lock.yamldoes not contain the corresponding@voltagent/[email protected]entry. The lockfile must be regenerated to reflect the dependency bump and prevent installation inconsistencies.
🤖 Fix all issues with AI agents
In @examples/with-playwright/package.json:
- Line 11: Update the @voltagent/core dependency in
examples/with-zapier-mcp/package.json from the patch-only range (~2.0.9) to the
caret range (^2.0.9) so it matches the other example packages using ^2.0.9, and
then regenerate/update pnpm-lock.yaml to reflect the changed specifier; leave
any intentionally pinned older examples (e.g., ^2.0.2) unchanged.
In @packages/core/CHANGELOG.md:
- Around line 133-147: The example for createWorkflowChain is broken because the
chain uses data.userId in the "fetch-user" step but no input schema is declared;
update the example by adding an input (e.g., define an input type/schema with
userId) to createWorkflowChain so the chain has a typed input available to
steps, or alternatively change the step to read from a defined field (e.g.,
input.userId) and reference that symbol; ensure the example shows
createWorkflowChain(..., input: { userId: string }) (or equivalent schema) so
the fetch-user execute handler can safely access userId.
🧹 Nitpick comments (2)
packages/core/CHANGELOG.md (1)
3-22: Align the import snippet with actual usage (avoid misleading unused imports).
The snippet importsandBranch/andForEach/andDoWhile/andDoUntil/andMap/andSleep/andSleepUntil, but the examples call chain methods (.andBranch(),.andForEach(), etc.) rather than the imported functions. Either remove the unused imports, or adjust examples to demonstrate the functional form consistently.Proposed doc tweak (remove unused imports)
import { createWorkflowChain, - andThen, - andBranch, - andForEach, - andDoWhile, - andDoUntil, - andMap, - andSleep, - andSleepUntil, + andThen, } from "@voltagent/core"; import { z } from "zod";examples/with-zapier-mcp/package.json (1)
9-9: Consider standardizing the semver range to match other examples.This file uses
~2.0.9(tilde) while most other example packages in this PR use^2.0.9(caret). Tilde allows only patch updates (2.0.x), whereas caret allows minor updates (2.x.x). Consider standardizing to caret for consistency across examples.♻️ Align with the pattern used in other examples
- "@voltagent/core": "~2.0.9", + "@voltagent/core": "^2.0.9",
📜 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/social-humans-hammer.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/social-humans-hammer.md
⏰ 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). (17)
- GitHub Check: cubic · AI code reviewer
- GitHub Check: Test cli
- GitHub Check: Test supabase
- GitHub Check: Test libsql
- GitHub Check: Test create-voltagent-app
- GitHub Check: Test core
- GitHub Check: Test docs-mcp
- GitHub Check: Test postgres
- GitHub Check: Test voice
- GitHub Check: Test logger
- GitHub Check: Test internal
- GitHub Check: Test server-core
- GitHub Check: Build (Node 20)
- GitHub Check: Build (Node 24)
- GitHub Check: Build (Node 22)
- GitHub Check: Lint (Node 20)
- GitHub Check: Cloudflare Pages
🔇 Additional comments (71)
packages/core/package.json (1)
4-4: Version bump is correct for patch release.The version update from 2.0.8 to 2.0.9 is appropriate for a patch release that includes new exports and workflow control features. The automated changeset workflow has correctly incremented the patch version.
packages/core/CHANGELOG.md (2)
149-172: Hooks example: please verify hook names + callback shapes match the shipped API.
The snippet useshooks.onSuspend/onError/onFinish/onEndwith(state, info)foronEnd. If any of these names/signatures differ in@voltagent/[email protected], this changelog will lead users astray. Consider adding/aligning with the exact exported types or linking to the API docs page that defines hook signatures.
174-219: Guardrails example: verify.andGuardrail()semantics and guardrail handler contracts.
This reads well, but since it’s a new public surface area (and guardrails are easy to get subtly wrong), I’d double-check:
createInputGuardrail/createOutputGuardrailhandler return shape (pass/action/modifiedInput|modifiedOutput)- whether
.andGuardrail({ outputGuardrails })applies to the next step only, the whole workflow from that point, or is a standalone step- generic usage
createOutputGuardrail<string>()matches the exported typingexamples/with-supabase/package.json (1)
8-8: LGTM! Version bump is correct.The dependency update to @voltagent/core ^2.0.9 is appropriate for this patch release.
examples/with-guardrails/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update to @voltagent/core ^2.0.9 is appropriate for this patch release.
examples/with-nextjs-resumable-stream/package.json (1)
21-21: LGTM! Version bump is correct.The dependency update to @voltagent/core ^2.0.9 is appropriate for this patch release.
examples/with-slack/package.json (1)
7-7: LGTM! Version bump is correct.The dependency update to @voltagent/core ^2.0.9 is appropriate for this patch release.
examples/with-retrieval/package.json (1)
7-7: Version bump to @voltagent/core ^2.0.9 is correct.The dependency update is appropriate. Note that the examples directory has pre-existing workspace-level dependency conflicts (vite version mismatch) that should be resolved separately from this change.
examples/with-composio-mcp/package.json (1)
8-8: LGTM! Dependency version bump is correct.The update to
@voltagent/core^2.0.9 aligns with the patch release and is correctly applied.examples/with-rag-chatbot/package.json (1)
8-8: LGTM! Version bump is consistent.The dependency update to
@voltagent/core^2.0.9 is correct.examples/with-cerbos/package.json (1)
9-9: LGTM! Dependency correctly updated.The version bump to
@voltagent/core^2.0.9 is accurate and consistent with the release.examples/with-peaka-mcp/package.json (1)
7-7: LGTM! Version update is correct.The
@voltagent/coredependency update to ^2.0.9 is properly applied.examples/with-mcp/package.json (1)
8-8: LGTM! Final dependency update is correct.The version bump to
@voltagent/core^2.0.9 completes the consistent update across all example packages.examples/with-postgres/package.json (1)
8-8: LGTM! Dependency version bump is consistent with the release.The update from
^2.0.8to^2.0.9aligns with the patch release described in the PR objectives.examples/with-voice-elevenlabs/package.json (1)
7-7: LGTM! Dependency version bump is consistent with the release.The update from
^2.0.8to^2.0.9aligns with the patch release described in the PR objectives.examples/with-subagents/package.json (1)
7-7: LGTM! Dependency version bump is consistent with the release.The update from
^2.0.8to^2.0.9aligns with the patch release described in the PR objectives.examples/with-pinecone/package.json (1)
8-8: LGTM! Dependency version bump is consistent with the release.The update from
^2.0.8to^2.0.9aligns with the patch release described in the PR objectives.examples/with-nestjs/package.json (1)
10-10: LGTM! Dependency version bump is consistent with the release.The update from
^2.0.8to^2.0.9aligns with the patch release. Since this release introduces new workflow control APIs, you may want to verify that the example projects still build and run correctly after the dependency update.examples/with-dynamic-parameters/package.json (1)
7-7: LGTM: example updated to@voltagent/core@^2.0.9.examples/with-nextjs/package.json (1)
10-10: LGTM: example updated to@voltagent/core@^2.0.9.examples/with-langfuse/package.json (1)
7-7: LGTM: example updated to@voltagent/core@^2.0.9.examples/with-nuxt/package.json (1)
7-7: LGTM: example updated to@voltagent/core@^2.0.9.examples/with-tavily-search/package.json (1)
7-7: Dependency bump is correct and version constraints are compatible.Verification confirms: no lingering
^2.0.8references exist, all example packages that were updated now reference^2.0.9, and all@voltagent/*packagepeerDependenciesdeclare^2.0.0, which safely accepts2.0.9. A few older examples still reference^2.0.0or^2.0.2, but these are compatible and do not conflict.examples/with-memory-rest-api/package.json (1)
8-8: LGTM: example aligned to@voltagent/core@^2.0.9.examples/with-cloudflare-workers/package.json (1)
7-7: LGTM: example aligned to@voltagent/core@^2.0.9.examples/with-mcp-elicitation/package.json (1)
8-8: LGTM: example aligned to@voltagent/core@^2.0.9.examples/with-a2a-server/package.json (1)
6-6: LGTM: example aligned to@voltagent/core@^2.0.9.examples/with-voltagent-managed-memory/package.json (1)
6-6: Dependency bump OK; ensure examples stay in sync with the published core release.
Given this is a dependency/version change, please verify the example still installs/builds against@voltagent/[email protected](and that any lockfile updates are included elsewhere in the PR).examples/with-vercel-ai/package.json (1)
7-7: Dependency bump OK; validate example install/build with@voltagent/[email protected].examples/with-whatsapp/package.json (1)
8-8: Dependency bump OK; validate example install/build with@voltagent/[email protected].examples/with-research-assistant/package.json (1)
7-7: Dependency bump OK; validate example install/build with@voltagent/[email protected].examples/with-working-memory/package.json (1)
7-7: Dependency bump OK; validate example install/build with@voltagent/[email protected].examples/with-dynamic-prompts/package.json (1)
7-7: LGTM!The version bump to
^2.0.9is correct and consistent with the patch release.examples/with-planagents/package.json (1)
9-9: LGTM!The version bump to
^2.0.9is correct and consistent with the patch release.examples/with-groq-ai/package.json (1)
7-7: LGTM!The version bump to
^2.0.9is correct and consistent with the patch release.examples/with-google-ai/package.json (1)
7-7: LGTM!The version bump to
^2.0.9is correct and consistent with the patch release.examples/with-chroma/package.json (1)
10-10: LGTM! Dependency version bump is correct.The @voltagent/core dependency has been correctly updated to ^2.0.9, consistent with the patch release.
examples/with-vector-search/package.json (1)
7-7: LGTM! Dependency version bump is correct.The @voltagent/core dependency has been correctly updated to ^2.0.9.
examples/with-tools/package.json (1)
7-7: LGTM! Dependency version bump is correct.The @voltagent/core dependency has been correctly updated to ^2.0.9.
examples/with-viteval/package.json (1)
7-7: LGTM! Dependency version bump is correct.The @voltagent/core dependency has been correctly updated to ^2.0.9.
examples/with-voltagent-actions/package.json (1)
7-7: LGTM! Dependency version bump is correct.The @voltagent/core dependency has been correctly updated to ^2.0.9.
examples/with-auth/package.json (1)
4-13: LGTM: example aligned to@voltagent/core@^2.0.9.examples/with-offline-evals/package.json (1)
4-13: LGTM:@voltagent/corebumped to^2.0.9.examples/with-voice-openai/package.json (1)
4-16: LGTM:@voltagent/corebumped to^2.0.9.examples/with-resumable-streams/package.json (1)
6-13: LGTM:@voltagent/corebumped to^2.0.9.examples/github-repo-analyzer/package.json (1)
7-7: LGTM! Dependency version bump looks good.The version update to
@voltagent/core@^2.0.9is consistent with the automated changeset release process.examples/with-workflow/package.json (1)
7-7: LGTM! Dependency version bump looks good.The version update to
@voltagent/core@^2.0.9is consistent with the automated changeset release process.examples/with-voice-xsai/package.json (1)
7-7: LGTM! Dependency version bump looks good.The version update to
@voltagent/core@^2.0.9is consistent with the automated changeset release process.examples/with-agent-tool/package.json (1)
8-8: LGTM! Dependency version bump looks good.The version update to
@voltagent/core@^2.0.9is consistent with the automated changeset release process.examples/with-amazon-bedrock/package.json (1)
8-8: LGTM! Dependency version bump looks good.The version update to
@voltagent/core@^2.0.9is consistent with the automated changeset release process.examples/next-js-chatbot-starter-template/package.json (1)
23-23: LGTM! Dependency version bump is consistent with the release.The @voltagent/core dependency has been correctly updated to ^2.0.9 as part of the automated release process.
examples/with-google-drive-mcp/server/package.json (1)
9-9: LGTM! Dependency version bump is consistent with the release.The @voltagent/core dependency has been correctly updated to ^2.0.9 as part of the automated release process.
examples/with-hugging-face-mcp/package.json (1)
7-7: LGTM! Dependency version bump is consistent with the release.The @voltagent/core dependency has been correctly updated to ^2.0.9 as part of the automated release process.
examples/with-voltops-retrieval/package.json (1)
7-7: LGTM! Dependency version bump is consistent with the release.The @voltagent/core dependency has been correctly updated to ^2.0.9 as part of the automated release process.
examples/with-thinking-tool/package.json (1)
7-7: LGTM! Dependency version bump is consistent with the release.The @voltagent/core dependency has been correctly updated to ^2.0.9 as part of the automated release process.
examples/with-client-side-tools/package.json (1)
8-8: LGTM: Dependency version bump aligns with release.The @voltagent/core dependency update from ^2.0.8 to ^2.0.9 is correct and consistent with the automated changeset release process.
examples/with-airtable/package.json (1)
7-7: LGTM: Dependency version bump is correct.The @voltagent/core dependency update to ^2.0.9 is consistent with the changeset release.
examples/with-voltagent-exporter/package.json (1)
7-7: LGTM: Version bump aligns with release.The dependency update to @voltagent/core ^2.0.9 is correct and consistent with the automated release process.
examples/with-youtube-to-blog/package.json (1)
7-7: LGTM: Dependency update is correct.The @voltagent/core version bump to ^2.0.9 is consistent with the changeset release workflow.
examples/with-voltops-resumable-streams/package.json (1)
8-8: LGTM: Version bump is correct.The @voltagent/core dependency update to ^2.0.9 aligns with the automated changeset release process.
examples/with-qdrant/package.json (1)
8-8:@voltagent/corebump to^2.0.9looks consistent—please smoke-test this example.
Given this is an external version resolution change, ensure install + build/start forexamples/with-qdrantstill passes and no peer-dep warnings/regressions appear.examples/with-custom-endpoints/package.json (1)
7-7:@voltagent/corebump to^2.0.9is fine—verify the example still builds cleanly.
Please run install + build/start forexamples/with-custom-endpointsto catch any drift with the new core patch release.examples/with-turso/package.json (1)
8-8:@voltagent/corebump to^2.0.9looks good—please run a quick install/build/start check.
This ensures the Turso/LibSQL example remains compatible with the new core patch version.examples/with-anthropic/package.json (1)
7-7:@voltagent/corebump to^2.0.9is straightforward—smoke-test the Anthropic example.
Please confirm install + build/start still succeeds forexamples/with-anthropic.examples/github-star-stories/package.json (1)
7-7:@voltagent/corebump to^2.0.9is consistent—please validate build/preview for this example.
Given thewranglerflow here, a quick build + preview check helps catch any runtime drift after the core patch release.examples/with-netlify-functions/package.json (1)
5-12: Dependency bump looks good; please verify the example still builds/runs with@voltagent/core@^2.0.9.
Main thing to confirm is CI/install + the example’s build/typecheck after the upgrade (and lockfile/workspace resolution if applicable).examples/with-recipe-generator/package.json (1)
4-12: Version alignment with the core release is correct; verify peers and runtime for this example.
After bumping@voltagent/core, ensure install doesn’t introduce peer-dep conflicts with the other@voltagent/*deps and that build/typecheck/start still pass.examples/base/package.json (1)
4-13: LGTM; please confirm the base example remains green on install + build/typecheck with@voltagent/core@^2.0.9.examples/with-mcp-server/package.json (1)
3-11: Looks fine; verify MCP integration still works after upgrading@voltagent/coreto^2.0.9.
Specifically watch for runtime errors/typing changes across@voltagent/core↔@voltagent/mcp-server.examples/with-google-vertex-ai/package.json (1)
4-13: Dependency bump is consistent; please re-verify build/typecheck (and a quick run) for the Vertex AI example with@voltagent/core@^2.0.9.examples/with-ollama/package.json (1)
5-5: LGTM! Dependency version bump aligns with the patch release.The update to
@voltagent/core@^2.0.9is correct and consistent with the changeset release described in the PR objectives.
| "@playwright/test": "^1.51.1", | ||
| "@voltagent/cli": "^0.1.20", | ||
| "@voltagent/core": "^2.0.8", | ||
| "@voltagent/core": "^2.0.9", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Expect: no remaining ^2.0.8 refs
rg -n '"@voltagent/core":\s*"\^2\.0\.8"' -S . && exit 1 || true
# Inspect current refs (expect: all are ^2.0.9 or intentionally different)
rg -n '"@voltagent/core":\s*"' -S examples packages | sed -n '1,200p'
# If you use pnpm/yarn/npm, also confirm the lockfile updated in this PR.
ls -la | rg -n 'pnpm-lock\.yaml|yarn\.lock|package-lock\.json' || trueRepository: VoltAgent/voltagent
Length of output: 8571
Dependency bump is consistent across examples; minor version specifier inconsistency found.
The @voltagent/[email protected] bump is correctly applied with no remaining ^2.0.8 references. Most examples align to ^2.0.9; however, examples/with-zapier-mcp/package.json uses ~2.0.9 (patch-only range) instead of ^2.0.9 for consistency with the others. Some older examples intentionally pin ^2.0.2 and should not be changed. Ensure pnpm-lock.yaml is updated with these changes.
🤖 Prompt for AI Agents
In @examples/with-playwright/package.json at line 11, Update the @voltagent/core
dependency in examples/with-zapier-mcp/package.json from the patch-only range
(~2.0.9) to the caret range (^2.0.9) so it matches the other example packages
using ^2.0.9, and then regenerate/update pnpm-lock.yaml to reflect the changed
specifier; leave any intentionally pinned older examples (e.g., ^2.0.2)
unchanged.
| ```ts | ||
| createWorkflowChain({ | ||
| id: "compose-result", | ||
| input: z.object({ userId: z.string() }), | ||
| }) | ||
| .andThen({ | ||
| id: "fetch-user", | ||
| execute: async ({ data }) => ({ name: "Ada", id: data.userId }), | ||
| }) | ||
| .andMap({ | ||
| id: "shape-output", | ||
| map: { | ||
| userId: { source: "data", path: "userId" }, | ||
| name: { source: "step", stepId: "fetch-user", path: "name" }, | ||
| region: { source: "context", key: "region" }, | ||
| constant: { source: "value", value: "ok" }, | ||
| }, | ||
| }); | ||
| ``` |
There was a problem hiding this comment.
Data shaping example: userId mapping looks incorrect after fetch-user overwrites data.
fetch-user returns { name, id }, so map.userId: { source: "data", path: "userId" } likely resolves to undefined. Consider returning userId from fetch-user (or mapping from the step output).
Proposed fix (keep `userId` in `data`)
.andThen({
id: "fetch-user",
- execute: async ({ data }) => ({ name: "Ada", id: data.userId }),
+ execute: async ({ data }) => ({ userId: data.userId, name: "Ada", id: data.userId }),
})
.andMap({
id: "shape-output",
map: {
userId: { source: "data", path: "userId" },
name: { source: "step", stepId: "fetch-user", path: "name" },
region: { source: "context", key: "region" },
constant: { source: "value", value: "ok" },
},
});| ```ts | ||
| createWorkflowChain({ | ||
| id: "retry-defaults", | ||
| retryConfig: { attempts: 2, delayMs: 500 }, | ||
| }) | ||
| .andThen({ | ||
| id: "fetch-user", | ||
| execute: async ({ data }) => fetchUser(data.userId), | ||
| }) | ||
| .andThen({ | ||
| id: "no-retry-step", | ||
| retries: 0, | ||
| execute: async ({ data }) => data, | ||
| }); | ||
| ``` |
There was a problem hiding this comment.
Retry example references data.userId but no input is defined.
As written, fetch-user uses data.userId but createWorkflowChain doesn’t declare an input, so this is likely copy/paste-broken (or relies on implicit any).
Proposed fix (add an input schema)
createWorkflowChain({
id: "retry-defaults",
+ input: z.object({ userId: z.string() }),
retryConfig: { attempts: 2, delayMs: 500 },
})
.andThen({
id: "fetch-user",
execute: async ({ data }) => fetchUser(data.userId),
})🤖 Prompt for AI Agents
In @packages/core/CHANGELOG.md around lines 133 - 147, The example for
createWorkflowChain is broken because the chain uses data.userId in the
"fetch-user" step but no input schema is declared; update the example by adding
an input (e.g., define an input type/schema with userId) to createWorkflowChain
so the chain has a typed input available to steps, or alternatively change the
step to read from a defined field (e.g., input.userId) and reference that
symbol; ensure the example shows createWorkflowChain(..., input: { userId:
string }) (or equivalent schema) so the fetch-user execute handler can safely
access userId.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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
#929
78ff377Thanks @omeraplak! - feat: add workflow control steps (branch, foreach, loop, map, sleep)Branching:
For-each and loops:
Data shaping:
Sleep:
Workflow-level retries:
Workflow hooks (finish/error/suspend):
Workflow guardrails (input/output + step-level):
Summary by cubic
Versioned packages for a patch release. @voltagent/core is now 2.0.9 with new workflow controls (branch, foreach/loops, map, sleep) plus hooks, guardrails, and retries.
New Features
Dependencies
Written for commit 9fe4531. Summary will update on new commits.
Summary by CodeRabbit
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.