RepoJournal
Vercel

@vercel

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

Pick a date

  1. Thu 21 may
  2. Sat 23 may
  3. Sun 24 may
  4. Mon 25 may
  5. Tue 26 may
  6. Wed 27 may
  7. Thu 28 may
  8. Fri 29 may
  9. Sat 30 may
  10. Sun 31 may
  11. Mon 1 jun
  12. Mon 8 jun
  13. Tue 9 jun
  14. Wed 10 jun
  15. Thu 11 jun
  16. Fri 12 jun
  17. Sat 13 jun
  18. Sun 14 jun
  19. Mon 15 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Fri 19 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

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

By RepoJournal · Filed · About Vercel

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].

Action items

References

  1. [1] fix(vite-frameworks): derive workflow roots ↗ vercel/workflow
  2. [2] fix(vite-frameworks): derive workflow roots (#2725) vercel/workflow
  3. [3] fix(next): derive workflow project root ↗ vercel/workflow
  4. [4] fix(next): derive workflow project root (#2729) vercel/workflow
  5. [5] feat(provider/google): support Gemini Interactions video output, usage, and omni dispatch ↗ vercel/ai
  6. [6] feat(harness): add utility functions for certain duplicated layers in harnesses ↗ vercel/ai
  7. [7] Version Packages ↗ vercel/ai
  8. [8] feat(assemblyai): support universal-3-5-pro and expand the transcription provider (#16548) vercel/ai
  9. [9] feat(mcp): add retry option for failed mcp tool calls ↗ vercel/ai
  10. [10] Remove 'silence this warning' from instant validation fix output (#95187) vercel/next.js
  11. [11] fix(turbopack): allow `#/` prefixed subpath import specifiers (#94461) vercel/next.js
  12. [12] Fix Navigation Inspector in Safari ↗ vercel/next.js
  13. [13] [oidc] Cache exchanged OIDC tokens in memory ↗ vercel/vercel
  14. [14] Accept marketplace integration terms with a single confirmation ↗ vercel/vercel
  15. [15] ci: publish via npm trusted publishing (OIDC) (#770) vercel/satori
  16. [16] docs: fix flexWrap default from 'wrap' to 'nowrap' (#767) vercel/satori
  17. [17] docs: fix flexWrap default from 'wrap' to 'nowrap' ↗ vercel/satori
  18. [18] ci: publish via npm trusted publishing (OIDC) ↗ vercel/satori

FAQ

What changed in Vercel on July 2, 2026?
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.
What should Vercel teams do about it?
If you maintain a monorepo with Astro, SvelteKit, or Next.js: pull the latest workflow packages and verify your build logs show cleaner root detection with no spurious scanning • If you're integrating AssemblyAI transcription: upgrade @ai-sdk/assemblyai and migrate to the speech_models parameter before the legacy speech_model gets sunset • If you use Turbopack with subpath imports ("#/*" patterns): pull the latest Next.js to unblock resolution
Which Vercel repositories shipped on July 2, 2026?
vercel/workflow, vercel/ai, vercel/next.js, vercel/vercel, vercel/satori

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.