Who contributed to Vercel on May 14, 2026?

6 developers shipped this update, including bhrigu123, kitfoster, github-actions[bot], lukesandberg, unstubbable, and vercel-release-bot.

What were the notable Vercel updates?

[cli] Rename `vercel connex` command to `vercel connect` (#16322), [cli] Rename `vercel connex` command to `vercel connect`, and [cli] Add `vercel connect detach` and `--triggers` flag on attach (#16328).

@vercel

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

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

VERCEL CLI RENAMED, SDK BREAKING CHANGES, NEXT.JS CACHE OVERHAUL

By RepoJournal · Filed 06:00 UTC on May 14, 2026 · About Vercel

6 people shipped this

lukesandberg @lukesandberg 2 cited

unstubbable @unstubbable 2 cited

bhrigu123 @bhrigu123 1 cited

kitfoster @kitfoster 1 cited

github-actions[bot] @github-actions[bot] 1 cited

vercel-release-bot @vercel-release-bot 1 cited

The CLI's connect command sheds its beta name while two SDK releases stack breaking changes across projects, users, and teams—and Next.js is overhauling how fetch respects HTTP cache headers.

Vercel shipped `vercel connect` as the official command name [1], dumping the experimental `connex` label across CLI surfaces, API endpoints, and help text [2]. The same command now supports `vercel connect detach` and a `--triggers` flag [3], letting teams register trigger destinations alongside connector attachments. Separately, the alias assignment flow now preserves user-provided deployment and alias IDs for API-side resolution, fixing microfrontend routing that needs explicit source URLs [4]. On the SDK side, back-to-back breaking changes landed: v1.21.4 restructured user events, team responses, and networking endpoints [5], immediately followed by v1.21.5 breaking project response shapes across three major methods [7]. The CLI is getting a major bump to v54.0.0, which requires `--follow` to stream logs [6]—a behavior shift that breaks existing scripts. Over in Next.js, fetch is finally respecting HTTP `Cache-Control` headers with session-dependent TTL-based invalidation [8], a fix that lands alongside simplified session-dependent task attributes [9] and better error surfacing for nested cache violations [10]. React upstream rolled to the latest commit [11], and invalid dynamic usage errors now surface properly through Flight in dev [12].

Action items

→ Update scripts calling `vercel logs` to add `--follow` flag before upgrading to CLI v54.0.0 vercel/vercel [immediate]
→ Audit SDK usage of projects, user events, and teams endpoints—v1.21.4 and v1.21.5 both break response shapes vercel/sdk [immediate]
→ Test Next.js fetch caching behavior in production; HTTP headers now respected with TTL invalidation vercel/next.js [plan]
→ Review any `vercel connex` references in docs and automation—officially `vercel connect` now vercel/vercel [monitor]

References

[1] [cli] Rename `vercel connex` command to `vercel connect` (#16322) vercel/vercel
[2] [cli] Rename `vercel connex` command to `vercel connect` ↗ vercel/vercel
[3] [cli] Add `vercel connect detach` and `--triggers` flag on attach (#16328) vercel/vercel
[4] [vercel] Preserve alias source for vc alias set ↗ vercel/vercel
[5] typescript - v1.21.4 - 2026-05-13 15:16:09 ↗ vercel/sdk
[6] Version Packages ↗ vercel/vercel
[7] typescript - v1.21.5 - 2026-05-14 04:09:42 ↗ vercel/sdk
[8] fetch: respect HTTP Cache-Control headers with TTL-based invalidation (#91729) ↗ vercel/next.js
[9] simplify session dependent tasks (#91729) ↗ vercel/next.js
[10] Show inner `"use cache"` as cause of nested-dynamic cache error ↗ vercel/next.js
[11] Upgrade React from `dd453071-20260506` to `d5736f09-20260507` ↗ vercel/next.js
[12] Surface invalid dynamic usage errors via Flight in dev ↗ vercel/next.js

Quick answers

What shipped in Vercel on May 14, 2026?: The CLI's connect command sheds its beta name while two SDK releases stack breaking changes across projects, users, and teams—and Next.js is overhauling how fetch respects HTTP cache headers. In total, 36 commits, 43 pull requests, and 22 releases landed.
Who contributed to Vercel on May 14, 2026?: 6 developers shipped this update, including bhrigu123, kitfoster, github-actions[bot], lukesandberg, unstubbable, and vercel-release-bot.
What were the notable Vercel updates?: [cli] Rename `vercel connex` command to `vercel connect` (#16322), [cli] Rename `vercel connex` command to `vercel connect`, and [cli] Add `vercel connect detach` and `--triggers` flag on attach (#16328).

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 1 day 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

@vercel 2 days ago

WORKFLOW 5.0 BETA ARRIVES WITH HOOK TOKEN RETENTION, AI SDK FIXES GEMINI AND BEDROCK HALLUCINATIONS

Workflow shipped its most ambitious beta yet with experimental token retention, while the AI SDK shipped five critical fixes across Gemini, Bedrock, and dynamic tool validation in a single push.

javascript 132 shipped 2-min read

@vercel 3 days ago

NEXT.JS PATCHES FIVE SECURITY HOLES OVERNIGHT WHILE VERCEL CLI GAINS AI GATEWAY BUDGET CONTROLS

Five security advisories dropped across Next.js in the last 24 hours, ranging from origin validation on internal redirects to fetch cache key collisions that could leak cached responses between requests.

+12

javascript 145 shipped 2-min read

Elsewhere on the wire

AI Agents about 9 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 9 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.