Skip to content

Version Packages (beta) - #104

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

Version Packages (beta)#104
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Feb 12, 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.

  • #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

@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.

Patch Changes

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.

  • #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

  • Updated dependencies [4a9d26b, ee944d2, 1471f25, 9cc11f5, 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.

  • #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-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.

  • #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

  • Updated dependencies [4a9d26b, ee944d2, 1471f25, 9cc11f5, 4017597, 438eaa6]:
    • @workflow/core@5.0.0-beta.39
    • @workflow/builders@5.0.0-beta.39
    • @workflow/web@5.0.0-beta.39
    • @workflow/rollup@5.0.0-beta.39
    • @workflow/vite@5.0.0-beta.39

@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

  • Updated dependencies [2677653, f05f642]:
    • @workflow/world-local@5.0.0-beta.33

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

Patch Changes

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

  • #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, 4017597, 438eaa6, ee944d2]:

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

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

Patch Changes

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

Patch Changes

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 15 times, most recently from 057a03d to 0b0ccf8 Compare February 19, 2026 02:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 8 times, most recently from dae1fc1 to d127a7d Compare February 26, 2026 20:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 5e5c154 to 0fea67f Compare February 27, 2026 20:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 5 times, most recently from 6f8bb50 to 03dfab3 Compare April 30, 2026 20:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 8 times, most recently from 96741e9 to 09a0c1d Compare May 9, 2026 20:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 12 times, most recently from 41c3171 to 2a446af Compare May 22, 2026 02:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 9 times, most recently from f4455ab to 62ec537 Compare May 28, 2026 08:33
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