Upstash adds multiple labels per run, n8n ships 2.26.0, and Temporal supports standalone Nexus operations

Labels and filtering get more expressive in Upstash Workflow

Upstash Workflow made a significant quality-of-life improvement this week: workflow runs can now carry multiple labels defined as string | string[] on both client.trigger and context.invoke. The log, DLQ, and cancel filters accept arrays to match runs that have any of the given labels — OR semantics rather than the previous single-label constraint. Workflow run logs now expose a labels: string[] field, and context.labels: string[] replaces the deprecated context.label (singular). For teams orchestrating complex branching workflows, this means you can tag a single run with e.g. ["region:us-east", "tier:free", "error:timeout"] and filter by any subset of those tags without needing custom logic.

n8n's busiest week: 2.26.0 leads a wave of patches

n8n had a particularly active week, kicking off with v2.26.0 on Monday. The feature release includes several notable fixes: the API now enforces the redaction floor when creating workflows, and the AWS Rekognition Node handles all binary data modes correctly. The team then followed with a rapid succession of patch releases — 2.26.1 (a CI fix), 2.26.2 (which adds instance settings env telemetry to core and improves credential fetching in the editor), 2.26.3 (fixing AI prompt suggestions in the editor), and 2.26.4 — all within the span of a few days. The 2.25.x and 1.123.x maintenance lines also received backports addressing security issues and a credential-scoped fetch fix for the editor.

Temporal's TypeScript SDK reaches a milestone with standalone Nexus operations

The Temporal TypeScript SDK v1.18.0 is the standout release this week, adding standalone Nexus Operations support. This introduces client.nexus, typed Nexus service clients, operation handles for result/describe/cancel/terminate, list/count APIs, Nexus client interceptors, and Nexus operation errors. The TemporalOperationHandler lets Nexus operations be backed directly by Temporal workflows. A follow-up v1.18.1 corrected continue-as-new handling in workflow-streams subscribe, activity info population, and removed OTel tags from worker metrics. The SDK also published a corrective v1.17.4 after v1.17.3 was accidentally released.

On the server side, v1.31.1 brought Go toolchain and Thrift security patches, fixed a search attribute creation race, and combined PostgreSQL Visibility schema upgrades. A separate v1.29.7 patch addressed security bumps for x/crypto, x/net, and Thrift, plus an encoding fix for the pgx simple protocol.

Inngest deepens observability

Inngest Server v1.27.0 improved trace grouping by step/group IDs in the UI, introduced deterministic finalized step span IDs, and added hard caps to extended trace metrics. The accompanying JS SDK v4.5.1 added step attribution attributes to all extended trace spans, bringing the server and client instrumentation into tighter alignment.