NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #2417 most downloaded on Packagist
Embedded durable workflow runtime and orchestration engine for Laravel applications.
Latest stable
2.22.0
Last release 14 days ago
08 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
623 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Corrected stable patch release for the dedicated storage-connection watchdog repair from #546. The runtime changes are the same as 2.2.6; package sour
Corrected stable patch release for the dedicated storage-connection watchdog repair from #546. The runtime changes are the same as 2.2.6; package source metadata now identifies the exact 2.2.7 release so published-package conformance can verify it. v2 task repair, activity timeout enforcement, worker-compatibility heartbeats, and the v1 watchdog use their model storage connection for engine-table checks. Default-connection behavior and wire protocols are unchanged. The 2.2.6 tag remains immutable and should not be used as a qualified release.
Superseded by [2.2.7](https://github.com/durable-workflow/workflow/releases/tag/2.2.7). Do not select 2.2.6 for new installs. The 2.2.6 published-pack
Superseded by 2.2.7. Do not select 2.2.6 for new installs. The 2.2.6 published-package verification failed because its bundled product-train metadata identified 2.2.5. The immutable tag was not rewritten; 2.2.7 contains the same storage-connection repair with corrected source identity and passed published-package/Laravel upgrade verification.
This patch repairs watchdog table checks for embedded Laravel installations with a dedicated workflows.storage.connection. The v2 task watchdog, worker-compatibility heartbeats, and v1 watchdog now inspect engine tables on the configured storage connection rather than the application default. Default-connection behavior, API, and schema are unchanged.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Patch release for failed local-activity Avro payload persistence. New failed, timed-out and cancelled local-activity exceptions are encoded with the r
Patch release for failed local-activity Avro payload persistence. New failed, timed-out and cancelled local-activity exceptions are encoded with the run codec; an idempotent migration repairs legacy plain-text exceptions in execution rows and terminal history snapshots. Cold replay and history import regression evidence is included. No SDK wire-protocol change.
Qualified patch release of the CarbonImmutable compatibility fix from 2.2.3. Embedded v2 activity leases and standalone activity starts accept immutab
Qualified patch release of the CarbonImmutable compatibility fix from 2.2.3. Embedded v2 activity leases and standalone activity starts accept immutable application dates; worker compatibility summaries retain immutable heartbeat timestamps. This tag also aligns the packaged Workflow source-release identity with 2.2.4. No portable protocol change.
The CarbonImmutable runtime fix in this tag is superseded by 2.2.4. The 2.2.3 published-package verification failed because its packaged source-releas
The CarbonImmutable runtime fix in this tag is superseded by 2.2.4. The 2.2.3 published-package verification failed because its packaged source-release identity still reported 2.2.2; use 2.2.4 instead. No published tag was moved or reused.
Qualified patch release for the MySQL operator-surface metadata optimization introduced in 2.2.1. One fresh table listing per connection/schema replac
Qualified patch release for the MySQL operator-surface metadata optimization introduced in 2.2.1. One fresh table listing per connection/schema replaces repeated metadata queries while preserving targeted fallback and immediate schema-drift detection. Also corrects the packaged source-release identity that caused 2.2.1 release verification to fail. No public workflow API change.
Superseded by Workflow 2.2.2. Do not use 2.2.1 as a qualified release: its published-package check failed because its source-release identity remained
Superseded by Workflow 2.2.2. Do not use 2.2.1 as a qualified release: its published-package check failed because its source-release identity remained 2.2.0. The immutable tag was not rewritten.
Reduce MySQL operator-surface readiness metadata checks to one fresh table listing per connection and schema. Keep targeted fallback for missing or non-identical names, immediate schema-drift detection, and the existing behavior on other databases or older Laravel versions. No public workflow API change.
Add WorkflowStub::requestCancellation() for a durable, idempotent cancellation request with a bounded cleanup deadline.
WorkflowStub::requestCancellation() for a durable, idempotent cancellation request with a bounded cleanup deadline.finally can run durable cleanup activities. Use cancellationShield() to let cleanup already in progress finish.cancel() and terminate() behavior unchanged. A cleanup deadline still falls back to terminal cancellation.This capability is embedded PHP only. The standalone Server and service-mode PHP, Python, and Rust SDKs do not yet expose this cooperative request protocol. Cleanup activities should be idempotent; forced termination and external side effects cannot be guaranteed to finish.
Adds validated failed-run redrive from an activity boundary, including reused activity history and provenance. Also corrects the package release ident
Adds validated failed-run redrive from an activity boundary, including reused activity history and provenance. Also corrects the package release identity so published-artifact verification succeeds. Server and SDK integrations are being qualified separately before the service-mode redrive feature is announced.
Record unambiguous failed activity step for future redrive
Only mark the failed sequence when an activity failure propagates. A workflow exception after an activity succeeds must not imply that the activity should be retried.
test(v2): cover replay of completed activity prefix for redrive
fix(v2): mark activity redrive boundary only for propagated failure
feat(v2): validate failed-run activity replay source
test(v2): qualify redrive plan against persisted failure
Draft embedded failed-run redrive with reused activity provenance
Preserve redrive replay time across query reconstruction
Preserve redrive lineage through embedded history import
Prove redriven run survives source history expiry
Preserve redrive replay clock in cold fiber runs
Verify service worker activity-failure redrive boundary
Preserve uncaught activity failure identity in worker commands
Require recorded worker definition for service redrive
Mark worker-owned workflow definition identity in history
Preserve workflow timeouts across failed-run redrive
Format redrive timeout handling
Reject redrive when activity history advances past failure
Co-authored-by: Durable Workflow support@durable-workflow.com
Corrects the published source-release identity for the v2-only install option introduced in 2.0.18. Set DW_V1_ENABLED=false before a fresh install to
Corrects the published source-release identity for the v2-only install option introduced in 2.0.18. Set DW_V1_ENABLED=false before a fresh install to omit legacy embedded v1 tables; existing installs retain the enabled default.
Superseded by 2.0.19: the v2-only install behavior is the same, but 2.0.19 corrects the packaged source-release identity and passed published-release
Superseded by 2.0.19: the v2-only install behavior is the same, but 2.0.19 corrects the packaged source-release identity and passed published-release verification.
Full Changelog: https://github.com/durable-workflow/workflow/compare/2.0.17...2.0.18
Resolve caller ID reservation against committed MySQL rows by @rmcdaniel in https://github.com/durable-workflow/workflow/pull/518
Full Changelog: https://github.com/durable-workflow/workflow/compare/2.0.16...2.0.17
Fix large inline history handling on MySQL without increasing database limits.
Fix large inline history handling on MySQL without increasing database limits.
Validated with native MySQL 8.0.43 defaults, SQLite, PostgreSQL, MariaDB, Laravel 9-13 source upgrades, and a PHP SDK large-payload workflow/activity journey. See #517 for qualification details. Server image follow-through is tracked in #515.
Readiness consumers can now preserve original schema-inspection exceptions with WaterlineEngineSource::status(throwOnInspectionFailure: true). This le
Readiness consumers can now preserve original schema-inspection exceptions with WaterlineEngineSource::status(throwOnInspectionFailure: true). This lets a runtime distinguish a temporary database disconnect from genuinely missing tables instead of losing the database error classification.
Default Waterline diagnostics and engine selection are unchanged. This patch has no database migration or wire-format change. Server must explicitly adopt the option; upgrading this library alone does not update an existing Server image.
Implementation: #516. Server adoption: durable-workflow/server#165.
Source validation passed: https://github.com/durable-workflow/workflow/actions/runs/35644831588 (MySQL, PostgreSQL, MariaDB, Laravel 9–13 upgrades, static analysis, regression corpus, and coverage). Published-package verification follows through the repository release workflow.
WaterlineEngineSource::status(throwOnInspectionFailure: true). Temporary
database connection failures can then be distinguished from genuinely missing
tables. Default Waterline diagnostics and engine selection are unchanged.Deterministic workflow time no longer shares mutable Carbon objects with callers. Deriving a deadline with Workflow::now()->addHour() cannot advance t
Deterministic workflow time no longer shares mutable Carbon objects with callers. Deriving a deadline with Workflow::now()->addHour() cannot advance the workflow clock or expire that deadline immediately. Mutating an object supplied to WorkflowFiberContext::setTime() also cannot change stored time.
Timestamp precision, timezones, Carbon mutable/immutable types, history-based advancement, and the wall-clock fallback outside workflows are preserved. No wire-format or database-schema change.
Upgrade the durable-workflow/workflow dependency and restart long-running PHP workers so they load the fix.
Implementation and regression evidence: #512 (fixes #511). Source validation: https://github.com/durable-workflow/workflow/actions/runs/34685503210 . Full MySQL, PostgreSQL, MariaDB, supported Laravel-major upgrades, static analysis, regression corpus and coverage passed. Published-package verification follows through the repository release workflow.
Workflow::now()->addHour() no longer advances workflow time or
expires the deadline immediately. Mutating a timestamp supplied to the fiber
context cannot change its stored time either. History-based clock advancement,
timestamp precision, timezones, and mutable or immutable Carbon types remain
unchanged.Reduce repeated work during full monitoring projection.
Reduce repeated work during full monitoring projection.
No public API, database schema, durable history, or portable payload protocol change. Full-history projection remains history-dependent; this release does not claim constant-time replay or new production capacity.
Fix: #508 / #509. Release metadata: #510.
The full source matrix passed unit/coverage, MySQL, PostgreSQL, MariaDB, Laravel 9-13 upgrade, quality, and regression checks. Published-package verification and affected-consumer delivery remain tracked in #508.
Fix schedule dispatch at exact timestamp boundaries.
Fix schedule dispatch at exact timestamp boundaries.
Fix: #505 / #506. Release metadata: #507.
Full scheduler-fix main CI passed MySQL, PostgreSQL, MariaDB, Laravel upgrade, coverage and regression checks. Publication verification and affected-consumer updates are tracked in #505.
Activities cannot bypass an elapsed deadline after a worker's lease expires. Task claiming preserves the elapsed deadline until the normal timeout swe
Activities cannot bypass an elapsed deadline after a worker's lease expires. Task claiming preserves the elapsed deadline until the normal timeout sweep settles it, including when an earlier worker already repaired the lease.
Schedule-to-close remains an overall deadline across worker restarts. The fix refuses late activity completion and avoids starting an extra activity effect after that deadline.
No schema migration or configuration change is required.
Fix: https://github.com/durable-workflow/workflow/pull/504 Issue and downstream delivery: https://github.com/durable-workflow/workflow/issues/503
Fixes Laravel's native mariadb connection being rejected by operator readiness and portable parity validation. Native MariaDB and the existing MySQL-d
Fixes Laravel's native mariadb connection being rejected by operator readiness and portable parity validation. Native MariaDB and the existing MySQL-driver MariaDB path are both covered in CI.
Thanks to @beschoenen for #500.
Validation: the complete main-branch test matrix and dependency security checks passed. Published-package verification runs after release.
Full changes: https://github.com/durable-workflow/workflow/compare/2.0.9...2.0.10
Fixes Laravel's native mariadb connection being rejected by operator readiness and portable parity validation. Native MariaDB and the existing MySQL-driver MariaDB path are both covered in CI.
Thanks to @beschoenen for #500.
Validation: the complete main-branch test matrix and dependency security checks passed. Published-package verification runs after release.
Full changes: 2.0.9...2.0.10
mariadb database driver in backend readiness and
capability reporting. MariaDB no longer appears unsupported when configured
with its own driver instead of mysql. Both driver paths retain real-database
locking and history checks; the native driver also exercises readiness and replay.Fix terminal activity timeout replay so workflow catch and finally blocks can recover and perform cleanup. The fix covers ordinary and local activitie
Fix terminal activity timeout replay so workflow catch and finally blocks can recover and perform cleanup. The fix covers ordinary and local activities, including existing persisted timeout histories, without application exception mappings.
Fix: #498. Implementation and regression coverage: #499.
Full main-branch validation passed, including MySQL/PostgreSQL feature matrices, supported Laravel upgrade checks, replay regression coverage, static analysis, and coverage. Published-package verification runs for this release.
Fixes child completion defects reported in #493 and #495.
Fixes child completion defects reported in #493 and #495.
No database migration, public API or payload-format change. Existing histories with contradictory terminal events are not automatically rewritten.
Qualified runtime: https://github.com/durable-workflow/workflow/actions/runs/34231911269 (full MySQL/PostgreSQL matrix, MariaDB checks, Laravel 9-13 upgrades, replay corpus and unit coverage). Final release metadata and required PR checks: https://github.com/durable-workflow/workflow/actions/runs/34233053446 . Published-package verification follows publication.
Standalone Server images require a separate dependency update; this package release does not deploy Server or Cloud.
Fixes eager external-payload decoding during activity metadata projection (#491). Summary, task, wait and parallel-child checks preserve lifecycle and
Fixes eager external-payload decoding during activity metadata projection (#491). Summary, task, wait and parallel-child checks preserve lifecycle and typed-history metadata without downloading activity arguments/results. Explicit decoded activity views retain their existing behavior.
Qualified with the full source test matrix, Laravel 9-13 upgrades and unit coverage: https://github.com/durable-workflow/workflow/actions/runs/34205502106. The release metadata checks passed in #492. Published-package verification runs separately after publication.
This engine patch supports the bounded Server external-payload fix under development in durable-workflow/server#142; it does not deploy or release Server.
Fixes Nexus service-call history projection throwing during workflow-task completion. Started, completed, failed, and cancelled events now retain thei
Fixes Nexus service-call history projection throwing during workflow-task completion. Started, completed, failed, and cancelled events now retain their call identity and project an operation summary without payload contents. No database migration or protocol change. Fix: #488; release metadata: #489. Full database, coverage, quality, and supported Laravel upgrade checks passed on the implementation; release metadata checks passed before tagging. Published-package verification follows this immutable tag.
Fixes early delayed-job delivery exhausting activity and timer transport attempts. Fractional-second wakeups round up without changing durable deadlin
Fixes early delayed-job delivery exhausting activity and timer transport attempts. Fractional-second wakeups round up without changing durable deadlines; early wakeups use fresh jobs while business retry limits remain unchanged. Long SQS timers relay through capped 900-second dispatches.
Fix: #485. Release metadata: #486. Full database, coverage, and Laravel upgrade checks passed for the correction. No database migration or protocol change.
Fix durable activity, timer, and memo calls in finally blocks when a suspended workflow Fiber is discarded. Cleanup continues through normal durable r
Fix durable activity, timer, and memo calls in finally blocks when a suspended workflow Fiber is discarded. Cleanup continues through normal durable replay without a force-closed Fiber error. Cancellation and termination do not run application cleanup automatically. Verified across the supported PHP/Laravel matrix, real queued execution, and fresh-process replay. See #481 and #480.
finally cleanup survives ordinary workflow-task suspension and
discarded replay Fibers. Cleanup activities, timers, and memo writes retain
normal success/failure replay behavior without running during local teardown.Schedule ticks now share bounded due-work and buffered-drain batches across namespaces while preserving oldest-first order within each namespace.
Schedule ticks now share bounded due-work and buffered-drain batches across namespaces while preserving oldest-first order within each namespace.
Fixes stable package identity reporting through the platform conformance API. Published-package verification can now validate an exact stable 2.x.y re
Fixes stable package identity reporting through the platform conformance API. Published-package verification can now validate an exact stable 2.x.y release after the 2.0 launch; retained prerelease artifact provenance is unchanged.
2.0.2 reports its stable package identity through the platform
conformance API, allowing published-package verification after the 2.0 launch.Preserves portable exception trace frames when Avro failure payloads contain PHP-only values such as object arguments. Unsupported trace fields are om
Preserves portable exception trace frames when Avro failure payloads contain PHP-only values such as object arguments. Unsupported trace fields are omitted without discarding the rest of the frame, with checked-in regression evidence proving the released failure and patched behavior.
2.0.1 keeps PHP exception traces Avro-portable when argument
capture is enabled, preserving each frame's durable fields while omitting
object and resource values that cannot cross the public payload boundary.Link organization-wide agent guidance by @rmcdaniel in https://github.com/durable-workflow/workflow/pull/439
Full Changelog: https://github.com/durable-workflow/workflow/compare/2.0.0-rc.55...2.0.0
Full Changelog: 2.0.0-rc.55...2.0.0
2.0.0 promotes the fully qualified release-candidate runtime to
the stable 2.0 line without changing its durable execution behavior.Workflow 2.0.0-rc.55 treats the official stable-v1 Y and Base64 serializer
settings as nonblocking migration diagnostics while v1 runs drain, without
changing the Avro-only codec used for all new v2 payloads.
Workflow 2.0.0-rc.54 validates service-mode parallel groups in the durable
yielded-command sequence domain, so signal-resumed condition waits retain
flat and nested mixed-group identity across cold replay and worker replacement.
Workflow 2.0.0-rc.53 preserves durable rejection reasons in history-export
command rows whose request payload is stored externally, matching run-detail
audit output while keeping accepted-command payload reasons private.
Workflow 2.0.0-rc.52 preserves the durable rejection reason on rejected
signal command audit rows after a fresh read, including when the request
payload is stored externally. Platform conformance suite 47 now pins the
invalid-argument and unknown-signal audit shapes and their no-mutation
invariants.
Workflow 2.0.0-rc.51 keeps retained protocol 1.18 local-activity attempt,
heartbeat, and retry-policy objects open to additive worker fields while
protocol 1.19 preserves the final closed report grammar. The package-owned
rolling-upgrade metadata states the 1.19 attempts requirement and nested
shape boundary explicitly so dependent current protocol mirrors can select
the same negotiated behavior.
Workflow 2.0.0-rc.50 reconstructs portable local-activity attempts as a
non-overlapping timeline using reported durations and retry backoff. Each
heartbeat timestamp is derived from its attempt start, aggregate heartbeat
state retains the chronologically latest report, and history snapshots now
expose lifecycle-correct running, retry, and terminal states through cold
persistence, export/import, and replay.
Workflow 2.0.0-rc.49 finalizes the portable local-activity command as an
ordered record_local_activity.attempts report. Worker attempt identity is
preserved independently of durable server attempt identity across every
attempt-scoped history event, cold persistence, export/import, and replay.
Reported heartbeat elapsed time now determines persisted heartbeat time
instead of workflow-task completion time. Negotiated protocol 1.18
completions that predate attempt reports remain accepted as one terminal
attempt, while protocol 1.19 selects the strict ordered report grammar.
Workflow 2.0.0-rc.48 makes SDK-reported local-activity attempt sequences
authoritative. The command grammar rejects unordered, contradictory, or
over-limit attempts and heartbeats, while service-mode completion projects
each attempt and terminal failure into the same operator-facing records used
by embedded execution. Worker-reported attempt identities remain scoped to
their activity executions while server-owned ULIDs keep durable attempt and
history references globally safe. Platform conformance suite 47 publishes
this typed grammar without changing the retained protocol 1.18 bytes.
Workflow 2.0.0-rc.48 owns method-dependency resolution across supported
Laravel versions, including contextual attributes, enum defaults, supplied
class parameters, and self and parent parameter types. The v2 unit suite
now publishes a machine-readable, branch-bound coverage summary and enforces
a non-decreasing baseline against the complete production source inventory.
Workflow 2.0.0-rc.48 adds deterministic durable selection and structured
concurrency for activities, child workflows, timers, signal waits, and
condition waits. Persisted winner markers remain authoritative across cold
replay, non-winning handles can continue, be awaited, or be cancelled, and
service workers share the same protocol-gated selection identity and member
key contract as the embedded Laravel runtime.
Workflow 2.0.0-rc.47 defines the host-facing workflow control plane around
ordinary workflow operations. Protocol 1.18 adds authoritative local-activity
command normalization and atomic attempt, heartbeat, retry, failure, timeout,
cancellation, and result history so replay never repeats a recorded local
side effect. Platform conformance suite 46 publishes the retained protocol
1.18 OpenAPI and AsyncAPI authorities for local activities, worker sessions,
and sticky execution while preserving the immutable 1.17 artifacts.
Reserved message-stream delivery uses a
separate runtime-only interface implemented by the default control plane,
while public signals remain unable to inject the reserved transport name.
The release audit also dereferences every advertised current and retained
worker-protocol resolver and verifies its SHA-256 digest before accepting
the public conformance mirror.
Workflow 2.0.0-rc.45 preserves an SDK-authored condition-wait occurrence
identity across open, satisfied, timed-out, and timeout-timer history.
Signal- and update-driven physical re-evaluations retain that identity, so
adjacent authored waits remain independent without inferring identity from
condition keys or predicate fingerprints. Worker protocol 1.17 gates the
occurrence field and registration capability so older Server nodes reject
the command before execution instead of silently dropping its replay
identity. Platform conformance suite 45 publishes the versioned 1.17
OpenAPI and AsyncAPI authorities and retains the prior 1.16 bytes.
Workflow 2.0.0-rc.44 separates the packaged history-export schema carrier
path from its retained immutable origin. Runtime manifest validation and the
published-package audit now enforce the same release, origin path, resolver,
artifact, and digest tuple while continuing to verify resolver bytes against
the current package carrier.
Workflow 2.0.0-rc.43 preserves canonical search-attribute type identity
through worker completion, full and paginated history, database restart, and
replay. Worker protocol 1.16 gates declared type metadata so older Server
nodes reject it instead of silently inferring a different type, while legacy
events without metadata retain an explicit unknown-type compatibility rule.
Platform conformance suite 44 publishes the versioned 1.16 OpenAPI and
AsyncAPI authorities and retains the prior 1.15 bytes.
Workflow 2.0.0-rc.42 makes non-indexed memo updates portable across
service-mode workers. PHP workflow authoring emits the language-neutral
Avro payload-envelope command and consumes only entry-matching memo history
during execution, cold replay, and query replay. Memo history and the
authoritative memo projection retain lossless Avro envelopes across database
reloads, preserving numeric branches, binary values, and map identity. Memo
patches are normalized independently of the current run state, while
structural key and encoded-size limits are enforced on the merged memo so
at-limit replacements remain valid. Integer-like top-level keys are rejected
before a host runtime can coerce their portable map identity.
History exports keep that envelope as the import authority while exposing a
separate JSON-safe memo projection, so export/import preserves exact memo
identity for operator readback and replay after a fresh database boundary.
Platform conformance suite 43 retains the version-one export schema bytes
while binding version two to the JSON-safe projection and lossless Avro memo
authority at the candidate's retained Workflow release source.
Workflow 2.0.0-rc.41 removes the unsupported root Composer Dependabot
update path for this lockfile-free library. GitHub dependency alerts remain
enabled, automated security-fix pull requests remain disabled, and the
scheduled per-major Composer audit continues to reconcile Laravel 9-13 with
the accepted-risk policy.
Workflow 2.0.0-rc.40 raises the embedded runtime's Laravel minimums to 9.52.17, 10.48.29,
11.44.1, 12.61.1, and 13.12.0 so every supported major receives all
available upstream fixes. Laravel 9-11 remain available for embedded upgrade
and drain paths, but upstream has not patched their remaining active
advisories; applications on those lines should move to Laravel 12.61.1 or
Laravel 13.12.0 and newer. A scheduled per-major Composer audit now owns this
library dependency instead of Dependabot trying to infer one installed
version from the package's intentionally unlocked multi-major constraint.
Workflow 2.0.0-rc.39 keeps database-backed Watchdog chains on fresh
delayed jobs, preserving queue affinity without accumulating attempts. A
generation lease converges duplicate ticks and safely releases ownership
when successor dispatch fails.
Workflow 2.0.0-rc.38 publishes worker protocol 1.15 as the current
conformance authority. The package contract and retained OpenAPI and AsyncAPI
specs now define the version-gated message-stream completion fields together.
Reserved runtime delivery now keeps durable message-stream input separate
from user-authored one-shot signals. The Workflow package source advances to
2.0.0-rc.37 with worker protocol 1.15 for portable stream consumption.
Service-mode workflow tasks can now merge non-indexed memo metadata through
the language-neutral upsert_memo command. The runtime records canonical
replay identity and merged projection data, preserves memo across
continue-as-new, enforces structural limits, and fences duplicate task
completions.
Standalone child-workflow completion now applies the recorded parallel-group path before resuming the parent. Successful child-only and mixed groups wait for every member, serialize concurrent child closures on the parent run, and create a single replay task while preserving retry and fail-fast behavior.
Advanced the Workflow package source to 2.0.0-rc.36 for the service-mode
child-completion barrier.
Standalone workflow-task completion now validates and records deterministic parallel activity, child-workflow, and timer metadata. Nested groups must be complete and sequence-aligned before transport, and timer waits now expose the same group/path diagnostics as activity and child waits.
Advanced the Workflow package source to 2.0.0-rc.34 for the service-mode
parallel-group contract.
Advanced the Workflow package source to 2.0.0-rc.33. Laravel now
container-constructs embedded v2 workflow and activity classes before the
engine binds durable runtime context. A package-owned transition contract,
isolated v2 queue default, upgrade-status command, supported-intersection
matrix, and published-artifact smoke make the stable-v1 to embedded-v2 path
executable without transferring v1 history.
Advanced the Workflow package source to 2.0.0-rc.32. History import now
validates Avro codec declarations only at schema-owned payload rows and
envelopes, preserving codec-looking memo and search-attribute data while
real non-Avro payload declarations continue to fail closed.
Platform conformance suite version 41 makes the lifecycle-neutral worker protocol OpenAPI bytes the current conformance authority. The former beta-worded binding remains available only through its explicit historical identity, while protocol version 1.13 and every wire shape remain unchanged.
Advanced the Workflow package source to 2.0.0-rc.14 for the corrected
conformance authority. Durable Workflow 2.0 remains a release candidate.
Platform conformance suite version 40 publishes the revision-bound CLI output-schema manifest and its complete JSON envelope plus JSONL record schema closure with HTTPS identities and SHA-256 byte bindings. The suite-39 revision remains retained with its original bytes.
Advanced the Workflow package source to 2.0.0-rc.13 for platform protocol
catalog 16. Its conformance bindings resolve the catalog and protocol-spec
bytes through immutable public documentation provenance. The aggregate
recommended product tuple remains RC5 until independently published
release-candidate artifacts pass exact-current qualification.
Historical command-contract gaps remain visible in operator metrics without warning fleet correctness once their runs are closed. Open runs still warn when operator command forms lack required safety data.
Projection repair can be limited to one namespace, and resolved wait snapshots now compare absent optional values consistently with projected nulls so repeated repair is idempotent.
Replaced the prerelease JSON-in-Avro wrapper with the fixed recursive
durable_workflow.protocol.Value schema and standard Avro single-object
framing. Native adapters now preserve booleans, signed 64-bit integers,
finite doubles, bytes, UTF-8 text, lists, and string-keyed maps.
Added a backup-first prerelease-history migration that recursively rewrites inline and external wrapper copies in retained event snapshots. Replacement external objects receive verified hashes and sizes while original objects remain recoverable, and affected exported histories must replay before the migration reports success.
Removed the package-owned hosted control-plane and runtime-target contract. Embedded Laravel, independent self-hosted Server, and managed Cloud remain separate deployment choices; Cloud placement stays behind the namespace endpoint.
Platform conformance suite version 37 Rust signal/query scenarios install
the exact synchronized durable-workflow =2.0.0-rc.5 crates.io artifact,
with prior observed bindings preserved by source revision and digest.
Embedded and standalone activity heartbeats now use the same attempt-before-execution row-lock order as timeout enforcement. Accepted heartbeats renew the current attempt deadline, while stale scanner snapshots cannot time out live, replaced, or already-closed attempts.
Release recovery now accepts release-candidate plans only when they retain a
coherent immutable beta qualification. The versioned recovery-consumer
conformance contract and release-docs audit now cover the rc channel.
Release-plan recovery now consumes immutable, exact-version release-note preparation authority before publishing a newly recorded plan.
Explicit release recovery rejects terminally superseded plans before and after publication preflight while keeping completed-plan verification idempotent.
Standalone workers now receive accepted declared signals even when the host has no embedded workflow definition or local wait projection. Signal tasks retain command order ahead of queued updates, and QueueFake update completion uses the configured workflow-run model query. Accepted signal inputs are also persisted on their history event so public-history consumers observe the same values as workers and query replay.
Workflow-task claims and renewals now resolve
workflows.v2.workflow_task_lease_seconds at runtime across remote,
queued, timer, local-activity, and repair-driven execution paths. Embedded
Laravel hosts retain an explicit 300-second default and may set
DW_V2_WORKFLOW_TASK_LEASE_SECONDS before caching configuration.
durable-workflow/workflow 2.0.0-rc.55
durable-workflow/workflow 2.0.0-rc.55
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 720512eefa0a5a97afeb410797cff8803ec76864
durable-workflow/workflow 2.0.0-rc.54
durable-workflow/workflow 2.0.0-rc.54
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: fdb2e60f332216196c33a39ed6df447f694e4dba
durable-workflow/workflow 2.0.0-rc.53
durable-workflow/workflow 2.0.0-rc.53
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 62d6eabb10021e4ad72a3d813faa8e24b1c945af
durable-workflow/workflow 2.0.0-rc.52
durable-workflow/workflow 2.0.0-rc.52
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: b98bd5640c9476b8b6d966a4a4f12243c3e9af08
durable-workflow/workflow 2.0.0-rc.51
durable-workflow/workflow 2.0.0-rc.51
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 4f96b651dcacb6927e730828dfb7add17d13f6da
durable-workflow/workflow 2.0.0-rc.50
durable-workflow/workflow 2.0.0-rc.50
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 3001081b57227fa114609683d5cf1b8a06d53a49
durable-workflow/workflow 2.0.0-rc.49
durable-workflow/workflow 2.0.0-rc.49
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: cd76a2f38273ccc37eb92883e67bf0e41cfb71b2
durable-workflow/workflow 2.0.0-rc.48
durable-workflow/workflow 2.0.0-rc.48
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 278fa0fddcf05bf96aedec9d2466867fb0eb7702
durable-workflow/workflow 2.0.0-rc.47
durable-workflow/workflow 2.0.0-rc.47
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: a0dd581eb3ef2695e8054d32ea40fb4db702d04c
durable-workflow/workflow 2.0.0-rc.46
durable-workflow/workflow 2.0.0-rc.46
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 37f9926e4f8d38f5417f2a54e3e7f318b8739888
durable-workflow/workflow 2.0.0-rc.45
durable-workflow/workflow 2.0.0-rc.45
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 5d8033aa0b82ab2ba3adf55d9bdd76f39e74260f
durable-workflow/workflow 2.0.0-rc.44
durable-workflow/workflow 2.0.0-rc.44
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 64a4dfdbbd090667082d4b8a03529ce99ba0b607
Nothing published for this version
durable-workflow/workflow 2.0.0-rc.42
durable-workflow/workflow 2.0.0-rc.42
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: b5af16ec0e6f803669980dab492cb63a508776ae
durable-workflow/workflow 2.0.0-rc.41
durable-workflow/workflow 2.0.0-rc.41
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: e703ef6a52b89d4f89b64683c5d23894ddb2ed73
durable-workflow/workflow 2.0.0-rc.40
durable-workflow/workflow 2.0.0-rc.40
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 20ded5c183b1574e5882ed1ce3ed658d9184ee93
durable-workflow/workflow 2.0.0-rc.39
durable-workflow/workflow 2.0.0-rc.39
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 7e0ebec11dd9faf0e91abd5a28b549bf91dfbf84
durable-workflow/workflow 2.0.0-rc.38
durable-workflow/workflow 2.0.0-rc.38
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: d9c55fe8869d5167c2e9579cda844449c11eca9a
durable-workflow/workflow 2.0.0-rc.37
durable-workflow/workflow 2.0.0-rc.37
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 8dc90d649ec00f92291fa6377c45fac60ebe5de0
durable-workflow/workflow 2.0.0-rc.36
durable-workflow/workflow 2.0.0-rc.36
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 2c20fb7698142080f675bc72b2f2d59fbac0cd3e
durable-workflow/workflow 2.0.0-rc.34
durable-workflow/workflow 2.0.0-rc.34
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: c235ef9e05994313fdc22bc8f0d409c670c39075
durable-workflow/workflow 2.0.0-rc.33
durable-workflow/workflow 2.0.0-rc.33
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 94f71a72e3f835365cc1a8cd3513ae6026a41020
durable-workflow/workflow 2.0.0-rc.32
durable-workflow/workflow 2.0.0-rc.32
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 350eed12454544b10fdb0ae6a189d47fe3840724
durable-workflow/workflow 2.0.0-rc.31
durable-workflow/workflow 2.0.0-rc.31
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: a4ce321a31ba5f4d9c25964cde81109bf253c5aa
durable-workflow/workflow 2.0.0-rc.30
durable-workflow/workflow 2.0.0-rc.30
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 2575be7fea28fd0f0d824dbc976775829b598373
durable-workflow/workflow 2.0.0-rc.14
durable-workflow/workflow 2.0.0-rc.14
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 018d1a99f5a39452b02c68d5737f81c31f19f67f
durable-workflow/workflow 2.0.0-rc.13
durable-workflow/workflow 2.0.0-rc.13
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: fc28432a82a2433959c6690505c52eabea4aca8c
durable-workflow/workflow 2.0.0-rc.12
durable-workflow/workflow 2.0.0-rc.12
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 9416c2a4d3fe71d85f77c2465ed8337c833a79ee
durable-workflow/workflow 2.0.0-rc.11
durable-workflow/workflow 2.0.0-rc.11
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 021fe5406ecc69bff51f61e4e052296c7e613e57
durable-workflow/workflow 2.0.0-rc.10
durable-workflow/workflow 2.0.0-rc.10
Prerelease artifact for Durable Workflow 2.0 validation. Source commit: 7c5878ad0b0f689bb1eba518548d0dd086e069d0
One column per quarter.