Conversation
Deploying voltagent with
|
| Latest commit: |
6df0f82
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a1e48fe6.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (85)
💤 Files with no reviewable changes (1)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (69)
📝 WalkthroughWalkthroughRemoved a changeset file, added changelog entries and package version bumps for Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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.
Actionable comments posted: 1
🧹 Nitpick comments (1)
examples/with-zapier-mcp/package.json (1)
7-7: Consider using^for consistency with other examples.This file uses tilde (
~2.6.7) for@voltagent/corewhile all other example packages in this PR use caret (^2.6.7). The tilde restricts updates to patch versions only, whereas other dependencies in this same file (e.g.,@voltagent/libsql,ai,zod) use caret.♻️ Suggested change for consistency
- "@voltagent/core": "~2.6.7", + "@voltagent/core": "^2.6.7",🤖 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 for "@voltagent/core" uses a tilde specifier "~2.6.7" which is inconsistent with other example packages that use caret; update the version specifier for "@voltagent/core" in package.json from "~2.6.7" to "^2.6.7" so it matches the caret style used by the other dependencies (e.g., "@voltagent/libsql", "ai", "zod").
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/server-core/package.json`:
- Around line 4-7: The package.json declares "@voltagent/core" at runtime as
"^2.6.7" but the peerDependencies still allow "^2.0.0", which can let consumers
install incompatible older core versions; update the peerDependencies entry for
"@voltagent/core" to "^2.6.7" so the peer floor matches the runtime dependency
and ensures the memory.options.readOnly feature from `@voltagent/core`@2.6.7 is
available to consumers.
---
Nitpick comments:
In `@examples/with-zapier-mcp/package.json`:
- Line 7: The dependency for "@voltagent/core" uses a tilde specifier "~2.6.7"
which is inconsistent with other example packages that use caret; update the
version specifier for "@voltagent/core" in package.json from "~2.6.7" to
"^2.6.7" so it matches the caret style used by the other dependencies (e.g.,
"@voltagent/libsql", "ai", "zod").
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 17803e4d-3db1-45b9-8496-42bc1449a24a
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (85)
.changeset/read-only-memory-mode.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-chat-sdk/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-feedback/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-middleware/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-retries-fallback/package.jsonexamples/with-retrieval/package.jsonexamples/with-slack/package.jsonexamples/with-subagents/package.jsonexamples/with-summarization/package.jsonexamples/with-supabase/package.jsonexamples/with-tavily-search/package.jsonexamples/with-thinking-tool/package.jsonexamples/with-tool-routing/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-chain/package.jsonexamples/with-workflow/package.jsonexamples/with-working-memory/package.jsonexamples/with-workspace/package.jsonexamples/with-youtube-to-blog/package.jsonexamples/with-zapier-mcp/package.jsonpackages/core/CHANGELOG.mdpackages/core/package.jsonpackages/e2e/package.jsonpackages/server-core/CHANGELOG.mdpackages/server-core/package.json
💤 Files with no reviewable changes (1)
- .changeset/read-only-memory-mode.md
| "version": "2.1.10", | ||
| "dependencies": { | ||
| "@modelcontextprotocol/sdk": "^1.12.1", | ||
| "@voltagent/core": "^2.6.6", | ||
| "@voltagent/core": "^2.6.7", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== packages/server-core/package.json =="
sed -n '1,120p' packages/server-core/package.json
echo
echo "== server-core references to `@voltagent/core` =="
rg -n --glob 'packages/server-core/**' '@voltagent/core'
echo
echo "== readOnly-related changes in core/server-core =="
rg -n --glob 'packages/core/**' --glob 'packages/server-core/**' 'readOnly|memory\.options'Repository: VoltAgent/voltagent
Length of output: 20448
Raise the @voltagent/core peer floor to ^2.6.7.
Line 7 bumps the runtime dependency to ^2.6.7, but the peer dependency on line 49 still allows ^2.0.0. This release adds the memory.options.readOnly feature (per CHANGELOG), which is newly implemented in @voltagent/core@2.6.7. The current peer range allows consumers to install @voltagent/server-core@2.1.10 alongside older core versions that do not support this feature, resulting in broken behavior without a warning.
Update the peer dependency to ^2.6.7 to match the runtime requirement.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/server-core/package.json` around lines 4 - 7, The package.json
declares "@voltagent/core" at runtime as "^2.6.7" but the peerDependencies still
allow "^2.0.0", which can let consumers install incompatible older core
versions; update the peerDependencies entry for "@voltagent/core" to "^2.6.7" so
the peer floor matches the runtime dependency and ensures the
memory.options.readOnly feature from `@voltagent/core`@2.6.7 is available to
consumers.
320212a to
6df0f82
Compare
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.7
Patch Changes
#1141
faa5023Thanks @omeraplak! - feat: add per-call memory read-only mode viamemory.options.readOnly.When
readOnlyis enabled, the agent still reads conversation context and working memory, but skips memory writes for the current call.What changes in read-only mode:
update_working_memory,clear_working_memory).get_working_memory).@voltagent/server-corenow acceptsmemory.options.readOnlyin request schema/options parsing.Before
After
#1142
0f7ee7cThanks @SergioChan! - fix(core): avoid duplicating stdout/stderr stream content in sandbox summary metadata@voltagent/server-core@2.1.10
Patch Changes
#1141
faa5023Thanks @omeraplak! - feat: add per-call memory read-only mode viamemory.options.readOnly.When
readOnlyis enabled, the agent still reads conversation context and working memory, but skips memory writes for the current call.What changes in read-only mode:
update_working_memory,clear_working_memory).get_working_memory).@voltagent/server-corenow acceptsmemory.options.readOnlyin request schema/options parsing.Before
After
Updated dependencies [
faa5023,0f7ee7c]:Summary by CodeRabbit
Release Notes
New Features
memory.options.readOnly. Enables reading conversation context and working memory while preventing writes to conversation history, step checkpoints, background input, and working memory update/clear operations.Chores