Repository navigation
Version Packages (beta) - #548
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
11 times, most recently
from
September 16, 2026 02:19
893ffe8 to
2b0aee2
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
September 16, 2026 20:19
104ae74 to
d7306a4
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
8 times, most recently
from
September 23, 2026 20:40
970b4f5 to
6644db5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
September 28, 2026 15:07
6643305 to
46bdb0b
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
September 29, 2026 08:18
5b1e9f1 to
d774ba4
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 29, 2026 20:32
d774ba4 to
fa909b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@workflow/web@5.0.0-beta.58
Major Changes
ad0fcc7Thanks @RihanArfan! - Replace Express withsrvxin the standalone server, adding ETag/304,Last-Modified, byte ranges and on-the-fly compression.Patch Changes
9d72807,20e8440,35bc428]:@workflow/cli@5.0.0-beta.58
Minor Changes
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.Patch Changes
ad0fcc7Thanks @RihanArfan! - Track the standalone web UI server as a srvxServer, following the@workflow/webchange.9d72807,20e8440,35bc428,29bc3e0,f58ab84,ee1a09b,35bc428,ad0fcc7,2d8b8a3]:@workflow/core@5.0.0-beta.58
Minor Changes
#2062
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.#4440
ee1a09bThanks @karthikscale3! - Add the optionalworld.telemetry.recordStepExecutionhook so Worlds can correlate flow requests with inline-executed workflow steps.Patch Changes
#4478
9d72807Thanks @VaguelySerious! - Worlds declare dynamic workflow support withcapabilities.dynamicWorkflowCode, replacinggetBackendCapabilities()#4443
29bc3e0Thanks @TooTallNate! - Serialize aDataViewas the bytes it views. It previously fell through to devalue's built-in encoding, which persists the whole backingArrayBuffer— for a view onto Node's pooledBufferallocator, unrelated process memory.Updated dependencies [
9d72807,20e8440,35bc428,f58ab84,ee1a09b,35bc428,2d8b8a3]:@workflow/web-shared@5.0.0-beta.58
Minor Changes
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.Patch Changes
29bc3e0Thanks @TooTallNate! - Add aDataViewreviver so run payloads containing one still hydrate in the observability UI.9d72807,20e8440,29bc3e0,ee1a09b]:workflow@5.0.0-beta.58
Minor Changes
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.Patch Changes
ad0fcc7,9d72807,20e8440,29bc3e0,ee1a09b]:@workflow/world@5.0.0-beta.40
Minor Changes
#2062
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.#4440
ee1a09bThanks @karthikscale3! - Add the optionalworld.telemetry.recordStepExecutionhook so Worlds can correlate flow requests with inline-executed workflow steps.Patch Changes
9d72807Thanks @VaguelySerious! - Worlds declare dynamic workflow support withcapabilities.dynamicWorkflowCode, replacinggetBackendCapabilities()@workflow/world-local@5.0.0-beta.49
Minor Changes
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.Patch Changes
#4478
9d72807Thanks @VaguelySerious! - Worlds declare dynamic workflow support withcapabilities.dynamicWorkflowCode, replacinggetBackendCapabilities()#4458
35bc428Thanks @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-postgres@5.0.0-beta.48
Minor Changes
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.Patch Changes
#4478
9d72807Thanks @VaguelySerious! - Worlds declare dynamic workflow support withcapabilities.dynamicWorkflowCode, replacinggetBackendCapabilities()#4428
efb58a0Thanks @pranaygp! - Leave job attempts past core's max-deliveries ceiling, so a run whose terminalrun_failedwrite 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
35bc428Thanks @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-vercel@5.0.0-beta.53
Minor Changes
#2062
20e8440Thanks @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 explicitexperimental_dynamic.stepsmap, which is not a security boundary: dynamic source runs with the deployment's full privileges. Off by default; a deployment opts in withWORKFLOW_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, and dynamic runs can only start on the current deployment.#4440
ee1a09bThanks @karthikscale3! - Add the optionalworld.telemetry.recordStepExecutionhook so Worlds can correlate flow requests with inline-executed workflow steps.Patch Changes
#4478
9d72807Thanks @VaguelySerious! - Worlds declare dynamic workflow support withcapabilities.dynamicWorkflowCode, replacinggetBackendCapabilities()#4458
35bc428Thanks @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
f58ab84Thanks @karthikscale3! - Limit inline workflow request correlation to the first 10 unique step IDs.#4458
35bc428Thanks @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
2d8b8a3Thanks @pranaygp! - ExportopenEventsChannelso code writing a run's events outside a queue delivery can use the WebSocket events transport.Updated dependencies [
9d72807,20e8440,ee1a09b]:@workflow/astro@5.0.0-beta.58
Patch Changes
@workflow/builders@5.0.0-beta.58
Patch Changes
9d72807,20e8440,29bc3e0,ee1a09b]:@workflow/errors@5.0.0-beta.25
Patch Changes
9d72807,20e8440,ee1a09b]:@workflow/nest@5.0.0-beta.58
Patch Changes
@workflow/next@5.0.0-beta.58
Patch Changes
9d72807,20e8440,29bc3e0,ee1a09b]:@workflow/nitro@5.0.0-beta.58
Patch Changes
9d72807,20e8440,29bc3e0,ee1a09b,ad0fcc7]:@workflow/nuxt@5.0.0-beta.58
Patch Changes
@workflow/rollup@5.0.0-beta.58
Patch Changes
@workflow/sveltekit@5.0.0-beta.58
Patch Changes
@workflow/vite@5.0.0-beta.58
Patch Changes
@workflow/vitest@5.0.0-beta.58
Patch Changes
9d72807,20e8440,29bc3e0,ee1a09b,35bc428]:@workflow/world-testing@5.0.0-beta.58
Patch Changes
ad0fcc7,9d72807,20e8440,29bc3e0,ee1a09b]: