The Wire · Showcase
EDGE RUNTIME OIDC NOW WORKS, NODE.JS GETS WEB API FLEXIBILITY
By RepoJournal · Filed · About Vercel
Vercel shipped the fixes that unblock edge functions authenticating with OIDC tokens and let Node.js developers opt into the Web API handler pattern without middleware overhead.
The edge runtime's OIDC implementation was broken because it tried to use the browser export, which resolves tokens to empty strings [1]. A new edge-light export with split sync and refresh modules fixes this and unblocks the entire serverless OIDC story. Separately, Node.js Serverless Functions now support opting into the Web API handler interface (Request → Response) via a static config export, giving developers the flexibility to write modern handler code without forcing it on middleware [2]. The CLI got native build fixes too: the native installer no longer prompts for updates, version flags now show (native) in human output, and standalone prebuilt deploys in pnpm/Turborepo monorepos stop failing on external symlinks [3][4]. Over in the AI stack, Vercel standardized on onEnd over onFinish for lifecycle callbacks across generateText, streamText, agents, and workflows [5], while Gemini 3 now auto-injects the skip_thought_signature_validator sentinel for replayed tool calls that lost their signature [6]. OpenAI's Responses API forwarding expanded to include web_search_call.action.queries [8], and telemetry moved from experimental to stable in v7 [7]. The Chat adapter ecosystem grew fast: low-level Slack helpers ship for custom runtimes that own their own routing [9][11], and Twilio got its first-class SMS, MMS, and voice adapter with runtime-light subpaths [10].
Action items
- → Deploy edge functions with OIDC authentication - this was broken until now vercel/vercel [immediate]
- → Review Web API handler adoption for Node.js functions - useWebApi config is now stable vercel/vercel [plan]
- → Update onFinish to onEnd in AI SDK implementations before v7 goes stable vercel/ai [plan]
- → Upgrade ncc if you support Node.js 24+; Node.js 20 is now unsupported vercel/ncc [monitor]
References
- [1] [oidc] add edge-light export ↗ vercel/vercel
- [2] [node] support useWebApi in static config ↗ vercel/vercel
- [3] [CLI] adding version and auto update fixes ↗ vercel/vercel
- [4] fix(cli): skip external symlinks in standalone prebuilt deploys (PIPE-6621) ↗ vercel/vercel
- [5] fix: rename onFinish to onEnd (#15245) vercel/ai
- [6] fix(google): auto-inject skip_thought_signature_validator on Gemini 3 replays (#15560) vercel/ai
- [7] docs: remove experimental telemetry warning (#15611) vercel/ai
- [8] feat(openai): forward web_search_call.action.queries from Responses API (#15656) vercel/ai
- [9] feat(slack): add low-level interaction helpers ↗ vercel/chat
- [10] feat(twilio): add sms, mms, and voice helpers ↗ vercel/chat
- [11] docs(slack): document low-level api subpaths ↗ vercel/chat
FAQ
- What changed in Vercel on May 28, 2026?
- Vercel shipped the fixes that unblock edge functions authenticating with OIDC tokens and let Node.js developers opt into the Web API handler pattern without middleware overhead.
- What should Vercel teams do about it?
- Deploy edge functions with OIDC authentication - this was broken until now • Review Web API handler adoption for Node.js functions - useWebApi config is now stable • Update onFinish to onEnd in AI SDK implementations before v7 goes stable
- Which Vercel repositories shipped on May 28, 2026?
- vercel/vercel, vercel/ai, vercel/chat