Who contributed to Vercel on May 13, 2026?

5 developers shipped this update, including adriancooney, tonypan2, bensabic, lgrammel, and anaclumos.

What were the notable Vercel updates?

cli/logs: Require explicit follow for deployments, [cli] Rename "Connex client" to "Connex connector" in user-visible strings, and feat: rename adapter.client to adapter.octokit / adapter.linearClient / adapter.webClient.

@vercel

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

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

VERCEL CLI SHIPS BREAKING CHANGES — LOGS NOW REQUIRE --FOLLOW FLAG

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

5 people shipped this

adriancooney @adriancooney 1 cited

tonypan2 @tonypan2 1 cited

bensabic @bensabic 1 cited

lgrammel @lgrammel 1 cited

anaclumos @anaclumos 1 cited

The Vercel CLI is tightening its logs behavior: `vercel logs` targeting a deployment now requires an explicit `--follow` flag to stream live output, treating all deployment arguments as historical filters by default.

This is a major breaking change [1] that forces developers to be intentional about live tailing versus historical inspection—a safety win for automation and scripts. The CLI also synchronized terminology across the stack [2], renaming "Connex client" to "Connex connector" to match the dashboard's updated feature naming. Over in the chat layer, adapters are getting more explicit—GitHub, Linear, and Slack SDKs are replacing the generic `.client` getter with SDK-specific names like `.octokit` and `.linearClient` [3], with deprecated aliases preserving backward compatibility. The AI SDK standardized on Start/End nomenclature [4], renaming `experimental_onEmbedFinish` to `experimental_onEmbedEnd`, while Google embedding models now support fileData for remote content [5]. On the security front, both vercel/workflow and vercel/ai removed the `pull_request_target` trigger from backport automation [6], eliminating a known privilege escalation vector in GitHub Actions. The SDK published v1.21.3 [7] with breaking response shape changes across projects, authentication, and deployments endpoints—review the Speakeasy changelog before consuming in downstream services.

Action items

→ Review and update any scripts or CI pipelines that call `vercel logs` without --follow before upgrading CLI vercel/vercel [immediate]
→ If using chat adapters, update `.client` references to `.octokit` / `.linearClient` / `.webClient` (deprecated aliases work now but won't forever) vercel/chat [plan]
→ Review @vercel/sdk v1.21.3 breaking changes in projects, authentication, and deployments endpoints vercel/sdk [plan]
→ Rename `experimental_onEmbedFinish` to `experimental_onEmbedEnd` in AI SDK integrations vercel/ai [monitor]

References

[1] cli/logs: Require explicit follow for deployments ↗ vercel/vercel
[2] [cli] Rename "Connex client" to "Connex connector" in user-visible strings ↗ vercel/vercel
[3] feat: rename adapter.client to adapter.octokit / adapter.linearClient / adapter.webClient ↗ vercel/chat
[4] fix: rename onEmbedFinish to onEmbedEnd ↗ vercel/ai
[5] feat(google): add fileData support to embedding model ↗ vercel/ai
[6] Remove pull_request_target trigger from backport workflow (#1972) vercel/workflow
[7] typescript - v1.21.3 - 2026-05-12 17:48:35 ↗ vercel/sdk

Quick answers

What shipped in Vercel on May 13, 2026?: The Vercel CLI is tightening its logs behavior: `vercel logs` targeting a deployment now requires an explicit `--follow` flag to stream live output, treating all deployment arguments as historical filters by default. In total, 30 commits, 35 pull requests, and 11 releases landed.
Who contributed to Vercel on May 13, 2026?: 5 developers shipped this update, including adriancooney, tonypan2, bensabic, lgrammel, and anaclumos.
What were the notable Vercel updates?: cli/logs: Require explicit follow for deployments, [cli] Rename "Connex client" to "Connex connector" in user-visible strings, and feat: rename adapter.client to adapter.octokit / adapter.linearClient / adapter.webClient.

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.