workflow@5.0.0-beta.57

@workflow/core@5.0.0-beta.57

• #4327 c0aad6d @VaguelySerious - When running start({ deploymentId }) cross-deploy, stamp the new run with the spec version that the target deployment reports on its capability probe, instead of the caller's own
• #4398 ff80d62 @pranaygp - Republish a force-claimed hook's victim wake on every replay within 24 hours of the takeover instead of only while the forced hook_created is the claimer's last own event, ensuring resilience against crashes
• #4415 20aa656 @alangenfeld - Stamp events written to another runtime's run (hook_received from resumeHook, run_cancelled from Run.cancel(), and the deployment-mismatch run_failed) with the run's spec version when it is older than the SDK's.
• #4392 35ebeb4 @pranaygp - Parallelize a suspension's hook event writes alongside its step, wait, and attribute events, so a step no longer waits for the hooks created with it to be registered before it can start
• #4216 25ec4ba @TooTallNate - Isolate lifecycle hook getters and reporting failures from terminal writes, and keep background stream operations alive until they settle.
• #4421 6ac572c @TooTallNate - Retry the max-deliveries run_failed write through queue redelivery when it fails transiently (429, 5xx, transport) instead of acking and leaving the run stuck running.
• #4348 f2daf40 @pranaygp - Added a resolveData: 'skip-step-inputs' option, which directs the World to leave out input from step_created and step_started events. Replay recomputes step arguments by re-running workflow code, and steps take their input from the step_started response or from memory, never from the replay log, so replay now reads the event log with this option and no longer downloads recorded step inputs. For workflows that pass growing state into their steps, this removes the part of the replay transfer that grows quadratically. A World that doesn't implement the option must treat it as 'all'.
• #4421 6ac572c @TooTallNate - QuickJS VM: defer a replay after a throttled lazy inline step's backoff, like the node engine, instead of queueing the never-created step as a background step that fails "step not found" until the delivery ceiling.
• #4408 bc18326 @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 2694663 @pranaygp - Mark WorkflowRunFailedError and WorkflowRunCancelledError as non-retryable, 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.
• #4387 548147a @alangenfeld - Avoid unnecessary queued continuations when released step streams finish draining after the inline wait budget expires.

@workflow/cli@5.0.0-beta.57

• #4327 c0aad6d @VaguelySerious - When running start({ deploymentId }) cross-deploy, stamp the new run with the spec version that the target deployment reports on its capability probe, instead of the caller's own

@workflow/world@5.0.0-beta.39

• #4348 f2daf40 @pranaygp - Added a resolveData: 'skip-step-inputs' option, which directs the World to leave out input from step_created and step_started events. Replay recomputes step arguments by re-running workflow code, and steps take their input from the step_started response or from memory, never from the replay log, so replay now reads the event log with this option and no longer downloads recorded step inputs. For workflows that pass growing state into their steps, this removes the part of the replay transfer that grows quadratically. A World that doesn't implement the option must treat it as 'all'.
• #4366 54b48ef @VaguelySerious - Classify each spec version as capability-only or structural (CAPABILITY_ONLY_SPEC_VERSIONS, STRUCTURAL_SPEC_VERSIONS, crossesStructuralSpecVersion), so a backend raising a run to its executor's version knows which moves need a fresh log

@workflow/world-local@5.0.0-beta.48

• #4348 f2daf40 @pranaygp - Added a resolveData: 'skip-step-inputs' option, which directs the World to leave out input from step_created and step_started events. Replay recomputes step arguments by re-running workflow code, and steps take their input from the step_started response or from memory, never from the replay log, so replay now reads the event log with this option and no longer downloads recorded step inputs. For workflows that pass growing state into their steps, this removes the part of the replay transfer that grows quadratically. A World that doesn't implement the option must treat it as 'all'.
• #4351 12fcca0 @VaguelySerious - Stop re-executing steps that run longer than 30s: local queue deliveries no longer have a default headers/body deadline

@workflow/world-postgres@5.0.0-beta.47

• #4348 f2daf40 @pranaygp - Added a resolveData: 'skip-step-inputs' option, which directs the World to leave out input from step_created and step_started events. Replay recomputes step arguments by re-running workflow code, and steps take their input from the step_started response or from memory, never from the replay log, so replay now reads the event log with this option and no longer downloads recorded step inputs. For workflows that pass growing state into their steps, this removes the part of the replay transfer that grows quadratically. A World that doesn't implement the option must treat it as 'all'.

@workflow/world-vercel@5.0.0-beta.52

• #4366 54b48ef @VaguelySerious - Fix runs started from an older deployment with deploymentId: 'latest' failing on a newer one
• #4348 f2daf40 @pranaygp - Added a resolveData: 'skip-step-inputs' option, which directs the World to leave out input from step_created and step_started events. Replay recomputes step arguments by re-running workflow code, and steps take their input from the step_started response or from memory, never from the replay log, so replay now reads the event log with this option and no longer downloads recorded step inputs. For workflows that pass growing state into their steps, this removes the part of the replay transfer that grows quadratically. A World that doesn't implement the option must treat it as 'all'.

@workflow/world-testing@5.0.0-beta.57

• #4348 f2daf40 @pranaygp - Added a resolveData: 'skip-step-inputs' option, which directs the World to leave out input from step_created and step_started events. Replay recomputes step arguments by re-running workflow code, and steps take their input from the step_started response or from memory, never from the replay log, so replay now reads the event log with this option and no longer downloads recorded step inputs. For workflows that pass growing state into their steps, this removes the part of the replay transfer that grows quadratically. A World that doesn't implement the option must treat it as 'all'. - workflow@5.0.0-beta.57

@workflow/next@5.0.0-beta.57

• #4409 0547d9d @pranaygp - Update the next devDependency to 16.3.6, matching the Next.js apps that wrap their config with withWorkflow()
• #4337 f20be08 @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/vite@5.0.0-beta.57

• #4370 38b5709 @alangenfeld - Rebuild workflows once per file change instead of once per Vite environment.

@workflow/errors@5.0.0-beta.24

• #4326 2694663 @pranaygp - Mark WorkflowRunFailedError and WorkflowRunCancelledError as non-retryable, 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.