Skip to content

Version Packages (beta) - #4446

Merged
VaguelySerious merged 1 commit into
mainfrom
changeset-release/main
Sep 29, 2026
Merged

VaguelySerious merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 28, 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/web@5.0.0-beta.58

Major Changes

  • #3193 ad0fcc7 Thanks @RihanArfan! - Replace Express with srvx in the standalone server, adding ETag/304, Last-Modified, byte ranges and on-the-fly compression.

Patch Changes

@workflow/cli@5.0.0-beta.58

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

Patch Changes

@workflow/core@5.0.0-beta.58

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

  • #4440 ee1a09b Thanks @karthikscale3! - Add the optional world.telemetry.recordStepExecution hook so Worlds can correlate flow requests with inline-executed workflow steps.

Patch Changes

  • #4478 9d72807 Thanks @VaguelySerious! - Worlds declare dynamic workflow support with capabilities.dynamicWorkflowCode, replacing getBackendCapabilities()

  • #4443 29bc3e0 Thanks @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.

  • Updated dependencies [9d72807, 20e8440, 35bc428, bf4b45c, f58ab84, ee1a09b, 35bc428, 2d8b8a3]:

    • @workflow/world@5.0.0-beta.40
    • @workflow/world-vercel@5.0.0-beta.53
    • @workflow/world-local@5.0.0-beta.49
    • @workflow/errors@5.0.0-beta.25

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

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

Patch Changes

workflow@5.0.0-beta.58

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

Patch Changes

  • Updated dependencies [ad0fcc7, 9d72807, 20e8440, 29bc3e0, ee1a09b]:
    • @workflow/cli@5.0.0-beta.58
    • @workflow/core@5.0.0-beta.58
    • @workflow/errors@5.0.0-beta.25
    • @workflow/next@5.0.0-beta.58
    • @workflow/nitro@5.0.0-beta.58
    • @workflow/typescript-plugin@5.0.0-beta.5
    • @workflow/astro@5.0.0-beta.58
    • @workflow/nest@5.0.0-beta.58
    • @workflow/rollup@5.0.0-beta.58
    • @workflow/sveltekit@5.0.0-beta.58
    • @workflow/nuxt@5.0.0-beta.58

@workflow/world@5.0.0-beta.40

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

  • #4440 ee1a09b Thanks @karthikscale3! - Add the optional world.telemetry.recordStepExecution hook so Worlds can correlate flow requests with inline-executed workflow steps.

Patch Changes

  • #4478 9d72807 Thanks @VaguelySerious! - Worlds declare dynamic workflow support with capabilities.dynamicWorkflowCode, replacing getBackendCapabilities()

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

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

Patch Changes

  • #4478 9d72807 Thanks @VaguelySerious! - Worlds declare dynamic workflow support with capabilities.dynamicWorkflowCode, replacing getBackendCapabilities()

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

  • Updated dependencies [9d72807, 20e8440, ee1a09b]:

    • @workflow/world@5.0.0-beta.40
    • @workflow/errors@5.0.0-beta.25

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

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

Patch Changes

  • #4478 9d72807 Thanks @VaguelySerious! - Worlds declare dynamic workflow support with capabilities.dynamicWorkflowCode, replacing getBackendCapabilities()

  • #4428 efb58a0 Thanks @pranaygp! - Leave job attempts past core's max-deliveries ceiling, so a run whose terminal run_failed write fails transiently at the ceiling is retried instead of stranded when the job runs out of attempts. Jobs enqueued before this release keep their stored cap of 49 attempts (executor transfers carry it forward); only jobs enqueued after upgrading get the headroom.

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

  • Updated dependencies [9d72807, 20e8440, ee1a09b, 35bc428]:

    • @workflow/world@5.0.0-beta.40
    • @workflow/world-local@5.0.0-beta.49
    • @workflow/errors@5.0.0-beta.25

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

Minor Changes

  • #2062 20e8440 Thanks @pranaygp! - Add experimental dynamic workflows: start() accepts workflow source as a string, compiles and stores it with the run through the run-payload serialization pipeline, and replays from that stored code. Steps are exposed to the source through an explicit experimental_dynamic.steps map, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in with WORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.

  • #4488 bf4b45c Thanks @shalabhc! - Default the events transport back to HTTP. The WebSocket events transport is now opt-in with WORKFLOW_EVENTS_TRANSPORT=ws; any other value, including unset or http, uses HTTP.

  • #4440 ee1a09b Thanks @karthikscale3! - Add the optional world.telemetry.recordStepExecution hook so Worlds can correlate flow requests with inline-executed workflow steps.

Patch Changes

  • #4478 9d72807 Thanks @VaguelySerious! - Worlds declare dynamic workflow support with capabilities.dynamicWorkflowCode, replacing getBackendCapabilities()

  • #4458 35bc428 Thanks @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, bound events requests at 60s instead of 300s, and retry event-log reads whose HTTP/2 stream the peer reset.

  • #4483 f58ab84 Thanks @karthikscale3! - Limit inline workflow request correlation to the first 10 unique step IDs.

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

  • #4469 2d8b8a3 Thanks @pranaygp! - Export openEventsChannel so code writing a run's events outside a queue delivery can use the WebSocket events transport.

  • Updated dependencies [9d72807, 20e8440, ee1a09b]:

    • @workflow/world@5.0.0-beta.40
    • @workflow/errors@5.0.0-beta.25

@workflow/astro@5.0.0-beta.58

Patch Changes

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

@workflow/builders@5.0.0-beta.58

Patch Changes

@workflow/errors@5.0.0-beta.25

Patch Changes

@workflow/nest@5.0.0-beta.58

Patch Changes

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

@workflow/next@5.0.0-beta.58

Patch Changes

@workflow/nitro@5.0.0-beta.58

Patch Changes

  • Updated dependencies [9d72807, 20e8440, 29bc3e0, ee1a09b, ad0fcc7]:
    • @workflow/core@5.0.0-beta.58
    • @workflow/web@5.0.0-beta.58
    • @workflow/builders@5.0.0-beta.58
    • @workflow/rollup@5.0.0-beta.58
    • @workflow/vite@5.0.0-beta.58

@workflow/nuxt@5.0.0-beta.58

Patch Changes

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

@workflow/rollup@5.0.0-beta.58

Patch Changes

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

@workflow/sveltekit@5.0.0-beta.58

Patch Changes

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

@workflow/vite@5.0.0-beta.58

Patch Changes

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

@workflow/vitest@5.0.0-beta.58

Patch Changes

  • Updated dependencies [9d72807, 20e8440, 29bc3e0, ee1a09b, 35bc428]:
    • @workflow/world@5.0.0-beta.40
    • @workflow/core@5.0.0-beta.58
    • @workflow/world-local@5.0.0-beta.49
    • @workflow/builders@5.0.0-beta.58
    • @workflow/rollup@5.0.0-beta.58

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

Patch Changes

  • Updated dependencies [ad0fcc7, 9d72807, 20e8440, 29bc3e0, ee1a09b]:
    • @workflow/cli@5.0.0-beta.58
    • @workflow/world@5.0.0-beta.40
    • @workflow/core@5.0.0-beta.58
    • workflow@5.0.0-beta.58

@github-actions
github-actions Bot requested a review from a team as a code owner September 28, 2026 10:31
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 65a86a3 to 2d6a3cf Compare September 28, 2026 20:49
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 2d6a3cf to 984832d Compare September 28, 2026 22:12
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 984832d to ed4cdbb Compare September 29, 2026 00:16
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ed4cdbb to 1e4d5db Compare September 29, 2026 03:42
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1e4d5db to 5756837 Compare September 29, 2026 04:02
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5756837 to 9e49efa Compare September 29, 2026 14:57
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9e49efa to 10918cb Compare September 29, 2026 16:35
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 10918cb to 88789e5 Compare September 29, 2026 17:05
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 88789e5 to 5f69c7c Compare September 29, 2026 18:02
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5f69c7c to 63a33ca Compare September 29, 2026 19:48
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 63a33ca to 05ff1fc Compare September 29, 2026 19:57
@VaguelySerious
VaguelySerious merged commit ee1bf67 into main Sep 29, 2026
23 of 24 checks passed
@VaguelySerious
VaguelySerious deleted the changeset-release/main branch September 29, 2026 21:17
@github-actions

Copy link
Copy Markdown
Contributor Author

No backport to stable for ee1bf67 (AI decision).

This is the changesets-generated "Version Packages (beta)" commit: it only bumps package versions, regenerates CHANGELOG entries, and moves consumed changeset files into .changeset/pre/. Release plumbing like this is explicitly excluded from backports, and 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:

ee1bf672ee850e76104807a65ec7d0f1a0dc8930

This branch was successfully deployed

1 active deployment
Preview – workflow-docs — 5384ed46 Deployed Sep 29, 2026 by vercel[bot]
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