fix(deps): peer the AI SDK v7 provider majors, not the v6 ones - #37
Merged
Conversation
Every provider peer range was one major behind the SDK this package depends on: with `ai` at ^7.0.66, the v3 line (v2 for deepseek and openai-compatible, v4 for bedrock/vertex, v3 for workers-ai-provider) speaks ai v6, so a consumer following the declared ranges installs a provider that cannot talk to the core — and npm refuses to resolve the tree once anything else pulls a v7-era provider in. The ranges now match what the devDependencies install and CI has been testing against since the AI SDK v7 bump. Same fix as the browser sibling. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011FKop4At26QqqkwVGEjJur
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every provider peer range is one major behind the SDK this package depends on. With
aiat^7.0.66, the declared ranges point at provider majors that target ai v6 — so a consumer who installs exactly what the peers ask for gets a provider that cannot talk to the core, and npm refuses to resolve the tree as soon as anything else pulls a v7-era provider in.Found in the browser sibling first (dudko-dev/agent-web#5, #6) while wiring its demo to the published package; this repo has the identical drift.
What
@ai-sdk/amazon-bedrock^4.0.97^5.0.0@ai-sdk/anthropic^3.0.72^4.0.0@ai-sdk/azure^3.0.55^4.0.0@ai-sdk/deepseek^2.0.30^3.0.0@ai-sdk/google^3.0.65^4.0.0@ai-sdk/google-vertex^4.0.113^5.0.0@ai-sdk/openai^3.0.54^4.0.0@ai-sdk/openai-compatible^2.0.42^3.0.0@ai-sdk/xai^3.0.84^4.0.0workers-ai-provider^3.1.13^4.0.0These are the majors the
devDependenciesinstall, i.e. exactly what CI has been testing against since the AI SDK v7 bump. No source changes;typecheck,format:check,build,test(167 passing) are green. Version bumped to0.0.23so the release workflow publishes it.Generated by Claude Code