Skip to content

Update dependency workflow to v5.0.0-beta.20#77

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/workflow-5.x
Open

Update dependency workflow to v5.0.0-beta.20#77
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/workflow-5.x

Conversation

@renovate

@renovate renovate Bot commented Jun 13, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
workflow (source) 5.0.0-beta.12 → 5.0.0-beta.20 age confidence

Release Notes

vercel/workflow (workflow)

v5.0.0-beta.20

Compare Source

Minor Changes
  • #​2516 84ccd40 Thanks @​VaguelySerious! - Inline execution now runs up to WORKFLOW_MAX_INLINE_STEPS (default 3) steps in parallel per suspension, each lazily created. An opt-in WORKFLOW_OPTIMISTIC_INLINE_START (default off) additionally starts step bodies before step_started is confirmed, reconciling the in-flight start before the terminal write so a lost create-claim is discarded; it is off by default because under contention a step body can run more than once (e.g. two runs writing to the workflow stream can corrupt it), so only enable it for idempotent steps.
Patch Changes

  • #​2475 2074f91 Thanks @​pranaygp! - Skip the per-step incremental events.list round-trip in the inline sequential loop by consuming an event-log delta returned from the step's terminal write (gated to the single-step case with no open hooks or waits).

    Add the opt-in CreateEventParams.sinceCursor contract so a step-terminal events.create can return the event-log delta since that cursor (via EventResult.events/cursor/hasMore).

    Return the inline delta from a step-terminal write when sinceCursor is supplied, computed identically to events.list so the consumed prefix cannot skew from the server log.

    Forward sinceCursor over the v4 wire in @workflow/world-vercel so the server can return the delta on a step-terminal response; older servers ignore it and the runtime falls back to events.list.

  • #​2478 e7ef9d8 Thanks @​pranaygp! - Lazy inline step start: the owned-inline runtime path now sends a single step_started carrying the step input, letting the world create the step on the fly and saving one round-trip per inline step.

    @workflow/world: step_started event data accepts an optional input, and EventResult gains a stepCreated ownership signal.

    @workflow/world-local: step_started with input atomically creates the step plus a synthetic step_created event; a lazy step_started for an already-existing step throws EntityConflictError so concurrent losers skip (exactly-once).

    @workflow/world-postgres: same lazy-create + exactly-once create-claim for the Postgres backend.

    @workflow/world-vercel: sends the step input on step_started over the v4 wire and threads the server's stepCreated signal into EventResult.

  • Updated dependencies [7aee0d4, 16b3670, 2074f91, e7ef9d8, 722bb7c, de91f20, ab2e9b8, 84ccd40, 939890d, a92c16d, 37312ed]:

v5.0.0-beta.19

Compare Source

Patch Changes

v5.0.0-beta.18

Compare Source

Patch Changes

v5.0.0-beta.17

Compare Source

Minor Changes

  • #​2363 926a5e7 Thanks @​karthikscale3! - Add WORKFLOW_TRACE_MODE with a new linked default: each workflow/step invocation span is now its own trace root with span links to the delivery and run-origin contexts, instead of one trace spanning the entire run. world-vercel now explicitly injects W3C traceparent/tracestate/baggage headers on outgoing workflow-server requests.

    Span names are also friendlier: workflow and step spans now use the short function name (e.g. workflow.execute processOrder, step.execute chargeCard, workflow.start processOrder) instead of the uppercase prefixes and full machine names (WORKFLOW_V2 workflow//./src/jobs/order//processOrder). The full name remains available in the workflow.name / step.name span attributes, and new workflowDisplayName / stepDisplayName helpers are exported from @workflow/utils.

    Behavioral changes to telemetry under the new default (set WORKFLOW_TRACE_MODE=continuous to restore the previous trace shape exactly; the span-name change applies in both modes):

    • A run no longer shares one trace ID: the trace of the request that called start() no longer contains the workflow's execution spans — navigate via span links or the workflow.run.id attribute instead.
    • Sampling decisions are made independently per invocation root (previously one parent-based decision covered the whole run), and the number of root spans/traces increases to one per invocation.
    • workflow.execute/step.execute invocation spans (formerly WORKFLOW_V2/STEP) become parentless roots, which changes parent/child-based queries and service-map edges.
    • Re-enqueued queue messages forward the original run-origin trace carrier unchanged, rather than each invocation's current context.
    • Queries or dashboards matching the old WORKFLOW_V2 .../STEP ... span names must switch to the new names.
    • The queue-delivered workflow.execute span kind changed from internal to consumer, matching the queue-delivered step.execute span (this applies in both modes).

    Existing attributes and baggage keys are unchanged, and everything remains a no-op when no OpenTelemetry SDK is registered.

Patch Changes

v5.0.0-beta.16

Compare Source

Minor Changes
  • #​2385 628795a Thanks @​pranaygp! - Add an allowReservedAttributes option to start() so framework-level callers can seed reserved $-prefixed run attributes at creation, matching the existing experimental_setAttributes option. The flag is carried through the resilient-start queue input so lazy run creation validates identically.
Patch Changes

v5.0.0-beta.15

Compare Source

Minor Changes

  • #​1853 303b6da Thanks @​TooTallNate! - Add opt-in wire-level framing for byte streams (type: 'bytes') so consumers can identify chunk boundaries — a prerequisite for transparent auto-reconnect. The framing decision is gated on a new framedByteStreams capability and recorded per-stream in the serialized ref (framing: 'framed-v1'); legacy raw streams continue to work unchanged.

  • #​2373 01c8c08 Thanks @​pranaygp! - Replace hook.hasConflict (a Promise<boolean> property) with hook.getConflict(), a method returning a promise that suspends the workflow to commit hook registration and resolves with the conflicting Run when another active hook owns the token (or null once the hook is registered), without waiting for hook payload data. Code using await hook.hasConflict should migrate to const conflict = await hook.getConflict() and branch on conflict !== null.

  • #​2226 ae8d6fe Thanks @​pranaygp! - Allow passing initial run attributes through start(), and speed up workflow-level setAttribute calls by using native events for recording attributes.

Patch Changes

v5.0.0-beta.14

Compare Source

Patch Changes

v5.0.0-beta.13

Compare Source

Minor Changes
Patch Changes

Configuration

📅 Schedule: (in timezone Europe/Rome)

  • Branch creation
    • Between 12:00 AM and 06:59 AM, only on Sunday and Saturday (* 0-6 * * 6,0)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/workflow-5.x branch 4 times, most recently from 834eb2b to 6b96385 Compare June 15, 2026 15:10
@renovate renovate Bot changed the title Update dependency workflow to v5.0.0-beta.15 Update dependency workflow to v5.0.0-beta.16 Jun 15, 2026
@renovate renovate Bot force-pushed the renovate/workflow-5.x branch from 6b96385 to d9e9a14 Compare June 16, 2026 03:32
@renovate renovate Bot changed the title Update dependency workflow to v5.0.0-beta.16 Update dependency workflow to v5.0.0-beta.17 Jun 16, 2026
@renovate renovate Bot force-pushed the renovate/workflow-5.x branch from d9e9a14 to 0bddf0c Compare June 18, 2026 03:45
@renovate renovate Bot changed the title Update dependency workflow to v5.0.0-beta.17 Update dependency workflow to v5.0.0-beta.19 Jun 18, 2026
@renovate renovate Bot force-pushed the renovate/workflow-5.x branch from 0bddf0c to 6d88ff7 Compare June 19, 2026 16:47
@renovate renovate Bot changed the title Update dependency workflow to v5.0.0-beta.19 Update dependency workflow to v5.0.0-beta.20 Jun 19, 2026
@renovate renovate Bot force-pushed the renovate/workflow-5.x branch 2 times, most recently from afdc396 to 3bdad60 Compare June 20, 2026 15:12
@renovate renovate Bot force-pushed the renovate/workflow-5.x branch from 3bdad60 to 1e2365c Compare June 21, 2026 02:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants