Sandboxes, CI pipelines, and stronger workflow guarantees

Inngest had the busiest week of the collection, splitting its attention between a brand-new product line and polish on its core SDK. The headline is the first release of @inngest/ci, a Labs project that lets you define CI pipelines in TypeScript and run them with Inngest on Sandboxes. It was followed quickly by a stability pass that pins pipeline runs to the same plan on every attempt, so runs end with fixed steps whether they pass or fail, jobs settled with Promise.allSettled no longer fail the pipeline, and machines stop being paused mid-run. Supporting that story, the Inngest server itself gained sandbox secret name arrays and a dashboard sidebar for managing them — you can now create a sandbox with secrets: ["OPENAI_API_KEY"] and import .env files into editable rows rather than hand-wiring credentials. On the SDK side, the metadata builders moved to a set() call that replaces all values for a kind, deprecating the repeat-call update() pattern, and runWithAsyncCtx is now exported from the experimental entrypoint for anyone wiring their own async context.

n8n tightens up its workflow surface

n8n shipped a wide spread of releases, but two themes dominate. First, safety: the 2.43 and 2.42 lines both block creating or updating workflows that contain deprecated nodes, a guardrail that keeps aging definitions from being reintroduced. Second, the Assistant experience got meaningful attention — self-hosted Assistant installations regained support for Kimi K3 and other OpenAI-compatible model providers, the Agent artifact now appears while the builder is still creating it, and the agent builder's system prompt was made static specifically to preserve prompt caching. Alongside that, the 2.43.0 line pulled together a batch of Agent Node and AI-builder fixes, including treating a blank folder path as no folder, and task runners were fixed to survive an unhandled promise rejection instead of dying mid-workflow. The Google Gemini node also picked up Nano Banana 2.1 and 2 Lite in its image model list across the 2.43 and 2.42 branches, and older 2.41.x users got the model-list refresh plus Gateway credit promotions on community nodes.

Temporal's storage layer and checker move forward

Temporal's Go ecosystem spent the week on foundational housekeeping. Four storage drivers — the GCS storage driver and its gcssdk counterpart, plus the S3 driver and its awssdkv2 variant — moved in lockstep to a minimum Go 1.26.0 and a minimum Go SDK of v1.49.0, which passes drivers a dedicated select context rather than the store context. The S3 driver additionally identifies stored objects by object_name while still writing and reading the legacy key field, so mixed-version deployments resolve claims in both directions. Separately, workflowcheck now catches non-deterministic code hidden behind same-package call cycles, such as logic reached through encoding/json, and reports reasons in stable source order — intermittent failures may become consistent, which is the point. The server itself routed SAA activity task validation correctly and lets task queue user data be preserved and observed.

Trigger.dev keeps pace

Trigger.dev put out a patch release covering its CLI and Docker image, with the matching Helm chart bump for self-hosted deployments so Kubernetes installs track the same version.