Who contributed to Vercel on August 17, 2026?

6 developers shipped this update, including shaper, lukesandberg, unstubbable, github-actions, Anthony Shew, and github-actions[bot].

What were the notable Vercel updates?

turbo-tasks-backend: Enforce that tasks exist when accessing them, turbo-tasks-backend: add persistence delete/tombstone plumbing for GC, and turbo-persistence: add key-value tombstones for MultiValue families.

@vercel

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

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

NEXT.JS TURBO LAYER GETS GARBAGE COLLECTION PLUMBING, AI PACKAGE FIXES PROVIDER USAGE DATA

By RepoJournal · Filed 06:57 UTC on August 17, 2026 · About Vercel

6 people shipped this

lukesandberg @lukesandberg 3 cited

shaper @shaper 2 cited

Anthony Shew @anthonyshew 2 cited

unstubbable @unstubbable 1 cited

github-actions[bot] @github-actions[bot] 1 cited

github-actions @github-actions

Next.js is laying the foundation for task garbage collection across its persistence layer while fixing a critical gap in how OpenAI-compatible providers report token usage.

The Next.js team shipped three interconnected changes to turbo-tasks-backend and turbo-persistence that together enable safe deletion of stale task data from disk [1] [2] [3]. The persistence layer now supports key-value tombstones for MultiValue families [3], while the tasks layer enforces that tasks exist before access and provides `get_or_create_task` for the rare cases that need it [1]. This is groundwork for full GC support but also closes basic API gaps in the database. Separately, the AI package fixed a subtle schema validation bug where nested `prompt_tokens_details` and `completion_tokens_details` from providers were being stripped during parsing because they used strict object schemas instead of loose ones [4] [5], meaning "custom provider-specific token breakdowns were being silently discarded." On the infra side, Next.js also anchored its six async local storages to global symbols so they behave as true singletons within a realm [6]. Turborepo shipped a canary release [7] and expanded its performance agent toolbox to prioritize end-to-end workflows over isolated microbenchmarks [8], while fixing gitignore handling in Docker contexts where git metadata is absent [9].

Action items

→ Integrate the OpenAI usage fix into your next AI package bump to preserve provider-specific token details vercel/ai [plan]
→ Monitor turbo-persistence and turbo-tasks-backend changes as they stabilize GC foundation for your builds vercel/next.js [monitor]
→ Test async local storage fixes if you have deeply nested module paths in your Next.js app vercel/next.js [monitor]

References

[1] turbo-tasks-backend: Enforce that tasks exist when accessing them ↗ vercel/next.js
[2] turbo-tasks-backend: add persistence delete/tombstone plumbing for GC ↗ vercel/next.js
[3] turbo-persistence: add key-value tombstones for MultiValue families ↗ vercel/next.js
[4] fix(openai-compatible): preserve unmapped usage fields in usage.raw ↗ vercel/ai
[5] fix(openai-compatible): preserve unmapped usage fields in usage.raw (#18561) vercel/ai
[6] Anchor the async local storage instances to global symbols ↗ vercel/next.js
[7] Turborepo v2.10.11-canary.4 ↗ vercel/turborepo
[8] feat: Expand performance agent toolbox ↗ vercel/turborepo
[9] fix: Respect gitignore without git metadata (#13756) vercel/turborepo

Quick answers

What shipped in Vercel on August 17, 2026?: Next.js is laying the foundation for task garbage collection across its persistence layer while fixing a critical gap in how OpenAI-compatible providers report token usage. In total, 9 commits, 9 pull requests, and 2 releases landed.
Who contributed to Vercel on August 17, 2026?: 6 developers shipped this update, including shaper, lukesandberg, unstubbable, github-actions, Anthony Shew, and github-actions[bot].
What were the notable Vercel updates?: turbo-tasks-backend: Enforce that tasks exist when accessing them, turbo-tasks-backend: add persistence delete/tombstone plumbing for GC, and turbo-persistence: add key-value tombstones for MultiValue families.

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

@vercel Aug 16

NEXT.JS ROUTER ARCHITECTURE SHIFTS INTO CONCURRENT MODE

The Next.js team is laying foundation for a concurrent-rendering-aware router rewrite, while simultaneously cleaning up years of structural debt across the client-side codebase.

javascript 31 shipped

@vercel Aug 15

WORKFLOW SHIPS RESILIENT STEP DISPATCH, NEXT.JS FIXES PAGES RUNTIME BREAKAGE

Workflow@5.0.0-beta.42 lands parallel queue publishing with transient failure recovery, while Next.js patches a critical Pages API adapter bug that breaks when routes import next/head.

javascript 116 shipped

@vercel Aug 14

NEXT.JS UNIFIES RSC RESPONSE PIPELINE, AI SDK FIXES SILENT TOOL DROPS

Next.js completed a multi-part refactor to route all RSC requests through a single NavigationFlightResponse format, eliminating hand-synced positional arrays and shared cache-write logic across the router.