Temporal's Go SDK ships standalone activities as GA while Trigger.dev pushes a breaking v4.6

Temporal's SDKs reach milestones

The headline of the week came from Temporal's Go SDK, which promoted standalone activities to general availability. That milestone brings a set of API adjustments: the Details option on StartActivityOptions was renamed to StaticDetails, GetDetails became GetStaticDetails, and new description fields for execution time and heartbeat count were added. The rename touches production code, so Go users should plan for the migration before upgrading.

The TypeScript SDK shipped a release with its own breaking changes — most notably, @temporalio/openai-agents now requires @openai/agents-core and @openai/agents-openai at ~0.14.3, meaning projects pinned to 0.13.x will hit peer dependency conflicts until they upgrade. The experimental external storage driver selector also changed its parameter type, and a new experimental feature was introduced.

On the server side, Temporal added panic handlers to its matching handler APIs and introduced a Nexus callback source header inspection toggle, hardening the matching layer against unexpected failures. A parallel patch for the v1.30 maintenance line brought the same panic-handler fix to older deployments.

Trigger.dev's breaking v4.6

Trigger.dev's v4.6.0 landed with breaking changes, and the v4.6.1 follow-up added schedule policy warnings to help users catch misconfigured schedules before they cause problems. v4.6.2 continued with authorization improvements, and v4.6.3 rounded out the week with further refinements. The Helm chart line kept pace, with chart updates tracking the CLI releases and a maintenance chart update for the older 4.5 line for users not yet ready to move to 4.6.

n8n's security and stability focus

n8n spent the week repairing data-encryption keys that had been stored as the raw instance key, a fix that landed across the 2.39 branch and the 2.40 branch. The team also fixed a blank workflow preview issue in the AI Assistant and swept parents parked on finished sub-executions, clearing a class of stuck executions.

On the 1.123 line, n8n allowed domain-restricted credentials to work in their own node and applied credential allowed domains to declarative node requests, tightening credential scoping. The 2.40 line also kept breaking-change detection running when a rule throws and sent number values correctly in credential inputs, fixes mirrored on the 2.39 branch. A v3 breaking-change rule for the storage directory rename gave users advance warning of an upcoming migration, while the editor fixed end-user credential revocation and added log streaming events for instance reports.

Inngest brings OAuth to the CLI

Inngest's CLI gained OAuth login support, storing credentials in the OS credential store and refreshing them automatically — a meaningful quality-of-life improvement for teams using Inngest Cloud. The server also added an opt-in mechanism to drop permanently unroutable queue items, which consumers must explicitly enable via WithPermanentConstraintErrorHandler; existing behavior is unchanged otherwise.