Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 8468902 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe core package dependency on ChangesAIHubmix provider dependency update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other Merge Risk: ⚪ Minimal · up to The provider upgrade and release note have no identified issue requiring a fix before merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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.
All reported issues were addressed across 3 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Resolve pnpm-lock.yaml conflict by regenerating from upstream's lockfile with pnpm@8.10.5 and keeping only the aihubmix subtree changes (dropped the incidental rolldown / @oxc-project/types re-resolution). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Core's registry adapter only passes { apiKey } to createAihubmix, so these
options can't be configured through @voltagent/core.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR Checklist
What is the current behavior?
@voltagent/coredepends on@aihubmix/ai-sdk-provider@^1.0.1. Because it's a caret range, installs stay on1.0.x(the lockfile currently resolves to1.0.1) and never pick up the 2.x line, which has been available since Feb 2026.What is the new behavior?
Bumps the dependency to
^2.2.1. The public API that the model registry uses (createAihubmix→buildApiKeyProvider("createAihubmix", "aihubmix")) is unchanged, and 2.x still targets AI SDK v6 /LanguageModelV3. Model routing is the same:claude-*goes to Anthropic Messages,gemini*goes to Gemini native, and everything else goes to OpenAI-compatible.What users get:
@ai-sdk/openai-compatible, which fixes a Zod validation error on stream chunks)fetchis forwarded to Claude / Gemini / Responses models (before, only OpenAI-compatible models got it)Authorizationheader on Claude / Gemini requestsbaseURL/appCodesettingszodpeer range^3.25.0 || ^4.0.0, which matches core'sNotes for reviewers
pnpm install --lockfile-onlywith the repo's pinnedpnpm@8.10.5. Besides the aihubmix subtree, pnpm also re-resolved a few transitiverolldown/@oxc-project/typespatch versions. I didn't touch those directly; I'm happy to drop them if you'd rather keep the lockfile diff minimal.pnpm install --frozen-lockfile,tsc --noEmitinpackages/core(0 errors), andvitest runonagent.spec.ts,model-provider-registry-minimax.spec.tsandmemory/adapters/embedding/ai-sdk.spec.ts(141 passed). Also checked thatresolveLanguageModel("aihubmix/gpt-4o-mini")returns av3model.Disclosure: I maintain
@aihubmix/ai-sdk-provider.🤖 Generated with Claude Code
Summary by cubic
Updates
@voltagent/corefrom@aihubmix/ai-sdk-provider^1.0.1to^2.2.1so it receives the provider’s 2.x fixes without changing the existingcreateAihubmixintegration.fetchto Claude, Gemini, and Responses models.Authorizationheaders from Claude and Gemini requests.apiKey-only core configuration;baseURLandappCodeare not exposed through the registry adapter.Written for commit 8468902. Summary will update on new commits.
Summary by CodeRabbit