Conversation
Deploying voltagent with
|
| Latest commit: |
85eda68
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6de4c3e1.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughThis pull request releases version 2.4.5 of Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 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)
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. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (2)
examples/with-nextjs-resumable-stream/package.json (1)
63-63: Stalerepository.directoryvalue — points to the wrong example folder.The
directoryfield says"examples/with-nextjs-ai-elements"but this package lives inexamples/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.
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
bb7f3f9Thanks @omeraplak! - fix: preserve stream output after startup probe on ReadableStream providersAgent.streamText()andAgent.streamObject()now probe stream startup using a tee'd branch instead of consuming and cancelling the originalfullStream.This prevents early stream interruption where some providers could emit reasoning events and then terminate before forwarding final
text-deltaoutput 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
Dependencies
Written for commit 85eda68. Summary will update on new commits.
Summary by CodeRabbit