Who contributed to Vercel on July 2, 2026?

10 developers shipped this update, including NathanColosimo, joshualipman123, felixarntz, github-actions[bot], aayush-kapoor, samselikoff, marcgreenstock, and TheBigSadowski, and 2 more.

What were the notable Vercel updates?

fix(vite-frameworks): derive workflow roots, fix(vite-frameworks): derive workflow roots (#2725), and fix(next): derive workflow project root.

WORKFLOW NAILS ROOT DETECTION ACROSS FRAMEWORKS WHILE AI SDK SHIPS GEMINI VIDEO SUPPORT

Vercel's build system just fixed how it derives project roots for Astro, SvelteKit, and Next.js, eliminating brittle path logic that broke on monorepos, while the AI SDK added full Gemini Interactions video output support and AssemblyAI's newest transcription models.

The workflow team landed three coordinated PRs [1][2][3][4] that rewrite root detection from first principles. Instead of guessing where your project lives, Workflow now derives paths from what the frameworks themselves use: Astro's `config.root` and `config.srcDir`, SvelteKit's workspace markers, and Next.js's explicit `outputFileTracingRoot` or `turbopack.root`. This fixes the silent route-scanning failures and module specifier drift that plagued monorepo deployments. On the AI front, @ai-sdk/google 4.0.4 now parses video output blocks from Gemini's Interactions API [5][7], letting multimodal models return generated video as part of normal responses, while the harness layer gained shared utilities [6] to stop duplicating shell quoting and sandbox logic across adapters. AssemblyAI support [8] expanded to the new `universal-3-5-pro` model and the speech_models parameter, and MCP tool calls [9] now retry on transient failures instead of burning tokens on model re-decisions. Next.js fixed Turbopack's `#/` import resolution [11] (it was incorrectly blocking the common `"#/*": "./src/*"` pattern), shipped Navigation Inspector fixes for Safari [12], and cleaned up the instant validation messaging [10]. On the platform side, OIDC token exchange [13] now caches in memory by token+audience hash, cutting round-trips on repeated calls, while CLI marketplace integration acceptance [14] collapsed three separate prompts into one. Satori switched to npm trusted publishing [15][18] and fixed its flexWrap docs [16][17].