workflow@4.8.10

@workflow/core@4.8.10

• #4176 e1f712b @pranaygp - Fix an unhandled rejection that could exit the process when the encryption-key lookup for a forwarded writable stream failed (for example a run metadata read that timed out) before anything was written to that stream. The lookup now starts on the first write, and a failure rejects that stream instead.
• #4443 3699c30 @TooTallNate - Serialize a DataView as the bytes it views. It previously fell through to devalue's built-in encoding, which persists the whole backing ArrayBuffer — for a view onto Node's pooled Buffer allocator, unrelated process memory.
• #4422 bc6a97f @TooTallNate - Retry the max-deliveries run_failed/step_failed write and the step handler's workflow re-queue through queue redelivery when they fail transiently (429, 5xx, transport) instead of acking and leaving the run stuck running.
• #4408 b23170d @pranaygp - start() with an explicit deploymentId (and so recreateRunFromExisting, i.e. Replay Run) no longer fails in a process that is not itself a deployment; it takes the cross-deployment path instead.
• #4326 5e6c79c @pranaygp - Mark WorkflowRunFailedError and WorkflowRunCancelledError as non-retryable, and make FatalError.is() honor the fatal marker, so a step that reads a terminal run's returnValue fails on its first attempt with the error intact instead of exhausting its retry budget first.
• #4179 d437c32 @karthikscale3 - Route unrecognized backend connection and stream failures through existing retry policies, rebuilding shared event connections after repeated HTTP/2 failures. Keep invalid backend URLs, blocked ports, and unsupported request headers out of those retries. Include error cause chains in run-failure logs to expose underlying socket, DNS, and TLS failures.

@workflow/cli@4.3.14

• #4443 3699c30 @TooTallNate - Add a DataView reviver so run payloads containing one still hydrate in the observability UI and CLI.

@workflow/world-local@4.4.2

• #4458 42c9810 @pranaygp - Upgrade undici to 7.30.0, which stops a failed HTTP/2 stream from leaving a phantom in-flight request on its connection.

@workflow/world-postgres@4.3.8

• #4458 42c9810 @pranaygp - Upgrade undici to 7.30.0, which stops a failed HTTP/2 stream from leaving a phantom in-flight request on its connection.

@workflow/world-vercel@4.7.5

• #4458 42c9810 @pranaygp - Send event requests with bodies too large to re-buffer over HTTP/1.1 so they no longer stall behind in-flight HTTP/2 streams, and retry event-log reads whose HTTP/2 stream the peer reset.
• #4179 d437c32 @karthikscale3 - Route unrecognized backend connection and stream failures through existing retry policies, rebuilding shared event connections after repeated HTTP/2 failures. Keep invalid backend URLs, blocked ports, and unsupported request headers out of those retries. Include error cause chains in run-failure logs to expose underlying socket, DNS, and TLS failures.
• #4458 42c9810 @pranaygp - Upgrade undici to 7.30.0, which stops a failed HTTP/2 stream from leaving a phantom in-flight request on its connection.

@workflow/web-shared@4.1.26

• #4443 3699c30 @TooTallNate - Add a DataView reviver so run payloads containing one still hydrate in the observability UI and CLI.

@workflow/next@4.1.14

• #4337 304e5dc @pranaygp - Fix next dev sometimes running the workflow build (and starting a second watcher) twice on startup when Next.js resets process.env between next.config evaluations

@workflow/errors@4.2.2

• #4326 5e6c79c @pranaygp - Mark WorkflowRunFailedError and WorkflowRunCancelledError as non-retryable, and make FatalError.is() honor the fatal marker, so a step that reads a terminal run's returnValue fails on its first attempt with the error intact instead of exhausting its retry budget first.