--- collection: workflow-orchestration collection_name: Background Jobs & Orchestration week_start: 2026-08-31 title: Sandbox control arrives in the JS SDK while n8n hardens under the hood release_count: 18 generated: 2026-09-07 canonical: https://releases.sh/collections/workflow-orchestration/digest/2026-08-31 --- # Sandbox control arrives in the JS SDK while n8n hardens under the hood Inngest's JavaScript SDK shipped a full sandbox snapshot lifecycle — create, list, get, wait, delete, and clone — alongside Trigger.dev's latest patch releases, while n8n pushed a wave of stability fixes across its 1.x, 2.36, 2.37, and 2.38 branches, including a security-driven dependency bump and several core execution fixes. ### Full sandbox lifecycle control in Inngest The big story this week is Inngest's JavaScript SDK maturing its step sandboxes from a simple execution primitive into a manageable resource. [Inngest's new sandbox snapshot APIs](/release/rel_Gx2cE1I_tdG739md-UwLj-inngest-4-20-0) — available on both the direct client and `step.sandbox` — let you create, list, get, wait for, delete, and clone sandbox snapshots. That last one is particularly interesting: cloning means you can establish a known-good state, let a step mutate it, then reset to baseline for the next run — a natural fit for parallelizing stateful jobs or testing deterministic behavior without rebuilding from scratch each time. The accompanying [Inngest 4.19.0](/release/rel_ZE44cxkm_G83O8HMR7Xe8-inngest-4-19-0) tightened the developer experience around this feature. Newly created sandboxes now wait for a `RUNNING` state by default before proceeding, with `runningTimeout: false` available as an explicit opt-out. That removes a whole class of flaky "sandbox not ready" races that would otherwise surface as intermittent failures in CI or production. A smaller housekeeping update to [@inngest/ai](/release/rel_G_pFwdHZL7D11k8xzkXLc-inngest-ai-0-1-8) — moving `@types/node` and `typescript` to dev dependencies — trims runtime weight for AI features that depend on the SDK. ### n8n's steady reliability march n8n spent the week shipping a chain of patch releases across four maintenance branches, and while no single release dominates, a clear reliability theme runs through them. Two fixes stand out for anyone deep in workflow execution. [n8n 2.37.9](/release/rel_kgQV3TMNPNDHkB_gxYWXd-n8n-2-37-9) restored mutating array methods on `$json` data in expressions — a behavior change that could silently break existing workflows that relied on in-place array operations. And [2.38.3](/release/rel_OSGwxx7WSaMRRjqDOYDkC-n8n-2-38-3) ensures running jobs are cleaned up when a workflow run rejects, closing a potential resource leak. Security got attention too, with [n8n 1.123.76](/release/rel_HWLoALPQfQbfkEHLGKAoJ-n8n-1-123-76) bumping `browserslist` to clear CVE-2026-73088/73089. Elsewhere, proxy environment variables are now applied consistently across packages and processes in [2.36.9](/release/rel_lwnQz1gMmDFpsvQqSLtgU-n8n-2-36-9) — a fix that matters for anyone running n8n behind a corporate proxy — and [2.38.1](/release/rel_jDgYSgEIFbsZOrq-6LgYR-n8n-2-38-1) added parameter binding for MongoDB sort and projection operations, plus an AI Builder fix for agent artifacts in the preview tab. Earlier in the week, [2.37.6](/release/rel__k_EAiR5cgbf7nXslQRL3-n8n-2-37-6) threaded execution IDs through dynamic-credential storage, addressing a correctness issue for workflows that fetch credentials at runtime, and [2.37.7](/release/rel_ZXFPIBjE4WEMavV0yxsl6-n8n-2-37-7) and [2.38.2](/release/rel_mKLAC3gOix_IkE5FlPrSd-n8n-2-38-2) shipped further stability patches. ### Trigger.dev patch cadence Trigger.dev kept its release train moving with [v4.5.16](/release/rel_gtDSkq0bon67C1mDKARoN-trigger-dev-v4-5-16) and [v4.5.15](/release/rel_Ou-biHL74qlCadwdzKktw-trigger-dev-v4-5-15), both carrying improvements to the platform's task execution. Self-hosters also saw three Helm Chart updates — [4.5.15](/release/rel_JtFYIvFjGzhMaIPdxg3p4-helm-chart-4-5-15), [4.5.14](/release/rel_4qBRKVQewuHhiHB0haTjv-helm-chart-4-5-14), and [4.5.13](/release/rel_6OT6NmCIgyp5m1yZj8RP5-helm-chart-4-5-13) — keeping the Kubernetes deployment path aligned with the core release. Nothing here is headline-grabbing, but the steady cadence reflects a project comfortable shipping incremental quality. Taken together, the week reads as one of consolidation: the most novel capability landed in Inngest's sandbox lifecycle, while n8n and Trigger.dev focused on hardening — fixing correctness bugs, closing security gaps, and smoothing out execution edges across the board. ## Releases covered ### Inngest - [inngest@4.20.0](https://releases.sh/release/rel_Gx2cE1I_tdG739md-UwLj-inngest-4-20-0) - [inngest@4.19.0](https://releases.sh/release/rel_ZE44cxkm_G83O8HMR7Xe8-inngest-4-19-0) - [@inngest/ai@0.1.8](https://releases.sh/release/rel_G_pFwdHZL7D11k8xzkXLc-inngest-ai-0-1-8) ### n8n - [n8n@2.37.9](https://releases.sh/release/rel_kgQV3TMNPNDHkB_gxYWXd-n8n-2-37-9) - [n8n@2.38.3](https://releases.sh/release/rel_OSGwxx7WSaMRRjqDOYDkC-n8n-2-38-3) - [n8n@1.123.76](https://releases.sh/release/rel_HWLoALPQfQbfkEHLGKAoJ-n8n-1-123-76) - [n8n@2.36.9](https://releases.sh/release/rel_lwnQz1gMmDFpsvQqSLtgU-n8n-2-36-9) - [n8n@2.38.1](https://releases.sh/release/rel_jDgYSgEIFbsZOrq-6LgYR-n8n-2-38-1) - [n8n@2.37.6](https://releases.sh/release/rel__k_EAiR5cgbf7nXslQRL3-n8n-2-37-6) - [n8n@2.37.7](https://releases.sh/release/rel_ZXFPIBjE4WEMavV0yxsl6-n8n-2-37-7) - [n8n@2.38.2](https://releases.sh/release/rel_mKLAC3gOix_IkE5FlPrSd-n8n-2-38-2) ### Trigger.dev - [trigger.dev v4.5.16](https://releases.sh/release/rel_gtDSkq0bon67C1mDKARoN-trigger-dev-v4-5-16) - [trigger.dev v4.5.15](https://releases.sh/release/rel_Ou-biHL74qlCadwdzKktw-trigger-dev-v4-5-15) - [Helm Chart 4.5.15](https://releases.sh/release/rel_JtFYIvFjGzhMaIPdxg3p4-helm-chart-4-5-15) - [Helm Chart 4.5.14](https://releases.sh/release/rel_4qBRKVQewuHhiHB0haTjv-helm-chart-4-5-14) - [Helm Chart 4.5.13](https://releases.sh/release/rel_6OT6NmCIgyp5m1yZj8RP5-helm-chart-4-5-13)