What should Vercel teams do about it?

If you maintain Cargo monorepos in CI, try the compile cache with --turobopack-compile-cache flag enabled • If you're testing Next.js 15 with output=export or output=standalone, verify supportsImmutableAssets behavior isn't breaking your build • Deploy Vercel CLI to pick up monorepo subdirectory build fixes and sandbox 3.4.0

Which Vercel repositories shipped on July 7, 2026?

vercel/turborepo, vercel/eve, vercel/next.js, vercel/vercel

TURBOREPO CARGO COMPILE CACHE LANDS FULLY EMBEDDED, NEXT.JS DISABLES IMMUTABLE ASSETS FOR EXPORTS

By RepoJournal · Filed 06:01 UTC on July 7, 2026 · About Vercel

Turborepo shipped zero-infrastructure Cargo compilation caching by embedding sccache directly into the binary, while Next.js locked down immutable assets for non-adapter output modes.

Turborepo's Cargo compile cache series landed its final pieces overnight. The feature serves Turborepo's remote cache as an sccache backend [1], eliminating the need for separate S3 or GitHub Actions cache infrastructure. But sccache required installation on PATH until today, when the team embedded it as a linked library, making the entire setup a single flag flip [2]. A critical fix landed simultaneously: CARGO_INCREMENTAL was blocking injection on every CI run [3], discovered during GHA validation. A fourth patch prevents storage failures from failing the build entirely [4], handling the case where bad credentials would tank the whole compilation. End-to-end coverage for Cargo workspaces landed to lock in the full surface from discovery through caching [5]. In Next.js, supportsImmutableAssets is now disabled for export and standalone output modes [11], since those paths bypass adapters and can't deliver the necessary asset data. Turbopack fixed a dynamic exports sealing conflict where barrel files re-exporting CJS chains would hit Object.seal restrictions [12]. Eve shipped three major features: subagent workflows return with a maxSubagents cap [7], skill files now write to `$HOME/.agents/skills` instead of polluting workspace directories [6], and all three subagent types now surface token usage to callers [8]. The Chat SDK channel defaults expanded with markdown rendering and streaming deltas [9], and Slack channel now preserves markdown when combining file uploads [10]. Vercel CLI removed the VERCEL_RESOLVE_ROOT_DIRECTORY guard, shipping monorepo subdirectory builds by default [13], and fixed generated service route preservation in Services V2 nested output [14]. CLI sandbox bumped to 3.4.0 [15], and `vercel list` now emits machine-readable JSON when project resolution fails [16].

FAQ

What changed in Vercel on July 7, 2026?: Turborepo shipped zero-infrastructure Cargo compilation caching by embedding sccache directly into the binary, while Next.js locked down immutable assets for non-adapter output modes.
What should Vercel teams do about it?: If you maintain Cargo monorepos in CI, try the compile cache with --turobopack-compile-cache flag enabled • If you're testing Next.js 15 with output=export or output=standalone, verify supportsImmutableAssets behavior isn't breaking your build • Deploy Vercel CLI to pick up monorepo subdirectory build fixes and sandbox 3.4.0
Which Vercel repositories shipped on July 7, 2026?: vercel/turborepo, vercel/eve, vercel/next.js, vercel/vercel

@vercel

TURBOREPO CARGO COMPILE CACHE LANDS FULLY EMBEDDED, NEXT.JS DISABLES IMMUTABLE ASSETS FOR EXPORTS

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

TURBOREPO CARGO COMPILE CACHE LANDS FULLY EMBEDDED, NEXT.JS DISABLES IMMUTABLE ASSETS FOR EXPORTS

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

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