Skip to content

workflow@5.0.0-beta.30

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Jul 21:58
Immutable release. Only release title and notes can be modified.
5de1b7a

@workflow/core@5.0.0-beta.30

  • #2850 f28150c @karthikscale3 - Report step progress alongside step-to-step overhead latency telemetry.
  • #2872 36c63af @mitul-s - Record the source run on replays: recreateRunFromExisting now stamps replayedFromRunId into the new run's executionContext (and start accepts a matching option) so tooling can surface a run as a replay and link back to its origin.
  • #2790 145835b @NathanColosimo - Centralize workflow event type classifiers and event-data payload field helpers.
  • #2687 9958424 @Osamaali313 - Fix extractStreamIds overflowing the stack on circular references. The hydrated observability data it walks comes from devalue, which preserves circular and repeated references, so a step result containing a cycle would crash run inspection (wf inspect and the web dashboard) with a RangeError. The traversal now tracks visited containers and skips cycles.
  • #2848 6603628 @VaguelySerious - Fix duplicate inline step execution when a hook or wait wakes a run while the step is still running (#2780). The lazy step_started now records the owning queue message ID, and wake replays schedule a delayed backstop for in-flight inline steps instead of immediately re-dispatching them. Disable with WORKFLOW_INLINE_OWNERSHIP=0.
  • #2874 48fcc4e @karthikscale3 - Add a namespace option to start(), recreateRunFromExisting(), reenqueueRun(), and wakeUpRun() for targeting deployments with namespaced queue topics, and make healthCheck() respect its timeout when the stream read hangs.
  • #2857 2c6ee61 @karthikscale3 - Add stream latency to OTEL spans

@workflow/cli@5.0.0-beta.30

@workflow/world@5.0.0-beta.18

  • #2850 f28150c @karthikscale3 - Report step progress alongside step-to-step overhead latency telemetry.
  • #2790 145835b @NathanColosimo - Centralize workflow event type classifiers and event-data payload field helpers.
  • #2848 6603628 @VaguelySerious - Fix duplicate inline step execution when a hook or wait wakes a run while the step is still running (#2780). The lazy step_started now records the owning queue message ID, and wake replays schedule a delayed backstop for in-flight inline steps instead of immediately re-dispatching them. Disable with WORKFLOW_INLINE_OWNERSHIP=0.

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

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

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

  • #2850 f28150c @karthikscale3 - Report step progress alongside step-to-step overhead latency telemetry.
  • #2876 84df8f3 @karthikscale3 - Update @vercel/queue from 0.3.1 to 0.4.0
  • #2873 4dce2ae @VaguelySerious - Cancel the v4 event frame stream when a reader stops early, so the response body's undici connection returns to the pool instead of leaking.
  • #2790 145835b @NathanColosimo - Centralize workflow event type classifiers and event-data payload field helpers.
  • #2848 6603628 @VaguelySerious - Fix duplicate inline step execution when a hook or wait wakes a run while the step is still running (#2780). The lazy step_started now records the owning queue message ID, and wake replays schedule a delayed backstop for in-flight inline steps instead of immediately re-dispatching them. Disable with WORKFLOW_INLINE_OWNERSHIP=0.
  • #2857 2c6ee61 @karthikscale3 - Add stream latency to OTEL spans

@workflow/web@5.0.0-beta.30

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

  • #2864 8b3a358 @mitul-s - Remove unused flex-1 from attribute copy-value rows so values hug their content.
  • #2790 145835b @NathanColosimo - Centralize workflow event type classifiers and event-data payload field helpers.
  • #2837 392d347 @mitul-s - Anchor the trace viewer shortcut helper to the timeline's left edge and hide it below a container-query width instead of a viewport breakpoint.

@workflow/builders@5.0.0-beta.30

  • #2853 df7e71d @NathanColosimo - Use the Windows-safe generated-file writer for step registration output.
  • #1947 25b1509 @VaguelySerious - Externalize the optional @opentelemetry/api peer in the Rollup/Vite framework builds (SvelteKit, Nitro, Nuxt, Astro, Vite) only when it isn't installed, so a build no longer fails with "failed to resolve import '@opentelemetry/api'". When the peer is present it is bundled/resolved as before, so tracing keeps working — including in self-contained outputs like Nitro's .output/server.

@workflow/rollup@5.0.0-beta.30

  • #1947 25b1509 @VaguelySerious - Externalize the optional @opentelemetry/api peer in the Rollup/Vite framework builds (SvelteKit, Nitro, Nuxt, Astro, Vite) only when it isn't installed, so a build no longer fails with "failed to resolve import '@opentelemetry/api'". When the peer is present it is bundled/resolved as before, so tracing keeps working — including in self-contained outputs like Nitro's .output/server.