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

VERCEL FUNCTIONS SHIPS WEBSOCKET NATIVE SUPPORT, EVE FIXES CRITICAL DEV PATH BLOCKERS

By RepoJournal · Filed · About Vercel

Vercel Functions now handles WebSocket connections natively in public beta, while Eve's dev runtime rebuilds and MCP connection flows are finally working end-to-end.

WebSocket support across Vercel Functions is now documented and shipping [1][2], complete with guidance on Socket.IO transports and Next.js experiments. Developers can stop reaching for polling workarounds and drop the myth that streaming requires Edge runtime. On the Eve side, three critical dev-facing fixes landed: MCP connections are now usable in local development [3], the dev-only rebuild route is wired up, and HITL approval resume handling works correctly with text shortcuts [4]. GitHub channel webhooks forwarded through Vercel Connect no longer require standard headers [5], inferring event type from payload shape instead. Eve's agent info probe now retries transient 5xx failures [6], stopping false negatives during dev worker reloads. CORS handling across Eve channels now defaults permissive with proper preflight support [7]. AI SDK v7 picked up Sentry observability [8], JSON response handlers now respect size limits [9], and patch releases flowed through @ai-sdk/rsc, @ai-sdk/svelte, and the full Node.js builder stack [10][11][12][13][14][15][16][17].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] feat(vercel-functions): WebSocket guidance + SSE/streaming clarification ↗ vercel/vercel-plugin
  2. [2] feat(vercel-functions): WebSocket guidance + SSE/streaming docs (#102) vercel/vercel-plugin
  3. [3] fix(eve): make MCP connections usable in dev ↗ vercel/eve
  4. [4] fix(eve): HITL approvals - repair resume contract ↗ vercel/eve
  5. [5] fix(eve): github channel - infer headerless webhooks ↗ vercel/eve
  6. [6] fix(eve): retry transient agent info probes ↗ vercel/eve
  7. [7] fix(eve): channels - default permissive CORS ↗ vercel/eve
  8. [8] docs: add Sentry observability guide ↗ vercel/ai
  9. [9] fix(provider-utils): limit JSON response handler reads ↗ vercel/ai
  10. [10] Version Packages ↗ vercel/ai
  11. [11] @ai-sdk/rsc@2.0.214 ↗ vercel/ai
  12. [12] @ai-sdk/svelte@4.0.214 ↗ vercel/ai
  13. [13] @vercel/static-build@2.11.4 ↗ vercel/vercel
  14. [14] @vercel/node@5.8.22 ↗ vercel/vercel
  15. [15] @vercel/nestjs@0.2.102 ↗ vercel/vercel
  16. [16] @vercel/koa@0.1.81 ↗ vercel/vercel
  17. [17] @vercel/hono@0.2.101 ↗ vercel/vercel

Quick answers

What shipped in Vercel on June 28, 2026?
Vercel Functions now handles WebSocket connections natively in public beta, while Eve's dev runtime rebuilds and MCP connection flows are finally working end-to-end. In total, 15 commits, 20 pull requests, and 22 releases landed.
Who contributed to Vercel on June 28, 2026?
6 developers shipped this update, including Timer, ruiconti, AndrewBarba, sergical, gr2m, and github-actions[bot].
What were the notable Vercel updates?
feat(vercel-functions): WebSocket guidance + SSE/streaming clarification, feat(vercel-functions): WebSocket guidance + SSE/streaming docs (#102), and fix(eve): make MCP connections usable in dev.

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?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.