$ the-wire · showcase
MEMORY GOES FIRST-CLASS, WORKFLOWS LEARN TO FAIL GRACEFULLY, AND SLACK PATCHES ATTACHMENTS
By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology
13 people shipped this
AndrewBarba
@AndrewBarba
2 cited
ctgowrie
@ctgowrie
2 cited
msullivan
@msullivan
1 cited
fantix
@fantix
1 cited
elprans
@elprans
1 cited
Tobias Koppers
@sokra
1 cited
Sebastian "Sebbie" Silbermann
@eps1lon
1 cited
jgruica
@jgruica
1 cited
bensabic
@bensabic
1 cited
github-actions
@github-actions
TooTallNate
@TooTallNate
VaguelySerious
@VaguelySerious
Niklas Mischkulnig
@mischnic
Eve's new memory core landed overnight, Next.js fixed a Turbopack deadlock, and chat adapters closed a security hole in attachment downloads.
Eve's memory system gets a first-class upgrade with path-authored providers and lifecycle hooks keyed to recall and capture events [1], plus a bounded file provider on top [2]. This is the architecture the team has been building toward. Meanwhile, vercel-py hardened workflow suspension: workflows now raise CancelledError instead of running side effects while suspended [3], and step errors serialize properly with a new WorkflowRunFailedError [4]. Django users get a Vercel Queues backend for Django Tasks [5]. Over in Next.js, Turbopack no longer deadlocks on re-export cycles [6], AVIF image optimization is back with sharp 0.35.4 [7], and a client-reference drop bug where module id 0 was treated as falsy is fixed [8]. Slack and Discord attachment downloads now refuse private and internal addresses, cap at 25 MB, and time out after 30 seconds [9]. "Slack sends the bot token only on hops to trusted Slack origins" [9]. Eve also fixed an extension regression where flat instructions collided [10] and corrected Agentcard connector setup [11].
Action items
- → Watch for the next eve release to pick up the first-class memory core and bounded file provider vercel/eve [plan]
- → Review workflow suspension semantics in vercel-py if you rely on hook.dispose() in finally blocks vercel/vercel-py [plan]
- → Upgrade to the next Next.js release to get the Turbopack cycle deadlock fix and AVIF re-enable vercel/next.js [plan]
- → Verify your chat adapters are pulling the shared guarded downloader to block SSRF vercel/chat [immediate]
References
- [1] feat(eve): memory - add first-class provider lifecycle ↗ vercel/eve
- [2] feat(eve): memory - add bounded file provider ↗ vercel/eve
- [3] workflow: prevent workflows from having side effects while suspending ↗ vercel/vercel-py
- [4] workflow: serialize run and step errors ↗ vercel/vercel-py
- [5] Add `vercel-django-tasks` -- Vercel Queues backend for Django Tasks ↗ vercel/vercel-py
- [6] Fix Turbopack re-export cycle deadlock (#97933) vercel/next.js ↗
- [7] Re-enable AVIF image optimization (#97931) vercel/next.js ↗
- [8] fix: don't drop client references when the concatenated module id is 0 (#97936) ↗ vercel/next.js
- [9] fix(adapters): guard attachment downloads across slack, discord, telegram, and whatsapp ↗ vercel/chat
- [10] fix(eve): scope flat extension instructions ↗ vercel/eve
- [11] fix(eve): set up Agentcard MCP connectors ↗ vercel/eve
