RepoJournal
Vercel

@vercel

Next.js + the Vercel platform - frontend infrastructure for the web

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

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].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] [codex] Fix partial world-local exclusive writes ↗ vercel/workflow
  2. [2] [world-vercel] Validate ref resolve responses before use ↗ vercel/workflow
  3. [3] [codex] Handle lazy stream key request failures ↗ vercel/workflow
  4. [4] [core] Forward-port: preserve event-log order in hook-vs-sleep replay races (#2171) ↗ vercel/workflow
  5. [5] fix: bump devalue to 5.8.1 ↗ vercel/workflow
  6. [6] [turbopack] Remove WebAssembly helpers from the default runtime (#94373) vercel/next.js
  7. [7] Add global config to enable Partial Prefetching ↗ vercel/next.js
  8. [8] Partial Prefetching: Default to App Shell only ↗ vercel/next.js
  9. [9] feat(openai): add namespaces for tool definitions ↗ vercel/ai
  10. [10] feat(provider/google-vertex): add Chirp speech-to-text (transcription) model support ↗ vercel/ai
  11. [11] feat(build-utils): gate client-side maxDuration upper bound behind env var (#16539) vercel/vercel
  12. [12] feat(build-utils): gate client-side maxDuration upper bound behind env var ↗ vercel/vercel
  13. [13] Support non-managed Connex connector creation ↗ vercel/vercel

Quick answers

What shipped 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. In total, 40 commits, 42 pull requests, and 22 releases landed.
Who contributed to Vercel on June 8, 2026?
8 developers shipped this update, including pranaygp, TooTallNate, VaguelySerious, acdlite, aayush-kapoor, 31Carlton7, smaeda-ks, and dvoytenko.
What were the notable Vercel updates?
[codex] Fix partial world-local exclusive writes, [world-vercel] Validate ref resolve responses before use, and [codex] Handle lazy stream key request failures.

More from @vercel

Daily updates, in your inbox

Follow Vercel

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?