RepoJournal
Vercel

@vercel

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

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

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

By RepoJournal · Filed · About Vercel

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

References

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

FAQ

What changed 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.
What should Vercel teams do about it?
Review and update any scripts or CI pipelines that call `vercel logs` without --follow before upgrading CLI • If using chat adapters, update `.client` references to `.octokit` / `.linearClient` / `.webClient` (deprecated aliases work now but won't forever) • Review @vercel/sdk v1.21.3 breaking changes in projects, authentication, and deployments endpoints
Which Vercel repositories shipped on May 13, 2026?
vercel/vercel, vercel/chat, vercel/ai, vercel/workflow, vercel/sdk

Related across the cluster

For your repos

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

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.