fix(deps): peer the AI SDK v7 provider majors, not the v6 ones - #6
Merged
Merged
Conversation
Every @ai-sdk/* peer range was one major behind the SDK this package actually depends on: with `ai` at ^7.0.66, the v3 provider line (v2 for deepseek and openai-compatible) speaks ai v6, so a consumer following the ranges installs a provider that cannot talk to the core — and npm refuses to resolve the tree at all once anything else pulls a v7-era provider in. Found while pointing the demo at the published package. The ranges now match what the devDependencies install and CI has been testing against all along. 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
Follow-up to #5, which fixed the same class of problem for
@browser-ai/*but only for those two entries.Every
@ai-sdk/*peer range is one major behind the SDK this package depends on. Withaiat^7.0.66, the v3 provider line (v2 fordeepseek/openai-compatible) targets ai v6 — so a consumer who follows the declared ranges installs a provider that cannot talk to the core, and npm refuses to resolve the tree at all as soon as anything else pulls in a v7-era provider:Found the same way as #5 — pointing the sibling demo (dudko-dev/agent-web-react#3) at the published package.
What
@ai-sdk/anthropic^3.0.0^4.0.0@ai-sdk/deepseek^2.0.0^3.0.0@ai-sdk/google^3.0.0^4.0.0@ai-sdk/openai^3.0.0^4.0.0@ai-sdk/openai-compatible^2.0.0^3.0.0@ai-sdk/xai^3.0.0^4.0.0These are exactly the majors the
devDependenciesinstall, i.e. what CI has been testing against since the AI SDK v7 bump. No source changes;typecheck,format:check,build,test(89 passing) are green. Version bumped to0.0.11so the release workflow publishes it.Generated by Claude Code