The Wire · Showcase
AI GATEWAY RULES HIT CLI, NEXT.JS FIXES SUSPENSE FLASH, WORKFLOW PATCHES CRITICAL ESBUILD VULN
By RepoJournal · Filed · About Vercel
Vercel shipped production-ready CLI commands for AI Gateway routing rules, while Next.js and Turborepo shipped fixes for cache handling and Windows PTY corruption that teams should pull immediately.
The AI Gateway rules commands [1] landed in the CLI, letting customers manage routing denials and rewrites directly from `vc` without api-key hops, authenticated through team ACL. Simultaneously, the AI SDK fixed a critical error classification bug [2] where gateway policy denials were surfacing as 500-class `GatewayInternalServerError` instead of the correct 403 `GatewayForbiddenError`, a fix that ships in today's canary releases [3] [4]. On the Next.js side, the streaming dev render now avoids premature Suspense fallback flashes when caches are warm [5], matching production behavior and shipping in v16.3.0-canary.51 [6]. Turborepo shipped three fixes: symlinked cache outputs now work without warnings [7], pnpm Docker prunes no longer surface stale workspace patches [8], and Windows ConPTY cursor queries no longer corrupt task output [9]. The critical move: Workflow patched a high-severity esbuild advisory (GHSA-gv7w-rqvm-qjhr) upgrading to 0.28.1 [10], and the team flagged this must be backported to the 4.x stable branch immediately. Observability surfaces in Workflow now render attributes properly [11], showing `attr_set` events on timelines and run-level attributes with reserved key badging.
Action items
- → Backport esbuild 0.28.1 upgrade (GHSA-gv7w-rqvm-qjhr) to workflow stable/4.x immediately post-merge vercel/workflow [immediate]
- → Upgrade to Next.js v16.3.0-canary.51 to fix Suspense fallback flashes in dev vercel/next.js [plan]
- → Pull latest Turborepo for symlink caching and Windows PTY fixes vercel/turborepo [plan]
- → Test AI SDK canary releases with updated GatewayForbiddenError handling vercel/ai [monitor]
References
- [1] [cli] Add `vercel ai-gateway rules` add/list/edit/remove commands ↗ vercel/vercel
- [2] fix(provider/gateway): map forbidden error responses to GatewayForbiddenError ↗ vercel/ai
- [3] @ai-sdk/[email protected] ↗ vercel/ai
- [4] @ai-sdk/[email protected] ↗ vercel/ai
- [5] Avoid a premature Suspense fallback flash in the streaming dev render ↗ vercel/next.js
- [6] v16.3.0-canary.51 ↗ vercel/next.js
- [7] fix: Cache outputs through internal symlinks ↗ vercel/turborepo
- [8] fix: Filter pruned pnpm workspace patches (#13075) vercel/turborepo
- [9] fix: Prevent ConPTY cursor query output ↗ vercel/turborepo
- [10] fix(deps): upgrade esbuild to 0.28.1 (GHSA-gv7w-rqvm-qjhr) ↗ vercel/workflow
- [11] Render attr_set events and run attributes in the observability UI ↗ vercel/workflow
FAQ
- What changed in Vercel on June 14, 2026?
- Vercel shipped production-ready CLI commands for AI Gateway routing rules, while Next.js and Turborepo shipped fixes for cache handling and Windows PTY corruption that teams should pull immediately.
- What should Vercel teams do about it?
- Backport esbuild 0.28.1 upgrade (GHSA-gv7w-rqvm-qjhr) to workflow stable/4.x immediately post-merge • Upgrade to Next.js v16.3.0-canary.51 to fix Suspense fallback flashes in dev • Pull latest Turborepo for symlink caching and Windows PTY fixes
- Which Vercel repositories shipped on June 14, 2026?
- vercel/vercel, vercel/ai, vercel/next.js, vercel/turborepo, vercel/workflow