Who contributed to Vercel on July 5, 2026?

1 developer shipped this update, including anthonyshew.

What were the notable Vercel updates?

perf: Stop materializing spans for the disabled daemon log layer (#13244), perf: Hash git blobs with hardware-accelerated SHA-1, and perf: Overlap external dependency hashing with package file hashing (#13234).

@vercel

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

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

TURBOREPO CUTS SPAN MATERIALIZATION OVERHEAD, NEXT.JS PREPS HMR CANCELLATION

By RepoJournal · Filed 06:00 UTC on July 5, 2026 · About Vercel

1 person shipped this

anthonyshew @anthonyshew 2 cited

Turborepo shipped five performance fixes overnight that compound into measurable latency drops on large monorepos, while Next.js lays groundwork for smarter Server Components hot reload.

The headline win comes from stopping unnecessary span materialization in Turborepo's daemon logger [1], which was declaring interest in INFO-level events across the entire process even when nothing was listening. On a 1500-package monorepo this cuts unnecessary slab allocations and span lifecycle overhead entirely. Two other fixes stack on top: hardware-accelerated SHA-1 for git blob hashing [2] cuts that cost 5-8x by dropping pointless collision detection, and overlapping external dependency hashing with file hashing [3] removes a serial bottleneck that was burning 47ms on large graphs. A critical fix lands for root-directory packages that were vacuously claiming every file in change mapping [4], breaking affected-only builds and watch-mode routing. Finally, Turborepo now releases the tokio runtime at exit [5] so background DNS lookups stop stalling the process for 4-5 seconds after all work completes. On the Next.js side, v16.3.0-canary.78 ships the experimental `serverComponentsHmrCancellation` flag [6], the first piece of a series that will cancel stale Server Components HMR refreshes when newer ones arrive. This is plumbing only, no behavior yet, but it signals the direction.

Action items

→ Update Turborepo to the latest commit - these five fixes compound on monorepos over 500 packages vercel/turborepo [plan]
→ Test canary.78 in staging if you're running large Server Components apps - HMR cancellation foundation is live vercel/next.js [monitor]

References

[1] perf: Stop materializing spans for the disabled daemon log layer (#13244) vercel/turborepo
[2] perf: Hash git blobs with hardware-accelerated SHA-1 ↗ vercel/turborepo
[3] perf: Overlap external dependency hashing with package file hashing (#13234) vercel/turborepo
[4] fix: Stop root-directory packages from claiming every file in change mapping ↗ vercel/turborepo
[5] perf: Release tokio runtime at exit so background DNS lookups never stall the user (#13231) vercel/turborepo
[6] Add `serverComponentsHmrCancellation` experimental flag (#95462) vercel/next.js

Quick answers

What shipped in Vercel on July 5, 2026?: Turborepo shipped five performance fixes overnight that compound into measurable latency drops on large monorepos, while Next.js lays groundwork for smarter Server Components hot reload. In total, 15 commits, 15 pull requests, and 2 releases landed.
Who contributed to Vercel on July 5, 2026?: 1 developer shipped this update, including anthonyshew.
What were the notable Vercel updates?: perf: Stop materializing spans for the disabled daemon log layer (#13244), perf: Hash git blobs with hardware-accelerated SHA-1, and perf: Overlap external dependency hashing with package file hashing (#13234).

TURBOPACK RUNTIME FIXES SHIP AS NEXT.JS LOCKS DOWN APP SHELL STREAMING

Sampoder eliminated a high-severity deoptimization in Turbopack's chunk URL resolution that was bailing out on large import trees, while the team shipped per-segment prefetch offsets to squeeze more performance out of static rendering.

javascript 12 shipped 1-min read

@vercel 2 days ago

NEXT.JS PLUGS MEMORY LEAK IN EDGE RUNTIME, FIXES DEV OVERLAY ENCODING BUGS

A critical sandbox memory leak that causes step-like heap growth in self-hosted Next.js servers is patched, while dev overlay symbolication now correctly handles project paths with special characters.

javascript 31 shipped 2-min read

@vercel 3 days ago

NEXT.JS OPTIMIZES APP ROUTING ENTRY POINTS WHILE WORKFLOW CUTS STREAM LATENCY 20 PERCENT

Next.js extracted invariant app-page handlers into shared runtime modules while Workflow's stream write batching moves into core, eliminating per-token round trips on idle producers.

+11

javascript 126 shipped 2-min read

@vercel 4 days ago

TWO CRITICAL SECURITY PATCHES LAND IN WORKFLOW AND EVE OVERNIGHT

Next 16.2.11 and PostCSS 8.5.12 patches ship across workflow to seal CVE vulnerabilities, while Eve locks down workflow failure visibility.

javascript 153 shipped 1-min read

Elsewhere on the wire

AI Agents about 21 hours ago

CLINE SHIPS FIVE CRITICAL AGENT FIXES AFTER END-TO-END TESTING BLITZ

Saoudrizwan just landed a cascade of fixes that prevent the agent loop from running wild, stop file reads from resolving to the wrong directory, and plug the compaction pipeline.

ai-agents 16 shipped 2-min read

Local LLMs about 21 hours ago

LLAMA.CPP SHIPS MINIMAX-M3 SPARSE ATTENTION, VLLM UNLOCKS HETEROGENEOUS PREFILL-DECODE

The inference stack gets a new model architecture and a fundamental shift in how prefill and decode can run on different hardware configurations.

+10

llms 125 shipped 1-min read

@CachyOS about 21 hours ago

GLIBC 2.43 REBUILD SHIPS, INSTALLER JUMPS TO C++26

CachyOS pushed glibc 2.43 through the pipeline while the CLI installer upgraded its C++ standard to C++26, signaling a major refresh across core infrastructure.

infra 97 shipped 1-min read

Elixir & Phoenix about 21 hours ago

ECTO FIXES SUBQUERY PLANNING IN JOINS, ELIXIR PATCHES IEX PARSING

Ecto's query planner now handles subqueries correctly in interpolated join filters, while Elixir fixes a syntax error that broke 'not in' as a continuation operator in IEx.