Temporal ships standalone activities GA as Trigger.dev lands a breaking major

Standalone activities reach GA

The week's most consequential change came from Temporal's Go SDK v1.49.0, which graduates standalone activities from experimental to generally available. That means the API surface is now stable enough to build on: options previously named Details are now StaticDetails, and description getters moved to GetStaticDetails, alongside new ExecutionTime and TotalHeartbeatCount fields. If you have code against the experimental version, the rename is the migration you need to budget for. Server-side, the v1.31.3 patch added panic handlers to the matching handler APIs and a Nexus callback source header inspection toggle, with the same panic-handling cherry-pick landing on the older maintained branch in v1.30.7. Those are unglamorous but exactly the kind of change that keeps a matching service from taking down a whole cluster when a handler misbehaves.

On the TypeScript side, SDK v1.24.0 carried two breaking changes worth flagging before you upgrade: @temporalio/openai-agents now demands @openai/agents-core and @openai/agents-openai at ~0.14.3, so projects pinned to 0.13.x will hit peer dependency conflicts, and the experimental external storage StorageDriverSelector now takes a StorageDriverSelectContext instead of StorageDriverStoreContext.

Trigger.dev's major release and a wave of Helm charts

The trigger.dev v4.6.0 release is the one to read the changelog for: it leads with breaking changes, and was followed within two days by v4.6.1, v4.6.2, and v4.6.3, each adding schedule-policy warnings and other refinements. The velocity suggests the team is shaking out rough edges quickly, so pinning to a specific patch rather than tracking the minor is the safer posture this week. Self-hosters got four matching chart releases — 4.6.0, 4.6.1, 4.6.2, and the backport 4.5.16, plus 4.6.3 — which is churn worth noting mostly as a signal that the 4.6 line is actively settling.

OAuth in the CLI, and a quiet correctness pass on security

Inngest Server v1.45.0 added CLI OAuth login, storing credentials in the OS credential store with automatic refresh and giving you inngest login, auth status, logout, and a --force re-login. It's a small quality-of-life win that removes long-lived tokens from shell history and CI configs. The follow-up v1.45.1 lets operators drop permanently unroutable queue items, but only when they explicitly opt in via WithPermanentConstraintErrorHandler — default behavior is unchanged, so nothing silently disappears from your queues.

n8n's week was a dense run of patches whose common thread was data integrity and credentials. The headliner is n8n@2.40.0, a minor with AI Agent fixes around preserving Anthropic thinking blocks across tool calls; from there the 2.40 line absorbed 2.40.1, 2.40.2, and 2.40.3, including a repair for data-encryption keys stored as the raw instance key — a fix duplicated onto the 2.39 branch in 2.39.8. Around it, credential-domain enforcement tightened across 2.39.5, 2.39.6, 2.39.7, 1.123.80, and 1.123.81, with breaking-change detection made resilient to throwing rules and number values fixed in credential inputs. If you run a mixed 1.x and 2.x fleet, the same fixes are landing on both tracks.