The Wire · Showcase
VERCEL CLI RENAMED, SDK BREAKING CHANGES, NEXT.JS CACHE OVERHAUL
By RepoJournal · Filed · About Vercel
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
FAQ
- What changed 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.
- What should Vercel teams do about it?
- Update scripts calling `vercel logs` to add `--follow` flag before upgrading to CLI v54.0.0 • Audit SDK usage of projects, user events, and teams endpoints—v1.21.4 and v1.21.5 both break response shapes • Test Next.js fetch caching behavior in production; HTTP headers now respected with TTL invalidation
- Which Vercel repositories shipped on May 14, 2026?
- vercel/vercel, vercel/sdk, vercel/next.js