Skip to content

ci(changesets): version packages#1090

Merged
omeraplak merged 1 commit intomainfrom
changeset-release/main
Feb 20, 2026
Merged

ci(changesets): version packages#1090
omeraplak merged 1 commit intomainfrom
changeset-release/main

Conversation

@voltagent-bot
Copy link
Copy Markdown
Member

@voltagent-bot voltagent-bot commented Feb 20, 2026

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.4.5

Patch Changes

  • #1088 bb7f3f9 Thanks @omeraplak! - fix: preserve stream output after startup probe on ReadableStream providers

    Agent.streamText() and Agent.streamObject() now probe stream startup using a tee'd branch instead of consuming and cancelling the original fullStream.

    This prevents early stream interruption where some providers could emit reasoning events and then terminate before forwarding final text-delta output to consumers.


Summary by cubic

Release @voltagent/core 2.4.5, fixing startup probing on ReadableStream providers to preserve stream output and prevent early termination. Updates example apps and lockfile to reference 2.4.5.

  • Bug Fixes

    • Agent.streamText() and Agent.streamObject() now probe startup via a tee’d branch, avoiding consumption/cancel of the original stream and preventing lost text-delta output.
  • Dependencies

    • Bump @voltagent/core to 2.4.5 across all examples; update core CHANGELOG and pnpm-lock.

Written for commit 85eda68. Summary will update on new commits.

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an issue where stream output could be interrupted prematurely during startup probes in streaming operations.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Feb 20, 2026

Deploying voltagent with  Cloudflare Pages  Cloudflare Pages

Latest commit: 85eda68
Status: ✅  Deploy successful!
Preview URL: https://6de4c3e1.voltagent.pages.dev
Branch Preview URL: https://changeset-release-main.voltagent.pages.dev

View logs

@joggrbot

This comment has been minimized.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 20, 2026

📝 Walkthrough

Walkthrough

This pull request releases version 2.4.5 of @voltagent/core with a bugfix for stream handling in ReadableStream providers. The version bump is propagated across 60+ example projects, a changeset entry is removed, and the core package changelog is updated to document the fix.

Changes

Cohort / File(s) Summary
Changeset Removal
.changeset/green-lizards-wave.md
Removed changeset entry documenting the 2.4.5 patch release.
Core Package Release
packages/core/package.json, packages/core/CHANGELOG.md
Bumped @voltagent/core version from 2.4.4 to 2.4.5 and added changelog entry for stream output preservation fix in startup probe handling.
Example Dependencies
examples/*/package.json (60+ files)
Updated @voltagent/core dependency from ^2.4.4 to ^2.4.5 across all example projects including base, github-repo-analyzer, next-js-chatbot, with-mcp, with-anthropic, and others.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A patch hops through the stream so bright,
No more interruptions in the night!
Version bumps cascade with glee,
Examples dance in unity—
The startup probe now flows just right! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The PR title clearly summarizes the main change: a version release automation action that updates package versions and dependencies to 2.4.5.
Description check ✅ Passed The PR description comprehensively explains the automated release context, the specific bug fix in @voltagent/core@2.4.5, and all affected packages, meeting the key informational requirements.
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

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

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

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
examples/with-nextjs-resumable-stream/package.json (1)

63-63: Stale repository.directory value — points to the wrong example folder.

The directory field says "examples/with-nextjs-ai-elements" but this package lives in examples/with-nextjs-resumable-stream. This is a pre-existing copy-paste leftover and not introduced by this PR, but it's worth correcting to keep npm metadata accurate.

🛠️ 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
package.json contains a stale repository.directory value referencing
"examples/with-nextjs-ai-elements"; update the "directory" field in package.json
to the correct path "examples/with-nextjs-resumable-stream" so the npm metadata
points to this package's actual folder (locate the "directory" JSON key in
package.json and replace its string value).
examples/with-zapier-mcp/package.json (1)

7-7: Consider normalizing version range operator from ~ to ^ for consistency.

This package uses ~2.4.5 (patch-level range: >=2.4.5 <2.5.0), while every other example in the repo uses ^2.4.5 (minor+patch range: >=2.4.5 <3.0.0). Changesets preserved the pre-existing ~ operator, but the divergence could cause this example to lag behind future minor releases while all others auto-update.

🔧 Suggested fix
-    "@voltagent/core": "~2.4.5",
+    "@voltagent/core": "^2.4.5",
🤖 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, The dependency declaration
for "@voltagent/core" uses a patch-range operator "~2.4.5" which diverges from
the rest of examples; update the version string in
examples/with-zapier-mcp/package.json from "~2.4.5" to "^2.4.5" to normalize
semver behavior, then regenerate the lockfile (npm/yarn/pnpm install) so the
lock reflects the change and run the example's install/tests to ensure nothing
breaks.
🤖 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: The package.json contains a stale repository.directory value
referencing "examples/with-nextjs-ai-elements"; update the "directory" field in
package.json to the correct path "examples/with-nextjs-resumable-stream" so the
npm metadata points to this package's actual folder (locate the "directory" JSON
key in package.json and replace its string value).

In `@examples/with-zapier-mcp/package.json`:
- Line 7: The dependency declaration for "@voltagent/core" uses a patch-range
operator "~2.4.5" which diverges from the rest of examples; update the version
string in examples/with-zapier-mcp/package.json from "~2.4.5" to "^2.4.5" to
normalize semver behavior, then regenerate the lockfile (npm/yarn/pnpm install)
so the lock reflects the change and run the example's install/tests to ensure
nothing breaks.

@omeraplak omeraplak merged commit 6c89e35 into main Feb 20, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants