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/core@2.6.1

Patch Changes

• #1103 edd7181 Thanks @omeraplak! - fix: preserve getter-based fullStream tee behavior after startup probing in streamText/streamObject

  This prevents TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is locked when SDK consumers iterate result.fullStream while other result accessors (such as result.text or UI stream helpers) are also consuming the stream.

---

Summary by cubic

Versioned packages for a patch release: @voltagent/core 2.6.1 fixes concurrent stream access to avoid ReadableStream lock errors, and all examples now depend on the new version.

• Bug Fixes

  • Preserve getter-based result.fullStream tee behavior after startup probing in streamText/streamObject, preventing ERR_INVALID_STATE when fullStream is iterated alongside result.text or UI stream helpers.

• Dependencies

  • Bump @voltagent/core to ^2.6.1 across examples, update pnpm-lock.yaml, and remove the consumed changeset file.

^{Written for commit bd8137e. Summary will update on new commits.}

Summary by CodeRabbit

• Bug Fixes

  • Resolved an issue where ReadableStream would lock when consumers access fullStream while other result accessors are concurrently active in streamText/streamObject operations.

• Chores

  • Updated all example projects to the latest version.

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	bd8137e
Status:	✅  Deploy successful!
Preview URL:	https://3b1c49c5.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR bumps the @voltagent/core package version from 2.6.0 to 2.6.1 across the monorepo. The patch fixes stream locking issues in streamText/streamObject by preserving getter-based fullStream tee behavior during startup probing, preventing ReadableStream locked errors.

Changes

Cohort / File(s)	Summary
Changeset Removal .changeset/witty-cameras-smile.md	Deleted changelog entry documenting the 2.6.1 patch fix.
Core Package Updates packages/core/package.json, packages/core/CHANGELOG.md	Version bumped from 2.6.0 to 2.6.1; new changelog entry added documenting the fullStream tee preservation fix for startup probing.
Example Dependencies examples/*/package.json (62 files)	Updated @voltagent/core dependency from ^2.6.0 to ^2.6.1 across all example projects.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix(core): avoid ReadableStream lock after fullStream startup probe #1103: Addresses the same core fix to preserve getter-based fullStream teeing after startup probing in streamText/streamObject.
• ci(changesets): version packages #1090: Related to the same stream-handling fix preventing ReadableStream locked errors during startup probing.

Poem

🐰 A hop, a skip, version's here so slight,
From 2.6.0 to 2.6.1, streams flow just right,
No locks, no tears, the tees dance free,
A rabbit's delight in consistency! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci(changesets): version packages' accurately describes the PR's purpose as a CI-driven version bump via the Changesets GitHub action.
Description check	✅ Passed	The PR description is comprehensive, explaining the auto-generated release notes, the specific patch fix, and dependencies updated across examples.
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 82 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

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

63-63: ⚠️ Potential issue | 🟡 Minor

Stale repository.directory — points to the wrong example.

The directory field references examples/with-nextjs-ai-elements, but this package lives at examples/with-nextjs-resumable-stream. While pre-existing, it can mislead tooling and package-registry links.

🔧 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
package.json "repository.directory" field value to the correct example folder:
change the current "examples/with-nextjs-ai-elements" string to
"examples/with-nextjs-resumable-stream" so the "directory" key accurately points
to this package; verify the "repository" object remains valid after the update.

🧹 Nitpick comments (1)

examples/with-zapier-mcp/package.json (1)

7-7: Inconsistent semver range: ~ vs ^ used across all other examples.

Every other example in this PR uses "@voltagent/core": "^2.6.1" (caret), while this package uses "~2.6.1" (tilde). The tilde constrains resolution to >=2.6.1 <2.7.0 (patch-only), while caret allows >=2.6.1 <3.0.0. This pre-existing inconsistency means future minor core releases won't be auto-resolved here. Consider aligning to ^ for consistency with the rest of the monorepo.

Based on learnings: Follow the monorepo structure — changes may impact multiple packages.

♻️ Proposed fix

-    "@voltagent/core": "~2.6.1",
+    "@voltagent/core": "^2.6.1",

🤖 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
semver for "@voltagent/core" in examples/with-zapier-mcp/package.json from
"~2.6.1" to "^2.6.1" to match the rest of the examples; locate the dependency
entry that currently reads "@voltagent/core": "~2.6.1" and change the tilde to a
caret so minor releases (>=2.6.1 <3.0.0) are allowed and consistent across the
monorepo.

🤖 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-nextjs-resumable-stream/package.json`:
- Line 63: Update the package.json "repository.directory" field value to the
correct example folder: change the current "examples/with-nextjs-ai-elements"
string to "examples/with-nextjs-resumable-stream" so the "directory" key
accurately points to this package; verify the "repository" object remains valid
after the update.

---

Nitpick comments:
In `@examples/with-zapier-mcp/package.json`:
- Line 7: Update the dependency semver for "@voltagent/core" in
examples/with-zapier-mcp/package.json from "~2.6.1" to "^2.6.1" to match the
rest of the examples; locate the dependency entry that currently reads
"@voltagent/core": "~2.6.1" and change the tilde to a caret so minor releases
(>=2.6.1 <3.0.0) are allowed and consistent across the monorepo.