$ the-wire · showcase
xAI drops Chat Completions, eve breaks registry installs, Turbopack widens tree-shaking
By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology
15 people shipped this
Sam Poder
@sampoder
1 cited
Stanzilla
@Stanzilla
1 cited
Andrew Barba
@AndrewBarba
1 cited
ruiconti
@ruiconti
1 cited
ai-sdk-factory
@ai-sdk-factory
1 cited
n1ckoates
@n1ckoates
1 cited
Tobias Koppers
@sokra
cmpadden
@cmpadden
chadhietala
@chadhietala
kkdawkins
@kkdawkins
github-actions
@github-actions
github-actions[bot]
@github-actions[bot]
shalabhc
@shalabhc
VaguelySerious
@VaguelySerious
karthikscale3
@karthikscale3
The day's heaviest changes are removals: AI SDK 7 deletes xAI's Chat Completions surface, eve republishes its registry items as channel/linear and connection/linear, and Turbopack moves re-export usage tracking forward so whole-namespace barrels shake.
feat(xai)!: remove Chat Completions API vercel/ai
AI SDK 7 already pointed xai() at the Responses API, and this removes xai.chat() entirely since the only Chat Completions features the SDK never supported were the n parameter and deferred completions. If you call xai.chat() directly, switch to the Responses path before upgrading.
refactor(eve): remove registry packages vercel/eve
The registry's single aggregate package created an inconsistent bare linear address and forced every catalog client to implement component selection, so Linear now ships as two independent items, channel/linear and connection/linear, and /add linear is gone. Install either or both explicit items instead.
[turbopack] Forward usage information across re-exports (#96282) vercel/next.js
Turbopack now forwards usage information across whole-namespace re-exports, covering the CommonJS re-export plus ESM star barrel case, which lets it tree-shake module graphs that previously kept dead members alive. It sits between the EsmAssetReferenceOptions refactor and the follow-up that narrows static member reads on namespace-valued named exports.
Pages Router: key the client router filter prefetch marker by the `as` path vercel/next.js
Router.prefetch() evaluated the client router filter against the as path but filed the __appRouter marker under the href pathname, with Router.change() looking it up the same way, so prefetch state could be missed when href and as diverged. The marker is now keyed by the normalized as pathname and effective locale.
feat(eve): add dynamic workflows vercel/eve
eve swaps the experimental uppercase Workflow path for a lowercase workflow factory from eve/tools/workflow; the factory builds a normal defineWorkflowTool while its private runner executes model-supplied JavaScript in isolation through the existing ctx.agent owner protocol. The removal of experimental_workflow makes this a breaking change.
fix: MCP OAuth callbacks reject stored external authorization servers when protected resource metadata rediscovery fails vercel/ai
In @ai-sdk/mcp, a failed callback-time protected resource metadata discovery made authInternal swallow the error and select the MCP server URL before loading the stored authorization-server pin, so the synthetic pin mismatched the stored Entra pin and the callback was rejected before any token request went out. Also landed quietly: eve exposes activation metadata on OTEL invoke_agent roots, Goo...
Action items
- → Replace xai.chat() calls with the Responses API path before upgrading to AI SDK 7 vercel/ai [plan]
- → Install channel/linear and connection/linear explicitly in place of the removed /add linear registry package vercel/eve [plan]
- → Migrate off experimental_workflow to the workflow factory from eve/tools/workflow vercel/eve [plan]
