RepoJournal
Vercel

@vercel

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

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

WORKFLOW HARDENS AGAINST SUPPLY CHAIN ATTACKS, TURBOREPO PATCHES CSRF AND SHELL INJECTION

By RepoJournal · Filed · About Vercel

Vercel shipped critical security fixes across Workflow and Turborepo while shipping new CLI features and hardening the entire platform against repository-controlled execution.

The most urgent story: Turborepo 2.9.13 landed three security patches [1][2][3] that block CSRF attacks on self-hosted deployments, disable VS Code extension commands in untrusted workspaces, and prevent malicious `yarnPath` values from executing during detection. Separately, Workflow closed a supply chain vulnerability [4] that would have let fork PR submitters execute arbitrary shell on CI runners by hardening how community world matrix fields flow through reusable workflows. On the builder front, Vercel shipped DetectEntrypointFn [5], a normalized entrypoint detector that lets services auto-detect their runtime entry point across Python, Node, and Go without guessing. The CLI got a polish pass with a simplified `vc setup` flow [6] and dropped the feature gate on `vercel connect` [7], pushing it to all users as a beta command. Workflow also fixed a DX nightmare where Next.js proxies reading request bodies broke queue logging with detached ArrayBuffer errors [8], plus added rendered link validation to catch broken homepage navigation [9]. Chat SDK shipped queue-debounce concurrency [10] for burst message handling, a dedicated `chat/ai` subpath to keep optional dependencies out of bundles [11], and first-class Vue and Svelte web adapter support [12]. Next.js hardened Instant Insights to silence duplicate validation warnings when dev render errors already surface [13], fixed a bug where `new Date()` was mislabeled as `Date.now()` in the error overlay [14], and shipped the long-awaited middleware rewrite fix for Server Actions [15][16].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] fix: Validate auth callback state ↗ vercel/turborepo
  2. [2] fix: Harden VS Code extension command execution ↗ vercel/turborepo
  3. [3] fix: Avoid project-local Yarn during detection ↗ vercel/turborepo
  4. [4] CI: drop setup-command input from reusable community-world workflows (#1828) vercel/workflow
  5. [5] Add normalized entrypoint detector for runtime builders ↗ vercel/vercel
  6. [6] [cli] refresh vc setup flow + aligned-label output ↗ vercel/vercel
  7. [7] [cli] connect: drop FF_CONNEX_ENABLED gate, mark beta in help (#16334) vercel/vercel
  8. [8] [codex] Fix detached ArrayBuffer proxy DX ↗ vercel/workflow
  9. [9] Validate homepage links in docs link lint ↗ vercel/workflow
  10. [10] feat(chat): add queue-debounce concurrency strategy (#495) vercel/chat
  11. [11] feat(chat): add `chat/ai` subpath for AI SDK utilities (#492) vercel/chat
  12. [12] feat(web-adapter): first class support for Vue and Svelte ↗ vercel/chat
  13. [13] Instant Insights: only report non-validatable if dev render is error free ↗ vercel/next.js
  14. [14] Fix `Date.now()` cause shadowing in sync IO error overlay ↗ vercel/next.js
  15. [15] Fix server action forwarding loop with middleware rewrites ↗ vercel/next.js
  16. [16] Fix server action forwarding loop with middleware rewrites (#93792) vercel/next.js

Quick answers

What shipped in Vercel on May 15, 2026?
Vercel shipped critical security fixes across Workflow and Turborepo while shipping new CLI features and hardening the entire platform against repository-controlled execution. In total, 30 commits, 40 pull requests, and 3 releases landed.
Who contributed to Vercel on May 15, 2026?
8 developers shipped this update, including anthonyshew, dnwpark, JohnPhamous, pranaygp, HugoRCD, gnoff, aurorascharff, and unstubbable.
What were the notable Vercel updates?
fix: Validate auth callback state, fix: Harden VS Code extension command execution, and fix: Avoid project-local Yarn during detection.

More from @vercel

Daily updates, in your inbox

Follow Vercel

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?