AI SDK minor/major drift between ai and its satellite packages produces errors that look like your code is wrong: parse failures, type errors, missing exports.

The v7 line-up (verified on npm 2026-09-26):
- ai: 7.0.x
- @ai-sdk/react: 4.0.x (declares ai 7.0.x as a dependency)
- @ai-sdk/svelte: 5.0.x, @ai-sdk/vue: 4.0.x, @ai-sdk/angular: 3.0.x
- @ai-sdk/openai: 4.0.x, @ai-sdk/provider: 4.0.x, @ai-sdk/provider-utils: 5.0.x
- @ai-sdk/otel: pairs with ai 7 for telemetry

Rules:
1. Upgrade ai and every @ai-sdk/* package in the same commit. npm install ai@latest @ai-sdk/react@latest @ai-sdk/openai@latest @ai-sdk/otel@latest.
2. Never hand-pin one package to a different major than the rest. ai@7 with @ai-sdk/openai@3 is a broken combo; the LanguageModel spec version will mismatch and you get UnsupportedModelVersionError or Model is not assignable to type LanguageModelV1.
3. The framework UI packages have independent majors, so do not expect @ai-sdk/react@7 to exist. Read the peer/dependency, not the major number.
4. After upgrading, run the codemods: npx @ai-sdk/codemod v7 (or v6/v5 if jumping from older). Codemods cover renames; they do not cover semantic changes like prepareStep carry-forward, so read the migration guide for your jump.
5. Lockfiles are the source of truth. When a teammate reports a stream error you cannot reproduce, diff the lockfile first.
6. zod must be ^4.1.8+ alongside AI SDK 5+. An old zod with a new ai is a TypeScript performance and type-correctness hazard.