Sandbox snapshots, execution cleanup, and a week of hardening for background job runners

Sandboxes become a managed resource in Inngest

The biggest functional shift this week came from Inngest, which turned sandboxes from something you spin up and babysit into a resource with a full lifecycle. The JS SDK's direct client and step.sandbox now expose create, list, get, wait, delete, and clone APIs, so a workflow step can snapshot a working environment — dependencies installed, state warm — and hand copies of it to parallel work without re-provisioning from scratch. That pairs with sandboxes now waiting for RUNNING by default instead of returning immediately, which removes the class of race conditions where code touched a box before it was actually up; the old fire-and-forget behavior is still available via an explicit runningTimeout: false opt-out. Together the two changes make sandbox provisioning something you can reason about inside a durable function rather than around it. Inngest's AI package also shed its runtime type dependencies in a small housekeeping pass that moves @types/node and TypeScript to dev dependencies.

n8n closes execution and expression leaks

n8n shipped a long run of patches across its 1.x and 2.x lines, and the throughline is cleanup — jobs and state that previously escaped their run. Running job cleanup now fires even when a workflow run rejects, closing a leak that would accumulate hung jobs after failures. Expressions got a fix of their own: mutating array methods on $json data work again inside expressions, restoring behavior that users had come to rely on. Two infrastructure-level fixes round out the week: dynamic-credential storage now threads the execution id through so credentials resolve in the right execution context, and proxy environment variables are applied consistently across packages and processes, which matters for anyone running n8n behind a corporate egress proxy. Security maintenance wasn't skipped either — browserslist was bumped to clear CVE-2026-73088 and CVE-2026-73089 on the 1.x line, and the MongoDB node gained parameter binding for sort and projection. The remaining releases in the run — the 2.37.x patches, 2.37.7, 2.38.2, and 1.123.77, plus 2.37.6 — are incremental hardening on the same themes. Notably, most of this lands on both the 1.123 and 2.36–2.38 lines, so upgrading isn't forced to get the fixes.

Trigger.dev keeps the self-hosted path current

Trigger.dev's week was quieter but consistent: the CLI picked up a batch of improvements and a follow-up round of CLI improvements shipped a day earlier, while the Helm chart tracked along in one, two, and three successive chart releases. If you deploy Trigger.dev on Kubernetes, the chart cadence is the part to watch; the CLI updates are the low-friction path for everyone else.

The theme: durable execution is growing up

Taken together, the week is about the unglamorous half of background jobs — making sure runs don't leak, sandboxes are actually ready before you touch them, and credential and proxy resolution behaves the same everywhere. Inngest is pushing sandbox lifecycle into the SDK proper; n8n and Trigger.dev are paying down the operational debt that shows up at scale.