125 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-05
stories 116

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

VERCEL-PY STANDARDIZES ON TYPESCRIPT SDK PAYLOADS, WORKFLOW ENGINE SHIPS QUICKJS VM

By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology

Python SDK workflows now speak the same wire format as TypeScript, eliminating serialization friction across the stack while the workflow engine ships inline step execution and WASM caching.

The vercel-py SDK achieved full payload interoperability with @workflow/core [1], replacing JSON serialization with devalue format so a Python workflow reads identically to one the TypeScript SDK started. This is a breaking change: workflows now take keyword arguments only and wire format shifts from `b"json"` to `b"devl"` [2]. Meanwhile, the workflow engine shipped QuickJS VM inline step execution [3], keeping the suspended WASM engine alive per invocation and dispatching durable side effects for each suspension, cutting latency by eliminating cold starts. The engine also now carries Hook retention deadlines across the QuickJS boundary [4] and requires `runId` on correlation ID lookups [5], tightening semantic guarantees. Across vercel/flags, a coordinated 6-release wave renamed Edge Config to Global Config throughout the SDK adapter ecosystem [6] [7], updating Statsig, Reflag, PostHog, and LaunchDarkly integrations. On the Next.js front, Turbopack fixed a production-only runtime emission bug where async-module machinery could be stripped from shared chunks [8], and addressed worker thread cleanup to prevent orphaned plugin isolates from blocking garbage collection [9]. The AI SDK fixed tool history validation that was rejecting valid follow-up messages after aborted tools [10], added FLUX 3 video model support to Black Forest Labs [11], and corrected streaming tool call handling for gateways that emit sparse or reused indexes [12].

Action items

References

  1. [1] workflow: make payloads interchangeable with the TypeScript SDK ↗ vercel/vercel-py
  2. [2] workflow: make payloads interchangeable with the TypeScript SDK (#224) ↗ vercel/vercel-py
  3. [3] QuickJS engine: inline step execution + WASM module caching (#3049) ↗ vercel/workflow
  4. [4] fix(core): preserve Hook retention in QuickJS ↗ vercel/workflow
  5. [5] [world] Require a runId on listByCorrelationId ↗ vercel/workflow
  6. [6] flags@4.3.0 ↗ vercel/flags
  7. [7] @flags-sdk/statsig@0.3.0 ↗ vercel/flags
  8. [8] Turbopack: don't strip async-module runtime from shared runtime chunks ↗ vercel/next.js
  9. [9] Turbopack: terminate failed plugin worker threads (#96592) ↗ vercel/next.js
  10. [10] fix: prevent aborted tool history from blocking follow-up messages (#18433) ↗ vercel/ai
  11. [11] feat(black-forest-labs): add video model support (FLUX 3) ↗ vercel/ai
  12. [12] fix: handle streamed tool calls with irregular or missing indexes ↗ vercel/ai

Quick answers

What shipped in Vercel on August 5, 2026?
Python SDK workflows now speak the same wire format as TypeScript, eliminating serialization friction across the stack while the workflow engine ships inline step execution and WASM caching. In total, 47 commits, 48 pull requests, and 21 releases landed.
Who contributed to Vercel on August 5, 2026?
14 developers shipped this update, including msullivan, fantix, ricardo-agz, github-actions[bot], Marcos Hernanz, lukesandberg, ai-sdk-factory[bot], and felixarntz, and 6 more.
What were the notable Vercel updates?
workflow: make payloads interchangeable with the TypeScript SDK, workflow: make payloads interchangeable with the TypeScript SDK (#224), and QuickJS engine: inline step execution + WASM module caching (#3049).