Graceful shutdown and MCP surface expansion

Safer worker shutdown in Temporal

The headline for orchestration reliability this week comes from the Temporal Go SDK. Version 1.44.1 introduces a long-awaited improvement to graceful shutdown: when the namespace supports poll completion, workers now notify the server during shutdown and let already-polled Workflow, Activity, and Nexus tasks finish within the WorkerStopTimeout window. Previously, stopping a worker meant immediately canceling in-flight polls, which could abandon tasks that had already been delivered to the SDK. Those abandoned tasks would then be retried—or worse, for workflow tasks, they could time out. The change directly addresses a class of reliability edge cases that operators of long-running Temporal clusters have been navigating with workarounds for years.

n8n's MCP story advances

n8n had a busy week, shipping a major version along with a string of patch releases across both its v1 and v2 tracks. The headline release is n8n 2.23.0, which bundles several long-standing bug fixes—including a fix for Azure Cosmos DB nodes that was preserving query parameter types instead of coercing them to strings, and a correction to the AI Builder's default switch node behavior. More interesting for the platform's direction is the experimental release 2.22.4-exp.0, which introduces a UI toggle for MCP access on workflow cards. This is part of a broader push to make MCP (Model Context Protocol) capabilities more visible and manageable directly from the editor surface, rather than buried in configuration.

The patch releases also included important fixes: 2.22.4 removes an overly aggressive temp directory cleanup that was breaking binary data rename operations, and 2.23.1 arrived shortly after the major to address any immediate regressions. On the security front, the v1 track 1.123.47 patched 16 CVEs across vm2, ws, protobufjs, and others, while 1.123.49 fixed a webhook connection leak that could cause MCP connections to accumulate over time.

Inngest and OpenTelemetry hygiene

Inngest shipped two releases worth noting. The Inngest Server v1.23.0 adds positional path parameters to the agentic CLI's invoke-function command, making it more ergonomic to call functions from the command line without having to specify every parameter as a flag. Separately, the JS SDK v4.5.0 bumps the minimum version of @opentelemetry/auto-instrumentations-node to address a security advisory in the transitive @opentelemetry/sdk-node and @opentelemetry/exporter-prometheus packages. Side-by-side with n8n's security patches, this is a reminder that OpenTelemetry's dependency tree—increasingly pervasive across the JS ecosystem—continues to be a vector that SDK maintainers need to actively monitor.