ci(changesets): version packages - #1393
Conversation
Deploying voltagent with
|
| Latest commit: |
b4beb36
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8ae9d5ba.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (14)
🚧 Files skipped from review as they are similar to previous changes (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe release updates ChangesPackage release updates
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This release PR updates package versions, changelogs, documentation, and example dependency ranges; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description accurately explains the automated release purpose and lists all package versions and release notes. However, it does not follow the repository template because it omits the PR checklist, current behavior, new behavior, issue reference, and reviewer notes sections. Resolution Add the required template sections and complete the applicable checklist items. State the current behavior, new behavior, issue reference or not applicable, and notes for reviewers. If this automated release format is intentional, document the repository exception for Changesets release PRs. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (14 skipped: 14 unsupported.)
✨ 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 |
fb8db39 to
4d11251
Compare
4d11251 to
b4beb36
Compare
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 101 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/mcp-server/package.json">
<violation number="1" location="packages/mcp-server/package.json:10">
P2: mcp-server@2.2.0's advertised annotations feature reads `tool.mcp` from @voltagent/core, a field only added in core 2.10.0, but peerDependencies still allows `^2.0.0`. Consumers pinned to core <2.10.0 will install mcp-server 2.2.0 without any warning and silently lose MCP annotation forwarding. Raise the @voltagent/core peer range to `^2.10.0` so npm/pnpm surfaces the incompatibility instead.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| }, | ||
| "devDependencies": { | ||
| "@voltagent/core": "^2.9.2", | ||
| "@voltagent/core": "^2.10.0", |
There was a problem hiding this comment.
P2: mcp-server@2.2.0's advertised annotations feature reads tool.mcp from @voltagent/core, a field only added in core 2.10.0, but peerDependencies still allows ^2.0.0. Consumers pinned to core <2.10.0 will install mcp-server 2.2.0 without any warning and silently lose MCP annotation forwarding. Raise the @voltagent/core peer range to ^2.10.0 so npm/pnpm surfaces the incompatibility instead.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/mcp-server/package.json, line 10:
<comment>mcp-server@2.2.0's advertised annotations feature reads `tool.mcp` from @voltagent/core, a field only added in core 2.10.0, but peerDependencies still allows `^2.0.0`. Consumers pinned to core <2.10.0 will install mcp-server 2.2.0 without any warning and silently lose MCP annotation forwarding. Raise the @voltagent/core peer range to `^2.10.0` so npm/pnpm surfaces the incompatibility instead.</comment>
<file context>
@@ -1,13 +1,13 @@
},
"devDependencies": {
- "@voltagent/core": "^2.9.2",
+ "@voltagent/core": "^2.10.0",
"zod": "^3.25.76"
},
</file context>
2 participants
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.10.0
Minor Changes
9aedd49Thanks @omeraplak! - Add type-safe MCP annotations and metadata to tools and forward them through the MCP server adapter.Patch Changes
844939cThanks @Iams4kura! - Preserve JavaScript replacement tokens in simple template variable values.@voltagent/mcp-server@2.2.0
Minor Changes
9aedd49Thanks @omeraplak! - Add type-safe MCP annotations and metadata to tools and forward them through the MCP server adapter.@voltagent/ag-ui@1.0.8
Patch Changes
4f50e75Thanks @nuthalapativarun! - Add README documentation@voltagent/evals@2.0.5
Patch Changes
eca69b5Thanks @nuthalapativarun! - Add README documentation@voltagent/postgres@2.1.3
Patch Changes
1c98550Thanks @nuthalapativarun! - Add README documentation@voltagent/voltagent-memory@1.0.5
Patch Changes
80827c3Thanks @nuthalapativarun! - Add README documentationSummary by CodeRabbit
New Features
Documentation
Chores