$ the-wire · showcase
Turbopack GC gets a config key and the runtime sheds peer state
By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
15 people shipped this
lukesandberg
@lukesandberg
2 cited
AndrewBarba
@AndrewBarba
1 cited
TooTallNate
@TooTallNate
1 cited
e0-gh-vercel-connect
@e0-gh-vercel-connect
1 cited
anthonyshew
@anthonyshew
1 cited
next-js-bot
@next-js-bot
github-actions[bot]
@github-actions[bot]
aayush-kapoor
@aayush-kapoor
ai-sdk-factory
@ai-sdk-factory
gr2m
@gr2m
github-actions
@github-actions
benpankow
@benpankow
OwenKephart
@OwenKephart
shalabhc
@shalabhc
vercel-gh-bot-5
@vercel-gh-bot-5
Next.js replaces the unused Turbopack GC env vars with an experimental config option, eve stops a pending provider request from running ahead of a user correction, and workflow opens run outcomes to application code.
Introduce config options for Turbopack GC vercel/next.js
Replaces the Turbopack GC environment variables, which the PR notes were unused and not ergonomic, with experimental.turbopackGc. It takes a boolean to turn GC on with defaults, or an object such as { minProgressMs: 100, rootTtlMs: 432e6 } to tune it, so any next.config.js still setting the env vars needs to move to the new key.
fix(eve): steering - interrupt pending generation in the core runtime vercel/eve
A correction sent before an assistant answer could wait behind an entire provider request, including provider-managed search, and produce both the original and corrected answers. The core runtime now interrupts pending generation through a dedicated durable steering signal, admits the correction through the existing ordered inbox, and continues the same turn.
feat(core): user-registerable workflow lifecycle hooks (registerLifecycleHooks) vercel/workflow
Fixes a real observability gap: runs that fail in the runtime after the workflow function parks (replay timeout, max deliveries, deployment mismatch) never reach a try/catch in workflow code. registerLifecycleHooks, exported from workflow/api, gives onRunCompleted and onRunFailed handlers the lazily-hydrated Run instance so an app can report every failed run to Sentry from one place instead of ...
fix(nest): isolate HTTP health handler from queue consumer vercel/workflow
The Nest Vercel builder used to duplicate the workflow queue consumer into an HTTP-addressable function and strip its queue trigger, which let HTTP requests shaped like queue callbacks reach workflow execution logic. It now emits a dedicated HTTP health function and keeps flow.func as the only queue-triggered consumer.
Store code generation AST paths in a shared trie vercel/next.js
Code generation now stores its AST paths in a per-module trie referenced by a 4-byte id rather than a Vec<AstParentKind> per path, since shared prefixes produced quadratic behavior in pathological cases. On a repro of 180 files each with a 1200-term chain, peak memory drops from 24.0 GB to 4.0 GB.
feat: Derive short names for Go workspace packages vercel/turborepo
Elsewhere in Turborepo, native Go packages get short Turborepo names derived from the final module-path component, so `--filter=example.com/acme/api` becomes `--filter=api` and `example.com/acme/api/v2#build` becomes `api/v2#build`; full module paths remain for Go imports and dependency resolution.
