Skip to content

Version Packages (beta) - #4345

Merged
TooTallNate merged 1 commit into
mainfrom
changeset-release/main
Sep 25, 2026
Merged

TooTallNate merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@workflow/astro@5.0.0-beta.57

Patch Changes

  • Updated dependencies [38b5709]:
    • @workflow/vite@5.0.0-beta.57
    • @workflow/builders@5.0.0-beta.57
    • @workflow/rollup@5.0.0-beta.57

@workflow/builders@5.0.0-beta.57

Patch Changes

@workflow/cli@5.0.0-beta.57

Patch Changes

@workflow/core@5.0.0-beta.57

Patch Changes

  • #4327 c0aad6d Thanks @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 Thanks @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 Thanks @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 Thanks @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 Thanks @TooTallNate! - Isolate lifecycle hook getters and reporting failures from terminal writes, and keep background stream operations alive until they settle.

  • #4421 6ac572c Thanks @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 Thanks @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 Thanks @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 Thanks @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 Thanks @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 Thanks @alangenfeld! - Avoid unnecessary queued continuations when released step streams finish draining after the inline wait budget expires.

  • Updated dependencies [54b48ef, f2daf40, 54b48ef, 2694663, 12fcca0]:

    • @workflow/world-vercel@5.0.0-beta.52
    • @workflow/world@5.0.0-beta.39
    • @workflow/world-local@5.0.0-beta.48
    • @workflow/errors@5.0.0-beta.24

@workflow/errors@5.0.0-beta.24

Patch Changes

  • #4326 2694663 Thanks @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.
  • Updated dependencies [f2daf40, 54b48ef]:
    • @workflow/world@5.0.0-beta.39

@workflow/nest@5.0.0-beta.57

Patch Changes

  • Updated dependencies []:
    • @workflow/builders@5.0.0-beta.57

@workflow/next@5.0.0-beta.57

Patch Changes

@workflow/nitro@5.0.0-beta.57

Patch Changes

@workflow/nuxt@5.0.0-beta.57

Patch Changes

  • Updated dependencies []:
    • @workflow/nitro@5.0.0-beta.57

@workflow/rollup@5.0.0-beta.57

Patch Changes

  • Updated dependencies []:
    • @workflow/builders@5.0.0-beta.57

@workflow/sveltekit@5.0.0-beta.57

Patch Changes

  • Updated dependencies [38b5709]:
    • @workflow/vite@5.0.0-beta.57
    • @workflow/builders@5.0.0-beta.57
    • @workflow/rollup@5.0.0-beta.57

@workflow/vite@5.0.0-beta.57

Patch Changes

  • #4370 38b5709 Thanks @alangenfeld! - Rebuild workflows once per file change instead of once per Vite environment.
  • Updated dependencies []:
    • @workflow/builders@5.0.0-beta.57

@workflow/vitest@5.0.0-beta.57

Patch Changes

@workflow/web@5.0.0-beta.57

Patch Changes

  • Updated dependencies [f2daf40, 12fcca0]:
    • @workflow/world-local@5.0.0-beta.48

@workflow/web-shared@5.0.0-beta.57

Patch Changes

workflow@5.0.0-beta.57

Patch Changes

  • Updated dependencies [c0aad6d, ff80d62, 20aa656, 35ebeb4, 25ec4ba, 6ac572c, 0547d9d, f20be08, f2daf40, 6ac572c, bc18326, 2694663, 548147a]:
    • @workflow/core@5.0.0-beta.57
    • @workflow/cli@5.0.0-beta.57
    • @workflow/next@5.0.0-beta.57
    • @workflow/errors@5.0.0-beta.24
    • @workflow/nitro@5.0.0-beta.57
    • @workflow/typescript-plugin@5.0.0-beta.5
    • @workflow/astro@5.0.0-beta.57
    • @workflow/sveltekit@5.0.0-beta.57
    • @workflow/nest@5.0.0-beta.57
    • @workflow/rollup@5.0.0-beta.57
    • @workflow/nuxt@5.0.0-beta.57

@workflow/world@5.0.0-beta.39

Patch Changes

  • #4348 f2daf40 Thanks @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 Thanks @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

Patch Changes

  • #4348 f2daf40 Thanks @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 Thanks @VaguelySerious! - Stop re-executing steps that run longer than 30s: local queue deliveries no longer have a default headers/body deadline

  • Updated dependencies [f2daf40, 54b48ef, 2694663]:

    • @workflow/world@5.0.0-beta.39
    • @workflow/errors@5.0.0-beta.24

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

Patch Changes

  • #4348 f2daf40 Thanks @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'.
  • Updated dependencies [f2daf40, 54b48ef, 2694663, 12fcca0]:
    • @workflow/world@5.0.0-beta.39
    • @workflow/world-local@5.0.0-beta.48
    • @workflow/errors@5.0.0-beta.24

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

Patch Changes

  • #4348 f2daf40 Thanks @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'.
  • Updated dependencies [c0aad6d, ff80d62, 20aa656, 35ebeb4, 25ec4ba, 6ac572c, f2daf40, 6ac572c, 54b48ef, bc18326, 2694663, 548147a]:
    • @workflow/core@5.0.0-beta.57
    • @workflow/cli@5.0.0-beta.57
    • @workflow/world@5.0.0-beta.39
    • workflow@5.0.0-beta.57

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

Patch Changes

  • #4366 54b48ef Thanks @VaguelySerious! - Fix runs started from an older deployment with deploymentId: 'latest' failing on a newer one

  • #4348 f2daf40 Thanks @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'.

  • Updated dependencies [f2daf40, 54b48ef, 2694663]:

    • @workflow/world@5.0.0-beta.39
    • @workflow/errors@5.0.0-beta.24

@github-actions
github-actions Bot requested a review from a team as a code owner September 24, 2026 00:13
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 438b6c2 to 6c5a74a Compare September 24, 2026 08:05
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 6c5a74a to e9bd40d Compare September 24, 2026 17:16
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from efe9386 to fe5535b Compare September 24, 2026 19:45
@github-actions

Copy link
Copy Markdown
Contributor Author

No backport to stable for 35c5b32 (AI decision).

This is an automated "Version Packages (beta)" release commit from the changesets action: it only bumps package versions, appends CHANGELOG entries, and moves consumed changeset files into .changeset/pre/. Release plumbing and version bumps are explicitly not backported; stable maintains its own independent (non-beta) version line.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

35c5b328c83bf8949ed16d9d7ac0f7342bba692a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant