Uh oh!
There was an error while loading. Please reload this page.
Version Packages (beta) - #3378
Merged
Merged
Conversation
Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 7, 2026 09:57
bbd5aff to
eb9e13fComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 7, 2026 17:13
9daf704 to
a8db185Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 7, 2026 20:01
60dc276 to
4bb86d3Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 7, 2026 22:18
019bea8 to
74dbf81Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 8, 2026 04:56
e775650 to
22349e9Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 10, 2026 00:35
b7bf9f1 to
264ddffComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 10, 2026 15:23
2314abc to
1aed119Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 10, 2026 20:53
f2fd984 to
dc61ea1CompareVaguelySerious
approved these changes
Aug 10, 2026
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 10, 2026 22:51
38e38a5 to
1a64f68Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 10, 2026 23:13
5c830cb to
2d5ca54Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 11, 2026 00:36
1a88a4f to
69c30ffComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 11, 2026 15:38
00e7e3f to
b7591fbComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
August 11, 2026 16:08
d56f28f to
6786db9CompareContributorAuthor
🧪 E2E Test Results✅ All tests passed E2E Test SummarySummary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ vercel-multi-region
|
ContributorAuthor
Sim WorldSimulated world deterministic testing for races. Traces 🟠 Mint-ordered log — 6 fail of 41 total
Full trace: 🟢 Append-only log — 0 fail of 41 total
Full trace: |
Uh oh!
There was an error while loading. Please reload this page.
ContributorAuthor
No backport to This is an automated changesets "Version Packages (beta)" release commit: it only bumps package versions, regenerates CHANGELOG entries, and updates To override, re-run the Backport to stable workflow manually via |
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
1 participant
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/builders@5.0.0-beta.41
Minor Changes
4ec7acaThanks @lucamaraschi! - Add an optional observer for accepted workflow SWC transform results.Patch Changes
#3084
264ddffThanks @shalabhc! - Add an opt-in WebSocket transport for event writes during step execution, enabled withWORKFLOW_EVENTS_TRANSPORT=ws. Defaults to HTTP; no behavior change unless explicitly enabled.Updated dependencies [
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,65139ac]:@workflow/world@5.0.0-beta.26
Minor Changes
439a495Thanks @karthikscale3! - Carry the run's pinned deployment on lazy resume messages so misrouted deliveries re-route before thehook_receivedwrite.Patch Changes
#3385
74dbf81Thanks @NathanColosimo! - Retry replay timeouts through normal queue redelivery instead of exiting the process, and keep Postgres jobs retryable through Core's terminal delivery limit.#3382
a8db185Thanks @VaguelySerious! - Fold new events returned byevents.createinto the replay log so a completed wait no longer needs a follow-upevents.listround trip#3389
6786db9Thanks @VaguelySerious! - Breaking: SpecVersion 6: Event IDs are now a dense per-run slot number, allocated by the world at publish time so a rejected write leaves no gap in the event log. A replay tells the world how many events it had read and gets back the ones it did not see, so an event that arrives from outside the replay and lands ahead of an event the replay wrote no longer fails the run withCORRUPTED_EVENT_LOG: it is held for whichever part of the workflow awaits it. A gap in the numbering fails the run instead of being replayed over.#3205
22349e9Thanks @NathanColosimo! - Load replay-event suffixes through one World request.#3124
65139acThanks @NathanColosimo! - Infer required run and step entities, including their start times, fromevents.createrequest types.@workflow/world-vercel@5.0.0-beta.37
Minor Changes
#3286
4bb86d3Thanks @NathanColosimo! - Support Hook minimum retention on Vercel.#3084
264ddffThanks @shalabhc! - Add an opt-in WebSocket transport for event writes during step execution, enabled withWORKFLOW_EVENTS_TRANSPORT=ws. Defaults to HTTP; no behavior change unless explicitly enabled.Patch Changes
#3385
74dbf81Thanks @NathanColosimo! - Retry replay timeouts through normal queue redelivery instead of exiting the process, and keep Postgres jobs retryable through Core's terminal delivery limit.#3382
a8db185Thanks @VaguelySerious! - Fold new events returned byevents.createinto the replay log so a completed wait no longer needs a follow-upevents.listround trip#3370
bf4dda6Thanks @VaguelySerious! - Recover from HTTP/2 connections that stop delivering event requests, and makeWORKFLOW_H2_MULTIPLEX=0disable HTTP/2 on the events path entirely#3389
6786db9Thanks @VaguelySerious! - Breaking: SpecVersion 6: Event IDs are now a dense per-run slot number, allocated by the world at publish time so a rejected write leaves no gap in the event log. A replay tells the world how many events it had read and gets back the ones it did not see, so an event that arrives from outside the replay and lands ahead of an event the replay wrote no longer fails the run withCORRUPTED_EVENT_LOG: it is held for whichever part of the workflow awaits it. A gap in the numbering fails the run instead of being replayed over.#3205
22349e9Thanks @NathanColosimo! - Load replay-event suffixes through one World request.#3191
665110bThanks @NathanColosimo! - Load the current replay log from non-Turborun_startedresponses while preserving Turbo's preload opt-out.#3124
65139acThanks @NathanColosimo! - Infer required run and step entities, including their start times, fromevents.createrequest types.Updated dependencies [
74dbf81,a8db185,439a495,6786db9,22349e9,65139ac]:@workflow/astro@5.0.0-beta.41
Patch Changes
4ec7aca,264ddff]:@workflow/cli@5.0.0-beta.41
Patch Changes
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,bf4dda6,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,665110b,69c30ff,4ec7aca,65139ac,4bb86d3,264ddff]:@workflow/core@5.0.0-beta.41
Patch Changes
#3385
74dbf81Thanks @NathanColosimo! - Retry replay timeouts through normal queue redelivery instead of exiting the process, and keep Postgres jobs retryable through Core's terminal delivery limit.#3124
65139acThanks @NathanColosimo! - Continue partialrun_startedevent preloads from their cursor instead of reloading the event log from the beginning.#3372
1a64f68Thanks @ar-tama! - FixDatesubclassing inside workflow functions. The deterministicDateoverride in the workflow VM now forwardsnew.targetviaReflect.construct, so subclasses likeTZDatefrom@date-fns/tzkeep their identity, methods, and fields. CallingDate()withoutnewnow returns the (fixed) time string per spec, instead of aDateobject.#3382
a8db185Thanks @VaguelySerious! - Fold new events returned byevents.createinto the replay log so a completed wait no longer needs a follow-upevents.listround trip#3286
4bb86d3Thanks @NathanColosimo! - Fail a workflow when its World deterministically rejects Hook creation.#3374
439a495Thanks @karthikscale3! - Carry the run's pinned deployment on lazy resume messages so misrouted deliveries re-route before thehook_receivedwrite.#3342
eb9e13fThanks @TooTallNate! - QuickJS engine: start invocations by restoring a bundle-hydrated VM-memory snapshot instead of re-evaluating the workflow bundle (~25× faster VM startup; bundles with module-scope randomness or clock reads automatically fall back to fresh evaluation). Disable withWORKFLOW_QUICKJS_BASELINE_SNAPSHOT=0.#3263
19b5b85Thanks @TooTallNate! - QuickJS engine: move serialization out of the VM onto the host, replacing the in-VM serde bundle with side-effect-free handle introspection (same wire format, 2–100× faster).#3406
fbebf71Thanks @VaguelySerious! - Fix replay divergence when a step result overtook an earlier sleep or hook delivery that was parked behind an unread hook's payload#3389
6786db9Thanks @VaguelySerious! - Breaking: SpecVersion 6: Event IDs are now a dense per-run slot number, allocated by the world at publish time so a rejected write leaves no gap in the event log. A replay tells the world how many events it had read and gets back the ones it did not see, so an event that arrives from outside the replay and lands ahead of an event the replay wrote no longer fails the run withCORRUPTED_EVENT_LOG: it is held for whichever part of the workflow awaits it. A gap in the numbering fails the run instead of being replayed over.#3205
22349e9Thanks @NathanColosimo! - Load replay-event suffixes through one World request.#3439
69c30ffThanks @VaguelySerious! - Stop reporting replay divergence for an event the workflow is still on its way to consuming, by waiting for in-flight step and hook deliveries instead of a fixed delay#3124
65139acThanks @NathanColosimo! - Infer required run and step entities, including their start times, fromevents.createrequest types.Updated dependencies [
74dbf81,a8db185,439a495,bf4dda6,6786db9,22349e9,665110b,65139ac,4bb86d3,264ddff]:@workflow/nest@5.0.0-beta.41
Patch Changes
4ec7aca,264ddff]:@workflow/next@5.0.0-beta.41
Patch Changes
#3084
264ddffThanks @shalabhc! - Add an opt-in WebSocket transport for event writes during step execution, enabled withWORKFLOW_EVENTS_TRANSPORT=ws. Defaults to HTTP; no behavior change unless explicitly enabled.Updated dependencies [
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,4ec7aca,65139ac,264ddff]:@workflow/nitro@5.0.0-beta.41
Patch Changes
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,4ec7aca,65139ac,264ddff]:@workflow/nuxt@5.0.0-beta.41
Patch Changes
@workflow/rollup@5.0.0-beta.41
Patch Changes
#3084
264ddffThanks @shalabhc! - Add an opt-in WebSocket transport for event writes during step execution, enabled withWORKFLOW_EVENTS_TRANSPORT=ws. Defaults to HTTP; no behavior change unless explicitly enabled.Updated dependencies [
4ec7aca,264ddff]:@workflow/sveltekit@5.0.0-beta.41
Patch Changes
4ec7aca,264ddff]:@workflow/vite@5.0.0-beta.41
Patch Changes
4ec7aca,264ddff]:@workflow/vitest@5.0.0-beta.41
Patch Changes
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,4ec7aca,65139ac,264ddff]:@workflow/web@5.0.0-beta.41
Patch Changes
a8db185,6786db9,22349e9,65139ac]:@workflow/web-shared@5.0.0-beta.41
Patch Changes
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,65139ac]:workflow@5.0.0-beta.41
Patch Changes
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,65139ac,264ddff]:@workflow/world-local@5.0.0-beta.35
Patch Changes
#3382
a8db185Thanks @VaguelySerious! - Fold new events returned byevents.createinto the replay log so a completed wait no longer needs a follow-upevents.listround trip#3389
6786db9Thanks @VaguelySerious! - Breaking: SpecVersion 6: Event IDs are now a dense per-run slot number, allocated by the world at publish time so a rejected write leaves no gap in the event log. A replay tells the world how many events it had read and gets back the ones it did not see, so an event that arrives from outside the replay and lands ahead of an event the replay wrote no longer fails the run withCORRUPTED_EVENT_LOG: it is held for whichever part of the workflow awaits it. A gap in the numbering fails the run instead of being replayed over.#3205
22349e9Thanks @NathanColosimo! - Load replay-event suffixes through one World request.#3124
65139acThanks @NathanColosimo! - Infer required run and step entities, including their start times, fromevents.createrequest types.Updated dependencies [
74dbf81,a8db185,439a495,6786db9,22349e9,65139ac]:@workflow/world-postgres@5.0.0-beta.33
Patch Changes
#3385
74dbf81Thanks @NathanColosimo! - Retry replay timeouts through normal queue redelivery instead of exiting the process, and keep Postgres jobs retryable through Core's terminal delivery limit.#3382
a8db185Thanks @VaguelySerious! - Fold new events returned byevents.createinto the replay log so a completed wait no longer needs a follow-upevents.listround trip#3389
6786db9Thanks @VaguelySerious! - Breaking: SpecVersion 6: Event IDs are now a dense per-run slot number, allocated by the world at publish time so a rejected write leaves no gap in the event log. A replay tells the world how many events it had read and gets back the ones it did not see, so an event that arrives from outside the replay and lands ahead of an event the replay wrote no longer fails the run withCORRUPTED_EVENT_LOG: it is held for whichever part of the workflow awaits it. A gap in the numbering fails the run instead of being replayed over.#3205
22349e9Thanks @NathanColosimo! - Load replay-event suffixes through one World request.#3124
65139acThanks @NathanColosimo! - Infer required run and step entities, including their start times, fromevents.createrequest types.Updated dependencies [
74dbf81,a8db185,439a495,6786db9,22349e9,65139ac]:@workflow/world-testing@5.0.0-beta.41
Patch Changes
74dbf81,65139ac,1a64f68,a8db185,4bb86d3,439a495,eb9e13f,19b5b85,fbebf71,6786db9,22349e9,69c30ff,65139ac]: