Orchestration platforms get serious about compatibility and sandbox trust

Compatibility as a hard guarantee

Temporal's TypeScript SDK spent the week drawing firmer lines around what Workers will accept. The headline is that Workers now refuse to load Workflow bundles built with a different SDK version — a deliberate break from silently tolerating drift that used to surface as confusing nondeterminism. That ties into the rest of the release: undocumented package subpaths outside explicit export maps no longer resolve, and protobufjs and long are now declared peer dependencies some package managers must install explicitly. In the same cut, Temporal's TypeScript SDK fixed a Workflow task replacement bug that could strand Workflows on nondeterminism errors, and rounded things out with Nexus callback link round-tripping, Workflow-only OpenTelemetry interceptor entrypoints, and experimental external storage error types with concurrency limits.

n8n's 3.0 arrives — and the bug fixes that come with any major

n8n's major line landed this week. The 3.0.0 release is the launch, with 2.46.0 (the last of the 2.x line, and the direct predecessor of 3.0) and the parallel 1.123.x branch close behind. Publishing hiccups followed within a day: 3.0.1 was tagged as a prerelease while 2.46.3 carried the fixes that mattered most in practice — resolving IMAP trigger expressions after activation and adding a cooldown before migration-owner reminders get resent. If you're shopping versions, the honest read is that the 2.46 line is where the stabilization landed, and 3.0.1 is the tip of the new branch.

Security is the strongest n8n theme this week. The 1.123.90 release requires a signed token to accept an invitation, closing an obvious trust hole. The 2.46.1 release added an execution-read permission check to Assistant/AI-builder flows and improved the v3 migration report for removed nodes and the Edit Image entries, so the upgrade path to the new major is more legible. A cluster of smaller but important harness fixes recur across the 2.45.x and 2.44.x branches: 2.45.5 and the 2.46.1 patch itself preserve undefined values in QuickJS expression results and keep the ExpressionError name through minification; 2.46.2 and 2.45.4 start sub-workflow error workflows when a pre-run check fails; 2.46.2 also hands each queue job to one idle worker in turn, the 2.45.6 release records dynamic time saved for queued executions, and 2.44.7 backs off IMAP reconnects when a server drops every new connection. 2.46.3 also brings the migration-reminder cooldown, while 1.123.88 released the SQLite write lock when the write connection fails to open — a genuine fix for self-hosters. On the connector side, an infinite pagination loop in the Google Drive v1 request and an MCP Server Trigger memory leak from idle sessions were both closed. The 1.123.89 and 1.123.91 patches rounded out the branch with legacy Code node expression fixes.

Trigger.dev's v4.8.2: runtimes, Convex, and sub-agents

Trigger.dev used the week to expand runtime surface. The v4.8.2 release adds a bun 1.4 runtime, an experimental Convex component, and streaming sub-agents via chat.forwardSubAgent — but it also carries two breaking changes, so bump deliberately. The matching Helm Chart 4.8.2 shipped alongside for self-hosters. The v4.8.3 CLI and server release followed as an incremental improvement pass, tracked by a 4.8.3 Helm chart.

Inngest: tightening the CI story

Inngest's biggest change is breaking: the @inngest/ci 0.7.0 release renames GitHub events to github-ci/* so CI tooling never collides with other github/* events in a shared environment. There's no alias, so every github.* trigger, github.waitForChecks(), github.waitForWorkflow() and the fixtures helpers need updating. The follow-up 0.7.1 release reworks the GitHub check output: a callout at the top states how long a cache hit saved or which test failed, tool findings show up as line annotations capped at 200 per check, and actions consolidate into a single row. In the runtime SDK, Inngest JS SDK 4.26.1 fixes memory growth when re-registering functions with the same ID, and 4.26.2 adds experimental command shims so a PATH program calls an app handler for privileged work rather than smuggling credentials into the sandbox. The Inngest Server v1.50.0-beta.1 prerelease is internal-only churn.