ci(changesets): version packages

[voltagent-bot]

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/cloudflare-d1@2.1.2

Patch Changes

• #1085 f275daf Thanks @omeraplak! - Fix workflow execution filtering by persisted metadata across adapters.

  • Persist options.metadata on workflow execution state so /workflows/executions filters can match tenant/user metadata.
  • Preserve existing execution metadata when updating cancelled/error workflow states.
  • Accept options.metadata in server workflow execution request schema.
  • Fix LibSQL and Cloudflare D1 JSON metadata query comparisons for metadata and metadata.<key> filters.

• #1082 73cf1d3 Thanks @omeraplak! - Fix workflow state persistence parity across SQL adapters.

  This update persists and returns input, context, and top-level workflowState in workflow state operations. It also ensures suspended workflow state queries include events, output, and cancellation, and adds adapter migrations/column additions where needed.

@voltagent/core@2.4.4

Patch Changes

• #1085 f275daf Thanks @omeraplak! - Fix workflow execution filtering by persisted metadata across adapters.

  • Persist options.metadata on workflow execution state so /workflows/executions filters can match tenant/user metadata.
  • Preserve existing execution metadata when updating cancelled/error workflow states.
  • Accept options.metadata in server workflow execution request schema.
  • Fix LibSQL and Cloudflare D1 JSON metadata query comparisons for metadata and metadata.<key> filters.

• #1084 95ad610 Thanks @omeraplak! - Add stream attach support for in-progress workflow executions.

  • Add GET /workflows/:id/executions/:executionId/stream to attach to an active workflow SSE stream.
  • Add replay support for missed SSE events via fromSequence and Last-Event-ID.
  • Keep POST /workflows/:id/stream behavior unchanged for starting new executions.
  • Ensure streamed workflow resume uses a fresh suspend controller so attach clients continue receiving events after resume.

@voltagent/libsql@2.1.2

Patch Changes

• #1085 f275daf Thanks @omeraplak! - Fix workflow execution filtering by persisted metadata across adapters.

  • Persist options.metadata on workflow execution state so /workflows/executions filters can match tenant/user metadata.
  • Preserve existing execution metadata when updating cancelled/error workflow states.
  • Accept options.metadata in server workflow execution request schema.
  • Fix LibSQL and Cloudflare D1 JSON metadata query comparisons for metadata and metadata.<key> filters.

• #1082 73cf1d3 Thanks @omeraplak! - Fix workflow state persistence parity across SQL adapters.

  This update persists and returns input, context, and top-level workflowState in workflow state operations. It also ensures suspended workflow state queries include events, output, and cancellation, and adds adapter migrations/column additions where needed.

@voltagent/postgres@2.1.2

Patch Changes

• #1082 73cf1d3 Thanks @omeraplak! - Fix workflow state persistence parity across SQL adapters.

  This update persists and returns input, context, and top-level workflowState in workflow state operations. It also ensures suspended workflow state queries include events, output, and cancellation, and adds adapter migrations/column additions where needed.

@voltagent/server-core@2.1.7

Patch Changes

• #1085 f275daf Thanks @omeraplak! - Fix workflow execution filtering by persisted metadata across adapters.

  • Persist options.metadata on workflow execution state so /workflows/executions filters can match tenant/user metadata.
  • Preserve existing execution metadata when updating cancelled/error workflow states.
  • Accept options.metadata in server workflow execution request schema.
  • Fix LibSQL and Cloudflare D1 JSON metadata query comparisons for metadata and metadata.<key> filters.

• #1084 95ad610 Thanks @omeraplak! - Add stream attach support for in-progress workflow executions.

  • Add GET /workflows/:id/executions/:executionId/stream to attach to an active workflow SSE stream.
  • Add replay support for missed SSE events via fromSequence and Last-Event-ID.
  • Keep POST /workflows/:id/stream behavior unchanged for starting new executions.
  • Ensure streamed workflow resume uses a fresh suspend controller so attach clients continue receiving events after resume.

• Updated dependencies [f275daf, 95ad610]:

  • @voltagent/core@2.4.4

@voltagent/server-elysia@2.0.6

Patch Changes

• #1084 95ad610 Thanks @omeraplak! - Add stream attach support for in-progress workflow executions.

  • Add GET /workflows/:id/executions/:executionId/stream to attach to an active workflow SSE stream.
  • Add replay support for missed SSE events via fromSequence and Last-Event-ID.
  • Keep POST /workflows/:id/stream behavior unchanged for starting new executions.
  • Ensure streamed workflow resume uses a fresh suspend controller so attach clients continue receiving events after resume.

• Updated dependencies [f275daf, 95ad610]:

  • @voltagent/core@2.4.4
  • @voltagent/server-core@2.1.7

@voltagent/server-hono@2.0.7

Patch Changes

• #1084 95ad610 Thanks @omeraplak! - Add stream attach support for in-progress workflow executions.

  • Add GET /workflows/:id/executions/:executionId/stream to attach to an active workflow SSE stream.
  • Add replay support for missed SSE events via fromSequence and Last-Event-ID.
  • Keep POST /workflows/:id/stream behavior unchanged for starting new executions.
  • Ensure streamed workflow resume uses a fresh suspend controller so attach clients continue receiving events after resume.

• Updated dependencies [f275daf, 95ad610]:

  • @voltagent/core@2.4.4
  • @voltagent/server-core@2.1.7

@voltagent/serverless-hono@2.0.9

Patch Changes

• #1084 95ad610 Thanks @omeraplak! - Add stream attach support for in-progress workflow executions.

  • Add GET /workflows/:id/executions/:executionId/stream to attach to an active workflow SSE stream.
  • Add replay support for missed SSE events via fromSequence and Last-Event-ID.
  • Keep POST /workflows/:id/stream behavior unchanged for starting new executions.
  • Ensure streamed workflow resume uses a fresh suspend controller so attach clients continue receiving events after resume.

• Updated dependencies [f275daf, 95ad610]:

  • @voltagent/server-core@2.1.7

@voltagent/supabase@2.1.3

Patch Changes

• #1082 73cf1d3 Thanks @omeraplak! - Fix workflow state persistence parity across SQL adapters.

  This update persists and returns input, context, and top-level workflowState in workflow state operations. It also ensures suspended workflow state queries include events, output, and cancellation, and adds adapter migrations/column additions where needed.

Summary by CodeRabbit

• New Features

  • Added stream attach support for in-progress workflow executions with event replay capability.

• Bug Fixes

  • Fixed workflow execution filtering by persisted metadata across adapters.
  • Fixed workflow state persistence parity across SQL adapters.

• Chores

  • Updated core and adapter package versions for compatibility and maintenance improvements.

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	819efb8
Status:	✅  Deploy successful!
Preview URL:	https://618d63d9.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Removed a changeset and applied package version bumps and changelog additions across core, server, and SQL adapter packages; many example package.json files updated to reference the new versions. No source-code logic edits beyond changelog and manifest updates in this diff.

Changes

Cohort / File(s)	Summary
Removed Changeset /.changeset/workflow-state-parity-adapters.md, /.changeset/workflow-stream-attach-1081.md	Deleted changeset files describing workflow-state-parity and stream-attach features.
Core Package packages/core/package.json, packages/core/CHANGELOG.md	Version bump to 2.4.4 and changelog entries adding metadata filtering fixes and stream-attach/streaming entries.
Server Packages packages/server-core/..., packages/server-elysia/..., packages/server-hono/..., packages/serverless-hono/...	Version bumps (server-core 2.1.7, server-elysia 2.0.6, server-hono 2.0.7, serverless-hono 2.0.9) and changelog entries introducing SSE attach/replay for in-progress executions; dependency updates to match core.
SQL Adapter Packages packages/libsql/package.json, packages/postgres/package.json, packages/cloudflare-d1/package.json, packages/supabase/package.json, packages/*/CHANGELOG.md	Adapter version bumps (libsql/postgres/cloudflare-d1 → 2.1.2, supabase → 2.1.3) and changelog entries documenting workflow state persistence/parity and metadata/filter fixes; devDependency @voltagent/core updated.
Examples (many) examples/*/package.json	Bulk dependency bumps across examples: typically @voltagent/core ^2.4.3 → ^2.4.4; many examples also update @voltagent/libsql, @voltagent/postgres, @voltagent/supabase, and server-related packages to their new patch versions.
Changelog-only updates packages/*/CHANGELOG.md	Multiple packages had changelog entries added/updated to reflect metadata filtering, workflow-state parity fixes, and stream-attach/streaming features.

Sequence Diagram(s)

mermaid
sequenceDiagram
participant Client as Client (attach)
participant Server as Server\n(API /workflows/:id/executions/:executionId/stream)
participant Core as Core Workflow Engine
participant DB as SQL Adapter / DB

Client->>Server: GET /workflows/:id/executions/:executionId/stream\n(Last-Event-ID / fromSequence)
Server->>Core: Request attach + optional replay
Core->>DB: Read persisted execution state, events, input, context, cancellation
DB-->>Core: Return persisted state and events
Core-->>Server: Stream SSE events (replayed then live)
Server-->>Client: Deliver SSE stream (attach + replay)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix(memory): add workflow state parity for SQL adapters #1082 — Implements the workflow state persistence/parity fixes referenced in multiple changelogs.
• feat(workflow): add attach endpoint for in-progress streams #1084 — Introduced stream-attach / SSE stream attach behavior referenced in changelogs.
• fix(workflow): persist execution metadata and fix SQL metadata filters #1085 — Metadata/filtering fixes for workflow execution filtering documented across changelogs.

Suggested reviewers

• omeraplak

Poem

🐇 I hopped through changelogs, nibbling a line,

Input and state now settle in time.
Streams attach, events replay on cue,
SQL and core synchronized true-blue.
A tiny carrot patch — happy hop! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides comprehensive release notes with all affected packages, version bumps, and detailed patch change descriptions. However, it does not follow the repository's PR description template with sections like PR Checklist, Bugs/Features, and Notes for reviewers.	While the description is complete and informative for a Changesets-generated PR, consider clarifying whether template compliance is required for automated release PRs generated by GitHub Actions.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci(changesets): version packages' is a standard automated release commit that clearly describes the primary change—versioning and releasing packages via changesets.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/main

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 67 files

[coderabbitai]

🧹 Nitpick comments (1)

examples/with-nextjs-resumable-stream/package.json (1)

63-63: Stale repository.directory — should be examples/with-nextjs-resumable-stream

The repository.directory field reads "examples/with-nextjs-ai-elements", which doesn't match this package's actual path. This is pre-existing and unrelated to this PR's changes, but worth correcting since npm uses this field to link back to the monorepo directory.

✏️ 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, Update the
repository.directory field in package.json for the
examples/with-nextjs-resumable-stream package: locate the repository object and
change repository.directory from "examples/with-nextjs-ai-elements" to the
correct path "examples/with-nextjs-resumable-stream" so the package points to
its actual monorepo directory.

🤖 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-nextjs-resumable-stream/package.json`:
- Line 63: Update the repository.directory field in package.json for the
examples/with-nextjs-resumable-stream package: locate the repository object and
change repository.directory from "examples/with-nextjs-ai-elements" to the
correct path "examples/with-nextjs-resumable-stream" so the package points to
its actual monorepo directory.

[coderabbitai]

🧹 Nitpick comments (1)

packages/serverless-hono/package.json (1)

4-8: LGTM — version bump and server-core dependency update are correct.

One pre-existing nuance worth noting: peerDependencies["@voltagent/server-core"] remains "^2.0.0" while dependencies["@voltagent/server-core"] is now "^2.1.7". A consumer pinned to server-core ^2.0.x would satisfy the peer constraint but miss the actual minimum required version. This gap predates this PR (it was ^2.1.4 vs ^2.0.0 before), but it continues to widen with each direct-dep bump. Consider aligning the peerDependency floor to the minimum functionally required version in a follow-up.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/serverless-hono/package.json` around lines 4 - 8, The
peerDependencies floor for "@voltagent/server-core" is out of sync with the
actual dependency version; update the peerDependencies entry for
"@voltagent/server-core" to match the minimum required version used in
dependencies (i.e., change the peer dependency from "^2.0.0" to the same semver
range as dependencies, e.g. "^2.1.7") so consumers cannot satisfy the peer
constraint with an older incompatible 2.0.x release; update the package.json
peerDependencies block accordingly and run a quick install/test to ensure
compatibility.

🤖 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/serverless-hono/package.json`:
- Around line 4-8: The peerDependencies floor for "@voltagent/server-core" is
out of sync with the actual dependency version; update the peerDependencies
entry for "@voltagent/server-core" to match the minimum required version used in
dependencies (i.e., change the peer dependency from "^2.0.0" to the same semver
range as dependencies, e.g. "^2.1.7") so consumers cannot satisfy the peer
constraint with an older incompatible 2.0.x release; update the package.json
peerDependencies block accordingly and run a quick install/test to ensure
compatibility.