The Wire · Showcase
WORKFLOW EVENT ORDERING FIXED, SANDBOX PINNING NODE VERSIONS, EVE GAINS SANDBOX STOPS
By RepoJournal · Filed · About Vercel
16 people shipped this
VaguelySerious
@VaguelySerious
2 cited
LukeSheard
@LukeSheard
1 cited
vercel-gh-bot-3
@vercel-gh-bot-3
1 cited
ctgowrie
@ctgowrie
1 cited
AndrewBarba
@AndrewBarba
1 cited
unstubbable
@unstubbable
1 cited
acdlite
@acdlite
1 cited
lucamaraschi
@lucamaraschi
ar-tama
@ar-tama
molebox
@molebox
github-actions[bot]
@github-actions[bot]
benpankow
@benpankow
JohnPhamous
@JohnPhamous
next-js-bot[bot]
@next-js-bot[bot]
icyJoseph
@icyJoseph
lubieowoce
@lubieowoce
Vercel shipped fixes across three major systems overnight: workflow's event consumer now respects delivery timing, sandbox images pin exact Node versions, and Eve lets authored code stop sandboxes mid-execution.
The workflow team closed a critical async bug where the events consumer would sit on unclaimed steps while the VM was mid-flight toward claiming them, creating phantom unconsumed-event warnings and replay divergence [1]. A companion fix ensures step results stay ordered even when waits park on unread hook payloads, preventing correlation ID swaps that would make replay permanently diverge [2]. Separately, sandbox Docker images now pin exact Node versions (22.23.2, 24.19.0, 26.7.0) instead of just major releases, both to guarantee reproducibility and to document the precise runtime each image tag uses [3]. Over in Eve, the sandbox backend now exposes `ctx.getSandbox().stop()` to allow authored hooks and tools to release compute at application-defined boundaries while preserving the durable session [5], and the Slack integration restructured approval messages to keep large tool inputs from bloating callback payloads, fixing a responsiveness regression [6]. Eve also fixed `eve build` to serialize Zod 3 input schemas by handling the missing JSON Schema converter [4]. Next.js kept the dev validation worker alive across HMR updates so stack frames now resolve correctly to source positions [7] and fixed the Nav Inspector hanging in an infinite prefetch loop on repeat captures [8].
One email a day. Unsubscribe in one click.
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. Read a past issue →
Action items
- → Review workflow event ordering fixes before next deploy - closes async ordering gaps vercel/workflow [plan]
- → Pin sandbox images to exact Node versions in your build matrix vercel/sandbox [plan]
- → Test authored sandbox `.stop()` calls if you use custom SandboxBackend vercel/eve [monitor]
- → Upgrade Next.js to fix Nav Inspector prefetch loop if you use instant navigation testing vercel/next.js [immediate]
References
- [1] [core] Gate the unconsumed-event check on delivery idleness ↗ vercel/workflow
- [2] [core] Keep step results ordered behind waits parked on unread hook payloads ↗ vercel/workflow
- [3] fix(images): pin exact Node versions ↗ vercel/sandbox
- [4] fix(eve): build tools with Zod 3 input schemas ↗ vercel/eve
- [5] feat(eve): allow authored sandbox stops ↗ vercel/eve
- [6] fix(eve): slack - keep large approvals responsive ↗ vercel/eve
- [7] Keep the dev validation worker alive across HMR updates ↗ vercel/next.js
- [8] Fix Nav Inspector request loop on repeat captures ↗ vercel/next.js
![langchain-oss-model-profiles[bot]](https://avatars.githubusercontent.com/in/2903571?v=4&s=48 "langchain-oss-model-profiles[bot]"){kind=small}
