Who contributed to Vercel on August 22, 2026?

17 developers shipped this update, including github-actions, ctgowrie, chadhietala, n1ckoates, ai-sdk-factory, ai-sdk-factory[bot], aayush-kapoor, and fireairforce, and 9 more.

What were the notable Vercel updates?

Version Packages, feat(eve): define channel audience metadata, and feat(eve): classify messaging channel audiences.

@vercel

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

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

EVE TRACING GOES PUBLIC-ONLY AS PRIVACY GATES LAND

By RepoJournal · Filed 06:56 UTC on August 22, 2026 · About Vercel

17 people shipped this

chadhietala @chadhietala 3 cited

github-actions @github-actions 2 cited

Pranay Prakash @pranaygp 2 cited

ai-sdk-factory[bot] @ai-sdk-factory[bot] 1 cited

aayush-kapoor @aayush-kapoor 1 cited

devjiwonchoi @devjiwonchoi 1 cited

Shalabh Chaturvedi @shalabhc 1 cited

ctgowrie @ctgowrie

n1ckoates @n1ckoates

ai-sdk-factory @ai-sdk-factory

fireairforce @fireairforce

lukesandberg @lukesandberg

bgw @bgw

lubieowoce @lubieowoce

VaguelySerious @VaguelySerious

Nathan Rajlich @TooTallNate

rickeyswuave @rickeyswuave

Eve's new audience-aware tracing means private and unknown conversations stop being traced by default, and that's a breaking change you need to plan for.

Eve shipped eve@0.43.0 with background tools reporting delegated task results in-process [1], but the real story is the three-PR audience stack that landed together [2][3][4]. The default trace policy now keeps only public conversations; private and unknown fail closed, and even an incoming traceparent can't bypass local policy [4]. The classification is deliberately conservative, mapping direct messages and restricted channels to private and leaving ambiguous guilds as unknown [3]. Meanwhile, the AI SDK fixed duplicate embedding usage accounting in OpenTelemetry spans, which was double-counting tokens and cost [5], and patched duplicate text and reasoning part IDs in multi-step streams [7]. Both fixes shipped in ai@7.0.76 [6]. Next.js removed its generated error codes entirely, deleting errors.json, the SWC plugin, and generated WASM [8], and added instant validation for unstable_navigation() outside Suspense . Workflow solved a sneaky bundler bug by holding process-wide state on globalThis [9], defaulted its events transport to WebSockets with an explicit opt-out [10], and started running four test suites CI was silently skipping [11]. The correlations are real: Eve's tracing changes and the AI SDK's telemetry fix both target observability correctness, and Workflow's WebSocket default follows the SDK's span-per-frame readiness.

Action items

→ Review Eve tracing configuration before next deploy; private and unknown conversations will no longer be traced by default vercel/eve [immediate]
→ Plan for the change in error handling after Next.js removes generated error codes; native Error.code and Error.name remain vercel/next.js [plan]
→ Monitor for any changes in telemetry token counts after the AI SDK OTEL fix is released vercel/ai [monitor]

References

[1] Version Packages ↗ vercel/eve
[2] feat(eve): define channel audience metadata ↗ vercel/eve
[3] feat(eve): classify messaging channel audiences ↗ vercel/eve
[4] feat(eve): configure audience-aware tracing ↗ vercel/eve
[5] fix: prevent duplicate embedding usage accounting in OpenTelemetry spans (#19252) vercel/ai
[6] Version Packages ↗ vercel/ai
[7] fix(ai): prevent duplicate text and reasoning part ids ↗ vercel/ai
[8] Remove generated error codes ↗ vercel/next.js
[9] fix(world-vercel,world-local): hold process-wide state on globalThis (#3728) vercel/workflow
[10] Default the events transport to WebSockets (#3702) vercel/workflow
[11] Run the test suites CI was silently skipping (#3733) vercel/workflow

Quick answers

What shipped in Vercel on August 22, 2026?: Eve's new audience-aware tracing means private and unknown conversations stop being traced by default, and that's a breaking change you need to plan for. In total, 73 commits, 79 pull requests, and 18 releases landed.
Who contributed to Vercel on August 22, 2026?: 17 developers shipped this update, including github-actions, ctgowrie, chadhietala, n1ckoates, ai-sdk-factory, ai-sdk-factory[bot], aayush-kapoor, and fireairforce, and 9 more.
What were the notable Vercel updates?: Version Packages, feat(eve): define channel audience metadata, and feat(eve): classify messaging channel audiences.

BREAKING: Vercel SDK Ship Double Breaking Changes

Two TypeScript SDK releases in two days break response shapes across projects, feature flags, and deployments.

+13

javascript 143 shipped

@vercel Aug 20

NEXT.JS REMOVES UNSTABLE_EAGER AS AI SDK BLOCKS UNSAFE TOOL EXECUTION

Next.js is cleaning house on Partial Prefetching while the AI SDK ships a safety patch that stops side-effecting tools from running after truncated model outputs.

+15

javascript 165 shipped

@vercel Aug 19

MCP OAuth hardening lands, Fireworks structured outputs fixed

AI SDK patches a security hole in OAuth client registration while unlocking structured outputs for Fireworks models.

+11

javascript 118 shipped

@vercel Aug 18

AI SDK fixes Gemini 3.7 Flash as chat and Eve harden core flows

Gemini 3.7 Flash just broke for minimal reasoning, and the fix that landed overnight says more about the AI SDK's trajectory than any feature release.

javascript 70 shipped

Elsewhere on the wire

AI Agents Aug 22

Cline hubs get drain and replay as Langchain plumb gates

Cline just shipped rollover-grade hub commands while Langchain exposes gateway internals, and OpenHands quietly broke its own monitoring contract.

ai-agents 42 shipped

Local LLMs Aug 22

SGLang ships v0.5.18 with 710 PRs and DeepSeek V4 FP4 auto-routing

The biggest release of the week just landed: SGLang v0.5.18 adds new models, fixes a silent disagg bug, and defaults DeepSeek V4 FP4 checkpoints to the right MoE runner.