Uh oh!
There was an error while loading. Please reload this page.
Version Packages (beta) - #3694
Closed
github-actions[bot] wants to merge 0 commit into
Closed
Conversation
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 20, 2026 19:42
bb755c6 to
c431cc1Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 20, 2026 20:20
ba4580e to
9454d51Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 21, 2026 18:32
89873de to
9b1b8c7Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 21, 2026 18:44
0f3be4f to
d5d19fcComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 21, 2026 18:59
24f06e8 to
d012bf0Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 21, 2026 19:46
6d6644e to
b3dbc6dComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 21, 2026 19:54
f5f5639 to
7b79ba3Compare
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 freeto 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/core@5.0.0-beta.44
Minor Changes
#3700
9b1b8c7Thanks @VaguelySerious! - Pin correlation-ID draw order to event-log order (Node.js VM engine), so two concurrent replays of the same run assign the same IDs even when one loaded a shorter event-log prefix. SetWORKFLOW_LOG_ORDER_DRAWS=0to opt back into arrival-order delivery resolution.#3570
9454d51Thanks @pranaygp! - Addworld.runs.waitForTerminalStatus(runId, { timeoutMs, signal, resolveData })method, which long-polls until the run reaches a terminal status.await run.returnValuenow internally uses this, if the World supports it, instead of using a polling interval.#3634
7b79ba3Thanks @pranaygp! - New runs are created with the sealed-log event identity (specVersion 7). A sealed-log run's event positions are assigned by the backend before each write commits, so concurrent writers never contend for a position. A position whose writer dies is closed by the backend with anoopevent; replay steps over those without delivering them or advancing the deterministic clock. SetWORKFLOW_SEALED_LOG=0to put a deployment back on the previous scheme. Every runtime reads sealed logs either way, and a run's version is fixed at creation, so the setting only affects new runs.Patch Changes
#3675
5b5a926Thanks @TooTallNate! - Step-argument serialization failures now fail the step with a catchableSerializationError(via astep_failedevent, like a step-body failure) instead of failing the run from outside the workflow, and when uncaught they fail the run immediately as aUSER_ERRORrather than retrying until max queue deliveries.Updated dependencies [
d012bf0,9454d51,7b79ba3]:workflow@5.0.0-beta.44
Minor Changes
9b1b8c7Thanks @VaguelySerious! - Pin correlation-ID draw order to event-log order (Node.js VM engine), so two concurrent replays of the same run assign the same IDs even when one loaded a shorter event-log prefix. SetWORKFLOW_LOG_ORDER_DRAWS=0to opt back into arrival-order delivery resolution.Patch Changes
5b5a926,9b1b8c7,9454d51,7b79ba3,8a2648e,37ed049]:@workflow/world@5.0.0-beta.29
Minor Changes
#3570
9454d51Thanks @pranaygp! - Addworld.runs.waitForTerminalStatus(runId, { timeoutMs, signal, resolveData })method, which long-polls until the run reaches a terminal status.await run.returnValuenow internally uses this, if the World supports it, instead of using a polling interval.#3634
7b79ba3Thanks @pranaygp! - New runs are created with the sealed-log event identity (specVersion 7). A sealed-log run's event positions are assigned by the backend before each write commits, so concurrent writers never contend for a position. A position whose writer dies is closed by the backend with anoopevent; replay steps over those without delivering them or advancing the deterministic clock. SetWORKFLOW_SEALED_LOG=0to put a deployment back on the previous scheme. Every runtime reads sealed logs either way, and a run's version is fixed at creation, so the setting only affects new runs.@workflow/world-local@5.0.0-beta.38
Minor Changes
#3570
9454d51Thanks @pranaygp! - Addworld.runs.waitForTerminalStatus(runId, { timeoutMs, signal, resolveData })method, which long-polls until the run reaches a terminal status.await run.returnValuenow internally uses this, if the World supports it, instead of using a polling interval.#3634
7b79ba3Thanks @pranaygp! - New runs are created with the sealed-log event identity (specVersion 7). A sealed-log run's event positions are assigned by the backend before each write commits, so concurrent writers never contend for a position. A position whose writer dies is closed by the backend with anoopevent; replay steps over those without delivering them or advancing the deterministic clock. SetWORKFLOW_SEALED_LOG=0to put a deployment back on the previous scheme. Every runtime reads sealed logs either way, and a run's version is fixed at creation, so the setting only affects new runs.Patch Changes
9454d51,7b79ba3]:@workflow/world-postgres@5.0.0-beta.36
Minor Changes
#3570
9454d51Thanks @pranaygp! - Addworld.runs.waitForTerminalStatus(runId, { timeoutMs, signal, resolveData })method, which long-polls until the run reaches a terminal status.await run.returnValuenow internally uses this, if the World supports it, instead of using a polling interval.#3634
7b79ba3Thanks @pranaygp! - New runs are created with the sealed-log event identity (specVersion 7). A sealed-log run's event positions are assigned by the backend before each write commits, so concurrent writers never contend for a position. A position whose writer dies is closed by the backend with anoopevent; replay steps over those without delivering them or advancing the deterministic clock. SetWORKFLOW_SEALED_LOG=0to put a deployment back on the previous scheme. Every runtime reads sealed logs either way, and a run's version is fixed at creation, so the setting only affects new runs.Patch Changes
9454d51,7b79ba3]:@workflow/world-vercel@5.0.0-beta.40
Minor Changes
#3570
9454d51Thanks @pranaygp! - Addworld.runs.waitForTerminalStatus(runId, { timeoutMs, signal, resolveData })method, which long-polls until the run reaches a terminal status.await run.returnValuenow internally uses this, if the World supports it, instead of using a polling interval.#3634
7b79ba3Thanks @pranaygp! - New runs are created with the sealed-log event identity (specVersion 7). A sealed-log run's event positions are assigned by the backend before each write commits, so concurrent writers never contend for a position. A position whose writer dies is closed by the backend with anoopevent; replay steps over those without delivering them or advancing the deterministic clock. SetWORKFLOW_SEALED_LOG=0to put a deployment back on the previous scheme. Every runtime reads sealed logs either way, and a run's version is fixed at creation, so the setting only affects new runs.Patch Changes
#3599
d012bf0Thanks @karthikscale3! - Preserve upstream HTTP status codes when fetching Workflow run encryption keys.Updated dependencies [
9454d51,7b79ba3]:@workflow/astro@5.0.0-beta.44
Patch Changes
8a2648e]:@workflow/builders@5.0.0-beta.44
Patch Changes
#3454
8a2648eThanks @josuediazflores! - Emitmanifest.jsonin a stable order and remove a redundant compilation round per no-op rebuild in Next dev.Updated dependencies [
5b5a926,9b1b8c7,9454d51,7b79ba3]:@workflow/cli@5.0.0-beta.44
Patch Changes
5b5a926,9b1b8c7,d012bf0,9454d51,7b79ba3,8a2648e]:@workflow/nest@5.0.0-beta.44
Patch Changes
8a2648e]:@workflow/next@5.0.0-beta.44
Patch Changes
#3454
8a2648eThanks @josuediazflores! - Emitmanifest.jsonin a stable order and remove a redundant compilation round per no-op rebuild in Next dev.Updated dependencies [
5b5a926,9b1b8c7,9454d51,7b79ba3,8a2648e]:@workflow/nitro@5.0.0-beta.44
Patch Changes
#3454
8a2648eThanks @josuediazflores! - Emitmanifest.jsonin a stable order and remove a redundant compilation round per no-op rebuild in Next dev.Updated dependencies [
5b5a926,9b1b8c7,9454d51,7b79ba3,8a2648e]:@workflow/nuxt@5.0.0-beta.44
Patch Changes
8a2648e]:@workflow/rollup@5.0.0-beta.44
Patch Changes
8a2648e]:@workflow/sveltekit@5.0.0-beta.44
Patch Changes
#3509
37ed049Thanks @dummdidumm! - Load SvelteKit route configuration through@sveltejs/load-config, including projects that configure SvelteKit exclusively invite.config.Updated dependencies [
8a2648e]:@workflow/vite@5.0.0-beta.44
Patch Changes
8a2648e]:@workflow/vitest@5.0.0-beta.44
Patch Changes
5b5a926,9b1b8c7,9454d51,7b79ba3,8a2648e]:@workflow/web@5.0.0-beta.44
Patch Changes
9454d51,7b79ba3]:@workflow/web-shared@5.0.0-beta.44
Patch Changes
#3692
a06afeeThanks @mitul-s! - Prefix trace viewer marker context cards with "Hook received" or "Attribute set" before the relative time.#3634
7b79ba3Thanks @pranaygp! - Render sealed log positions (noopevents) as the log rows they are: shown in event lists, excluded from span geometry and trace duration, since a seal's timestamp belongs to whichever reader wrote it rather than to the run.#3684
4bd533dThanks @karthikscale3! - Display short step names when observability events contain a workflow-prefixed name.Updated dependencies [
5b5a926,9b1b8c7,9454d51,7b79ba3]:@workflow/world-testing@5.0.0-beta.44
Patch Changes
5b5a926,9b1b8c7,9454d51,7b79ba3]: