The Wire · Showcase
WORKFLOW RUNTIME FIXES CORRUPTION BUGS, NEXT.JS CUTS BUNDLE SIZE
By RepoJournal · Filed · About Vercel
Workflow's event-log replay just got three critical defense-in-depth patches that close corruption vectors, while Next.js ships runtime wins and Partial Prefetching defaults.
The workflow team shipped back-to-back fixes for replay divergence and data corruption [1][2][3][4]. The most immediate: exclusive file writes were exposing partial contents before atomic publication [1], and zero-byte ref responses were corrupting the in-memory event log [2]. A third fix defers encryption-key lookups until stream data is actually read, preventing cascading failures on key resolution timeouts [3]. All three are patch-level and should roll out silently. Next.js cut the Turbopack runtime by 2KB [6] and shipped global config for Partial Prefetching [7][8], which now defaults to App Shell only on dynamic pages. The AI SDK added OpenAI tool namespaces [9] and Google Vertex speech-to-text support [10]. The CLI now gates maxDuration limits behind an environment variable [11][12], letting teams override the 900-second client-side cap at build time. A batch of infrastructure upgrades landed: devalue 5.8.1 to address npm audit findings [5], and vercel 54.10.0 ships non-managed Connex creation [13].
Action items
- → Deploy workflow patches to staging immediately - three replay corruption fixes stacked vercel/workflow [immediate]
- → Pull Next.js main to get Partial Prefetching defaults and runtime wins vercel/next.js [plan]
- → Upgrade devalue to 5.8.1 in workflow dependencies vercel/workflow [plan]
- → Monitor Turbopack sourcemap content-hashing on production builds with sourcemaps enabled vercel/next.js [monitor]
References
- [1] [codex] Fix partial world-local exclusive writes ↗ vercel/workflow
- [2] [world-vercel] Validate ref resolve responses before use ↗ vercel/workflow
- [3] [codex] Handle lazy stream key request failures ↗ vercel/workflow
- [4] [core] Forward-port: preserve event-log order in hook-vs-sleep replay races (#2171) ↗ vercel/workflow
- [5] fix: bump devalue to 5.8.1 ↗ vercel/workflow
- [6] [turbopack] Remove WebAssembly helpers from the default runtime (#94373) vercel/next.js
- [7] Add global config to enable Partial Prefetching ↗ vercel/next.js
- [8] Partial Prefetching: Default to App Shell only ↗ vercel/next.js
- [9] feat(openai): add namespaces for tool definitions ↗ vercel/ai
- [10] feat(provider/google-vertex): add Chirp speech-to-text (transcription) model support ↗ vercel/ai
- [11] feat(build-utils): gate client-side maxDuration upper bound behind env var (#16539) vercel/vercel
- [12] feat(build-utils): gate client-side maxDuration upper bound behind env var ↗ vercel/vercel
- [13] Support non-managed Connex connector creation ↗ vercel/vercel
FAQ
- What changed in Vercel on June 8, 2026?
- Workflow's event-log replay just got three critical defense-in-depth patches that close corruption vectors, while Next.js ships runtime wins and Partial Prefetching defaults.
- What should Vercel teams do about it?
- Deploy workflow patches to staging immediately - three replay corruption fixes stacked • Pull Next.js main to get Partial Prefetching defaults and runtime wins • Upgrade devalue to 5.8.1 in workflow dependencies
- Which Vercel repositories shipped on June 8, 2026?
- vercel/workflow, vercel/next.js, vercel/ai, vercel/vercel