BetaWeekly digests are a beta — we're trying something new. Feedback welcome.
Workflow engines turn to credential hygiene and tighter run control
November 9–15, 2026
Temporal's Go SDK reworked query replay and RPC timeouts while adding AWS Secrets Manager credential loading, Inngest brought event subscriptions into running steps, and Trigger.dev shipped a security patch plus tighter deploy and API key controls.
The week at a glance
Replay the weekBiggest releases
- 01Temporal Go SDK v1.51.0 changes query replay and ContinueAsNew interceptors
Temporal - 02Inngest Server v1.52.0 adds step.subscribe inboxes and inngest deploy CLI
Inngest - 03Temporal Go SDK Lambda worker v0.2.0 loads client credentials from Secrets Manager
Temporal - 04Temporal Go SDK envconfig v1.1.0 requires Go 1.26 and adds config extensions
Temporal - 05Inngest Server v1.53.0 prevents sleep ID collisions between runs
Inngest
Credentials move out of config files
The week's clearest thread ran through Temporal's Go tooling: secrets are being pushed out of plaintext config and into managed stores. The new Secrets Manager client config extension lets envconfig profiles pull API keys and TLS cert/key/CA from AWS Secrets Manager by secret ID, and the Lambda worker now loads client options through that same extension, so a deployed worker can read its Temporal credentials from a secret ID env var instead of shipping them alongside the code. Supporting this, envconfig gained extensible profile fields and client config extensions, allowing plugins to read their own config from profile.<profile>.ext.<name> tables and env vars, plus an AdditionalProfileFields option for nested extras. That envconfig release also raises the minimum Go version to 1.26, a bump the Lambda worker carries too, and turns duplicate array keys in TOML into an error.
Temporal widens its replay and timeout controls
Temporal's Go SDK v1.51.0 did the heavier lifting this week. Queries delivered without new history now stop replay at the last completed workflow task, so pending signals no longer get applied to closed workflows — a subtle correctness fix for anyone whose query handlers assumed they were seeing a live state. The same release adds a client.Options.RPCTimeout for raising the default RPC cap above ten seconds (shorter caller deadlines still win, and long-poll calls keep their own timeouts), an experimental SignalWithStartWorkflow, and an opt-in WorkflowTaskFailureError payload codec error that fails the current task rather than the whole execution. Premature activity cancellation on heartbeat errors is fixed too.
Inngest lets running steps listen, and stops sleeps colliding
Inngest's step.subscribe inboxes are the headline: a run can now receive and read matching events while it executes, rather than waiting for a function to be re-triggered. That release also added an inngest deploy CLI for building and deploying apps described in inngest.toml, exposed app sync history through new v2 API endpoints with CLI and MCP equivalents, and fixed run details showing a previous run's selected step after navigation. A follow-up fixed sleep ID collisions between runs that reuse an event key, a bug that could bite anyone scheduling sleeps per-key, and moved the lake's JSON columns to JSON text so ->> and json_* operators work — at the cost of an in-place baseline DDL change with a migration to run.
Trigger.dev hardens deploys
Trigger.dev's week was mostly about who can do what. Its security release moves deployed tasks onto the November 2026 Node.js security releases, closing high-severity HTTP/2 and TLS vulnerabilities; only tasks that themselves run an HTTP/2 or HTTPS server inside them are exposed, and the CLI needs updating and redeploying either way. Alongside it came trusted publishing for GitHub Actions, restricting deploys to a chosen repository, branch, or environment, and custom access and saved presets for API keys, so each key gets exactly the permissions it needs and teams can see how it is used. The earlier v4.8.4 update had already landed outbound OIDC for tasks, inbound trusted publishing, and the API key management overhaul that these build on.
n8n's patch train
n8n cut sixteen releases across three version lines, and the recurring item is a fix for limiting resume attempts on stuck waiting and queued executions. Elsewhere the expression engine kept node references matching consistently, the Public API began rejecting edits to read-only credential nodes, and operators got a fix for retry backoff surviving a trigger failure right after reactivation plus trusted-source cache keys kept in a single Redis cluster slot and an opt-out from prompt caching for endpoints that reject the cache fields. The current release line stopped redacting executions that use global credentials, while the editor fixed JSON highlight contrast on light themes.
Releases covered8
- Temporal Go SDK secretsmanager v0.1.0 reads client credentials from AWS Secrets Manager (opens in new tab)
- Temporal Go SDK Lambda worker v0.2.0 loads client credentials from Secrets Manager (opens in new tab)
- Temporal Go SDK envconfig v1.1.0 requires Go 1.26 and adds config extensions (opens in new tab)
- Temporal Go SDK v1.51.0 changes query replay and ContinueAsNew interceptors (opens in new tab)