Proxy routing, credential scoping, and protobuf churn across the job stack

n8n cleans up the plumbing around proxies and credentials

n8n's week was almost entirely corrective, and two threads run through it. The first is networking: OAuth2 token requests now go through environment proxies in every process, closing a gap where some processes bypassed the proxy configuration. The distroless runner image got a related round of fixes, with glibc copied in as a matched pair and the missing local atomic library staged alongside it — the kind of build repair that mostly matters to self-hosted operators whose containers were failing to start.

The second thread is credential scoping. A domain-restricted credential that previously refused to authenticate to the node it belonged to now works in its own node, a fix that landed on both the current and previous release lines.

Elsewhere the API surface got a defensive pass: decorator routes that accept a body now require a JSON content type, and the binary data endpoint was adapted to match. Alongside those, the larger 2.37.0 cut brought fixes across the Agent Node's prompt-source options and patched autosave and publish events in the AI builder. The earlier 2.36.6 release was editor-only housekeeping, surfacing the personalization survey and community registration modal on the Instance AI landing page. Taken together, it's a maintenance week: nothing new to learn, several sharp edges filed off.

Inngest puts scores and AI usage on the run timeline

Inngest shipped one feature release, and it's about observability rather than execution. Scores recorded on a step now appear as a badge on that step's bar in the run timeline, with a hover card listing each score and its value — so a run's quality signals sit next to its timing instead of in a separate view. The same release adds a run-level AI usage summary, which should make it easier to see how much of a workflow's work is being done by models and at what cost. If you instrument steps with scores today, this is the payoff.

Temporal's TypeScript SDK takes a protobufjs major

Temporal's TypeScript SDK shipped one release with a breaking note worth reading before you upgrade: protobufjs moved to v8 and protobufjs-cli to v2. Because Temporal's generated protobuf message types are part of the public API surface — largely through @temporalio/proto and the client's raw gRPC interfaces — the upgrade changes some generated types. Most applications never touch those directly, but if you do, expect to adjust type annotations rather than runtime behavior.

Trigger.dev keeps deploying

Trigger.dev's two releases were small and deployment-focused, most notably changes to how trigger.dev deploy behaves alongside a follow-up round of improvements and fixes. Nothing here changes how you write tasks; it's the kind of churn you pick up with an update before your next deploy.