The Wire · Showcase
WORKFLOW SOCKET FIX STOPS CI CRASHES, TURBOREPO HARDENS AGAINST PANICS
By RepoJournal · Filed · About Vercel
The workflow team fixed a critical CI failure where stale socket files caused ECONNREFUSED crashes on Vercel, while turborepo removed unwrap() calls across five crates to eliminate panic paths in production.
The workflow socket fix [1] resolves a nasty bug where cached `.next/cache/workflow-socket.json` files persisted across Vercel CI builds, causing the webpack loader to connect to dead processes and crash with ECONNREFUSED. Moving the socket file to `.next/workflow-socket.json` (outside the preserved cache directory) eliminates the inter-build contamination entirely. Meanwhile, turborepo is systematically hardening its Rust codebase by removing unwrap() and expect() calls across the API mock [2], API client [3], microfrontends proxy [4], run summary [5], and task executor [6] crates. These are boundary paths where panics have no business happening; failures now surface as typed errors instead. On the Next.js side, rootParams shipped enabled by default [7], removing the config flag and opening the door for broader adoption once route handlers and Server Actions support lands. The Next.js team also added an instrumentation client inject option [8] to let next.config.js drive bootstrap code without touching user source files. AI SDK dropped missing READMEs for the otel and mcp packages [9] [10], and fixed a subtle Google provider bug where tool call args wouldn't form because the code assumed `willContinue` was always present when it could be absent [11]. Google's new managed agents feature is now supported in the SDK [12].
Action items
- → Merge workflow socket fix before next CI run to stop ECONNREFUSED crashes vercel/workflow [immediate]
- → Exit prerelease mode on workflow and ai when ready for stable release vercel/workflow [plan]
- → Test rootParams in your Next.js app now that it's enabled by default vercel/next.js [monitor]
- → Update to latest AI SDK if using Google provider with tool calls vercel/ai [plan]
References
- [1] fix(next): move workflow-socket.json out of .next/cache to fix ECONNREFUSED ↗ vercel/workflow
- [2] fix: Remove Vercel API mock unwrap usage ↗ vercel/turborepo
- [3] fix: Remove api client unwrap usage (#12881) vercel/turborepo
- [4] fix: Remove microfrontends proxy unwrap usage (#12880) vercel/turborepo
- [5] fix: Remove run summary expect usage (#12879) vercel/turborepo
- [6] fix: Remove task executor unwrap usage (#12878) vercel/turborepo
- [7] Enable rootParams by default (#93863) vercel/next.js
- [8] Add nextConfig.instrumentationClientInject ↗ vercel/next.js
- [9] chore: add readme for @ai-sdk/otel ↗ vercel/ai
- [10] chore: add readme for @ai-sdk/mcp ↗ vercel/ai
- [11] fix(google): fix streaming tool call args ↗ vercel/ai
- [12] feat(provider/google): add support for managed agents in the Interactions API ↗ vercel/ai
FAQ
- What changed in Vercel on May 20, 2026?
- The workflow team fixed a critical CI failure where stale socket files caused ECONNREFUSED crashes on Vercel, while turborepo removed unwrap() calls across five crates to eliminate panic paths in production.
- What should Vercel teams do about it?
- Merge workflow socket fix before next CI run to stop ECONNREFUSED crashes • Exit prerelease mode on workflow and ai when ready for stable release • Test rootParams in your Next.js app now that it's enabled by default
- Which Vercel repositories shipped on May 20, 2026?
- vercel/workflow, vercel/turborepo, vercel/next.js, vercel/ai