Packages

@workflow/errors

5.0.5 · 20 Oct 2026Apache-2.01.2M / weekRepositorynpmAtom feed

15 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 5.x · latest line
  2. 5.0.5

    20 Oct 2026
    • @TooTallNate - Add a QuickJS snapshotting hint and docs link to MaxEventsExceededError

  3. 5.0.4

    12 Oct 2026
    • @VaguelySerious - Add InBandSupersededError and optional inBand/expectedSeqInBand event-create params for the in-band writer fence. @workflow/world-vercel forwards them, does not retry a fenced write in-process, and records the fence on its event spans. The runtime does not use them yet.

  4. 5.0.1 – 5.0.33 releases that only update dependencies@workflow/world 5.0.3@workflow/utils 5.0.1Show each
  5. 5.0.0

    30 Sep 2026
    • breaking

      Initial v5 beta release

    • breaking

      Run and step errors are now serialized through the workflow serialization pipeline, preserving original class identity and cause chains on WorkflowRunFailedError.cause. Pre-upgrade failed runs in the world-postgres legacy error text column surface as error: undefined on read; the original payload is still readable directly from the errorJson column for manual inspection.

    • Validate world.analytics arguments up front: an invalid id, an out-of-range page limit, an oversized attribute filter, or a half-open startTime/endTime window now throws a WorkflowWorldError with code: 'INVALID_ARGUMENT' and field set to the offending parameter, instead of failing the request. The message names the method, the parameter, and what it received. Adds ANALYTICS_RUN_SCOPED_PAGE_LIMIT, ANALYTICS_PAGE_LIMIT and ANALYTICS_MAX_ATTRIBUTE_FILTERS.

      Deprecate analytics.events.listByCorrelationId() in favour of analytics.events.list({ runId, correlationId }).

      Fix analytics.attributes.list() timestamps being shifted by the local UTC offset.

  6. 4.x
  7. 4.2.2

    30 Sep 2026
    • @pranaygp - Mark WorkflowRunFailedError and WorkflowRunCancelledError as non-retryable, and make FatalError.is() honor the fatal marker, so a step that reads a terminal run's returnValue fails on its first attempt with the error intact instead of exhausting its retry budget first.

  8. 4.2.1

    31 Jul 2026
    • @shalabhc - Enforce a server-supplied per-run event limit (default 25K)

  9. 4.2.0

    29 Jul 2026
    • @VaguelySerious - Add an optimistic-concurrency guard for event creation (on by default; opt out with WORKFLOW_PRECONDITION_GUARD=0): replay-context event creations send a stateUpdatedAt snapshot timestamp, and the runtime reloads the event log and retries (then falls back to a fresh re-invocation) when the backend reports a newer out-of-band event with a 412 PreconditionFailedError. Backends without guard support ignore the snapshot, so this is backward-compatible and fails open.

  10. 4.1.5

    22 Jul 2026

    Reading the note…

  11. 4.1.4

    11 Jun 2026

    Reading the note…

  12. 4.1.3

    2 Jun 2026

    Reading the note…

  13. 4.1.2

    22 May 2026

    Reading the note…

  14. 4.1.1

    16 Apr 2026

    Reading the note…

  15. 4.1.0

    7 Apr 2026

    Reading the note…