Vercel AI SDK Major Version Mode: Plan a Rename and Migration
Use Vercel AI SDK's explicitly invoked contributor workflow for a major-release export rename, deprecation alias and matching migration note.
中文Setup for Claude Code (AI SDK contributor workflow)
Claude Code in a disposable AI SDK checkout with Node.js and pnpm as declared by the project. Invoke this contributor workflow explicitly for a major release.
- Open a scratch checkout of Vercel AI SDK at the GitHub revision below. Copy the full `skills/major-version-mode/` folder into `.claude/skills/major-version-mode/` and start a fresh Claude Code session.
- This is an internal contributor guide. Use it only with the AI SDK source layout and a disposable local checkout.
- Invoke /major-version-mode explicitly. Read the current release guidance and identify the next migration guide before proposing the edit.
Example task
Ask Claude Code to plan an explicitly authorized major-release rename of a fictional export `draftReply` to `prepareReply`. Include a deprecated alias and a short before-and-after import example. Check which import paths and tests need updating without changing a real release.Expected result
The plan keeps the old import working through the deprecated alias, demonstrates the new import and records the move in the migration guide. It does not imply that older provider spec versions must change.
Upstream documentation
Original SKILL.md on GitHub · Apache-2.0 license · Source reviewed
Frequently asked question
When should Vercel AI SDK's major version mode be used?
The source describes it for explicitly requested work on the next AI SDK major release. It supports migration guidance and controlled compatibility changes rather than silently activating for ordinary work.