Skip to content

Version Packages (beta) - #391

Closed
github-actions[bot] wants to merge 0 commit into
mainfrom
changeset-release/main
Closed

github-actions[bot] wants to merge 0 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 15, 2026 •

Copy link
Copy Markdown

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/core@5.0.0-beta.39

Minor Changes

  • #3186 4a9d26b Thanks @alangenfeld! - Record the compute instance that ran each step attempt: CreateEventParams.computeInstanceId is stamped on step_started writes, forwarded in the world-vercel v4 frame meta alongside vercelId, read back on AnalyticsEvent / AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.

  • #3244 ee944d2 Thanks @pranaygp! - Stamp the creating client's environment into the queue message's runInput, and refuse a queue delivery whose run was created in a different environment than the consuming deployment runs in, so one run ID can no longer be forked into two environments.

  • #3145 1471f25 Thanks @VaguelySerious! - Strengthen the event-creation precondition guard: replay-context writes now also send the number of loaded events, so a snapshot that is missing an event is rejected instead of committing a divergent event log, and a rejection restarts the replay in-process (consuming the events a world may attach to the rejection) rather than re-committing the rejected payload or re-invoking over the queue. @workflow/world-local and @workflow/world-postgres do not implement the check.

  • #2989 9cc11f5 Thanks @alangenfeld! - Emit a faas.instance OTEL span attribute (a synthesized per-warm-instance id) on the flow and step route spans, so traces can distinguish which compute instance handled each request.

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

  • #1834 438eaa6 Thanks @TooTallNate! - Make resumeHook() resilient to transient hook_received event write failures (429/5xx) by carrying the payload on the queue message for the runtime to materialize. Returned Hook gets a new resilientResume: true flag when this fallback path is taken.

Patch Changes

  • #3288 679dfa9 Thanks @NathanColosimo! - Simplify hardened serialization: intrinsic captures assert at import instead of degrading per use, URLSearchParams now serializes natively on Node 18, and bound-function getters are reported as guest code (previously a getter defined via fn.bind() executed with an empty report).

  • #3257 b732e91 Thanks @TooTallNate! - Serializing values built inside the node:vm workflow VM no longer executes workflow code, using engine brand checks and host intrinsics captured at boot.

  • #3273 4174a6e Thanks @VaguelySerious! - Treat an empty VERCEL_URL as not running on Vercel, so a .env.local left behind by vercel env pull no longer makes local runs fail with Invalid URL

  • #3208 4017597 Thanks @alangenfeld! - Report replay-divergence counts on event writes that recover or exhaust replay retries.

  • Updated dependencies [4a9d26b, 1471f25, c93f6f7, 31f92df, 4017597, 438eaa6, ee944d2, 2677653, aa78a7e, f05f642, ee944d2]:

    • @workflow/world@5.0.0-beta.24
    • @workflow/world-vercel@5.0.0-beta.35
    • @workflow/errors@5.0.0-beta.15
    • @workflow/world-local@5.0.0-beta.33

@workflow/errors@5.0.0-beta.15

Minor Changes

  • #3145 1471f25 Thanks @VaguelySerious! - Strengthen the event-creation precondition guard: replay-context writes now also send the number of loaded events, so a snapshot that is missing an event is rejected instead of committing a divergent event log, and a rejection restarts the replay in-process (consuming the events a world may attach to the rejection) rather than re-committing the rejected payload or re-invoking over the queue. @workflow/world-local and @workflow/world-postgres do not implement the check.

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

Minor Changes

  • #3186 4a9d26b Thanks @alangenfeld! - Record the compute instance that ran each step attempt: CreateEventParams.computeInstanceId is stamped on step_started writes, forwarded in the world-vercel v4 frame meta alongside vercelId, read back on AnalyticsEvent / AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.

  • #3293 a799025 Thanks @alangenfeld! - Surface an analytics event's vercelId in the run sidebar's Metadata list as a copyable "Request ID", and stop rendering the literal text null for a provenance id the analytics contract left empty. Also order Metadata rows missing from the panel's explicit order list after the listed ones instead of ahead of them, so a failed step's Error Code no longer renders above the step's own name.

Patch Changes

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

  • #3294 dc4cf94 Thanks @mitul-s! - Use defined Geist typography utilities throughout the shared observability UI.

  • Updated dependencies [4a9d26b, ee944d2, 1471f25, 9cc11f5, 679dfa9, b732e91, 31f92df, 4174a6e, 4017597, 438eaa6, ee944d2]:

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

workflow@5.0.0-beta.39

Minor Changes

  • #3145 1471f25 Thanks @VaguelySerious! - Strengthen the event-creation precondition guard: replay-context writes now also send the number of loaded events, so a snapshot that is missing an event is rejected instead of committing a divergent event log, and a rejection restarts the replay in-process (consuming the events a world may attach to the rejection) rather than re-committing the rejected payload or re-invoking over the queue. @workflow/world-local and @workflow/world-postgres do not implement the check.

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

  • #1834 438eaa6 Thanks @TooTallNate! - Make resumeHook() resilient to transient hook_received event write failures (429/5xx) by carrying the payload on the queue message for the runtime to materialize. Returned Hook gets a new resilientResume: true flag when this fallback path is taken.

Patch Changes

  • #3288 679dfa9 Thanks @NathanColosimo! - Simplify hardened serialization: intrinsic captures assert at import instead of degrading per use, URLSearchParams now serializes natively on Node 18, and bound-function getters are reported as guest code (previously a getter defined via fn.bind() executed with an empty report).

  • #3257 b732e91 Thanks @TooTallNate! - Serializing values built inside the node:vm workflow VM no longer executes workflow code, using engine brand checks and host intrinsics captured at boot.

  • Updated dependencies [4a9d26b, ee944d2, 1471f25, 9cc11f5, 679dfa9, b732e91, 31f92df, 4174a6e, 4017597, 438eaa6]:

    • @workflow/core@5.0.0-beta.39
    • @workflow/errors@5.0.0-beta.15
    • @workflow/cli@5.0.0-beta.39
    • @workflow/next@5.0.0-beta.39
    • @workflow/nitro@5.0.0-beta.39
    • @workflow/typescript-plugin@5.0.0-beta.5
    • @workflow/astro@5.0.0-beta.39
    • @workflow/nest@5.0.0-beta.39
    • @workflow/rollup@5.0.0-beta.39
    • @workflow/sveltekit@5.0.0-beta.39
    • @workflow/nuxt@5.0.0-beta.39

@workflow/world@5.0.0-beta.24

Minor Changes

  • #3186 4a9d26b Thanks @alangenfeld! - Record the compute instance that ran each step attempt: CreateEventParams.computeInstanceId is stamped on step_started writes, forwarded in the world-vercel v4 frame meta alongside vercelId, read back on AnalyticsEvent / AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.

  • #3145 1471f25 Thanks @VaguelySerious! - Strengthen the event-creation precondition guard: replay-context writes now also send the number of loaded events, so a snapshot that is missing an event is rejected instead of committing a divergent event log, and a rejection restarts the replay in-process (consuming the events a world may attach to the rejection) rather than re-committing the rejected payload or re-invoking over the queue. @workflow/world-local and @workflow/world-postgres do not implement the check.

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

  • #1834 438eaa6 Thanks @TooTallNate! - Make resumeHook() resilient to transient hook_received event write failures (429/5xx) by carrying the payload on the queue message for the runtime to materialize. Returned Hook gets a new resilientResume: true flag when this fallback path is taken.

  • #3244 ee944d2 Thanks @pranaygp! - Add an optional World.getEnvironment() hook and an optional environment field on RunInputSchema, so the environment a run was created in can travel with its queue message.

Patch Changes

  • #3208 4017597 Thanks @alangenfeld! - Report replay-divergence counts on event writes that recover or exhaust replay retries.

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

Minor Changes

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

Patch Changes

  • #3255 2677653 Thanks @AndrewBarba! - Bound stalled local queue deliveries and redeliver their durable messages instead of waiting indefinitely.

  • #3297 aa78a7e Thanks @TooTallNate! - Converge a redelivered hook_received re-ensure on its already-committed (runId, resumeId) claim instead of rejecting with HookNotFoundError when the hook was disposed after the resume was recorded. The rejection made the queue consumer ack the redelivery as "nothing left to resume", silently dropping any continuation the message carried.

  • #3215 f05f642 Thanks @AndrewBarba! - Retry transient EPERM unlink failures on Windows when deleting hook and entity JSON files. A concurrent reader briefly holding a file open made deleteJSON throw a share-violation EPERM, which surfaced as a failed operation — for example a failed run.cancel() while deleteAllHooksForRun raced hook polling.

  • Updated dependencies [4a9d26b, 1471f25, 31f92df, 4017597, 438eaa6, ee944d2]:

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

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

Minor Changes

  • #3186 4a9d26b Thanks @alangenfeld! - Record the compute instance that ran each step attempt: CreateEventParams.computeInstanceId is stamped on step_started writes, forwarded in the world-vercel v4 frame meta alongside vercelId, read back on AnalyticsEvent / AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.

  • #3145 1471f25 Thanks @VaguelySerious! - Strengthen the event-creation precondition guard: replay-context writes now also send the number of loaded events, so a snapshot that is missing an event is rejected instead of committing a divergent event log, and a rejection restarts the replay in-process (consuming the events a world may attach to the rejection) rather than re-committing the rejected payload or re-invoking over the queue. @workflow/world-local and @workflow/world-postgres do not implement the check.

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

  • #3244 ee944d2 Thanks @pranaygp! - Implement getEnvironment(), reporting the environment this client's writes are attributed to from the same resolution that produces the x-vercel-environment request header.

Patch Changes

@workflow/astro@5.0.0-beta.39

Patch Changes

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

@workflow/builders@5.0.0-beta.39

Patch Changes

@workflow/cli@5.0.0-beta.39

Patch Changes

@workflow/nest@5.0.0-beta.39

Patch Changes

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

@workflow/next@5.0.0-beta.39

Patch Changes

@workflow/nitro@5.0.0-beta.39

Patch Changes

@workflow/nuxt@5.0.0-beta.39

Patch Changes

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

@workflow/rollup@5.0.0-beta.39

Patch Changes

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

@workflow/sveltekit@5.0.0-beta.39

Patch Changes

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

@workflow/vite@5.0.0-beta.39

Patch Changes

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

@workflow/vitest@5.0.0-beta.39

Patch Changes

@workflow/web@5.0.0-beta.39

Patch Changes

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

Patch Changes

  • #3230 31f92df Thanks @karthikscale3! - Lazy hook resumption: on a fast path, resumeHook() writes the hook_received event and dispatches the workflow queue message concurrently instead of sequentially, cutting a round trip off resume latency. A (runId, resumeId) dedup constraint keeps the two writers converging on exactly one event; the runtime falls back to the sequential path when dedup support is unavailable or when WORKFLOW_DISABLE_LAZY_HOOK_RESUME=1. resumeHook() resolves to a ResumedHook (a Hook plus an optional resilientResume: true flag, set only when the direct write failed transiently and the resume was recovered via the queue consumer's re-ensure) — preserving the contract introduced alongside the resilient-resume work.

  • Updated dependencies [4a9d26b, 1471f25, 31f92df, 4017597, 438eaa6, ee944d2, 2677653, aa78a7e, f05f642]:

    • @workflow/world@5.0.0-beta.24
    • @workflow/errors@5.0.0-beta.15
    • @workflow/world-local@5.0.0-beta.33

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

Patch Changes

@snyk-io

snyk-io Bot commented Jun 15, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions github-actions Bot closed this Jun 16, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 792f0da to d4dd6f9 Compare June 16, 2026 20:35
@github-actions github-actions Bot reopened this Jun 16, 2026
@github-actions github-actions Bot closed this Jun 17, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 32a1908 to cb18139 Compare June 17, 2026 02:18
@github-actions github-actions Bot reopened this Jun 17, 2026
@github-actions github-actions Bot closed this Jun 17, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3fe9c50 to b805a8d Compare June 17, 2026 08:18
@github-actions github-actions Bot reopened this Jun 17, 2026
@github-actions github-actions Bot closed this Jun 17, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1296d25 to da37349 Compare June 17, 2026 20:39
@github-actions github-actions Bot reopened this Jun 17, 2026
@github-actions github-actions Bot closed this Jun 18, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from e2c593c to 2074f91 Compare June 18, 2026 02:18
@github-actions github-actions Bot reopened this Jun 18, 2026
@github-actions github-actions Bot closed this Jun 18, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7e69374 to 939890d Compare June 18, 2026 14:19
@github-actions github-actions Bot reopened this Jun 18, 2026
@github-actions github-actions Bot closed this Jun 18, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from dc0b377 to ab2e9b8 Compare June 18, 2026 20:54
@github-actions github-actions Bot reopened this Jun 18, 2026
@github-actions github-actions Bot closed this Jun 19, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 43c0a17 to 37312ed Compare June 19, 2026 02:18
@github-actions github-actions Bot reopened this Jun 19, 2026
@github-actions github-actions Bot closed this Jun 19, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 903651c to b563126 Compare June 19, 2026 08:18
@github-actions github-actions Bot reopened this Jun 19, 2026
@github-actions github-actions Bot closed this Jun 19, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from e35cc18 to 90efb96 Compare June 19, 2026 14:34
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from a6f6aca to 332c63c Compare June 23, 2026 02:18
@github-actions github-actions Bot reopened this Jun 23, 2026
@github-actions github-actions Bot closed this Jun 23, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3261502 to 6855282 Compare June 23, 2026 20:26
@github-actions github-actions Bot reopened this Jun 23, 2026
@github-actions github-actions Bot closed this Jun 24, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 89562e3 to 55e2110 Compare June 24, 2026 02:38
@github-actions github-actions Bot reopened this Jun 24, 2026
@github-actions github-actions Bot closed this Jun 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from e07463e to 24f3707 Compare June 29, 2026 20:36
@github-actions github-actions Bot reopened this Jun 29, 2026
@github-actions github-actions Bot closed this Jun 30, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 98783c9 to 654f959 Compare June 30, 2026 02:18
@github-actions github-actions Bot reopened this Jun 30, 2026
@github-actions github-actions Bot closed this Jun 30, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1fd0af3 to fc5bdcb Compare June 30, 2026 08:18
@github-actions github-actions Bot reopened this Jun 30, 2026
@github-actions github-actions Bot closed this Jul 1, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 606c4d1 to f76377b Compare July 1, 2026 02:18
@github-actions github-actions Bot reopened this Jul 1, 2026
@github-actions github-actions Bot closed this Jul 1, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 000daf4 to 7eabc1f Compare July 1, 2026 20:31
@github-actions github-actions Bot reopened this Jul 1, 2026
@github-actions github-actions Bot closed this Jul 2, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 571252f to 532b0e1 Compare July 2, 2026 08:18
@github-actions github-actions Bot reopened this Jul 2, 2026
@github-actions github-actions Bot closed this Jul 2, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1cee959 to dd36e26 Compare July 2, 2026 20:52
@github-actions github-actions Bot reopened this Jul 2, 2026
@github-actions github-actions Bot closed this Jul 3, 2026
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.

0 participants