vercel-upgrade-migration

# Vercel Upgrade Migration ## Overview Safely upgrade Vercel CLI, Node.js runtime versions, and framework versions (especially Next.js) on Vercel. Covers breaking change detection, vercel.json schema changes, and rollback strategy. ## Current State !`vercel --version 2>/dev/null || echo 'Vercel CLI not installed'` !`node --version 2>/dev/null || echo 'N/A'` !`cat package.json 2>/dev/null | jq -r '.dependencies.next // "no next.js"' 2>/dev/null || echo 'N/A'` ## Prerequisites - Current Vercel CLI installed - Git for version control - Test suite available - Preview deployment for testing ## Instructions ### Step 1: Check Current Versions ```bash # Current CLI version vercel --version # Current Node.js runtime on Vercel cat package.json | jq '.engines.node' # Or check vercel.json cat vercel.json | jq '.functions' # Check for available CLI updates npm outdated -g vercel # Check framework version npm ls next react ``` ### Step 2: Upgrade Vercel CLI ```bash # Upgrade to latest npm install -g vercel@latest # Or specific version npm install -g vercel@39 # Verify vercel --version ``` **CLI breaking changes to watch for:** - v28+: `vercel env pull` output format changed - v32+: `vercel dev` uses new function runtime - v37+: `vercel.json` `builds` property deprecated in favor of framework detection ### Step 3: Upgrade Node.js Runtime ```json // package.json — specify the Node.js version { "engines": { "node": "20.x" } } ``` Available runtimes on Vercel: | Runtime |...